Skip to main content
Process Builder and Workflow Rules to Flow

Your Process Builder automation still runs. If it breaks now, Salesforce will not fix it.

A free 15-check PDF from Clientell AI, the AI agent for Salesforce admins, that moves Workflow Rules and Process Builder to Flow, one object at a time. Salesforce ended support for both on 31 Dec 2025.

Free printable checklist

Get the checklist (PDF)

Two printable pages. Enter your work email and the PDF opens on this page at once. Free addresses such as Gmail do not work.

We may email you Salesforce admin tips now and then. You can unsubscribe at any time. Privacy policy

Source: Workflow Rules & Process Builder End of Support (Salesforce Help).

What you get

  • Count every active Process Builder process and Workflow Rule, object by object
  • Mark each one: the Migrate to Flow tool moves it, moves part of it, or you rebuild it by hand
  • Deactivate each old Workflow Rule or process, never delete it, so you can switch it back on

Printable checklist

Count each Workflow Rule and process, rank them by object, migrate in a sandbox, test, switch over, watch. Each check has a pass line, so you know when it is done.

Opens after you enter your work email above

Migration effort calculator

Enter how many processes and Workflow Rules are still active, and your hours per item. You get the total hours and cost of the migration.

Open the calculator

The full guide

What still runs, what the Migrate to Flow tool cannot convert, and the order Salesforce suggests, with the Salesforce Help page for each point.

Read the guide

Do it by hand first

How much old automation still runs in your org?

Count before you plan. Each count below uses a Setup page and a query that Salesforce documents. Run the queries with the Salesforce CLI (sf data query -o your-org -q "...") or any SOQL (Salesforce Object Query Language) tool you already use.

Check 1

How many Process Builder processes are still active?

Setup path: Setup > Process Automation > Process Builder (or type Builder in the Quick Find box). Sort the Status column for Active.

Salesforce still lets you edit, activate and deactivate existing processes. In the API, a Process Builder process has the process type Workflow. This query counts the active ones.

SELECT COUNT()
FROM FlowDefinitionView
WHERE ProcessType = 'Workflow'
AND IsActive = true

Keep the WHERE filter. FlowDefinitionView does not support queryMore(), so a query with no filter can fail in a large org.

Sources: Workflow Rules & Process Builder End of Support (Salesforce Help); Process Builder (Salesforce Help); FlowDefinitionView object reference (Salesforce Developers).

Check 2

How many Workflow Rules do you have, and which are on?

Setup path: Setup > Process Automation > Workflow Rules (or type Workflow Rules in the Quick Find box). Sort the Active column for checkmarks.

This query lists every workflow rule and the object it runs on. The on or off flag is not a plain column, so read it from the Active column in Setup.

SELECT Id, Name, TableEnumOrId
FROM WorkflowRule

This one needs the Tooling API. With the CLI, add --use-tooling-api to the command.

Sources: Workflow Rules & Process Builder End of Support (Salesforce Help); Workflow Rules (Salesforce Help); WorkflowRule, Tooling API (Salesforce Developers).

Official Salesforce sources

The Salesforce Help and developer pages behind this checklist.

Last updated: October 21, 2026

Questions

Did Process Builder and Workflow Rules stop working on 31 December 2025?

No. Salesforce says active Workflow Rules and processes "continue to run as they did before, even after December 31, 2025." What stopped is support and bug fixes. Salesforce also says they "may continue to function", so plan the move now.

Source: Workflow Rules & Process Builder End of Support (Salesforce Help).

Can I still create new Workflow Rules or Process Builder processes?

Not in a normal org. Salesforce blocked new workflow rules in Winter '23 and new processes in Summer '23. Build all new automation in Flow Builder.

Sources: Block New Workflow Rule Creation (Salesforce release note); New Process Creation Is No Longer Available (Salesforce release note).

Does the Migrate to Flow tool convert everything?

No. It supports only record-triggered processes. It cannot move custom event or invocable processes, or workflow rules that create tasks, use record types or read fields on related records. Salesforce says to migrate and test in a sandbox before anything reaches production.

Source: Migrate to Flow Tool Considerations (Salesforce Help).

Which automation should I move first?

Start with the object that has the fewest workflow rules and processes. List your automation by object first, as Salesforce suggests. Its planning guide calls processes that send email alerts or update fields on the same record good beginner options.

Source: Planning Your Switch to Flow Builder (Salesforce Help).

Is a record-triggered flow faster than Process Builder?

Yes, for same-record updates. Salesforce says a record-triggered flow can update a record "10 times faster than a record-change process." Before-save flows give that speed. Salesforce calls them Fast Field Updates.

Source: Before-Save Record-Triggered Flows (Salesforce Help).

How long does the migration take?

It depends on how many items you have and how complex they are. Salesforce says the move "may take a significant amount of time and testing". Put your own counts into the effort calculator on this page for an estimate.

Source: Workflow Rules & Process Builder End of Support (Salesforce Help).

Want the count without the queries? Ask Clientell AI.

Clientell AI is an AI agent for Salesforce admins. Connect a sandbox or production org, and it reads your org in read-only mode first. Then ask: “List every active Process Builder process and Workflow Rule, by object.” It lists them. Then it drafts the replacement Flow you pick and shows it to you.

Start in a sandbox. Clientell AI asks before it changes anything in production.

Your checklist comes with a link to the 14-day free trial. No card needed.