Workflow Rules and Process Builder end of support: what it means for your org

What end of support means

It's not a retirement. Your automations keep running just as before. Here's what changes:

• Salesforce won't fix bugs that show up in them.
• Support won't take cases about them.
• You can't create new rules or processes. Everything new goes in Flow.

The risk is silent. A release changes something, a rule stops behaving the same way, and you find out when an order doesn't reach the ERP or an alert doesn't go out.

How to find out how many you have

In Setup, search for Workflow Rules and Process Builder. If you'd rather have a complete list, these two queries give it to you in seconds. The first one runs against the Tooling API: in the Developer Console, check Use Tooling API.

SELECT Id, Name, TableEnumOrId
FROM WorkflowRule

SELECT ApiName, Label, LastModifiedDate
FROM FlowDefinitionView
WHERE ProcessType = 'Workflow' AND IsActive = true

In the second one, ProcessType = 'Workflow' is how Salesforce internally identifies Process Builder processes.

Three ways forward

1. Migrate to Flow

Salesforce has a tool, Migrate to Flow, that converts simple rules into Flows. It works well with field updates and simple email alerts. With scheduled actions, complex criteria or processes that call other processes, review the result by hand.

2. Rebuild it in Flow by hand

This is the option for logic that has grown over the years. Use it to consolidate into a single Flow per object what's currently spread across rules, processes and triggers, and to review the order of execution.

3. Rebuild it outside Salesforce

If you're thinking about leaving Salesforce, it makes no sense to pay twice: first to move everything to Flow, then to rebuild it in the new CRM. Inventory the logic, decide what's still alive and build it once, where it's going to live.

What usually breaks in a migration

• Scheduled actions: the ones already in the queue don't migrate on their own.
• Field updates that re-trigger rules: the order of execution changes with Flow.
• Outbound Messages: they can be sent from Flow, but you have to set them up again.
• Processes that call other processes: they're hard to debug and often hide duplicate logic.

Before you migrate, count

Many orgs discover during this review that some of their automations no longer do anything useful: alerts to people who have left, fields nobody looks at, rules for a process that changed years ago. Counting before you migrate saves work. And it's a good time to ask how much of your org is still in use.

Sources: end of support for Workflow Rules and Process Builder (Salesforce Ben), Tooling API guide (Salesforce Developers).