Migrating workflows to flows following retiring announcements some time ago is relatively simple and pain-free. However, I personally find it worth reevaluating everything that is going on in the org automation-wise before migrating. I try and tidy everything up before cracking on with migrating workflows. You may have a fairly clean org for either restarting with a new org, recently have it, or have done routine upkeep on processes using the migration tool may work for you.
Migrating Workflows To Flow
How to use Migration To Flows
- Go To Setup
- Go to process automation
- Click on Migrate To Flow
This will now display a list of workflows to migrate. This will display a list view of all the workflows to be migrated.
Select the workflow you want to migrate and click the options at the end. You will be presented with a popup asking you to switch activation after you have tested it with a link to Test in Flow Builder what this will do is deactivate the workflow and activate the flow.
You can click the show details about the optimal performance; in this case, it will tell you that it is migrated to a before save flow and if you wanted to add actions like emails you would need to change it to an after-save flow. If you need to see differences between before and after save performance click here and read under the performance section. You can also see the source information used on the Salesforce website here. Once you have clicked switch activation it will show the below screen.
So this has now been done you will need to rinse and repeat as many times as you need to migrate. I would always check to see if you can combine workflows before doing this so you have a tighter operation.
Process Builders and Further Learning
At this moment in time there is no tool for process builders but from what I’ve come across this will be available later this year probably towards November or December with an aim to retire process builders by next spring release. I would take the time if you have the opportunity to stay ahead of the curve on this and evaluate what you have in terms of automation. There is currently a limit of 2000 flows. If you are well under this you can look at possibly replacing apex triggers to make it easier to maintain. I have covered before save and after save record triggered flows as apex replacements with real-world examples.
As soon as I have more information on migrating process builders to flows I share that information. Until then you may want to check out my other tutorials.
