Definition
Migrate to Flow is a Setup tool that helps administrators convert legacy Process Builder processes and Workflow Rules to Flows. Salesforce is retiring Process Builder and Workflow Rules in favor of Flow as the unified automation tool, and this migration assistant automates much of the conversion process.
Real-World Example
The admin at Velocity Partners uses Migrate to Flow to convert 15 legacy Workflow Rules on the Case object into Record-Triggered Flows. The tool analyzes each workflow rule's criteria and actions, generates equivalent Flow logic, and creates the new Flows in inactive status for the admin to review and test before activating.
Why Migrate to Flow Matters
Migrate to Flow is a built-in Setup tool in Salesforce that assists administrators in converting legacy Process Builder processes and Workflow Rules into Flows. Salesforce has announced the retirement of Process Builder and Workflow Rules in favor of Flow as the single, unified automation engine. The Migrate to Flow tool analyzes the existing automation's criteria, conditions, and actions, then generates equivalent Flow logic — typically as Record-Triggered Flows. The generated Flows are created in an inactive state, giving admins the opportunity to review, test, and validate the converted logic before activating it and deactivating the legacy automation.
As the retirement timeline approaches, organizations with dozens or hundreds of legacy automations face a significant migration effort. The Migrate to Flow tool handles straightforward conversions well — simple field updates, email alerts, and task creation — but complex processes with multiple criteria nodes, invocable processes, or cross-object updates may require manual adjustment after migration. Organizations that delay migration risk running unsupported automation that does not receive bug fixes or new features. The recommended approach is to inventory all legacy automations, prioritize them by business criticality, use the tool for bulk conversion of simple automations, and manually rebuild the complex ones with Flow's more powerful capabilities like orchestration and screen flows.
How Organizations Use Migrate to Flow
- Velocity Partners — Velocity Partners used Migrate to Flow to convert 15 legacy Workflow Rules on the Case object into Record-Triggered Flows. The tool successfully converted 12 rules automatically, and the remaining 3 required manual adjustment due to time-dependent actions that needed to be rebuilt as Scheduled Paths in Flow. The entire migration was completed in 2 weeks instead of the estimated 6 weeks for manual rebuilding.
- NorthStar Retail — NorthStar Retail had 42 Process Builder processes across their Sales and Service clouds. They ran Migrate to Flow on all 42 and found that 30 converted cleanly. The remaining 12 had cross-object updates and invocable process calls that needed to be refactored into subflows. By combining automated migration with manual refactoring, they completed their full migration in one quarter.
- Clearwater Insurance — Clearwater Insurance used the migration as an opportunity to consolidate automation. They had 8 separate Workflow Rules on the Policy object that each handled one field update. After running Migrate to Flow, they combined all 8 into a single Record-Triggered Flow with multiple decision elements, reducing the total number of automations on the object from 8 to 1 and making the logic easier to maintain.