Ever since Salesforce announced that Process Builder and Workflow Rules are to be retired at Dreamforce 21’, there has been a lot of buzz around migration of flows. For most admins this generated some questions: What does it mean for my organisation? Is there going to be a tool for this?
First of all there are plenty of benefits for all of us.
With this direction, Salesforce allows you to keep everything in one place, so no more scattered automations.
Do you know this feeling when you have to update or troubleshoot an automation process but you’re not sure where to look for it? Is it a flow, a process builder or maybe a workflow rule? That’s in the past.
Well, except for the legacy ones ( but we’ll come to those). Flow is by far the strongest declarative automation tool we can use in Salesforce. Now, with flow, you can do everything you could do in a process builder or workflow rules and more. Here the highlights of the record-triggered flow’s capabilities:
- Apart from updating a record when it’s created or updated, flow can trigger automation after deletion of a record
- Flow can delete records
- You can add the scheduled path to record-triggered flow
- You can trigger subflows ( with a preview option, you can analyse the subflow from the same place)
- With Flow Trigger Explorer, you can define and order in which your record-triggered automations are orchestrated all is manageable in one place (coming in Spring ‘22 release)
- Trigger actions (email, chatter post, approval process, subflow)
- Create or update multiple records of a related object
- Before-save update is carried out 10 times faster compared to process builder
What will happen to my current processes?
Although Salesforce will not delete or disable the legacy automations, it will disable a possibility to create new automations with Workflow Rules and Process Builder by the end of the year. This will most likely happen in Winter ‘23 release. So your processes will still be active, however it is encouraged to plan your migration beforehand in order to make sure your org is up to date with all features.
What do I need to consider when migrating the legacy automations to flow?
Most importantly, always carefully analyse your processes. Try not to look at them as just automations you need to migrate but processes you may want/need to optimise. There are a number of things to consider:
- Have a deep dive into why they were created in the first place.
Are they still valid? Can they be simplified?
- Which type of record-triggered flow optimisation to use?
- Before-save flow: The general rule is that you should use the before-save to update fields on newly created or changed records
- After-save flow: use it to trigger an action such as subflow or send email
- Try to keep a limited number of flows per object. Of course, this is the best practice advice and every case needs to be considered individually. However, it is best to try to keep your flows to the minimum. Can you migrate a couple of processes to one flow instead of creating a new flow for each process?
- Test, test, test to make sure that your new flow works as intended before you deactivate the legacy automations
Are there any Salesforce migration tools I could use?
In order to make the transition easier, Salesforce will be providing a Migrate to Flow tool to assist you with migration . For now, only supports transition from workflow rules only:
- Workflow Rules migration tool: currently in Beta, although not yet fully supporting all cases
- Process Builder migration tool: not yet available. Salesforce is planning on releasing the first version of it by the end of this year – estimated for Winter ’23
Apart from that, you will be able to find some additional migration tools on app exchange.
How can Mooza help you with Migration to Flows?
Our experienced team can help you with analysis, expertise and migrate your processes to flows. We can also provide you with training and share best practices.
Let’s arrange a free call and see how the knowledge and skills of the Mooza development team will meet your business goals.