Case study

A document migration checked record by record

Documents had to be moved between student records before a fixed date, after which the originals would be gone. A common plan is to migrate, check a sample and fix complaints as they arrive. This one was verified record by record first.

Consulting engagement about 2 min read

The situation

Document records are easy to underestimate. Each one ties a file to a student, a type, a status and a date, and each of those links has to survive the move. A missing transcript or a document attached to the wrong student is found at the worst possible moment, usually by the student.

Here the documents had to be moved from one set of student records to another ahead of a cleanup that would remove the originals. There was a deadline, and no second chance once it passed.

What I did

  • Migrated the full set, not a pilot. Every document record in scope, through the student system’s supported interfaces, in test first and with a check-only run before the live one.
  • Verified every record. Each migrated record was compared with its source before sign-off. Not a sample. All of them.

Safeguards

The migration was rehearsed before the production run. The verification was a separate step from the migration, with its own record of what it compared and what it found.

The result

The production migration was delivered on deadline with zero defects, and the client signed off on a record-by-record verification instead of a sample.

What I would tell another school

“We checked a sample” means “we do not know about the rest.” If the tooling can compare a hundred records it can compare all of them. Insist that it does.

Printed from https://www.datazak.com/work/document-migration-verified/. An address in parentheses after a link that begins with a slash is a page on https://www.datazak.com.

More work

Full-time architect role

A financial aid migration you can run twice

A check-only report is read and approved first; then one command corrects financial aid records for a whole student population, can be run again safely, and leaves before-and-after evidence for every student.

Full-time architect role

Two AI agents and one audit trail

A second AI agent independently re-checks AI-assisted migration work against the source systems and writes the audit trail, in place of spot checks by hand.

Consulting engagement

The race that emailed students an empty link

A timed job sometimes lost a race with the email scheduler, so students got an invitation with no link. Now the link is saved as soon as the record is.

Have a system that needs untangling?

Tell me what you run and where it hurts. The first call is 30 minutes, free, and you will leave with a clear next step whether or not we work together.

Search this site

Up and Down move, Enter opens the result, Esc closes.