The salesforce process builder retirement date end of life 2025 2026 question is now urgent for every Salesforce admin.
Salesforce officially announced that Process Builder is being retired, and while you can still view existing processes, you can no longer create or edit them — Salesforce stopped allowing new Process Builder creation in 2023 and has been pushing all automation to Flow Builder since.
That means every process still running in your org is frozen technology: it works today, but it cannot be modified, and unsupported automations are a known source of broken business logic during major releases. This guide covers the exact retirement timeline, what still works, how to migrate safely, and the five steps to complete your transition before year-end deadlines.
Why Salesforce Is Retiring Process Builder
Salesforce's position is clear: Flow Builder is the future of all declarative automation. In official communications and the "Automate Your Business Processes" Trailhead module, Salesforce states that Flow is the recommended tool and that Process Builder will not receive new capabilities.
Salesforce's own guidance in its help documentation tells admins to build new automation in Flow Builder rather than Process Builder.
The reasoning is practical. Flow supports more trigger points, better error handling, subflows, and debugging tools that Process Builder never had. Salesforce also reports that the vast majority of new automation created on the platform is now built in Flow.
Understanding the salesforce process builder retirement date end of life 2025 2026 timeline helps admins prioritize which processes need attention first, especially those on business-critical objects.
Maintaining two parallel automation engines splits engineering resources, so consolidation benefits everyone — including you, since bugs in legacy tools often go unfixed.
How to apply this: Open your org today and check Setup → Process Automation → Process Builder to see how many processes exist and when each was last edited.
The Actual Retirement Timeline: What Happened and What's Next
There is no single date when running processes stop working. The retirement is staged, which is why the salesforce process builder retirement date end of life 2025 2026 window confuses so many admins.
Key milestones from Salesforce's official announcements:
- Winter '23 release: Salesforce stopped allowing admins to create new Process Builder automations.
- Ongoing: Existing processes remain editable for a transition period, but Salesforce has signaled continued restriction of edits.
- 2025–2026: The focus shifts to organizations fully migrating runtime processes to Flow. Salesforce has advised that future releases may restrict even viewing and editing legacy tools.
The practical takeaway: a process that runs fine today can still become unmaintainable overnight after a release. If your org upgrades annually three times a year, waiting is risk, not safety.
The salesforce process builder retirement date end of life 2025 2026 milestone should be treated as a hard deadline for completing your migration, not the starting point for planning it.
How to apply this: Check your current release notes on Salesforce Help for the latest Process Builder restrictions before your next sandbox refresh.
What Still Works and What Doesn't
Understanding the boundary between "deprecated" and "dead" prevents panic and missed deadlines. The salesforce process builder retirement date end of life 2025 2026 transition period means different capabilities have different statuses, and knowing which is which saves hours of confusion.
| Capability | Current status | Action to take |
|---|---|---|
| Running existing processes | Still execute | Inventory them now |
| Creating new processes | Blocked | Use Flow Builder |
| Editing old processes | Restricted/varies | Plan migration |
| Official support & fixes | Legacy only | Don't rely on it |
| New features | None ever | Migrate to Flow |
The keyword to remember: running ≠ supported. Your automation executes, but if it breaks after a platform update, fixes are not guaranteed. As the salesforce process builder retirement date end of life 2025 2026 deadline approaches, the gap between what runs and what's supported will only widen.
One common scenario: a company discovers a Process Builder flow silently failing after a Spring release update, with no error email configured — and no engineer able to edit the process to fix it.
How to apply this: Add error notifications to your remaining processes now, even while you plan the migration.
Step 1: Audit and Inventory Every Process
You cannot migrate what you cannot see. Start with a complete inventory of Process Builder automation, including process name, object, trigger criteria, and actions performed. Given the salesforce process builder retirement date end of life 2025 2026 timeline, this audit should happen before anything else.
A helpful method is exporting process definitions via the Metadata API or a tool like Gearset, which includes automated documentation and dependency analysis for Salesforce DevOps. Gearset's comparison and deployment features are widely used specifically for migration projects like this one.
Pay special attention to:
- Processes that call Apex or invoke other automations
- Processes on high-volume objects (Leads, Cases, Opportunities)
- Orphaned processes no one remembers building
How to apply this: Build a spreadsheet with columns for owner, complexity, and last-modified date, and rank processes by business criticality. Your inventory is the foundation for every other step in the salesforce process builder retirement date end of life 2025 2026 migration plan.
Step 2: Choose Your Migration Approach
There are three realistic paths, and most organizations use a mix. The salesforce process builder retirement date end of life 2025 2026 deadline will determine how aggressive you need to be with each approach.
- Manual rebuild in Flow — best for complex logic; gives you full control and lets you improve the design.
- Automated conversion tools — tools like the open-source Process Builder to Flow Converter community utilities and Gearset's migration tooling can translate much of the logic automatically.
- Decommission — audit work often reveals processes that duplicate each other or are no longer needed; deleting them is faster than migrating them.
In one documented pattern, teams find that 20–30% of inventoried processes can simply be retired because the business process changed years ago. Verify this against your own inventory rather than assuming. With the salesforce process builder retirement date end of life 2025 2026 window closing, every process you can decommission is one less migration to manage.
How to apply this: Tag each process in your inventory as "rebuild," "convert," or "delete" before writing a single new Flow.
Step 3: Migrate, Test, and Deploy Safely
Migrating automation is change management, not copy-paste. The biggest technical risk is duplicate execution — if the new Flow and the old Process Builder both fire on the same record save, you get double emails, double field updates, or worse.
This risk only grows as the salesforce process builder retirement date end of life 2025 2026 transition period continues and more processes migrate in parallel.
Your safe sequence:
- Build the Flow in a sandbox.
- Deactivate the Process Builder version.
- Test the Flow with real-world record scenarios, including bulk loads of 200+ records.
- Deploy during a low-activity window.
- Monitor debug logs and Flow error emails for the first week.
Bulkification deserves emphasis: Process Builder handled record batches differently than Flow does, and untested migrations can hit governor limits in production. Teams that treat the salesforce process builder retirement date end of life 2025 2026 deadline seriously test bulk scenarios before every deployment.
How to apply this: Use a DevOps platform like Gearset or Salesforce's own Change Sets to move each migrated Flow through sandbox → UAT → production with rollback protection.
Step 4: Govern Against New Process Builder Debt
Migration fails permanently when new Process Builder logic keeps appearing. Enforce the end of life at the policy level. The salesforce process builder retirement date end of life 2025 2026 window is your opportunity to reset automation standards permanently.
- Document an automation standard naming Flow as the only approved declarative tool.
- Remove Process Builder access permissions for non-admin profiles.
- Add a line to your org onboarding checklist covering the salesforce process builder retirement date end of life 2025 2026 timeline so new team members inherit the standard.
- Schedule a quarterly review of
Setup → Flowsto catch unmanaged automation.
According to Salesforce's Architect guidance on automation, orgs with a single documented automation strategy resolve production incidents faster and pass security reviews more easily. The Salesforce Architects site publishes the reference frameworks worth adopting. Governance is what prevents your team from repeating the salesforce process builder retirement date end of life 2025 2026 scramble with the next legacy tool.
How to apply this: Write your one-page automation policy this week and circulate it to every user with "Customize Application" permission.
Frequently Asked Questions About salesforce process builder retirement date end of life 2025 2026
Will my existing Process Builder automations stop working in 2025?
No confirmed date exists for runtime shutdown of existing processes. Salesforce's staged retirement means running processes continue executing, but the salesforce process builder retirement date end of life 2025 2026 signals that editing and support will keep shrinking. The risk isn't sudden failure — it's owning automation you can no longer fix.
Plan migration rather than waiting for a cutoff announcement.
Can I still edit a Process Builder process if I absolutely need to?
Editability has been progressively restricted since Salesforce stopped new creation. Some legacy processes may open in view-only mode depending on your release. If editing is blocked and the fix is urgent, your realistic path is building the replacement Flow immediately and deactivating the old process — not waiting for Salesforce to restore edit rights.
The salesforce process builder retirement date end of life 2025 2026 timeline means edit restrictions will only tighten further.
What is the best tool to convert Process Builder to Flow automatically?
Gearset offers automated Process Builder-to-Flow conversion with dependency analysis, and several open-source converter utilities exist on GitHub for simpler processes. Automated tools handle criteria and immediate actions well, but scheduled actions and complex logic usually need manual rework.
Always review converted Flows against your inventory before deployment, especially as the salesforce process builder retirement date end of life 2025 2026 deadline approaches.
Do scheduled actions in Process Builder migrate to Flow?
Not automatically. Flow uses a different pattern — typically a scheduled path within a record-triggered Flow or a separate scheduled Flow with a date-based filter. This is the single most common manual rework item in conversions, so flag every scheduled action in your audit spreadsheet as high-effort.
Given the salesforce process builder retirement date end of life 2025 2026 timeline, scheduled actions should be prioritized early in your migration sprint.
What happens to Process Builder if I never migrate and ignore the deadline?
You inherit compounding risk: frozen logic, no new fixes, potential viewing restrictions in future releases, and failed audit findings. In practice, unmaintained automation eventually breaks after a Salesforce release update, and the emergency rebuild happens without documentation or testing. Migrating on your schedule is dramatically cheaper than rebuilding during an outage.
The salesforce process builder retirement date end of life 2025 2026 deadline exists to give you time to act deliberately — use it.
Conclusion
The salesforce process builder retirement date end of life 2025 2026 window is your deadline for action, not a date to memorize. Key takeaways:
- New Process Builder creation is already blocked — Flow Builder is the only supported path forward.
- Running processes still execute but receive no real support, making them latent production risks.
- A staged migration — inventory, classify, convert, test, govern — turns an emergency into routine work.
- Automated tools and a written automation standard keep Process Builder debt from returning.
Start today: export your process inventory, tag each item as rebuild, convert, or delete, and book the first sandbox migration sprint. Admins who finish this transition early will spend the next release cycle improving automation instead of firefighting it.
The salesforce process builder retirement date end of life 2025 2026 milestone is your opportunity to modernize your automation strategy for the next decade of Salesforce development.
