Use this link to share with your colleagues:
All About Migrating Current Automation to Flow: https://help.pm.leapevent.tech/a/1915345
Flow is Salesforce's tool for automation.
Previously, Salesforce recommended their Workflow and Process Builder tools to create automation, but Salesforce is phasing out workflows and processes. While existing automation may continue to work with these tools, if something goes wrong with a workflow or process you will need to migrate the automation to Flow and make any fixes there.
In this article, we'll cover:
- The retirement of Workflow and Process Builder and what it means for you
- The overall process to migrate workflows and processes to Flow
- Best practice recommendations for migrating automation to Flow
To help set you up for success, we’ve put guidelines together to help you avoid interfering with PatronManager functionality, corrupting your data, and to prevent negative impacts to your customizations due to PatronManager product upgrades.
Workflow, Process Builder, and Flow fall under Salesforce Administration and is therefore outside the scope of PatronManager support services. If you have questions or need assistance, reach out in the Client Community or reference Salesforce's resources.
Retiring Workflow and Process Builder
Salesforce's retirement of Workflow and Process Builder means that, as of December 31, 2025, workflows and processes will no longer receive Salesforce support.
This means that, while workflows and processes may continue to work after December 31, 2025, if automation breaks, it will not be able to be fixed.
In other words, if you need to change a workflow or process, or if one stops working, you will need to recreate it in Flow to update it.
You can read more about Salesforce's retirement of Workflow and Process Builder here.
The Process to Migrate Workflows and Processes to Flow
Before you begin, we recommend making sure you have a basic understanding of Workflow and Process Builder to migrate automation. If you need a refresher, check out our articles on these topics here.
1. Check existing automation
In order to migrate workflows or processes to Flow, the first step will be to see what automation you already have built.
We recommend checking out all of your existing active workflows and processes to see what's in place and what the automation currently does.
If a workflow or process isn't active, then you can ignore it and it doesn't need to be migrated.
If you see packaged PatronManager workflows named "Delete Draft Orders" and "New Contact via Patron Signup," you can go ahead and deactivate them! These workflows are now obsolete, and do not need to be migrated to Flow.
2. Evaluate whether existing automation is still necessary
This is a great chance to do some cleanup in your account! After checking what workflows and processes already exist in Workflow and Process Builder, talk with your team about whether the automation is still necessary.
For example, perhaps you previously had a workflow in place that emailed your development director each time a donation is made, but your development director archives all of these emails anyway. Or perhaps you had a process in place that updated a custom field on your Contacts that you no longer use as an organization.
If an automation is no longer necessary, then there's no need to migrate it over to a Flow and you can simply deactivate it.
Not sure what an existing workflow or process does? You can try deactivating it to see if you notice any differences. This still gives you the flexibility to reactivate it if you do need this automation before migrating it to Flow!
3. Learn about Flow
If you haven't already, make sure to learn about Flow! This will help ensure that you have the base knowledge needed in order to complete the migration.
4. Select your migration path
There are two options to migrate your existing automation to Flow:
- You can migrate custom workflows and processes to Flow yourself
- You can hire a consultant to migrate automation to Flow
If you choose to migrate your custom workflows and processes to Flow yourself, we recommend checking out Salesforce's Migrate to Flow tool, which will help convert automation over to Flow.
5. Execute your plan!
Whichever option you choose, DIY or working with a consultant, the next step is to actually migrate workflows and processes over to Flow.
If you need assistance while migrating automation, make sure to reach out in the Client Community.
Some Best Practice Recommendations
Test changes in a sandbox
When migrating automation over to Flow, we recommend testing changes, including your new Flows, in a sandbox first before deploying your work in your production account.
A sandbox will allow you a safe place to test changes without affecting your real-life data.
Know your resources
As you migrate automation to Flow, knowing what resources are available to you is helpful.
We recommend consulting the articles in our Automating PatronManager chapter of the Help Tab for guidance and general knowledge of the different automation options.
You can also learn more about Workflow, Process Builder, and Flow from Salesforce's learning tool, Trailhead. Salesforce also has some great resources on migrating automation to Flow in Salesforce Help here.
Additionally, we have some upcoming and recorded webinars on automation in PatronManager. Make sure to check them out or register for upcoming webinars from the Webinars section of the Help Tab.