Salesforce Will End Support for Workflow Rules and Process Builder—Here’s What Clients Need to Do Now
- Caitlin Stevens
- Sep 17, 2025
- 2 min read
Salesforce is officially ending support for Workflow Rules and Process Builder on December 31, 2025. This means admins, partners, and customers must migrate their automation to Flow to avoid unsupported business processes, reliability issues, and missed platform features. Here’s what this transition means—and a checklist Petite Cloud Solutions clients (and all Salesforce orgs) should follow to stay ahead.
Why Is This Change Happening?
Salesforce is consolidating all declarative automation* into Flow, a single unified platform that is more scalable, secure, and future-ready than Workflow Rules or Process Builder. Automation in Flow benefits from:
Enhanced flexibility for complex business logic
Easier maintenance and troubleshooting
Ongoing investments and new features, unlike legacy automation tools
*Declarative Automation: Using point-and-click rather than writing code.
What Will Happen After 2025?
No customer support or bug fixes for Workflow Rules or Process Builder after December 31, 2025.
Existing automations may keep working for a time but will gradually become less reliable as new Salesforce features ship exclusively for Flow.
Creating new Workflow Rules and Process Builders is already disabled, and their continued use puts businesses at platform risk.
How to Prepare: The Migration Checklist
1. Audit Existing Automation
Identify all active Workflow Rules and Process Builders in Setup > Process Automation.
Make a list by object, priority, and business impact for all automations to migrate.
2. Use Official Tools to Migrate
Use the Migrate to Flow tool to convert your rules/processes—start with high-value or frequently used automations.
Not every process will be migrated perfectly; expect some manual tweaks, especially with complex logic.
3. Optimize and Modernize
Review whether each automation is still needed or can be improved as part of the migration.
Streamline where possible—moving “as is” isn’t always best.
4. Test Thoroughly
Test all new Flows in a sandbox to catch errors or business interruptions before going live.
5. Get Help as Needed
Train your team on Flow or partner with Petite Cloud Solutions to ensure a smooth transition and take full advantage of the modern toolset.
6. Check for Managed Packages
Automations in managed packages must be updated by the vendor; coordinate with ISVs as needed.
Final Tips
Don’t delay—migration projects can take months, especially for larger orgs or those with undocumented logic.
Migration is not just a technical task. It’s an opportunity to clean up your automation landscape, eliminate redundancies, and ensure your Salesforce investment stays resilient and scalable.
Start conversations with stakeholders now about priorities and business-critical processes, so the migration goes smoothly.
Contact Petite Cloud Solutions if you need expert guidance in auditing, migrating, and optimizing your automation for this major Salesforce platform evolution.
The end of support is coming for Workflow Rules and Process Builder. Get ahead—migrate to Flow and make your Salesforce automation ready for the future.
Comments