One price, agreed before we start
A migration is a project, not a subscription. You get a fixed price for the engagement after scoping, with the exclusions already identified — so the number does not move once work begins.
What moves the price
Three things, in roughly this order of impact. Everything else is noise by comparison.
- 01
How much there is
Record count is the headline number, but it is not linear — the tenth thousand costs far less than the first. Volume mostly sets how long loading runs, not how much work goes into it.
- 02
How the source behaves
A platform that gives us reliable access to everything is a fraction of the cost of one that requires an export, hands over files in awkward formats, or withholds part of the history. This is usually the biggest single factor.
- 03
How much has to be decided
Straight migrations are cheaper than consolidations. Merging two organizations means adjudicating duplicates and reconciling setups that have diverged — work that needs your people as much as ours.
Included in every engagement
These are not upsells. A migration without them is not a migration we would put our name to.
Scoping, before you commit
The record census, the predicted exclusion list, and a timeline — produced before you sign anything, and yours to keep either way.
A test migration you review
Real records in your real destination, inspected by your team, before anything runs at volume.
The reconciliation report
A line per source record: where it landed, what state it reached, and the reason if it did not. This is the deliverable, not a byproduct.
Remediation of held records
Where something can be fixed and re-migrated, we do it as part of the engagement rather than as a change request.
What we don’t do
There is no self-serve tier. Handing you a tool and a login would transfer the risk you are paying to avoid, and the failure modes here are not ones you find out about in time to fix.
We also do not price per record and then discover the work afterwards. The scope is agreed first, which occasionally means telling you a migration is not worth doing — that conversation is cheaper for both of us before a contract than after one.
Get a number for your migration.
Four questions, one business day, and a scope with a price and a timeline attached. No obligation to go ahead.