Consolidating two Salesforce orgs into one instance without stopping the business

The problem

The play

1. 1
   Rationalize fields before migrating anything

   Assessed roughly 2,900 fields against a 5 percent fill-rate cutoff. About 1,700 carried over; the rest were retired rather than dragged into the new org, so the merge shed schema debt instead of doubling it.

2. 2
   Data migration and collision handling

   Consolidated into a single instance holding roughly 50k accounts and 90k contacts, about 48k accounts and 73k contacts migrated in, the balance native to the surviving org, with roughly 1,050 colliding accounts deduped as part of the load rather than left for later.

3. 3
   Metadata, access and record-type remap

   Remapped users, roles, profiles, page layouts and record types (a legacy type, a combined new-business-and-expansion type, and a renewal type), and added Google SSO so access consolidated alongside the data.

4. 4
   Automation modernization, not lift-and-shift

   Inventoried roughly 60 Process Builder and Flow automations across both orgs. About 30 were slated to migrate and 11 required a full Process Builder to Flow rebuild, identified up front so the effort was scoped rather than discovered mid-cutover.

5. 5
   Cutover sequencing around the business

   Sequenced cutover steps after hours to protect live selling and the weekly board-reporting window.

What it moved

From a LeanScale case studyRead the full case study →