The Process Builder to Flow migration tool is a page in Salesforce Setup called Migrate to Flow. It skips processes that start from a platform event or another process, criteria on related-object fields, and workflow rules with Tasks, record types, relative dates or multiple currencies. It converts the other record-triggered processes and workflow rules into record-triggered flows. You rebuild the skipped ones by hand in Flow Builder.
The tool converts one process or workflow rule at a time, and you test the result in Flow Builder. As of October 2026, active processes and rules still run, but support and bug fixes ended on December 31, 2025 (Salesforce Help).
Clientell AI, the AI Salesforce admin, connects to your org (production or sandbox), lists the Process Builder processes and Workflow Rules it finds, and drafts the flow for each one. See the AI Salesforce flow builder.
Which route fits: the tool, a rebuild by hand, or an AI admin?
A typical org uses all three routes. The tool takes the workflow rules that only update fields. A rebuild by hand takes the rules with Tasks. An inventory comes before both.
| Migrate to Flow tool | Rebuild by hand in Flow Builder | Clientell AI | |
|---|---|---|---|
| What it does | Converts one process or rule into a flow | You build the record-triggered flow yourself | Reads your org, lists processes and rules, drafts each flow |
| Finds what still runs | No. You pick from its list | No. You catalog first | Yes |
| Tasks, record types, related-record fields | Skipped | Supported | Drafted for your review |
| Switching the old one off | Switch Activations for workflow rules only | You do it | Asks before it changes anything in production |
| Cost | Included in Salesforce | Admin time | Clientell MCP $249 a month, Clientell Platform $500 a month, 14-day trial with no card |
Use the tool for everything it supports. Rebuild by hand where it stops. Bring in an AI admin when you cannot yet say what runs or what each item does. For each item on your list, this order of questions picks the route:
- Is it active, and does anyone still need it? If not, retire it and skip the migration.
- Is it record-triggered? A process that starts from a platform event or another process goes to a rebuild by hand.
- Does it use a feature from the skip table below? Rebuild that part by hand, using the matching Flow element.
- Does a process have scheduled actions still waiting? Migrate the single criteria that owns them, in the same org as the process.
- Everything else goes through the tool. A workflow rule with only field updates comes out as a Fast Field Updates flow.
The tool has one edge no other route has. Migrated in the same org, the new flow checks for the old process's pending scheduled actions and takes them over (Salesforce Help, Migrate to Flow Tool Considerations). A flow built by hand, or deployed from another org, starts fresh.
Knowing what each old item does is the slow part of every route, because the person who built it has often left. One consultant who inherited a large Case automation put it plainly: "It was too large to read" (customer story). For the full order of work, from inventory to rollback, follow our guide to migrating Process Builder to Flow.
What is the difference between Workflow Rules, Process Builder and Flow?
All three react when a record changes. They differ in where they run in the order of execution, the fixed list of steps Salesforce follows on every save.
| Workflow Rules | Process Builder | Record-triggered Flow | |
|---|---|---|---|
| Support | Ended 31 Dec 2025 (Help) | Ended 31 Dec 2025 | Where Salesforce says to build |
| New ones in a normal org | Blocked since Winter '23 (release note) | Blocked since Summer '23 (release note) | Allowed |
| Where it runs on a save | After the Apex after triggers | Later, with no set order between processes | Before-save: before Apex before triggers. After-save: after processes |
| Control of run order | Fixed place | None between processes | Trigger Order from 1 to 2,000 (Help) |
The run-order rows follow the Apex guide's order of execution. Speed is the other gain. A before-save record-triggered flow "can update a Salesforce record 10 times faster than a record-change process" (Salesforce Help).
What does the Migrate to Flow tool convert?
Salesforce made the tool generally available for workflow rules in Summer '22 (Salesforce Admins). It added processes in Spring '23, custom metadata references in process formulas in Winter '24 (release note), and partial migration of most process actions in Spring '24 (Salesforce Admins).
As of October 2026, Salesforce documents this coverage (Salesforce Help, Migrate to Flow Tool Considerations):
- Processes, migrated with no extra setup: record update, record create, invoke flow, invoke Apex and email alert. The tool builds an Actions and Related Records (after-save) flow. A process criteria that only sets
Opportunity.NextStepis a typical clean case (Trailhead). - Processes, migrated but needing setup in Flow Builder: Post to Chatter, Quick Action, Submit for Approval, Send Custom Notification, Live Message Notification, Send Surveys and Quip actions. Click Needs Review after the run to see them.
- Workflow rules: field-based criteria, formula criteria, field updates, email alerts, outbound messages and time-dependent actions. A rule with only field updates becomes a Fast Field Updates (before-save) flow.
Two behaviours surprise people. An invoke flow action becomes a Subflow element, which runs in the same transaction as the parent. A process whose invoked flow makes callouts or pauses needs a redesign with an asynchronous path. Salesforce also warns that "record-triggered flows can behave differently from similar workflow rules", because they sit in a different place in the order of execution.
How do I run the tool and check the result?
The tool never edits or switches off the original until you tell it to. That makes a test run cheap (Salesforce Help, Migrate to Flow).
- Open Setup > Migrate to Flow in a sandbox and select the process or rule.
- Read the Migratable column. It says whether a process migrates fully or partially.
- Select the criteria and click Migrate to Flow.
- For a partial migration, click Needs Review. Expected result: a list of actions to finish in Flow Builder.
- Open the new flow from Setup > Flows. Expected result: a new flow, inactive, that you can open in Flow Builder.
- Debug it in Flow Builder against a test record, then compare the result with the old automation.
If the result is wrong, leave the flow inactive and fix it, or delete it and rebuild by hand. The old process or rule keeps running in the meantime. If you already used Switch Activations on a workflow rule, the undo is to deactivate the flow and reactivate the rule. The step-by-step migration guide covers deploying and switching over in production.
What can the Migrate to Flow tool not move?
Salesforce lists eight kinds of gap, each with a by-hand fix (Salesforce Help, Migrate to Flow Tool Considerations):
| Item | What the tool does | Your move |
|---|---|---|
| Processes that start from a platform event or another process | Not supported. The tool takes record-triggered processes only | Rebuild by hand |
Criteria on a field from a related object (field traversals), such as Opportunity.Account fields | Not supported | Rebuild by hand with a Get Records element |
| Cross-object reference in a formula | Cannot migrate | Rewrite the formula by hand |
| Custom metadata reference in a process formula | Migrates, but you cannot edit it with the resource picker | Check the formula after the run |
| Recursion | Not fully supported. The flow evaluates the record one time | Test the records that relied on re-evaluation |
| Scheduled actions in a process | Migrate only when you select the single criteria that owns them | Migrate that criteria on its own |
| Workflow rules with Tasks, record types, global variable fields, related-record fields, relative dates or multiple currencies | Cannot migrate | Rebuild by hand |
| Workflow rules with the operators does not contain, includes, excludes or within, or picklist comparisons | Cannot migrate | Rebuild with custom condition logic |
A workflow rule that uses one of these features may not show up in the tool's list at all (Trailhead). That is usually why a rule seems to be missing.
How do I rebuild what the tool skips?
Salesforce publishes the by-hand method for each gap (Salesforce Help, Migrate to Flow Tool Considerations; Equivalent Features in Flows and Workflow Rules):
| Old item | Build it in Flow with |
|---|---|
| Workflow Task | A Create Records element on Task. Assigned To maps to Task.OwnerId, Due Date to Task.ActivityDate, Comments to Task.Description |
| Unsupported entry criteria | A Decision element inside the flow. The flow then runs on every save, so watch performance |
| The does not contain operator | A Contains condition with the custom logic NOT 1 |
| Relative dates such as TODAY or NEXT WEEK | A Decision element |
| Email alert or outbound message | An Action element |
Time trigger, such as a reminder before a custom Renewal_Date__c date | A scheduled path, in a flow optimized for Actions and Related Records |
| Field update on the Owner field with a notification | Not supported in flows. Plan another way to notify the new owner |
Order the new flows as you build them. Space Trigger Order values, for example 10, 20, 30, so you can slot a flow in later (Salesforce Help). Our Flow Builder best practices cover fault paths and naming.
How do I find active Process Builders and Workflow Rules with a query?
Setup works for a short list: sort the Active column in Setup > Process Automation > Workflow Rules, and the Status column in Setup > Process Automation > Process Builder (Salesforce Help). For a long list, query.
Process Builder. The API stores a process as ProcessType = 'Workflow', "a process that is invoked when a record is created or edited" (FlowDefinitionView, Salesforce Developers). Run this SOQL:
SELECT ApiName, Label, ProcessType, ActiveVersionId, LastModifiedDate FROM FlowDefinitionView WHERE ProcessType = 'Workflow' AND IsActive = true
To count versions by status (Active, Obsolete, Draft), query the Tooling API:
sf data query -o <your-org> --use-tooling-api -q "SELECT ProcessType, Status, COUNT(Id) cnt FROM Flow GROUP BY ProcessType, Status"
On FlowDefinitionView, COUNT(Id) fails. Use COUNT() with a WHERE clause instead.
Workflow Rules. List every rule with the Tooling API:
sf data query -o <your-org> --use-tooling-api -q "SELECT Id, Name, TableEnumOrId FROM WorkflowRule"
The WorkflowRule.TableEnumOrId column gives the object, such as Opportunity or a custom object. WorkflowRule has no Active column. To see which rules are active, retrieve the Workflow metadata with sf project retrieve start -m Workflow. Each rule in the XML carries an <active> flag (Metadata API, Workflow). Pending time-based actions show in Setup > Time-Based Automations (Salesforce Help).
Everything else on the object. Open Flow Trigger Explorer from Setup > Flows. It shows the flows that run when a record of one object is created, updated or deleted, and lets you reorder them (Salesforce Help).
One special case: Salesforce migrates Process Builder processes used by Marketing Cloud Connect to record-triggered flows itself, when the related journeys are stopped or published (Salesforce Help).
Where can I get the Process Builder to Flow checklist?
Get the printable Process Builder to Flow checklist. It puts the find, rank and migrate steps on one page for your team, and asks for a work email. The Process Builder to Flow guide covers the same plan in more depth.
To see what still runs before you choose a route, run the free, read-only flow audit. Clientell AI can work in a sandbox, and it asks before it changes anything in production. See our security and privacy details.
Try it in Clientell AI: "Find every active Process Builder process and Workflow Rule on the Opportunity object, and draft the flow for the one with the most actions." Start the 14-day trial, no card.
Common questions about the Migrate to Flow tool
Why is my workflow rule missing from the Migrate to Flow list?
It probably uses a feature the tool cannot migrate, such as a Task, a record type, a related-record field or a relative date (Trailhead). Rebuild that rule by hand.
Can the tool migrate Process Builder scheduled actions?
Yes, if you select only the single criteria that owns the scheduled action. With several criteria selected, no scheduled actions migrate. They become scheduled paths named ScheduledPath__# in the flow (Salesforce Help).
Can the tool migrate a process that uses custom metadata?
A custom metadata reference in a process formula migrates since Winter '24, but you cannot edit it with the resource picker afterward (release note). Check the flow formula by hand after the run.
What happens to an invoke flow action?
The tool turns it into a Subflow element, which runs in the same transaction as the parent flow. If the invoked flow makes callouts or pauses, redesign it with an asynchronous path (Salesforce Help).
Last updated: October 22, 2026
