Salesforce has ended support for Workflow Rules and Process Builder and directs the logic to Flow. Announcement day broke nothing — every process kept running — and that is exactly why estates still carry them years later. Retired-engine automation is migration work with a deadline attached, wearing the costume of a system that works fine.
What actually bites, and when
Three things. Support: when behavior goes wrong in a retired engine, there is no fix coming. Composition: new capability — including Agentforce actions — composes with Flow, so logic stranded in old engines becomes invisible to what you build next. And people: fewer admins each year can debug a Process Builder chain confidently.
Migrate per object, not per process
The subtle failure mode: migrating processes one at a time changes the execution order between the ones that shared an object’s save cycle. Workflow rules and processes on one object participate in that object’s order; moving them as a set into one record-triggered Flow preserves it, moving them piecemeal silently reshuffles it. Group the work by object, and check first whether each rule still does anything — a rule inert for years is a delete, not a migration, and that is the cheapest outcome available.
Horus Eye files retired-engine findings one per object for exactly this reason — and excludes managed-package rules from the count, because the vendor migrates those, not you.
