Salesforce workflow rules still run in a lot of orgs, but they are now a retired tool. New workflow rules could not be created from Winter '23, and Salesforce ended support for workflow rules and Process Builder on 31 December 2025. Existing rules may keep firing, but they get no fixes and no new features. Every new automation capability lands in Flow.
This is a practical guide to what that means for an admin or developer who still has workflow rules in production.
Workflow types in Salesforce, and where each one lives now
| Old tool | What it did | Where that job lives now |
|---|---|---|
| Workflow rule | Field updates, email alerts, tasks, outbound messages on one object | Record-triggered flow |
| Process Builder | Multi-step logic, related record updates, invoking Apex | Record-triggered flow |
| Approval process | Multi-step approvals | Still supported, can be launched from Flow |
| Time-dependent workflow action | Actions X days before or after a date | Scheduled path on a record-triggered flow |
| Outbound message | SOAP call on record change | Still available as a Flow action |
Flow vs workflow rules: what you gain
Before-save updates. A record-triggered flow set to "Fast Field Updates" runs before the record is saved, which is much faster than a workflow field update and does not trigger another save cycle.
Related records. Workflow rules could only update the record itself or its master in a master-detail relationship. Flow can create, update and delete any related records.
One place for logic. Flow can call Apex, subflows and external services, so logic that used to be split across workflow rules, Process Builder and triggers can sit in one ordered set of flows per object.
A real example, rebuilt
The classic rule: when an Opportunity is Closed Won, stamp a date field, email the account owner, and create a follow-up task 30 days later.
- Setup, Flows, New Flow, Record-Triggered Flow.
- Object: Opportunity. Trigger: created or updated. Entry condition:
StageNameequals Closed Won, run only when the record is updated to meet the condition. - Before-save path (Fast Field Updates): an Update Triggering Record element that sets
Won_Date__cto{!$Flow.CurrentDate}. - After-save flow (a second flow, or the same flow set to "Actions and Related Records"): a Send Email action or your existing email alert.
- Add a Scheduled Path 30 days after Close Date with a Create Records element for the Task.
- Debug, test in a sandbox, activate, then deactivate the old workflow rule.
Migrating without breaking things
- Run the Migrate to Flow tool in Setup for simple rules. It handles field updates and email alerts well. Review everything it generates.
- Inventory first. List every active workflow rule and Process Builder per object, because two tools firing on the same object make migration order matter.
- Consolidate per object. Aim for one before-save and one after-save flow per object where you can, and use Flow Trigger Explorer to check order.
- Test with realistic data volumes. Bulk updates through Data Loader are where badly built flows hit limits.
- Deactivate the old rule the same day the flow goes live, or both will run and you will get double emails and double tasks.
The full version of this guide, with more automation examples for Sales Cloud, is on our blog.
Top comments (0)