Spreadsheet to System Migration Plan
Most businesses do not run on one spreadsheet. They run on several, owned by different people, each partially correct, and none consulted at the moment a decision is made. This plan sequences the move so the highest-risk records go first and the project produces a visible result before anyone loses patience.
Migrations rarely fail on technology. They fail because the sequence was wrong, because incomplete historical records stalled the project, or because the old spreadsheet was left available as a fallback and never actually died. This plan is ordered by risk rather than by convenience. The registers that carry audit exposure move first, because they are also the smallest datasets and the fastest way to show the change was worth making. It is written for a service or contracting business of any size, and applies whichever platform you have chosen.
What it covers
- Stage one — people and their qualifications, licences and renewal dates. Highest audit exposure, smallest dataset, fastest visible win.
- Stage two — equipment, its calibration or service intervals, and the certificates behind them.
- Stage three — clients, sites and assets. The structure everything else attaches to.
- Stage four — jobs, work orders and scheduling, once the qualification and calibration checks above are enforceable.
- Stage five — costing, which depends on jobs existing first.
- Stage six — historical records, selectively and possibly never in full. Migrate what is still doing work.
- Gap register — every record that cannot be reconstructed, with a documented decision about how it is treated.
- Parallel period — one cycle only, with a fixed date on which the old system is switched off.
- Baseline measurement — taken before anything moves, because nobody remembers it accurately afterwards.
- Named internal owner — with authority to decide about incomplete records. This cannot be outsourced to the vendor.
- Field adoption plan — tested with the least enthusiastic user, not the most.
- Go-live criteria — written down in advance and checked, rather than declared.
How to use it
Start with the gap register, not the data: Export what you have and reconcile it against what you are obliged to hold. Most businesses find a share of records incomplete at this step — and that finding is itself the most valuable output of the whole exercise, whether or not you go ahead.
Do not wait for perfect data: The gaps exist whether or not you migrate; migration is simply what makes them visible. Load what is verifiable, record what is not, and make a documented decision about each category. A documented baseline is defensible in an audit. A silent gap is not.
Pilot with your hardest client: Not your easiest. The demanding client is the case the system has to survive, and finding out in a pilot is far cheaper than finding out in production.
Set the switch-off date at the start: Projects that leave the old spreadsheet available as an optional fallback never finish. Put the date in writing before stage one begins.
Frequently Asked Questions
Why migrate qualifications before financial data?
Because that is where the risk is, and because it is the fastest thing to show value on. A lapsed qualification discovered by a client costs a mobilisation and damages an approval; a late report costs annoyance. The qualification register is also usually the smallest dataset in the business, so it delivers a visible result within weeks instead of months — which is what keeps a project funded.
What do we do about records we simply cannot reconstruct?
Record the gap explicitly, make a documented decision about how that category is treated going forward, and date it. Auditors accept a documented baseline decision. What they do not accept is a register that silently implies completeness it does not have — and that is exactly what you create by quietly loading partial data and saying nothing.
Should we migrate historical job records?
Decide by whether the data is still doing work rather than by completeness for its own sake. Records feeding an active calculation — thickness readings driving a corrosion rate, qualifications supporting a current certification — must move. Closed jobs from years ago can stay archived in place with an index entry. Migrating everything is a common way to double a timeline for no operational benefit.
Can this be done without a full-time internal owner?
Realistically no. Someone internal has to decide about incomplete records, interpret your own procedures, and settle what the client reporting formats actually need. Those decisions cannot be outsourced. It does not need to be a full-time role, but it needs a named person with the authority to decide, or the project stalls at the first ambiguous record.
See it running on your own workflow
Thirty minutes, your job types and your reporting formats, co-presented by an ASNT NDT Level III. Affordable, accessible, fully customizable — request a demo and a tailored quote.
Related: Replacing spreadsheets — the full guide · Inspection management software · Business management platform · All free resources