Salesforce Workflow Rules & Process Builder Will No Longer Be Supported by End of 2025
You may have heard that Salesforce will no longer support Workflow Rules and Process Builder on December 31, 2025. Although Workflow Rules and Process Builders might still work after the cutover date, they will no longer receive customer support or bug fixes.
Salesforce recommends that you migrate your automation to Flow Builder, a modern, extensible, low-code automation solution by the end of 2025.
Replacing Workflow Rules and Process Builders shouldn’t be seen just as a technical task. In recent years, we have seen an increase in deadwood in Salesforce implementations that over time, can slow down business processes. The Workflow Rules and Process Builders replacement should be seen as an opportunity to discuss what those automations are doing and identify opportunities to simplify or even move to out-of-the-box functionality when possible.
Considerations for a migration:
- Workflow Rules and Process Builders should be analyzed holistically and in the frame of the business process that they are trying to solve for: It is not a straight 1:1 replacement with a Flow.
- We recommend grouping existing Workflow Rules and Process Builders by Object, then analyzing and categorizing the actions and context of each node in Process Builders.
- Before jumping into Flows, evaluate if the Workflow Rules and Process Builders were replaced with out-of-the-box functionality.
- Replace scheduled actions in Process Builders with a scheduled path in Flow. This is a good opportunity to re-evaluate the frequency and filter of the processing records to optimize performance.
- Although Flow is a declarative tool, we strongly recommend adopting a Flow framework, the same as you would (or should!) do with your code development standards, and following best practices to avoid hitting governor limits. Flows can get out of control very quickly in organizations that don’t have clear guidelines, especially in large IT groups.
This is a great opportunity to remove technical debt.
In a recent project, we were able to move from almost 100 Process Builders to less than 20 Flows, eliminating unnecessary processes. Also, by using the CLD Flow guidelines, System Admins find it easy to understand what each Flow is doing by simply looking at the element names, facilitating troubleshooting and enhancements.
Although moving out of Workflow Rules and Process Builders before the end of the year might sound intimidating, we can help! Hit us up if you’d like to learn more!
