What You Need to Know and Do Now
Salesforce is officially moving away from two of its long-standing automation tools—Workflow Rules and Process Builder—in favor of the more powerful and future-ready Salesforce Flow. This change is a strategic evolution in how automation is delivered within the Salesforce platform.
Workflow Rules & Process Builder End of Support
Why the Change? Introducing Salesforce Flow
Salesforce Flow is the next-generation automation solution that unifies and replaces both Workflow Rules and Process Builder. It offers a more powerful, flexible, and scalable way to build and manage automations—from simple field updates to multi-step logic, screen flows, and integrations.
Flow supports:
- Visual automation via drag-and-drop configuration.
- Fine-grained control over logic and execution order.
- Better performance and error handling.
- Reusability and modular design for complex business processes.
Salesforce’s goal is to consolidate automation capabilities into a single tool that better supports the scale and complexity of modern business needs—making Flow the strategic platform for automation moving forward.
What’s the Timeline?
- Winter ’23 Release: As of 2023 you have not been able to create new Workflow Rules or Process Builder automations. These tools are now legacy. The new Salesforce Flow feature may already be familiar to you.
- By December 31, 2025: Salesforce will end support for Workflow Rules and Process Builder. While Salesforce has not committed to a “hard shutoff” date, any workflows or processes still running after this point will do so at your own risk. No support, bug fixes, or compatibility assurances will be provided.
What If You Don’t Migrate?
If you aren't able to prioritize a Salesforce Flow migration in the near term, you're increasing the risk of your automation continuing to work flawlessly. Here’s why that’s a problem:
- No Support for Fixes: Any issues or failures in your Workflow Rules or Process Builder automations will not be supported by Salesforce. You won’t be able to modify or update them using the old tools. You'll have to make an "emergency migration" as a workaround to quickly address any issues.
- Emergency Migrations Are Risky: If a critical business process fails unexpectedly, you’ll be forced to rebuild the solution urgently in Flow—with no time to plan, test, or validate.
- Higher Risk of Errors: Rushed, last-minute migrations often result in partial, fragile, or error-prone solutions that can disrupt operations.
- Loss of Operational Continuity: Any delay in re-establishing automations could lead to missed notifications, delayed approvals, or incomplete data updates.
In short, waiting until something breaks could cost you more than the time you save by deferring the migration.
Your Action Plan: What You Should Do Now
- Audit Your Existing Automations
Inventory all Workflow Rules and Process Builder logic still active in your system.
- Login to Salesforce and go to Setup
- In the Quick Find box at the top of the left navigation, type in “Process Builder”
- Similarly, search for “Workflow Rules”
- Prioritize Based on Business Impact
Migrate mission-critical processes first, especially those that support revenue or compliance. - Use Salesforce’s “Migrate to Flow” Tools
Salesforce provides utilities that help automate parts of the migration process.
Official Guide from Salesforce Admins - Build Your Flow Expertise
Enroll your team in Flow training to ensure future automation work is scalable and efficient.
Flow Basics Trailhead Module - Test in Sandbox Before Deploying
Ensure every Flow is carefully tested to replicate existing business logic accurately before it goes live.
We're Here to Help
Migrating to Flow doesn’t have to be disruptive. We help organizations assess, plan, and execute Flow migrations that preserve existing functionality and unlock new capabilities.
If you need support developing a roadmap or executing a phased transition, let’s talk.