Salesforce's Migrate to Flow tool handles most of the mechanics. The remaining work is reviewing the converted flows for clarity, naming, and error handling.
- Inventory existing Automated Actions
List every Workflow Rule, Process Builder, and Approval Process Action. Group by automation tool and impact.
- Run Migrate to Flow per Workflow Rule
Setup, search for Migrate to Flow. Pick a Workflow Rule or Process Builder. The tool generates an equivalent Record-Triggered Flow.
- Review the converted Flow
Check element naming, decision logic, and fault paths. Rename auto-generated elements for clarity. Add error logging.
- Test in sandbox
Use Flow Debug with sample data, then run integration tests in the sandbox. Confirm parity with the legacy behaviour before activating.
- Deactivate the legacy automation
Once the new Flow is active and validated, deactivate the original Workflow Rule or Process Builder. Keep them inactive (not deleted) for one release in case rollback is needed.
- Field Updates with Re-evaluate Workflow Rules turned on can produce loops. Flow conversion preserves the setting; audit before activation.
- Outbound Messages do not have a direct Flow equivalent. Replace with Flow plus HTTP Callout or a Platform Event publish.
- Approval Process Automated Actions are still supported. They have not been migrated to Flow-only yet, so existing Approval Process automation continues to work.
- Email Alerts assigned to user lookup fields require those lookups to be populated. Empty fields silently send no email.