Salesforce Workflow Rules to Flow: A Migration Checklist That Won't Break Your Automations
Salesforce has made it clear: Workflow Rules and Process Builder are on the way out, and Flow is the future. If your org still runs on old workflow rules, migration is not optional — but a rushed migration is how working automations quietly break. Here is a checklist that keeps the move safe.
1. Inventory everything before you touch anything
Start with a full list of every Workflow Rule and Process Builder process in the org: what object it fires on, its criteria, and every action it takes. Use the Flow Migration Tool in Setup to see what Salesforce can convert automatically — but treat its output as a starting point, not a finished job. Many rules convert cleanly; the ones with time-based actions and complex criteria need a human eye.
2. Map each rule to the right Flow type
Not every Workflow Rule becomes the same kind of Flow. A rule that updates a field on the same record becomes a record-triggered, before-save Flow — the fastest option, and usually a straight replacement. A rule that creates a task or sends an email becomes a record-triggered, after-save Flow. A rule that fires on a schedule becomes a scheduled Flow. Getting the type wrong is the most common migration mistake, and it is also the easiest to avoid if you decide it before you build.
3. Rebuild the logic, don't just copy it
Workflow Rules let you get away with sloppy logic — a criteria formula that nobody understands, an update that fires on every edit. Flow gives you Decision elements, fault paths, and proper debugging, so use them. When you rebuild a rule, ask whether the criteria still make sense: many old rules encode business logic that changed years ago. Migration is the one moment you get to clean house, so take it.
4. Test in a sandbox with real data
Never migrate directly in production. Build the Flow in a sandbox, then test it against real scenarios: create the record, edit the record, and check that the field updates, the task is created, and the email is sent. Pay special attention to order of execution — a Flow that runs before a validation rule can behave differently from a Workflow Rule that ran after it. Our guide to how to set the run context of a Salesforce Flow explains the user-versus-system context question that decides whether your Flow can even see the data it needs.
5. Switch over one rule at a time
Deactivate the old Workflow Rule only after the new Flow is live and verified. Run them in parallel for a week if you can — the Flow does the work, and the old rule stays as a safety net you can reactivate. If anything looks wrong, you roll back in seconds instead of rebuilding under pressure. And when the Flow sends alerts, make sure they reach the right people — our walkthrough on custom notifications with Flow shows how to route them properly.
6. Document what you migrated — and what you deleted
Every migration leaves behind rules that are obsolete, duplicated, or already covered by another automation. Delete them, and write down what you removed and why. Six months from now, when someone asks why a rule is gone, that note is the difference between a five-minute answer and a half-day investigation.
Migration is not a weekend project, but it is not a scary one either. Inventory, map, rebuild, test, switch over one at a time — and your org comes out faster, cleaner, and ready for whatever Salesforce builds next.
Originally published at Way2Force — practical guides on Salesforce Flow, automation, and CRM.
Top comments (0)