Skip to main content
Salesforce · Migration guide · Last verified 28 Oct 2026

Process Builder and Workflow Rules to Flow: inventory, order, migrate

Salesforce no longer supports Workflow Rules and Process Builder as of 31 Dec 2025. Unsupported since 31 Dec 2025, still running in your org: active ones keep running as before, with no customer support and no bug fixes, and Salesforce has announced no retirement date. Start with an inventory of every process, rule and Apex trigger, migrate one object at a time in dependency order, and test each move in a sandbox first.

No card. Connect production, then a sandbox to test the first moves. Clientell runs on desktop.

What is true today

Are Process Builder and Workflow Rules still running?

Yes. Salesforce says: “Salesforce no longer supports Workflow Rules and Process Builder as of December 31, 2025.” In the same article it says your active ones “continue to run as they did before”.

Process Builder and Workflow Rules status by date, with the Salesforce source
Winter ’23New workflow rules can no longer be created in a normal org.Block New Workflow Rule Creation, release note
Summer ’23New processes can no longer be created in Process Builder.New Process Creation Is No Longer Available, release note
31 Dec 2025End of support. Salesforce no longer provides customer support or bug fixes for either tool.Workflow Rules & Process Builder End of Support
Today (checked 28 Oct 2026)Active rules and processes “continue to run as they did before”. You can still edit, activate and deactivate them.Workflow Rules & Process Builder End of SupportWorkflow RulesProcess Builder
Retirement dateNone announced on the Salesforce pages we read. That is the absence of a date, not a promise there will never be one.Workflow Rules & Process Builder End of Support

So the risk is quiet: an automation nobody owns keeps changing records, and when it breaks there is no fix from Salesforce. In Salesforce Ben’s 2026 admin survey, 56.3% of admins said technical debt is their biggest challenge, and 2% of respondents called their org clean and well maintained (Salesforce Ben).

The inventory

What should a Process Builder and Workflow Rule inventory include?

One row for every Process Builder process, Workflow Rule and Apex trigger, and the record-triggered flows already on the same objects. Triggers are on the list because they run on the same objects and can write the same fields, even though Migrate to Flow never touches them. These are the 15 columns.

Inventory columns for Process Builder, Workflow Rules and Apex triggers
01NameThe label as Setup shows it, plus the API name.Where: The Setup list for each tool.
02TypeProcess Builder, Workflow Rule, Apex trigger, or record-triggered flow.Where: Which list you found it in.
03ObjectThe object it runs on, such as Case or Opportunity.Where: The object column in each list, or TableEnumOrId in the queries.
04ActiveYes or no. Inactive items still go on the sheet, marked no.Where: Status column for processes, Active column for rules, Status for triggers.
05Trigger eventCreated only, or created and edited. For a trigger: before or after insert, update, delete.Where: The process start, the rule evaluation criteria, the trigger Usage fields.
06CriteriaWhen it fires, in one line. Flag a related-object field or a formula.Where: Open the item and read its criteria.
07ActionsEvery action: field update, email alert, task, outbound message, Apex, another flow or process, Chatter, scheduled or time-based.Where: Open the item and read its actions.
08Fields writtenObject.Field for every field it sets, including fields on related records.Where: The field updates and record updates inside the actions.
09Other automation on the objectNames of the other processes, rules, triggers and flows on the same object. Mark any that write the same field.Where: Filter the sheet by object. Add flows from the Flows list.
10Pending scheduled actionsYes or no, and how many are queued today.Where: Setup, Time-Based Automations.
11Migrate to FlowTool can, partly, or by hand.Where: The table further down this page, from Salesforce’s limits list.
12RiskLow, medium or high, using the rule in the migration order section.Where: Your call, from the actions and fields written.
13OwnerThe person or team who can say what it is for. If nobody, write “no owner”.Where: Ask. Last modified by is a start, not an answer.
14Still neededYes, no or ask. One line of reason for every no.Where: The owner.
15Migration orderWave number, then position in the wave, such as 1.2.Where: The migration order rules below.

Copy the header row into a sheet

Select the line below and paste it into the first row of Google Sheets or Excel. It is tab separated, so each name lands in its own column.

Name	Type	Object	Active	Trigger event	Criteria	Actions	Fields written	Other automation on the object	Pending scheduled actions	Migrate to Flow	Risk	Owner	Still needed	Migration order

Fill it from the org

The Setup lists give you names. These queries give you counts and objects to check the sheet against. The first two come from our earlier guide, where we ran them on a developer org on 21 Oct 2026. The workflow rule query needs the Tooling API.

How many Process Builder processes are still active?

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

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.

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

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

SELECT Id, Name, TableEnumOrId
FROM WorkflowRule

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

Which Apex triggers run on the same objects?

Setup, Quick Find box: Apex Triggers, select Apex Triggers. The list shows each trigger, its object and whether it is active.

SELECT Name, TableEnumOrId, NamespacePrefix,
  UsageBeforeInsert, UsageAfterInsert,
  UsageBeforeUpdate, UsageAfterUpdate,
  UsageBeforeDelete, UsageAfterDelete
FROM ApexTrigger
WHERE Status = 'Active'

Field names are from Salesforce's ApexTrigger object reference. We have not yet run this one on a test org, so check the result against the Setup list.

Sources FlowDefinitionView object reference (Salesforce Developers), WorkflowRule, Tooling API (Salesforce Developers), ApexTrigger object reference (Salesforce Developers), Monitor the Workflow Queue (Salesforce Help)

A worked example: the Case object

Acme Foods is made up. The rows show how the fields-written and order columns work together. They are not from a real org.

Worked example of the inventory for the Case object
Case priority on createWorkflow RuleWrites: Case.PriorityReads: Case.OriginTool canOrder: 1.1Only updates fields, so the tool can make it a before-save flow. That runs before every workflow rule, so the escalation rule still sees Priority.
Case escalation emailWorkflow RuleWrites: None (email alert)Reads: Case.PriorityTool canOrder: 1.2Reads Priority. As an after-save flow it runs after row 1, whether row 1 is still a rule or a before-save flow. If row 1 had to be after-save too, move both in one cutover and test it.
Case SLA reminderWorkflow RuleWrites: None (time-based email)Reads: Case.StatusTool canOrder: 1.3Has queued actions. Rehearse in a sandbox, then migrate it in production.
Account last-case dateProcess BuilderWrites: Account.Last_Case_Date__cReads: Any new CaseCheckOrder: 2.1Writes to Account. Moves in the same wave as the Account automation.
CaseTriggerApex triggerWrites: Case.Priority (before update)Reads: Case.TypeNot in scopeOrder: StaysWrites the same field as row 1, and an Apex before trigger runs after a before-save flow, so on update its value can win. Test row 1 with this trigger on.

Clientell Platform builds this inventory from your org: every process, rule, Apex trigger and flow, with what each one touches. Nothing changes in your org without your approval.

Start the 14-day trial

Migration order

Which Process Builder or Workflow Rule should you migrate first?

Order by dependency, not by age. Each rule below says whether it is Salesforce’s advice or our own rule of thumb.

  1. 01

    Take out what nobody needs.

    Our rule

    Inactive items, and active ones the owner says are not needed, do not get migrated. Leave them deactivated, not deleted, and write the reason on the sheet.

  2. 02

    Start with the smallest object.

    Salesforce

    Salesforce: “Pick the object that has the least number of Workflow Rules and processes associated with it.” A first move that goes wrong should be cheap.

  3. 03

    Inside an object, the simple ones first.

    Salesforce

    Salesforce calls processes that send email alerts or update fields on the same record “good beginner options”. Tasks, related-record updates, related-object criteria and anything next to an Apex trigger go last.

  4. 04

    Check where a writer and its readers will run.

    Our rule

    When one item writes a field and another item’s criteria read it, a reader only sees the value if the writer runs earlier in the save. Salesforce’s order is roughly: before-save flows, Apex before triggers, Apex after triggers, workflow rules, processes, after-save flows. Write down where each item runs today and where it will run after the move. A writer that becomes a before-save flow runs before the remaining Workflow Rules and processes. When the writer and a reader are both before-save flows, or both after-save flows, set their Trigger Order so the writer runs first. A writer that becomes an after-save flow runs after any workflow rule or process still reading it, so that reader can miss the value. In that case move the writer and its readers in one cutover, or test the in-between state in a sandbox before you go one at a time. What happens in your org also depends on the triggers and flows already on the object.

  5. 05

    Keep linked items in one wave.

    Our rule

    A process that invokes another process, or a rule and a process that write the same field, move in the same wave and get tested together.

  6. 06

    Pair objects that update each other.

    Our rule

    When automation on Case updates Account, put the Account automation in the next wave at the latest and test one record that fires both.

  7. 07

    Queued actions move in production.

    Salesforce

    For a process or rule with scheduled actions still waiting, rehearse in a sandbox, then run Migrate to Flow in production itself. Salesforce says to migrate in the same org as the original; a flow deployed from another org does not take over the waiting actions.

The risk column

  • LowOnly sends an email alert, or only updates fields on its own record.
  • MediumHas a scheduled or time-based action, or calls another flow.
  • HighCreates tasks, updates related records, uses related-object criteria, or shares a field with an Apex trigger.

Sources Planning Your Switch to Flow Builder (Salesforce Help), Migrate to Flow Tool Considerations (Salesforce Help), Triggers and Order of Execution (Salesforce Developers)

Sandbox test order

How do you test a migrated flow in a sandbox?

Salesforce says to migrate and test in a sandbox before production. Run this order once per wave; the last two steps take it to production. Steps marked “Our rule” are our judgment, and the result in your org depends on what else runs on the object. Salesforce also warns that record-triggered flows can behave differently from similar workflow rules, because they run at a different point in the save.

  1. 01

    Check the sandbox matches production.

    Run the same inventory queries in both. If the counts differ, refresh the sandbox or note the gap before you test anything.

  2. 02

    Write the test records down first.

    For the object: one record that meets the criteria, one that does not, one edited into the criteria, one edited while already in it, one with blank fields, one owned by a queue, and a small bulk load with Data Loader.

  3. 03

    Record the old behaviour.

    With the old automation on and no new flow active, save every test record. Write down each field change, email and record created.

  4. 04

    Migrate the wave.

    Run Migrate to Flow on the items marked “tool can” or “partly”, then build the “by hand” ones. New flows are created inactive.

  5. 05

    Swap one pair at a time.

    Deactivate the old item, activate its new flow. For a workflow rule, the tool’s Switch Activations button does both. For a process, you do both yourself.

  6. 06

    Rerun fresh copies of the same records.

    Compare row by row: expected, old result, new result, match. Every difference is fixed or signed off by the owner.

  7. 07

    Test with the neighbours on.

    Keep the Apex triggers and other flows on the object active. For paired objects, save one record that fires both.

  8. 08

    Set the trigger order and run again.

    Give each flow on the object a Trigger Order from 1 to 2,000, spaced out (10, 20, 30). Flows with the same value run in alphabetical order of API name.

  9. 09

    Route the fault alerts, then make one flow fail on purpose.

    A fault path on its own tells nobody: once a fault path handles an error, Salesforce does not send its default flow error email for it. On each fault path, send the alert somewhere a person looks, such as an email action, a custom notification or a record in an error log your team checks. Before-save flows allow fewer elements, so check what your flow type can do. Then save a record with a bad value and confirm the alert arrives where you routed it.

  10. 10

    Get the owner’s sign-off, then pick the production route.

    No queued actions: deploy the tested flows. Deployed flows arrive inactive by default, but a setting in Process Automation Settings can deploy them active. Before you deploy, confirm that setting is off so the flows land inactive. If you cannot confirm it, pause writes to the object before the deploy, as in the next step. Queued actions waiting: do not deploy. Run Migrate to Flow in production on the original item, repeating what you did in the sandbox, because Salesforce says only a flow migrated in the same org can take over the waiting actions. Look at Time-Based Automations before and after the switch, and confirm on a test record that waiting actions run once.

  11. 11

    Cut over in production, one item at a time.

    Our rule: pick a quiet window and, where you can, pause the integrations and bulk jobs that write to the object before the deploy or the production migration. Keep them paused until you have confirmed exactly one version is active. Deactivate the original first, then activate the replacement. For a workflow rule, Switch Activations does both in one step. Once exactly one of the two is active, resume writes and watch the first real records. Deactivate, do not delete, so you can switch back.

Sources Move Processes and Workflows to Flow Builder with the Migrate to Flow Tool (Salesforce Help), Migrate to Flow Tool Considerations (Salesforce Help), Define the Run Order of Record-Triggered Flows for an Object (Salesforce Help), Customize What Happens When a Flow Fails (Salesforce Help)

Migrate to Flow

What does the Migrate to Flow tool skip?

The tool is in Setup (Quick Find: Migrate to Flow). It supports record-triggered processes, and for workflow rules it supports field-based criteria, field updates, email alerts, outbound messages and time-dependent actions. The rest is partly migrated or built by hand. The full list, with the fix for each, is in our post on what the Migrate to Flow tool skips.

What each old action becomes in Flow, and whether Migrate to Flow handles it
Update the same recordUpdate Records, or a before-save flow if it only updates fieldsTool can
Email alert, outbound messageAn Action elementTool can
Time-dependent workflow actionA scheduled pathTool can
Invoke ApexAn Apex actionTool can
Scheduled actions in a processA scheduled path, if you select the single criteria that owns itPartly
Invoke another flowA Subflow elementPartly
Chatter post, quick action, approval, custom notificationFlow actions that need extra setupPartly
Update related recordsGet Records and Update RecordsCheck
Task (workflow rule)Create Records on the Task objectBy hand
Invocable process, or criteria on a related-object fieldRebuild in Flow BuilderBy hand

Sources Migrate to Flow Tool Considerations (Salesforce Help), Equivalent Features in Flows and Workflow Rules (Salesforce Help), Move Processes and Workflows to Flow Builder with the Migrate to Flow Tool (Salesforce Help)

Ways to do it

Five ways to move Process Builder and Workflow Rules to Flow

Every way needs the same inventory and the same sandbox tests. They differ in who builds the list and who drafts the flows.

Five ways to migrate, what each is good for and what to watch
By hand, with Migrate to FlowSmall orgs, and teams that want to learn Flow item by item.Watch: The inventory and the test notes are a spreadsheet you keep up to date yourself.
Claude Code with the Salesforce CLIDevelopers who already pull metadata into a project and want help reading it.Watch: The agent only knows the files you retrieved. Check its answers against the org.
Claude Code with Clientell MCPAbout Clientell MCPTeams working in Claude Code, Cursor, Codex or VS Code who want the agent to see every process, rule, trigger and flow on an object.Watch: You still run the tests and the switch-over.
Clientell PlatformAdmin teams who want the inventory built from the org, and a drafted flow to review for the items they pick.Watch: Testing, ordering and sign-off stay with your team.
Managed ServicesAbout Managed ServicesOnly if you have no Salesforce admin or developer of your own.Watch: A monthly service, not a tool. Talk to us first.

To size the work with your own counts and hour estimates, use the automation migration effort calculator.

Checklist

The nine steps, with how you know each one is done

Print this page or copy the list. Setup menu names can differ slightly between releases.

  1. 1.Count what still runs.

    Done when: The active count in each Setup list matches the queries.

    Setup, Quick Find: Workflow Rules. Then Process Builder. Then Apex Triggers. Then Flows.

  2. 2.Fill in the inventory, by object.

    Done when: Every active item has a row with every column filled in, or marked “ask”.

  3. 3.Rank by risk and set the order.

    Done when: You can say in one sentence why the first object goes first.

  4. 4.Sort each item by what Migrate to Flow can do.

    Done when: Every row says tool can, partly or by hand. The by-hand count is a number.

    Setup, Quick Find: Migrate to Flow.

  5. 5.Migrate in a sandbox.

    Done when: One new flow per migrated item, each with a description that names the old item.

  6. 6.Test each flow, using the test order above.

    Done when: Every test record matches, or the difference is signed off.

    Setup, Quick Find: Debug Logs.

  7. 7.Order the flows on each object.

    Done when: Flow Trigger Explorer shows the same order as your sheet.

    Setup, Quick Find: Flows, then Flow Trigger Explorer.

  8. 8.Switch over, one pair at a time.

    Done when: Exactly one of the old item and its flow is active, and one record that meets the criteria gives one set of results, not two.

    Setup, Quick Find: Time-Based Automations, to see what is queued first.

  9. 9.Watch after go-live.

    Done when: Every fault path sends an alert to a named person or a place your team checks, and you have seen one arrive in a test.

Already moved some? The cleanup checklist for processes and rules still firing in 2026 covers what to switch off and what to keep.

What we checked and when

Last verified 28 Oct 2026

On 28 Oct 2026 we re-read Salesforce’s end of support article (001096524) and compared the status and wording on this page with it. The Migrate to Flow limits, Setup paths and queries were checked on 21 Oct 2026 against the pages linked in each section. We re-read the article before changing anything here.

Change log

  • 28 Oct 2026: Published. Brings together our Process Builder to Flow guide and migration blog post, and adds the inventory columns, the migration order and the sandbox test order.

Common questions

Do Process Builder processes and Workflow Rules still run in 2026?

Yes. Salesforce stopped supporting both on 31 Dec 2025, and says your active ones “continue to run as they did before”. What ended is customer support and bug fixes. Salesforce has not announced a retirement date.

Can I still create a new process or workflow rule?

Not in a normal org. The Winter ’23 release blocked new workflow rules and the Summer ’23 release blocked new processes. You can still edit, activate and deactivate the ones you have.

Why are Apex triggers on the inventory?

Migrate to Flow does not touch them, but they run on the same objects and can write the same fields. A flow sits at a different point in the save than the rule it replaces, so you test each new flow with the triggers on.

Should I merge everything into one flow per object?

You do not have to. Salesforce says several flows per object are manageable when you set a Trigger Order and check them in Flow Trigger Explorer.

Definitions: Process Builder and Workflow Rule in our glossary.

Start with the inventory from your own org

Clientell Platform lists every Process Builder process, Workflow Rule, Apex trigger and flow, with what each one touches, so you can pick the first five to move. It reads records live under your own Salesforce permissions and does not store them. Nothing changes in your org without your approval. $500 a month for 3 platform seats and 1 org. The trial runs 14 days, no card, and the clock starts when you connect your first org.

No card. Connect production, then a sandbox to test the first moves. Clientell runs on desktop.