The salesforce process builder retirement date end of life is a milestone every Salesforce admin eventually has to plan for. Salesforce has officially scheduled the retirement of Process Builder and Workflow Rules for December 31, 2025, after announcing the shift when Flow was introduced. That means any automation built with the legacy tool needs a new home.
If you're still running critical business logic through Process Builder, you're working against a clock.
The problem is not the date itself — it's everything that happens before it. Orgs with dozens of processes, complex entry criteria, and overlapping rules can't migrate overnight, and a rushed rebuild can break approvals, notifications, and record updates.
This article breaks down what the retirement actually means, how the timeline works, what to migrate first, and the practical steps that keep your org running. You'll get a clear migration plan, a comparison table, and answers to the edge-case questions admins ask most.
What the Process Builder Retirement Date Actually Means
The retirement means Process Builder and Workflow Rules stop being supported for new automation and are gradually phased out. Salesforce positions Flow as the single replacement tool for building automation going forward.
The key distinction is between building new processes and running existing ones. When the salesforce process builder retirement date end of life passes, you will no longer be able to create new processes or modify existing ones through the legacy interface. Existing automations may continue to run for a period, but without support or bug fixes.
That creates real risk. An unsupported process that fails silently — say, a broken approval notification — is hard to diagnose when no official support path exists.
Salesforce's official Flow resource page explains that Flow is the recommended tool for all automation needs. The messaging is consistent: consolidate onto one platform.
Why the Legacy Tool Is Being Retired
Salesforce has stated that maintaining three separate automation tools (Workflow Rules, Process Builder, and Flow) increases complexity and confusion. Consolidating to Flow reduces the number of places where logic can conflict.
- Fewer tools mean clearer debugging
- Flow supports more complex logic and integrations
- A single automation platform simplifies governance
How to apply this: Audit your org today by running a report of all active Process Builder processes and Workflow Rules, then tag each one by business criticality.
The Full Retirement Timeline and Key Milestones
The timeline is a phased sequence, not a single switch. Understanding the milestones helps you plan migration work in the right order.
Salesforce announced the retirement in 2021 and set the end-of-life for December 31, 2025. Since then, the company has encouraged admins to adopt Flow and has added migration tooling to reduce manual rebuild work.
The phases look roughly like this:
- Announcement and transition period — new features focus on Flow; legacy tools still work fully
- Migration phase — admins rebuild processes in Flow; Salesforce provides conversion helpers
- End-of-life — legacy tool creation and editing disabled
- Post-retirement — existing automations run without active support
The exact behavior after the salesforce process builder retirement date end of life depends on your org's configuration and Salesforce's implementation. Salesforce's official release notes are the authoritative source, so check them before you finalize any assumptions.
What Happens If You Miss the Deadline
Miss it and you lose the ability to edit legacy processes. Existing ones may keep firing, but you can't adjust them — meaning a change in business rules becomes a rebuild under pressure.
A common scenario: a sales team wants a discount approval threshold changed, and the admin discovers the process can no longer be edited because it lives in the retired tool. The fix is a full Flow rebuild with no lead time.
How to apply this: Put your migration deadline at least two quarters before the salesforce process builder retirement date end of life so you have buffer for testing.
How to Migrate Before the Process Builder End of Life
Migration means rebuilding each process as a Flow, then testing and deactivating the legacy version. The good news is that Salesforce offers conversion tooling to reduce manual effort.
The migration approach depends on complexity. Simple record updates convert cleanly. Complex processes with branching logic and multiple objects often need to be rebuilt with Flow's more powerful elements.
A practical sequence:
- Inventory all processes and rules
- Prioritize by business impact, not by number
- Rebuild in Flow, starting with the highest-risk item
- Test in a sandbox with real data volumes
- Deactivate the legacy process only after the Flow runs cleanly
The most common mistake is deleting the old process too early. Keep it deactivated but intact until the new Flow has run in production for a defined period — often 30 days — while you continue tracking the salesforce process builder retirement date end of life.
Testing Your Rebuilt Flows
Test with production-like data. Record-triggered flows behave differently under bulk operations, and a process that worked for one record can hit governor limits when 200 records update at once.
For debugging, tools like Salesforce Workbench let you run queries and inspect data, while Google Search Console is unrelated to CRM but useful if your Salesforce data feeds a website. For org-level monitoring, Salesforce's built-in Setup Audit Trail tracks who changed what.
How to apply this: Run a bulk test with at least 200 records before you deactivate any legacy process, and log the results against the salesforce process builder retirement date end of life.
Comparing Process Builder, Workflow Rules, and Flow
Understanding how the three tools differ helps you decide what your rebuild should look like.
| Tool | Status | Best for | Migration action |
|---|---|---|---|
| Workflow Rules | Retiring | Simple field updates, email alerts | Rebuild as simple Flow |
| Process Builder | Retiring | Multi-step updates, approvals | Rebuild as record-triggered Flow |
| Flow | Active | Complex logic, integrations | Target platform |
| Apex Triggers | Active | Bulk-heavy, complex code | Keep if already coded |
| Third-party apps | Active | Niche add-ons | Verify Flow compatibility |
The comparison shows why Flow is the destination: it covers the simple cases Workflow Rules handled and the branching logic Process Builder supported, plus far more.
Salesforce's Trailhead module on Flow explains its trigger types and element library in detail. The learning curve is real, but the payoff is a single automation system.
Where Each Tool Falls Short
Workflow Rules can't do branching. Process Builder can branch but struggles with complex loops and bulk performance. Flow handles both but requires learning its element model.
How to apply this: Map each legacy process to the Flow type it needs — record-triggered, scheduled, or screen — before you start building, and note how close each one sits to the salesforce process builder retirement date end of life.
Practical Risks and How to Manage the Transition
The main risks are missed automations, broken approvals, and performance regressions after migration. All three are manageable with a disciplined process.
The biggest hidden risk is overlapping logic. If a Workflow Rule and a Process Builder process both update the same field, their order of execution matters — and that ordering can change when you move to Flow.
A second risk is institutional knowledge. The admin who built a process five years ago may have left, and the logic may not be documented anywhere.
According to Salesforce's Automation guidance, Flow is the supported path for new automation, and the company recommends consolidating sooner rather than later. Acting early spreads the work.
Building a Migration Checklist
A checklist keeps the work visible and auditable. At minimum, track:
- Process name and owner
- Business function it supports
- Migration status (not started, in build, tested, live)
- Deactivation date of the legacy item
How to apply this: Store the checklist in a shared spreadsheet or a Salesforce custom object so the whole team can see progress, with a column showing days remaining until the salesforce process builder retirement date end of life.
Frequently Asked Questions About salesforce process builder retirement date end of life
What happens to existing Process Builder automations after retirement?
Existing automations may continue to run after the salesforce process builder retirement date end of life, but they lose official support and cannot be edited. In practice, a business rule change after that date forces a rebuild under time pressure. Plan for a rebuild window even if your processes still fire, because an uneditable automation is a liability.
Can I convert Process Builder to Flow automatically?
Salesforce offers conversion tooling that migrates many simple processes into Flow, but complex branching logic often needs manual rebuilding. A process with multiple decision elements and cross-object updates is a common case where automatic conversion falls short.
Review every converted Flow in a sandbox before promoting it, since the conversion treats the salesforce process builder retirement date end of life as a hard cutoff you must meet.
Does the retirement affect Workflow Rules too?
Yes. Workflow Rules are retired alongside Process Builder as part of the same consolidation onto Flow. Admins sometimes focus only on processes and overlook simple field-update rules, which is a frequent oversight. Inventory both tools together so the salesforce process builder retirement date end of life doesn't surprise you with forgotten Workflow Rules still live in production.
Will my org break on the retirement date if I do nothing?
Not necessarily on day one, but you lose the ability to modify unsupported automations. A scenario where leadership changes a discount rule and the admin cannot edit the legacy process is the typical failure point. Treat the salesforce process builder retirement date end of life as the deadline for migration work, not the day your org stops functioning.
How long does a typical migration take?
Simple processes convert in hours; complex ones can take weeks each depending on logic and testing. An org with 50 active processes is a common scenario that takes several months of part-time admin work. Start with a high-impact process to build team confidence before scaling, and track progress against the salesforce process builder retirement date end of life.
Conclusion
The salesforce process builder retirement date end of life is a fixed deadline, and the work is real — but it's also a chance to clean up years of tangled automation. Key takeaways:
- Process Builder and Workflow Rules retire December 31, 2025; plan to finish well before
- Flow is the single supported replacement for both tools
- Inventory and prioritize by business impact, not by count
- Test with bulk data and keep legacy processes intact until Flows prove stable
The next step is concrete: open your org, export a list of every active Process Builder process and Workflow Rule, and assign a priority to each one this week. Treating the salesforce process builder retirement date end of life as a project with a schedule — not a surprise — is what separates a smooth transition from a broken one.
