Salesforce ended support for Workflow Rules and Process Builder on December 31, 2025. Existing automation still runs, but bugs will not be fixed and support will not help. How to inventory, migrate with the Migrate to Flow tool, and consolidate overlapping automation as you go.
Since December 31, 2025, Salesforce no longer supports Workflow Rules or Process Builder. Active automation keeps running exactly as before. What changed is that there are no bug fixes and no customer support for it, so any problem in those automations is now yours alone. Flow Builder is the supported replacement.
Book a free 30-minute call. You'll leave knowing what we'd do first and roughly what it costs, whether or not you hire us.
List every active Workflow Rule and Process Builder process per object, with what it does and when it fires.
Look for overlap. Orgs that grew over years often have a workflow rule, a process and a trigger all updating the same field. Decide the intended behavior before migrating any of it.
Use Salesforce's Migrate to Flow tool for straightforward cases, in a sandbox first.
Consolidate into one record-triggered flow per object and timing where possible, and set the order explicitly.
Test with realistic data volumes; flows that run per record can hit limits that the old automation avoided.
Deactivate the old automation only after the flow is proven, and keep it for rollback for a release cycle.
Once a month: what changed in tech that month and what it means for you, from cloud and AI to security and the tools you build with. Every item links to its source. No sales pitch, unsubscribe in one click.
Book a free 30-minute call about it. Bring your setup and your bill; you'll leave knowing what we'd do first and roughly what it costs, whether or not you hire us.
Or keep reading
Dynamics CRM On-Premises Is Ending: Dynamics 365 Online, Salesforce, HubSpot or Something Custom
Dynamics CRM 2016 reached end of support on January 13, 2026, and on-premises Dynamics 365 Customer Engagement 9.x leaves mainstream support on January 12, 2027. How to choose the next CRM, and why the plugins, integrations and reports built around the old one decide the timeline.
Read
Replacing Salesforce or HubSpot: A Self-Hosted CRM (Twenty) or One You Build
A CRM is contacts, companies, deals, activities and a pipeline view. At $90–$195 per seat per month, ten seats cost $11k–$23k a year. Twenty is an open-source CRM you can run yourself; building on Postgres is the other route. What each option costs, what you lose, and how to migrate without losing history.
Read
As of October 25, 2026. Provided as is, for general information, and accurate to the best of our knowledge on the date shown. Not legal, compliance, tax, financial or other professional advice. Prices, limits and vendor services change; check current vendor documentation before relying on anything here. Terms of use.