Skip to content

Resource · migration

Plan a controlled move from spreadsheets.

Map fields and owners, clean records, run a small pilot and reconcile the result before a wider cutover.

Spectra guide · Source review: 3 November 2026

Use the working documents

Start blank, or inspect the clearly labelled fictional example.

Download editable CSVOpen printable A4 sheetOpen fictional completed exampleDownload fictional example CSV

At a glance

Migration changes ownership and working habits as well as fields. Inventory the real sources, preserve ambiguity, decide permissions and retention, and reconcile a bounded pilot before a wider cutover.

01 / Map

Find the work between the cells.

List every spreadsheet, inbox, shared folder and personal workaround. For each field, identify its owner, source, update trigger, readers and downstream hand-off.

02 / Clean

Make a decision for duplicates and unclear status.

Do not convert an ambiguous historic status into a false approval. Record what is retained as reference, merged, corrected, excluded or escalated—and who authorised that treatment.

03 / Pilot

Reconcile before expanding.

Agree pilot population, acceptance checks, permissions, communication, support and rollback before moving real data. Compare counts and critical fields, test exports and retain the evidence for the go/no-go decision.

A pilot that cannot name its population, its acceptance checks and its rollback action is not a pilot. Stop and write those three decisions on the blank kit before moving records. This website does not perform the migration.

Bring the job. Explore the next step.

Discuss your workflow