Salesforce just dropped two big updates. One’s overdue. The other’s a game-changer. Both will shift how you handle automation and data sync. Here’s what matters.
1. End of the road for Workflow Rules and Process Builder
Salesforce is officially pulling the pin on these legacy automation tools. Support ends 31 December 2025. After that, no bug fixes, no support. Your old automations might still run — but if they break, you’re out of luck.
The short version:
- No support post-2025 – Salesforce won’t touch these tools after the cut-off.
- Still functional (for now) – But relying on them is risky and short-sighted.
- Migration required – Flow Builder is the future. It’s the only tool getting updates and support.
Why Flow Builder matters:
- Handles complex logic (loops, subflows, conditions)
- Better performance and error handling
- Built for scale — and here to stay
What you need to do:
- Audit your active Workflow Rules and Process Builders
- Prioritise what to migrate based on business impact
- Use Salesforce’s migration tool for simple cases
- Rebuild manually where logic gets messy
- Test thoroughly, then deactivate the old automation
Need help with the planning or execution? We’ve done this before — we’ll get you there faster and cleaner.
2. Syncing Salesforce data just got (a lot) cheaper
From 15 April, Salesforce has slashed the cost of syncing structured data from its own tools — CRM, Marketing Cloud, Personalisation, and Commerce Cloud.
The new rate: 500 credits per 1 million rows, batch or streaming. That’s a 75% discount from the old rate.
Translation: Syncing first-party Salesforce data across your ecosystem is now far more affordable.
If you’ve been holding off on real-time integrations or cross-cloud reporting because of cost, this unlocks new options. The time is ripe to revisit that architecture.
Bottom line:
Legacy automation is on the way out. Internal data syncing just got cheaper. Both changes should nudge you toward a cleaner, more future-ready Salesforce setup.
Need help sorting the signal from the noise — or building a smarter plan?
Let’s talk.
