Automation Estate Migration: Process Builder to Flow

Salesforce's deprecation of Workflow Rules and Process Builder wasn't a surprise, but for large orgs with years of accumulated automation, "migrate before the deadline" is easier said than documented. Pushpay had an estate of dozens to hundreds of automations spanning multiple teams — most of them undocumented.

The Challenge

The problem wasn't the migration itself — it was that no one had written down what the existing automations were supposed to do. Rules written years earlier by people who'd since left the company contained embedded business logic that existed nowhere else. Migrating them without understanding them meant risking silent changes to processes that teams depended on daily.

The Approach

I partnered with RevOps and Sales to document the existing automation logic before touching anything. That process surfaced business rules that had never been written down — edge cases, exception handling, and sequencing dependencies that only became visible when someone had to articulate them in plain language.

With the logic documented, I rebuilt each automation in Flow — maintaining functional equivalence where the original logic was sound, and flagging and correcting cases where it wasn't. The documentation artifact became the migration checklist and the ongoing operational reference.

Outcome

The automation estate was migrated ahead of the deprecation timeline. Undocumented business rules were captured in writing for the first time. The documentation produced in the process had value well beyond the migration — for the first time, the team had a readable record of what each automation did and why.