Skip to content
Get a quote

Workflow Rules and Process Builder are out of support

Deadline: December 31, 2025

Short answer

Salesforce ended support for Workflow Rules and Process Builder on December 31, 2025. Existing automations still run, but Salesforce no longer provides support or bug fixes, and new ones can't be created. Use the Migrate to Flow tool for simple rules and redesign the rest in Flow Builder. FlitStack AI's Salesforce implementation service inventories and rebuilds them.

By

What we handle5
  • Find every active rule and process
  • Convert simple workflow rules
  • Rules the tool can't convert
  • Processes the tool can't fully convert
  • Order of execution

What the native tool does, and where it stops

TaskNative toolWith FlitStack AI
Find every active rule and processSetup > Process Automation > Workflow Rules (sort by Active) and Process Builder (sort by Status).A written inventory of every active automation, what it does and what depends on it.
Convert simple workflow rulesMigrate to Flow converts rules that meet its criteria, including field updates, email alerts and scheduled actions.Uses the tool where it fits, then tests each converted flow against real records in a sandbox.
Rules the tool can't convertUnsupported: record types in criteria, related-record fields, global variables, Task actions, relative dates, multi-currency, some operators and functions.Redesigns them directly in Flow Builder.
Processes the tool can't fully convertNo platform-event or process-started processes, scheduled actions or field traversals; invocable actions can't migrate.Rebuilds them as record-triggered or scheduled flows, with async paths for callouts.
Order of executionFlow Trigger Explorer sets the order of record-triggered flows.Consolidates per-object automation into fewer flows with a defined order.
Deploy safelyBuild and test in a sandbox; activate in production, then deactivate the old rule.Staged deployment with side-by-side testing and a rollback plan for each object.

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”.
DateEvent
March 2024End of support date announced (reported by Salesforce Ben)
Before end of supportCreation of new rules and processes disabled
December 31, 2025End of support: no bug fixes or customer support
TodayExisting automations still run, unsupported

How do I find the automations I need to migrate?

Salesforce’s article gives the starting point:

  1. Workflow Rules: Setup > Process Automation > Workflow Rules, then sort by the Active column.
  2. 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:

ConvertsDoesn’t convert
Workflow rulesRules that meet the tool’s criteriaCriteria 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 BuilderRecord-change processes with most actions: record updates, record creates, invoke flow, invoke Apex, email alertsProcesses 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?

  1. Inventory every active rule and process, as above.
  2. 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.
  3. Classify each item: convert with the tool, redesign in Flow Builder, or retire because nobody needs it.
  4. Work in a sandbox. Trailhead’s advice: build and test there, never debug flows in production with live data.
  5. Use Fast Field Updates (before-save flows) for rules that only update the triggering record.
  6. Move callouts and long-running actions to an asynchronous path.
  7. Set the order of record-triggered flows on each object with Flow Trigger Explorer.
  8. Test with real scenarios: creates, updates, bulk loads through Data Loader, and edge cases such as recursion.
  9. Deploy object by object. Activate the flow, deactivate the old rule or process in the same release, and watch for duplicate actions.
  10. 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:

  1. Revenue and customer-facing automation: opportunity stage updates, quote or order logic, emails that customers receive.
  2. Automation on high-volume objects, such as leads, cases and tasks, where a failure affects thousands of records a day.
  3. Processes that call Apex or other flows, because a fault there is harder to trace.
  4. Rules with scheduled or time-based actions, which the tool doesn’t convert from processes.
  5. Simple internal field updates, which the tool usually handles and are low risk.
  6. 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.

Questions, answered

A few useful answers.

Do Workflow Rules and Process Builder still work after December 31, 2025?

Yes. Salesforce says active Workflow Rules and Process Builder processes continue to run as before. The change is that Salesforce no longer provides customer support or bug fixes for them.

Can I still create new Workflow Rules or processes?

No. Trailhead describes both tools as now disabled. New automation has to be built in Flow Builder.

What does the Migrate to Flow tool convert?

Workflow rules that meet its criteria, and record-change processes with most actions (record updates, record creates, invoking flows or Apex, email alerts). It can't convert rules that use record types, related-record fields, global variables or Task actions, or processes started by platform events or other processes, scheduled actions or field traversals.

Is this a data migration?

No, it is a process migration. Your records stay where they are. What changes is the automation that acts on them, so the work is inventory, redesign, testing and deployment rather than moving data.

Get a quote

Rather have it done for you?

FlitStack AI maps, validates and migrates your data, sets up the process in the new system, and keeps a one-click rollback.

Get a quote