I slot into your implementation as the migration lead, under your SOW or mine, and hand your client a clean, reconciled org on go-live day while your consultants stay on the build. Twenty years in the ecosystem, 8x certified, 100+ migrations, and I teach this to 35,000 people on YouTube, so your client gets the specialist, not the bench.
The build finishes on schedule. Then the client’s data shows up: three systems, no households, ten years of notes, and a go-live date nobody wants to move. The migration becomes the critical path, and your PM becomes the migration lead by default.
Data is where implementations slip. A dedicated lead with a repeatable process keeps the data workstream off the critical path, and keeps your go-live date where you put it.
Hourly migration work done by consultants who’d rather be building eats the project margin. I scope it, fix the price where the source data supports it, and finish it.
The client remembers go-live day: whether they found their clients, or a pile of orphaned contacts. That memory is attached to your firm’s name, not the data.
Under your SOW, as part of your team: source analysis, mapping, transformation, load, validation, cutover. Your PM gets status; your client gets a clean org.
When the client wants to contract for the data separately, I run under my own SOW and coordinate with your team. Same handoffs, same deliverables, one less line on your proposal.
The load failed, the counts don’t reconcile, or the household model never got decided. I come in, diagnose it in a week, and finish it.
Thirty minutes with the prospect’s export and I’ll tell you what’s really in it, so your proposal prices the migration it’s actually going to take.
All of it runs through the same seven-step method, in the same order, on every engagement — so your PM can see the whole sequence up front and slot it into the project plan. See the full methodology, step by step →
Most of my partner work is FSC for RIAs and wealth advisories: Redtail and Wealthbox sources, households, financial accounts, relationship groups. I also migrate Sales Cloud and Service Cloud orgs, org-to-org consolidations, and legacy databases into whatever your team is building.
An Inc. 5000 Salesforce consultancy brought me in to own the data side of a client implementation: legacy records mapped, cleaned and loaded while their team stayed focused on the build.
Every acquired practice lands in the same FSC data model on a predictable timeline. The same playbook a partner’s client gets.
A repeatable migration intake process for each acquired practice, privacy preserved between offices, no duplicate records created against custodial data feeds.
“Data migration is the scariest part of the project for everyone in the room. It’s my favorite part.”
Elise Pottinger, SMC Migrations
Thirty minutes is enough to tell you what the client’s data will and won’t do, and roughly what it’ll take to land it cleanly in the org your team is building.
