How to: Convert Salesforce Process Builders to Flows

Chances are you’ve heard about Salesforce retiring Workflow Rules and Process Builder:  “Starting in Summer ’23, we’re blocking the creation of Process Builder Processes. You can still activate, deactivate, and edit any existing Processes. For new automation, use Flow.”  But I’d argue it’s time to just fully audit and migrate all your Process Builders.  There are a few reasons why:

• You’ll prune out old/redundant Process Builders and catch inevitable typos.
• You’ll vastly speed up your automation.  Process Builder is the slowest of the slow, especially if it’s the same-record field updates before-save (which is probably most of your Process Builders).  Flows are ~10x faster.
• You can finally rearchitect stupid choices.
  • Here’s an example node on a Process Builder on the Contact Object:

Node: Not Primary Contact
Criteria (ALL):
1. Account.Primary_Contact__r.Id != Contact.Id
2, Primary_Contact__c = TRUE
Actions:
1. Uncheck Primary Contact – IF(Primary Contact = TRUE){ Primary Contact = FALSE }
Evaluate Next Criteria

This Process Builder was waiting for a Contact to be updated, and if the Contact.Primary_Contact__c checkbox was checked, but didn’t match the Account.Primary_Contact__c lookup on the associated Account record, it would uncheck the box on the Contact. A much cleaner way to do this would be to listen for changes to the Account.Primary_Contact__c lookup field and check/uncheck the Primary_Contact__c checkbox on the relevant Contacts when updated.

Note: there’s also the edge case to consider if a Primary Contact is re-parented to a different Account, but you’d have to decide what the correct business logic would be in that situation.

Do future you a favor