To migrate Process Builder to Flow, run Salesforce's Migrate to Flow tool in a sandbox, test the new flow, deploy it, then activate it and deactivate the old process. Support for Process Builder and Workflow Rules ended on December 31, 2025, yet active ones still run (Salesforce Help).
The Migrate to Flow tool is a page in Salesforce Setup. It converts a Process Builder process or a workflow rule into a record-triggered flow that you open in Flow Builder. A record-triggered flow is a flow that runs when a record is created, updated or deleted.
Clientell AI, the AI Salesforce admin, connects to your org, lists every Process Builder process and Workflow Rule it finds, and drafts each flow for you to review. See how in the AI Salesforce flow builder.
What are the steps to migrate Process Builder to Flow?
Eight steps cover the whole move:
- Find every active process and workflow rule.
- Rank them by risk, and drop the ones nobody needs.
- Convert each one with the Migrate to Flow tool, in a sandbox.
- Finish what the tool could not convert, by hand.
- Test the flow against the old behaviour.
- Deploy the flow to production. It arrives inactive.
- Switch over in one sitting.
- Keep a way back until the flow has run clean.
What changed for Process Builder and Workflow Rules?
As of October 2026, nothing has been switched off. Salesforce says your active Workflow Rules and processes "continue to run as they did before". What ended on December 31, 2025, is customer support and bug fixes (Salesforce Help, published 29-09-2026). You can still edit, activate and deactivate them (Salesforce Help).
The risk is slow, not sudden. Each Salesforce release (Spring, Summer and Winter) changes the platform around an old process, and no one at Salesforce fixes it when it breaks. Salesforce warns the move "may take a significant amount of time and testing, so we suggest starting now".
How do I find every process and workflow rule in my org?
Salesforce gives two Setup paths (Salesforce Help):
- Workflow Rules: open Setup > Process Automation > Workflow Rules. Sort the Active column.
- Process Builder: open Setup > Process Automation > Process Builder. Sort the Status column for Active.
For each active item, write down six things: the object, the trigger (created, or created and edited), the criteria, the actions, any scheduled or time-based action, and the owner. Mark anything that calls Apex, another flow or an outside system.
A long list is faster to pull with a query. In the API, a Process Builder process is a FlowDefinitionView row where FlowDefinitionView.ProcessType is Workflow. Our Migrate to Flow tool guide has the exact queries for processes and workflow rules.
The hard part is what each one does, not the list. One consultant inherited a large Case flow nobody had documented:
"I asked Clientell AI to decipher the flow into a manageable text block so I could then understand what it did and where to look for issues." Robert Smith, independent Salesforce consultant
His flow investigation went from 4 to 6 hours of reading to about 20 minutes, and a wait of 2 to 5 days for a developer went away (customer story).
Which processes should I migrate first?
Rank by risk, not by age. Start where a mistake is cheap, so you learn the tool on safe ground. Salesforce's own advice is to begin with the object that has the fewest rules and processes (Salesforce Help, Planning Your Switch to Flow Builder).
| Order | What it is | Why this order |
|---|---|---|
| 0 | Inactive or unused automation | Do not migrate it. Confirm nobody needs it, then retire it. |
| 1 | Workflow Rules with field updates only | The tool turns them into Fast Field Updates (before-save) flows. |
| 2 | Processes that send email alerts or update the same record | Salesforce calls these "good beginner options". |
| 3 | Processes with Chatter posts, quick actions or approvals | These actions migrate but need extra setup in Flow Builder. |
| 4 | Processes and rules with scheduled or time-based actions | Pending actions must hand over cleanly to the new flow. |
| 5 | Anything that calls Apex, invokes another flow or makes a callout | Most links to other automation. Test these last and hardest. |
Look for overlap while you rank. Salesforce names three common culprits: several processes and rules on one object, processes that re-trigger each other, and a flow and a rule that update the same field.
How do I run the Migrate to Flow tool?
Salesforce made the tool generally available for workflow rules in Summer '22 (Salesforce Admins). It added record-triggered processes in Spring '23 (Salesforce Admins) and partial migration of most process actions in Spring '24 (Salesforce Admins). Rehearse in a sandbox first (Salesforce Help, Migrate to Flow).
Check your permissions first. Salesforce lists Manage Flow and View All Data to work with processes, plus Customize Application to activate or deactivate them.
- Open Setup > Migrate to Flow (type Migrate to Flow in the Quick Find box).
- Select the process or workflow rule.
- Click Migrate to Flow.
- For a process, select the criteria to migrate. You can move all criteria into one flow, or each criteria into its own flow.
- Click Migrate to Flow again.
- For a partial migration, click Needs Review to see the actions that still need setup.
- Click Test in Flow Builder to open the new flow.
Expected result: a new flow in Setup > Flows, created as inactive. Nothing changes for users until you activate it (Trailhead).
The tool treats the two old tools differently:
| Workflow rule | Process Builder process | |
|---|---|---|
| Flow it creates | Fast Field Updates (before-save) when the rule only updates fields | Actions and Related Records (after-save) |
| Switch Activations button | Yes. It deactivates the rule and activates the flow in one click. | No. You activate the flow and deactivate the process yourself. |
| Scheduled actions | Time-dependent actions become scheduled paths | Migrate only when you select the single criteria that owns them |
| What it cannot take | Rules with unsupported features may not appear in the list | Processes that are not record-triggered |
Sources: Salesforce Help, Migrate to Flow Tool Considerations and the Trailhead project Migrate Workflows to Flow Builder.
Here is a worked example from the Trailhead project. The process Opportunity above 5000 has a criteria called Opportunity Lost above 5000, and its only action sets Opportunity.NextStep. You migrate that one criteria. In the Start element you switch the flow to Fast Field Updates, because it only updates the triggering Opportunity. You save it as a new version and activate it. Then you deactivate the process in Setup > Process Automation > Process Builder (Trailhead).
Use the same rule for your own processes. A process that only updates the record that triggered it belongs in a Fast Field Updates flow. Salesforce says a before-save flow can update a record "10 times faster than a record-change process" (Salesforce Help).
What do I do with the parts the tool cannot convert?
Rebuild them in Flow Builder. Common cases are Workflow Rules with Tasks, record types or fields on related records, and processes that are not record-triggered. The full list, with the by-hand fix for each, is in our guide to what the Migrate to Flow tool skips.
Check your edition before you split one process into many flows. Essentials and Professional editions allow only 5 flows of each flow type. Enterprise, Unlimited, Performance and Developer editions allow 2,000 flows of each type to be active, and 4,000 flows in total (Salesforce Help, Flow Limits per Org). Salesforce granted some Essentials and Professional orgs a higher limit to help with this move (release note).
How do I test the new flow before it goes live?
Test in the sandbox, with the old process off, against notes you wrote before the move.
- Write down what the old process did for a record that meets each criteria, and for one that does not. For the Opportunity example, that is one Opportunity that meets the
Amount > 5000criteria and one that does not. - Make test records for every branch. Include one that fires each action: field update, email alert, record create.
- Save each record with the new flow active. Expected result: every field, email and record matches your notes.
- Load a small batch of records at once with Data Loader. A flow that passes one record can still hit limits in bulk.
- If a result differs, read the debug log and the flow's fault email, fix the flow, and run the records again.
- If the old process allowed recursion, test those records again. A migrated process evaluates the record only one time.
- Ask the process owner to confirm the result.
Set the run order before you test. A record-triggered flow takes a Trigger Order from 1 to 2,000, and flows with the same value run in alphabetical order of API name (Salesforce Help). Space the values out, for example 10, 20, 30. Our Flow Builder best practices cover fault paths and naming.
How do I deploy the flow and switch off the old process?
Deploy the tested flow, then switch over in one sitting.
- Deploy the flow with a change set or the Metadata API. An active flow arrives in production as inactive (Salesforce Help, Change Set Considerations for Flows).
- Open the flow's versions. Each deploy creates a new version in production, so pick the one you tested.
- Activate the flow.
- Deactivate the old process or workflow rule straight away.
- Edit one live record of each kind. Expected result: the same field values and emails as before.
Steps 3 and 4 belong together. If both run, the same field updates twice and emails go out twice.
One exception changes the plan. A process with scheduled actions still waiting should be migrated in production itself, after you rehearse it in a sandbox. Salesforce says to migrate in the same org as the original, so the new flow can take over the queued actions. A flow deployed from another org is treated as a new flow, and the waiting actions do not move to it (Salesforce Help, Migrate to Flow Tool Considerations).
Production orgs have a Setup > Process Automation Settings option to deploy processes and flows as active, if your release process needs it (Salesforce Help).
How do I roll back if the new flow misbehaves?
Plan the way back before you switch over.
- Deactivate the old process. Do not delete it.
- Note the old process version and the time you switched.
- If the flow misbehaves, deactivate the flow first, then reactivate the old process.
- Fix the flow in the sandbox and test again.
- Delete the old process only after the flow has run clean through a full business cycle, such as a month end or a quarter close.
Check the Process Builder version list after each deploy. One team reported that a CLI deploy can create a new inactive process version even when nothing changed (Salesforce Stack Exchange).
Can an AI admin do the migration safely?
Yes, if it follows the same rules you would: sandbox first, and no change in production without a person saying yes. Clientell AI works in a sandbox or in production, and it asks before it changes anything in production. See our security and privacy details.
Start with the free, read-only flow audit. It flags end-of-life workflow rules and competing automation on each object. For a printable version of this plan, get the Process Builder to Flow checklist or read the Process Builder to Flow guide.
Try it in Clientell AI: "Find every Process Builder process and Workflow Rule on the Opportunity object, rank them by risk, and draft the flow for the riskiest one without changing anything yet." Start the 14-day trial, no card.
Common questions about migrating Process Builder to Flow
Can I still create a new process or workflow rule?
No, not in a normal org. The Winter '23 release blocked new workflow rules (release note), and the Summer '23 release blocked new processes (release note). Build new automation in Flow Builder.
Will a migrated flow run in the same order as the old workflow rule?
Not always. Salesforce warns that record-triggered flows can behave differently from similar workflow rules, because they sit in a different place in the order of execution (Salesforce Help). Set a Trigger Order and test the records that other automation also touches.
Should I merge many processes into one flow per object?
You do not have to. Salesforce says several flows per object are manageable when you order them with Trigger Order and Flow Trigger Explorer (Salesforce Help).
Do email alerts and outbound messages carry over?
Yes. The tool supports workflow rules with email alerts and outbound messages, and it migrates process email alerts with no extra setup. In the flow they become Action elements (Salesforce Help).
Last updated: October 22, 2026




