My Workflow Rules And Process Builder Still Work. Is This Actually Urgent?
Yes, on a quarter horizon rather than a weekend one. Salesforce ended support for Workflow Rules and Process Builder on 31 December 2025. Existing automations still run and no retirement date has been announced, but you cannot create new ones and bugs found now will not be fixed. Nothing switches off, but the risk grows every quarter you wait.
How urgent is it for my org?
The first thing to break is usually the org around the automations. A record updates twice or a field gets overwritten, and the cause is a Workflow Rule and a Flow firing on the same object with no agreed order. Then staffing: admins hired since 2025 have never built a Process Builder process, so only your longest-serving people can maintain them.
| Your situation | Real risk | When to act |
|---|---|---|
| A few simple rules, no Flows yet | Low | Next quarter |
| Workflow Rules and Flows on the same objects | High | Now, ordering bugs are possible |
| Process Builder driving revenue or billing | High | Now, an unfixable bug is expensive |
| Nobody left who built the originals | High | Now, while intent can be explained |
Will the Migrate to Flow tool do it for me?
Partly. It handles simple cases, but its documented considerations rule out a lot of real orgs.
- It converts record-triggered processes only, not custom event or invocable ones.
- Cross-object references in formulas cannot be migrated.
- Time-based processes split into several scheduled flows, so the shape of the automation changes.
What do I do about it this week?
- Export every active Workflow Rule and process, grouped by object.
- Mark each as needed, obsolete or unknown, and deactivate the obsolete ones instead of migrating them.
- Find objects where a Workflow Rule and a Flow both fire. Those go first.
- Run the Migrate to Flow tool on the simplest survivors. What it refuses is your real scope.
What should I avoid?
- Do not migrate everything at once, or you will never know which of forty changes caused the regression.
- Do not migrate automation nobody can explain. A faithful conversion preserves a bug you could have deleted.
- Do not read the missing retirement date as reassurance.
Related questions
Can I still edit my existing Workflow Rules?
Yes. Editing, activating and deactivating still work. Only creating new ones is blocked.
Does any of this affect Flows I already built?
No. Flows remain the supported path. Just watch execution order where old and new automation overlap.
Keep reading
- Process Builder is unsupported: what to migrate to Flow first covers the ordering of an actual migration in more depth.
- The automation audit is the exercise behind steps one and two above.
- AI lead qualification in Salesforce shows what this work looks like once the legacy layer is gone.
- Why did my n8n workflow stop without an error? is the same question asked of a different platform.
We do this kind of migration as CRM and revenue operations automation work, usually starting with the list of automations nobody has opened in three years.