Use the Migrate to Flow tool in Setup to convert a Workflow Rule into a record-triggered flow, test it, and switch the live automation over. The steps below follow the assisted Workflow Rule path; Process Builder works similarly but adds a step to choose which criteria to migrate.
- Open the tool
From Setup, type "Migrate to Flow" in Quick Find and select it, or open the Workflow Rules page and click "Migrate your workflow rules to flows." The tool lists your existing rules and processes on separate tabs.
- Select and convert one item
On the Workflow Rules tab, pick a single rule and click Migrate to Flow. The tool generates an equivalent record-triggered flow and opens a Migration details window. Convert one rule at a time so each conversion is easy to review.
- Test in Flow Builder
Click Test in Flow Builder to open the generated flow. Read the entry condition and elements, then run it against sample records in a sandbox to confirm it reproduces the rule's behavior before you change anything live.
- Switch activations
When the flow checks out, click Switch Activations. This deactivates the original Workflow Rule and activates the new flow in one action, so both automations never run at the same time.
Lists the org's Workflow Rules. Select one rule per migration and use Migrate to Flow to generate its record-triggered flow.
Lists Process Builder processes. After selecting a process you choose which criteria nodes to migrate, into one flow or several.
Opens the generated flow so you can inspect the logic and run it against records before activating it.
Performs the cutover for a Workflow Rule by deactivating the rule and activating the flow together.
- Migrate and test in a sandbox before doing the cutover in production; a converted flow is structurally similar but not identical to its source.
- Never leave the old rule and the new flow active at once. Both fire on the same record change and cause doubled emails or field updates.
- Cross-object Field Updates and complex nested formulas may not convert cleanly and need manual rework with extra Flow elements.
- Some older or unusual action types are not supported. Review every generated flow rather than trusting the output blindly.
- Keep a written map of which rule or process became which flow so future maintenance knows where each piece of logic moved.