Chances are you’ve heard about Salesforce retiring Workflow Rules and Process Builder “soon”. The FAQ from Salesforce provides a lot of context, including why Flow is better in almost every way. But the details are still a bit murky:
- “At the moment, we don’t have an official timeline for all phases of retirement.”
- “We’re looking at turning off Create New [Workflow Rule/Process Builder] near the end of 2022.”
- “Shutting off running automation (your rules ‘just stop working’) would be the final step in the EOL process.”
Salesforce released a Workflow Rule > Flow migration tool in Spring 2022. But so far there’s no help for migrating Process Builders. So here are three ways (from least to most painful) to simplify the inevitable migration.
Do future you a favor
There are a couple things we can do now to make the full migration from Salesforce Process Builders to Flows easier:
- Start building everything new on Flow. This is a simple discipline that can help you get started on the change curve.
- Anytime you need to edit an existing Process Builder, that’s the cue to rebuild it in Flow, and delete the old Process Builder once you’ve verified the functionality in Flow. This will help you hack away at the backlog.
Then audit the remaining Salesforce Process Builders
If you’re looking for even more granular advice (i.e. how to start this process in a sandbox and perform extensive testing of all automation), Salesforce recorded a good webinar on the topic:
Ready to unleash the full power of Salesforce, without hiring another full time employee?
Learn about our Salesforce admin support package.
