Feature Retirement: Process Builder + Workflow Rules — Hello Flow!

This has been in the works for a while, and it was made official at Dreamforce this year — Process Builder and Workflow Rules are being retired and the focus moving forward will be the ever-expanding power and feature-set of Flow..

This has been in the works for a while, and it was made official at Dreamforce this year — Process Builder and Workflow Rules are being retired and the focus moving forward will be the ever-expanding power and feature-set of Flow. We talked about Salesforce Flow when it made it’s debut, and there were rumblings, even then, that it looked to be gearing itself up to be Salesforce’s flagship tool for automation, and now we have a timeline for the transition. Today, we’ll quickly run through what to expect and when to expect it!

Deprecation Timeline  

Like all much-used features facing retirement, Salesforce is giving admins, users, and orgs plenty of time to prep their migration plan. The deprecation will be rolled out over the course of 3 releases, along with tools to help orgs migrate their existing processes into Flow: Spring 22: Will introduce a migration tool for Workflow Rules. Summer 22: Will introduce a migration tool for Process Builder. Winter 23: Will mark the official retirement/deprecation and you’ll no longer be able to create new Workflow Rules or Process Builders from there on out.

So, about a year from today, we’ll all be using Flow when it’s time to build a new in-org automation and, in the interim, there’ll be plenty of opportunity to transition your existing processes over as well.

What Will Happen to My Existing Process Builders and Workflow Rules?  

Besides delivering tools to make migration easy, there’s also explicit indication from Salesforce that existing PBs and WRs will be deactivated. In all likelihood they’ll go the way of S-controls and, while you won’t be able to create new ones, you’ll still be able to tweak your pre-existing programs. But, while it may be tempting to take the “if it aint broke don’t fix it” approach, the added functionality of Flow, it’s continued support and updates with releases, and the fact that retired features make it harder to find qualified staff to work on them, should be all the incentive you need to start planning an effective transition.

Until then, keep working hard, smart, and happy. And we’ll see you in the cloud.