Deadline passed: December 31, 2025. Salesforce no longer supports Workflow Rules and Process Builder. Nothing switched off on that date. Your automations keep running, but if one breaks, Salesforce won’t fix the bug or help you through support. The longer the old automations run unsupported, the more of your sales process depends on logic nobody can get fixed.
This is a process migration, not a data migration. The records stay put. What moves is the logic that acts on them.
What exactly changed on December 31, 2025?
Salesforce’s help article, updated in 2026, puts it plainly:
- Status: Salesforce no longer supports Workflow Rules and Process Builder as of December 31, 2025.
- Your automations: active rules and processes “continue to run as they did before”.
- What’s gone: customer support and bug fixes for these two features.
- Creation: Trailhead says both tools are now disabled, so new automation is built in Flow.
- Recommendation: plan to migrate active rules and processes to Flow Builder, using the Migrate to Flow tool and Salesforce’s support resources. Salesforce warns it “may take a significant amount of time and testing”.
| Date | Event |
|---|---|
| March 2024 | End of support date announced (reported by Salesforce Ben) |
| Before end of support | Creation of new rules and processes disabled |
| December 31, 2025 | End of support: no bug fixes or customer support |
| Today | Existing automations still run, unsupported |
How do I find the automations I need to migrate?
Salesforce’s article gives the starting point:
- Workflow Rules: Setup > Process Automation > Workflow Rules, then sort by the Active column.
- Process Builder: Setup > Process Automation > Process Builder, then sort by Status.
For each active item, record the object, the trigger and criteria, every action (field update, email alert, task, outbound message, invoked flow or Apex), any scheduled or time-based actions, and who owns the business process it supports. Note where several rules and processes act on the same object, because they will need a defined order in Flow.
What can the Migrate to Flow tool convert?
From Trailhead’s project on migrating workflows and processes:
| Converts | Doesn’t convert | |
|---|---|---|
| Workflow rules | Rules that meet the tool’s criteria | Criteria with no defined actions, global variable fields, fields on related records, record types, Task actions, relative date values, multiple currencies, and some operators (such as Includes, Within) and functions (such as TIMENOW) |
| Process Builder | Record-change processes with most actions: record updates, record creates, invoke flow, invoke Apex, email alerts | Processes started by a platform event or another process, scheduled actions, field traversals; invocable actions can’t migrate |
Two warnings from the same module: processes with recursion evaluate the record only once after migration, so test them; and converted output is partial for most process actions.
How do I migrate Workflow Rules and Process Builder to Flow?
- Inventory every active rule and process, as above.
- Group by object. Plan one record-triggered flow per object and timing (before-save or after-save) where possible, instead of one flow per old rule.
- Classify each item: convert with the tool, redesign in Flow Builder, or retire because nobody needs it.
- Work in a sandbox. Trailhead’s advice: build and test there, never debug flows in production with live data.
- Use Fast Field Updates (before-save flows) for rules that only update the triggering record.
- Move callouts and long-running actions to an asynchronous path.
- Set the order of record-triggered flows on each object with Flow Trigger Explorer.
- Test with real scenarios: creates, updates, bulk loads through Data Loader, and edge cases such as recursion.
- Deploy object by object. Activate the flow, deactivate the old rule or process in the same release, and watch for duplicate actions.
- Document each flow’s purpose and owner, so the next admin isn’t starting from zero.
Which automations should I migrate first?
Not every rule carries the same risk. A practical order:
- Revenue and customer-facing automation: opportunity stage updates, quote or order logic, emails that customers receive.
- Automation on high-volume objects, such as leads, cases and tasks, where a failure affects thousands of records a day.
- Processes that call Apex or other flows, because a fault there is harder to trace.
- Rules with scheduled or time-based actions, which the tool doesn’t convert from processes.
- Simple internal field updates, which the tool usually handles and are low risk.
- Anything nobody can explain. Confirm with the business whether it is still needed before rebuilding it; retiring it is often the right answer.
What goes wrong in Flow migrations?
- Double execution. The new flow is activated, the old rule isn’t deactivated, and every record gets two emails.
- Order changes. Workflow rules, processes and flows ran in a fixed order; a flow can run earlier or later than the rule it replaced.
- Bulk behaviour. A flow that works for one record can hit limits when Data Loader updates 10,000.
- Lost time-based actions. Scheduled actions in processes don’t convert and need scheduled paths.
- Unowned logic. Nobody remembers why a rule exists, so it is copied blindly instead of retired.
How do I test a converted flow?
Test each flow with the cases the old rule handled: a new record, an update that meets the criteria, an update that doesn’t, a bulk update through Data Loader, and a record that triggers other automation. Compare the results field by field with the same test run against the old rule in a sandbox copy, before you deactivate it.
Should I fix automation before or after a CRM migration?
If you are moving data into Salesforce, build the destination’s automation in Flow from the start rather than recreating old Workflow Rules. If you are moving data out of Salesforce, inventory the Workflow Rules and processes anyway: they document how your sales process works, and the new CRM needs the same rules.
When to bring in FlitStack AI
FlitStack AI is a data-migration platform sold as software plus a done-for-you service, and it also sets up processes in the destination. For this change, the Salesforce implementation service inventories every Workflow Rule and process, uses Migrate to Flow where it fits, redesigns the rest in Flow Builder, and tests and deploys them object by object in a sandbox first. If the automation work is part of a wider move, the data side runs through the same team, with validation and one-click rollback.
See the Salesforce migration hub, or book a free scoping call with your automation count.