Salesforce Migration
Legacy CRM moves, multi-org consolidation and sandbox-to-production cutovers — mapped, de-duplicated and reconciled against the source before anybody switches over.
01
The problem
Why people call us about this.
A
Two orgs after an acquisition and two versions of the same customer.
B
A legacy CRM nobody wants to pay for and nobody dares turn off.
C
A previous migration left duplicates you are still cleaning up.
02
What’s covered
The Salesforce we actually configure.
Migrations are judged on the day after. Every load below is rehearsed twice against production volumes, with a variance report you sign before the real one runs.
03
How it runs
Five phases, and what you see at the end of each.
01 · Week 1
Inventory
What exists, who owns it, and which system is really the source of truth. Almost always surfaces something nobody knew was live.
A written map
02 · Weeks 2–3
Contract
The design in writing, with each decision and its reversal cost named. This is where we argue with the brief — before money is spent.
A signed scope
03 · Middle
Build
Built against the contract and reviewed against it. You see working software every two weeks, in your own sandbox.
Fortnightly demos
04 · Late
Prove
Volume testing at twice expected load, deliberate failure injection, and a replay run with your team watching.
A test evidence pack
05 · Final week
Hand over
Runbook, monitoring, escalation path and a named owner on your side — then a month watching it together before we step back.
Runbook and owner
04
First call
Thirty minutes. Three answers.
You speak to a certified architect, not a sales engineer. No deck, no discovery fee, and no obligation to go further — you leave the call with three things whether you hire us or not.
Whether this is even the right line
About a third of the time it is not, and we say so. Usually the ask is custom development when the real problem sits in the data model underneath.
A shape and a range
Roughly how long, roughly how many people, and the band it falls in. The firm number follows discovery about two weeks later, and it holds.
The two risks we would flag
The things most likely to blow the timeline on a project like yours — named on the call, before anyone has signed anything.
Book it for this week.
Pick a slot directly in the calendar — most questions get answered inside the thirty minutes.
05
FAQ
Asked on nearly every call.
How do you avoid duplicates?
External IDs and a defined upsert strategy, matching rules designed from your real data, and two full dry runs with a variance report you sign off before the production load runs.
Do we move all the history?
Usually not all of it. Open records and recent history move; deep archives are often better in cheaper storage. It is a cost decision we put in front of you rather than make quietly.
What if the cutover goes wrong?
There is a tested rollback rather than a paragraph promising one exists. We rehearse it during the second dry run, with your team watching.
Can you consolidate two orgs after an acquisition?
Yes, and it is a large share of this work. The hard part is never technical — it is agreeing whose process wins, and we will push you to decide that early.
Other lines