When did Salesforce end support for Process Builder and workflow rules?

December 31, 2025. Since then Salesforce no longer provides customer support or bug fixes for either.

Do Process Builder processes and workflow rules still run?

Yes. Existing processes and rules keep running, and you can still edit, activate and deactivate them. What ended is support: if one breaks, Salesforce won't fix the bug. New automation features only come to Flow.

Do I have to migrate everything to Flow?

Nothing forces you to on a date. But every release that passes makes unsupported automation a bigger risk, and it is one more thing layered on your objects when you add flows or agents. Most teams migrate object by object, starting with the objects that change most.

What is the Migrate to Flow tool?

A tool in Salesforce Setup that converts workflow rules and Process Builder processes into record-triggered flows. It handles straightforward automation well. Review and test what it produces before you activate it, and expect to rebuild anything it can't convert by hand.

How do I find out how many I have?

In Setup, open Process Builder and Workflow Rules and filter to active. The VanguardOps free scan also counts active Process Builder processes and active workflow rules, names them, and puts a dollar figure on leaving them in place.

How long does a migration take?

It depends on how many there are and how tangled they are. The VanguardOps cost model budgets 4 hours for a medium finding and 12 for a high one before scaling for the number of items: 12 active processes on one finding comes to about 17 hours of architect time. Treat that as a starting estimate, not a quote.

Guide

Process Builder migration to Flow: what to do now that support has ended

Salesforce ended support for Process Builder and workflow rules on December 31, 2025. They still run, but bugs in them won’t be fixed. The job now is to find what’s still active, move it to record-triggered flows one object at a time, and switch the old automation off.

By VanguardOps, written by a Salesforce architect with 13+ years in enterprise orgs. Updated November 11, 2026.

What actually ended on December 31, 2025?

Support, not the features. Here is what changed and what didn’t.

What end of support means for Process Builder and workflow rules
	Before	Now
Existing processes and rules run	Before: Yes	Now: Yes
You can edit, activate and deactivate them	Before: Yes	Now: Yes
Salesforce fixes bugs in them	Before: Yes	Now: No
Salesforce support will help with them	Before: Yes	Now: No
New features	Before: Flow only	Now: Flow only

Check Salesforce’s own help article on the retirement for the current wording before you quote it to anyone.

Why move if it still works?

A bug has no fix coming. If a release changes how an old process behaves, you are on your own.
It stacks. Every new flow you add to an object runs alongside the old workflow rules and processes on it. The order they fire in gets harder to predict with each one.
Agents make it matter more. An Agentforce agent that updates a record sets off all the automation on that object. You want that to be one thing you understand.
The people who built it are leaving. Fewer admins each year have ever worked in Process Builder.

A seven-step migration plan

Count what’s active. List every active Process Builder process and workflow rule. Inactive ones can simply be deleted later.
Group by object. Migrate an object at a time, not a rule at a time. That is how you avoid a half-old, half-new object.
Write down what each one does. One line each: when it fires and what it changes. This is also where you find the ones nobody needs any more.
Decide the target design. Field updates on the same record belong in a before-save flow, which is faster. Emails, tasks, updates to other records and callouts belong after save. Aim for a small number of flows per object with clear entry conditions.
Convert in a sandbox. Use Migrate to Flow for the simple ones and rebuild the rest by hand. Don’t activate the converted flow and leave the old rule on: both will fire.
Test with real scenarios. Create, update and bulk load records. Compare the results with the old behavior, including time-based actions.
Switch over, then watch. Deploy the flow, deactivate the old automation in the same release, and watch flow error emails for a couple of weeks before you delete the old version.

What VanguardOps tells you about it

The scan reads your org’s automation metadata and reports:

How many Process Builder processes are still active, by name.
How many workflow rules are still active, by name. A scan checks up to 100 rules; if your org has more, the report says so and gives the count as “at least”.
Where flows, triggers and workflow rules are stacked on the same object and the same event.
A dollar figure: fewer than 10 active is a medium finding, 10 or more is high. Both are priced as a retired feature, at $2,100 a year before scaling for how many there are. See the formula.

It does not migrate anything for you, and a scan changes nothing in your org.

Common questions

When did Salesforce end support for Process Builder and workflow rules?: December 31, 2025. Since then Salesforce no longer provides customer support or bug fixes for either.
Do Process Builder processes and workflow rules still run?: Yes. Existing processes and rules keep running, and you can still edit, activate and deactivate them. What ended is support: if one breaks, Salesforce won't fix the bug. New automation features only come to Flow.
Do I have to migrate everything to Flow?: Nothing forces you to on a date. But every release that passes makes unsupported automation a bigger risk, and it is one more thing layered on your objects when you add flows or agents. Most teams migrate object by object, starting with the objects that change most.
What is the Migrate to Flow tool?: A tool in Salesforce Setup that converts workflow rules and Process Builder processes into record-triggered flows. It handles straightforward automation well. Review and test what it produces before you activate it, and expect to rebuild anything it can't convert by hand.
How do I find out how many I have?: In Setup, open Process Builder and Workflow Rules and filter to active. The VanguardOps free scan also counts active Process Builder processes and active workflow rules, names them, and puts a dollar figure on leaving them in place.
How long does a migration take?: It depends on how many there are and how tangled they are. The VanguardOps cost model budgets 4 hours for a medium finding and 12 for a high one before scaling for the number of items: 12 active processes on one finding comes to about 17 hours of architect time. Treat that as a starting estimate, not a quote.