SpectraResource · migration
Move the job trail out of the spreadsheet maze.
Map ownership, clean deliberately, pilot a bounded record and keep a rehearsed rollback.
Published by Spectra · no named expert reviewer is claimed · last reviewed 17 September 2026 · operational guidance, not technical, legal or safety certification.
The practical answer
Migration is a change to ownership and habits as well as fields. A pilot makes unknowns visible; it does not make historic data clean, prove a service commitment or remove the need for permission and retention decisions.
Map
Find the work hidden between the cells.
List each spreadsheet, inbox, shared folder and personal workaround. For every field, identify owner, source, update trigger, readers and downstream hand-off before deciding what moves.
- Source and field owner
- New controlled field/state
- Cleaning or duplicate decision
- Permission and retention decision
- Validation and rollback owner
Worked sample
Map a fictional three-site rollout with an explicit duplicate.
Synthetic sample: MSR-031 appears in a sales sheet and an installation tracker. The mapping sheet keeps one new job reference, treats the duplicate contact as a review decision, and preserves ambiguous historic status as reference rather than converting it into a false ‘approved’ state.
Cut over
Reconcile before expanding.
Agree pilot acceptance, error handling, permissions, retention, communication and rollback before a wider cutover. A migration worksheet cannot determine legal duties or authorise access to personal or customer data.
A sample, not a promise