Skip to main content
Effort calculator

How long will the move take you?

Total hours = tool items x (tool hours + test hours) + hand items x (hand hours + test hours). This automation migration effort calculator applies that sum to your active Process Builder processes and Workflow Rules. The numbers shown first are examples. Change every one of them.
Your estimate162 h · $9,720

1How many items still run?

Sample numbers. Replace them with your own counts. Both counts are in Setup, as the box below shows.

Where to get both counts
  • In Setup. Workflow Rules: Quick Find box, Workflow Rules, sort the Active column. Processes: Quick Find box, Builder, select Process Builder, sort the Status column for Active.
  • With queries. Run them with the sf CLI. The first query is normal SOQL (Salesforce Object Query Language, the query language for Salesforce data), so the Developer Console Query Editor can run it too. The count of rows returned is your count.

Active processes (normal SOQL, as above):

SELECT Id, ApiName, Label, ProcessType, TriggerType, ActiveVersionId, LastModifiedDate, IsActive FROM FlowDefinitionView WHERE ProcessType = 'Workflow' AND IsActive = true

Workflow rules (Tooling API: add --use-tooling-api in the sf CLI). This lists every rule, active or not:

SELECT Id, Name, TableEnumOrId FROM WorkflowRule

The active flag of a rule sits in Metadata, and Salesforce says to query it one rule at a time: SELECT Id, Metadata FROM WorkflowRule WHERE Id = '<rule Id>', then read Metadata.active. Step 1 of the guide has every query and the failure notes.

Sources, checked 21 Oct 2026: Workflow Rules path, Process Builder path, End of Support article, FlowDefinitionView, WorkflowRule, Developer Console Query Editor.

2What can the tool not handle? (sample numbers)

20%

Your estimate. Salesforce publishes no figure for this share. Walk your sheet through the list below (guide, step 4) and count.

Salesforce says Migrate to Flow cannot take

  • Custom event and invocable processes (it supports only record-triggered processes)
  • Process criteria with a field from a related object, or custom metadata types
  • A cross-object reference in a formula
  • Recursion (not fully supported)
  • Workflow rules with: criteria with no actions, global variable fields, fields on related records, record types, some operators, some formulas, Tasks, relative date values, multiple currencies

Also budget time for scheduled actions (select the single criteria), invoke flow (it becomes a subflow) and actions that need extra setup. Source: Migrate to Flow Tool Considerations, checked 21 Oct 2026.

3How many hours does each item take? (inputs)

Your own estimates, not Salesforce figures. Test and review is counted for every item, tool or hand.

4Who does the work, and at what rate? (inputs)

Salary plus overhead, divided by hours worked.

5Which objects should move first?

Optional

Type your own objects and how many active items each has (step 2 of the guide). The order below is built from what you enter. Names stay in this page.

Salesforce facts on this page were checked on 21 Oct 2026: End of Support article, Migrate to Flow Tool Considerations, Planning Your Switch to Flow Builder, Workflow Rules path, Process Builder path, FlowDefinitionView, WorkflowRule. The hours, the share and the costs are the visitor's own inputs. Nothing here is a Salesforce figure. Last updated: October 22, 2026.

Worked example: how do 60 items add up to 162 hours?

Example: 25 processes and 35 rules make 60 items. Say 20 percent need hand work. That is 12 items by hand and 48 by tool.

Hand work takes 4 hours to build plus 1.5 hours to test and review, so 12 x 5.5 = 66 hours. The tool path takes 0.5 hours to run and tidy plus 1.5 hours to test, so 48 x 2 = 96 hours. The total is 66 + 96 = 162 hours.

At 60 dollars an hour that costs 9,720 dollars. Two people share it, so each carries 81 hours. These hours are example inputs, not Salesforce figures.

FAQ: common questions about the automation migration effort calculator

Where do I find my counts of processes and rules?

In Setup, search Workflow Rules and Process Builder, then count the active ones. The box under step 1 also has queries you can run.

Does Salesforce publish a time estimate for the migration?

No. Salesforce says only that the migration may take a significant amount of time and testing. Every hour on this page is your own estimate.

What does the Migrate to Flow tool not handle?

It supports only record-triggered processes, and it cannot take some criteria, formulas and workflow rule types. The list in step 2 comes from the Salesforce Migrate to Flow considerations article.

Why are test and review hours counted for every item?

A migrated flow still needs a sandbox test and a review before you switch it on. The calculator adds your test hours to each item, by tool or by hand.

Now check the count against your org.

Connect a sandbox or production org and Clientell AI lists your active Process Builder processes and Workflow Rules for you. 14-day free trial, no card.

Start the 14-day free trialDownload the checklist (PDF)

No card needed