Method
Verified migration: your history arrives complete, and we prove it
Verified migration is our method for moving information from an old system to a new one without losing records. We read the full dump of the previous system, run a process that can be repeated, reconcile table by table and file by file against the source, and the old system is switched off only when the numbers match.
Why does data get lost in a migration?
Rarely through one big mistake. It gets lost at the edges:
- The work is done on a sample or a partial export, not on the full dump.
- Attachments (photos, PDFs, lab results) are left behind because they live outside the database.
- A field the old system used differently from what its name says is copied literally.
- Nobody cross-checks the counts at the end, so what's missing never shows up.
How we do it, step by step
- Full dump. We work on the complete copy of the previous system, not on a sample or on what a report exports.
- The people who used the system describe it first. Before reading a single table, the people who ran the old system tell us how they used it. That's where the fields that mean something else turn up.
- A process that can be repeated. The migration is a program that runs as many times as needed and always gives the same result, not a one-off manual task.
- Reconciliation against the source. We count records table by table in the source and in the destination. Files are compared by their content fingerprint, so a repeated attachment isn't counted twice and a missing one shows up.
- Corrections that can be undone. Every correction is applied after saving how the data looked before the change.
- Running side by side, then the cutover. The new system runs alongside the old one while the migration is checked, and the old one is switched off only when the numbers match.
In numbers: FUNCUAN
FUNCUAN runs Barranquilla's animal welfare program: a high-volume veterinary clinical operation. We migrated its complete legacy system:
Frequently asked questions
What happens to attachments: photos, PDFs, X-rays?
They are migrated with the records they belong to and counted separately. At FUNCUAN that was more than 500,000 files, compared by their content fingerprint.
Do we have to switch the old system off on day one?
No. The new system runs alongside the old one while the migration is checked. The old one is switched off when the numbers match, not before.
What if the old system has no documentation?
That's normal. That's why we start with the people who used it and with the full dump: we rebuild the documentation ourselves.
What if something doesn't match?
It gets fixed in the process and the process runs again, until the counts match the source. Until they do, the old system stays on.
Do you have years of history in a system nobody maintains?
Tell us which system it is and how many years of data it holds. In 30 minutes we'll tell you what the migration would look like.