Five questions to ask any migration team
Put these to whoever touches your data — the new software's migration team, an IT shop, a freelancer, or us. They're neutral buying criteria: any competent team can answer all five in writing. Print it and keep it by the phone.
Will you give me a written list of what does not come across?
Every migration carries some things and drops others. A team that knows its coverage can put the exclusions in writing before work starts. If the answer is vague, the gaps will be discovered after your old system is gone.
Do I get source-vs-extracted record counts for every record type?
Not a summary — a per-type reconciliation: patients or matters, appointments, documents, ledger entries, each counted in the old system and counted again in what was extracted, with every variance explained.
Who holds my original data, and until when?
The safe answer: you do, untouched, until you've signed off on the results. Be wary of any process that requires surrendering your only copy.
What happens to working copies when the project ends?
There should be a retention schedule and a certificate of destruction — not a shrug. Your practice's records shouldn't live on indefinitely on someone's project drive.
Is the price fixed before work begins — and what changes it?
An hourly estimate against a shutdown deadline transfers all the risk to you. A fixed price with a written change-control rule (nothing changes without your signature) transfers it back.
Our answers to all five live in the sample validation report and on how it works — in writing, which is the point.
Want the five answers in writing, about your system?
Book a 30-minute rescue call or send details firstThe call, the scoping, and the quote are free. So are the export guides — even if you do it yourself.