The salesforce process builder retirement date 2025 2026 marks a hard deadline that every Salesforce admin should already have on their calendar. Salesforce has confirmed that Process Builder and Workflow Rules reach end of support on December 31, 2025, with no new activations permitted after that point.
The problem is that thousands of orgs still run critical automations on these legacy tools, and migration to Flow is not a simple toggle. This guide breaks down the exact dates, what actually stops working, how to plan a safe migration, and the mistakes that catch teams off guard.
What the Official Retirement Timeline Actually Says
The retirement happens in stages, not all at once. Understanding each milestone matters because missing an early one can freeze your ability to edit existing processes.
Salesforce's official position is clear: Process Builder and Workflow Rules are retired, and Flow is the designated replacement. The salesforce process builder retirement date 2025 2026 breaks down into clear milestones:
- December 31, 2025: No new Process Builder or Workflow Rule activations are allowed in any org.
- After the 2025 cutoff: Existing automations continue to run but receive no bug fixes, security patches, or support.
- Spring and Summer releases: Newly created legacy automations are blocked entirely, and migration tooling is emphasized.
A common misconception is that everything shuts off the moment the salesforce process builder retirement date 2025 2026 passes. In practice, running processes keep executing, which creates a false sense of safety. The real risk is silent drift: an unsupported engine plus changing business logic equals broken automation with no vendor help.
How to apply this: Pull a full inventory of active processes and workflow rules in Setup today, and flag every one with an owner name and a business-criticality rating.
Why Salesforce Is Retiring Process Builder and What Replaces It
Flow is the replacement, and it is not a like-for-like swap. Process Builder offered a simplified, form-based way to automate record updates; Flow offers a visual canvas with branching, loops, and error handling that covers far more ground.
Salesforce's own documentation frames the shift around reliability and maintainability. The Salesforce Help portal states that Flow is the primary automation tool going forward, and that legacy tools will no longer receive enhancements. The practical consequence is that any new automation requirement must be built in Flow, even if a process would have been faster to configure.
One subtlety: a single Process Builder can often be split into multiple Flows, or consolidated with others. In one case, an admin consolidated eight record-triggered processes into three flows, cutting maintenance overhead noticeably. That consolidation work is where most migration time actually goes.
The salesforce process builder retirement date 2025 2026 deadline matters less than the quality of the rebuild. A rushed one-to-one conversion often copies old logic flaws into a new engine.
How to apply this: Before converting anything, document the business intent behind each process, not just its configuration. Rewrite from intent, not from the old build.
How to Plan Your Migration Before the Deadline
Start with assessment, not conversion. The migration sequence that works reliably follows four phases, and skipping the first one is the most common failure point.
- Inventory: Export every process and workflow rule using the Process Builder list view and a metadata retrieval tool.
- Triage: Sort each item into retire, convert, or consolidate.
- Build: Recreate logic in Flow, testing in a sandbox first.
- Validate: Run both old and new automations in parallel in a sandbox before cutover.
The salesforce process builder retirement date 2025 2026 gives you a fixed finish line, so work backward from it. If your org runs dozens of automations, allocate weeks rather than days.
| Migration Step | What it tells you | Action to take |
|---|---|---|
| Inventory export | Total automation count | Assign an owner to each item |
| Triage review | Which processes are obsolete | Retire dead logic first |
| Sandbox build | Whether Flow logic matches | Test with real record data |
| Parallel run | Behavioral differences | Compare field-level results |
| Cutover | Readiness to deactivate | Deactivate one process at a time |
How to apply this: Set a personal migration deadline at least 60 days before the official cutoff to leave room for unexpected test failures.
Common Migration Mistakes That Cost Teams Time
Tight coupling between processes and other automation is the biggest hidden trap. Many orgs have Process Builder triggers that depend on workflow field updates, and those chains break in unexpected ways during conversion.
A second frequent mistake is translating logic literally. A process that fired on every edit may become a Flow that fires in a loop, causing recursion errors. Salesforce provides guidance on avoiding recursive flows, which is worth reading before you build.
The salesforce process builder retirement date 2025 2026 also affects testing windows. Teams that wait until the final quarter often find their sandbox refresh cycle collides with the deadline, leaving no time for parallel validation.
- Check for cross-object dependencies before deactivating anything.
- Test with bulk data loads, not single records.
- Confirm field-level permissions for Flow run contexts.
- Document every deactivated process with its Flow replacement.
How to apply this: Build a dependency map for your five most critical automations and identify which ones trigger others.
Tools and Resources That Speed Up the Transition
Salesforce's native migration tooling handles much of the heavy lifting. The Migrate to Flow tool inside Setup converts many processes automatically, though it requires review afterward.
For metadata retrieval and comparison, Workbench lets you inspect and download automation metadata across orgs. For documentation and test evidence, Salesforce Trailhead offers free modules on Flow fundamentals and migration patterns.
The salesforce process builder retirement date 2025 2026 makes automated conversion tools valuable, but none of them fully replace human review. Converted flows frequently need error handling added because Process Builder lacked it entirely.
How to apply this: Run the Migrate to Flow tool on a single low-risk process first, then review the generated flow line by line before scaling up.
Frequently Asked Questions About salesforce process builder retirement date 2025 2026
What exactly happens to running processes after the deadline?
Existing automations continue to execute after support ends, but they receive no updates or fixes. If a related object changes, your process may silently fail. Plan to deactivate legacy automations deliberately rather than waiting for the salesforce process builder retirement date 2025 2026 to force the issue.
Can I still create a new Process Builder in 2025?
No. New activations are blocked well before the final cutoff, and the restriction applies across all editions. If a business need appears, build it in Flow from day one. Treating the salesforce process builder retirement date 2025 2026 as the only deadline will leave you blocked mid-project.
Does this affect Workflow Rules too, or just Process Builder?
Both retire on the same timeline. Workflow Rules share the same end-of-support date, so any org still relying on them needs the same migration plan. Check both lists together when you scope the salesforce process builder retirement date 2025 2026 work.
What if my org is on a legacy edition with limited Flow features?
Some older editions have restricted Flow capabilities. Confirm your edition's limits with your Salesforce account team early, because a platform upgrade may be needed. The salesforce process builder retirement date 2025 2026 deadline does not pause for licensing negotiations.
How do I test that a converted Flow behaves identically?
Run both versions in a sandbox against the same test records and compare field-level results. Use bulk test data to catch governor limit issues. The salesforce process builder retirement date 2025 2026 is fixed, so build your validation window into the plan from the start.
Conclusion
The retirement is a fixed deadline with real consequences for unsupported automation. The salesforce process builder retirement date 2025 2026 will not move, so your migration plan should. The key takeaways:
- Support ends December 31, 2025, with new activations blocked earlier.
- Running processes keep working but receive zero vendor help.
- Flow is the only forward path, and rebuilt logic should follow business intent.
- Parallel sandbox testing is the safest way to catch behavior changes.
Start your inventory this week, assign owners, and set an internal deadline well ahead of the cutoff.
