Why this problem happens
The spreadsheet fails gradually: a column gains several meanings, files move to another tool, people keep private copies, and status depends on whoever last remembered to edit the row.
- Only one person understands the spreadsheet logic.
- Rows do not store files, messages, and stage history cleanly.
- Multiple versions create conflicting case status.
- Invoices, delivery, and remakes are tracked in separate files.
A practical operating fix
Replace the operating habit before replacing the archive. Map only the fields and active cases the team still needs, then choose a firm point after which new work enters the shared system.
- 1 Identify the fields your spreadsheet is trying to manage.
- 2 Move active cases into structured case records.
- 3 Use stage status, due dates, and owners instead of free-text notes.
- 4 Stop adding new work to the spreadsheet after the team is trained.
Migration field map
Decide where each spreadsheet column belongs before moving data
A clean migration does not reproduce every old column. It separates case identity, changing workflow state, supporting evidence, and commercial follow-up into records the team can maintain.
| Spreadsheet content | Structured destination | Migration decision |
|---|---|---|
| Case, dentist, patient reference, requested work | Case identity and intake fields | Keep when needed to identify and produce current work |
| Due date, stage, owner, hold reason | Live workflow fields | Standardize values before import or manual setup |
| File paths, email notes, scan links, photos | Case attachments and notes | Move current evidence; do not import broken references |
| Delivered, invoice, paid, balance | Delivery and commercial status | Reconcile open balances and avoid duplicating settled history |
Retain historical records according to the lab’s legal, accounting, contractual, and clinical-documentation obligations; this guide does not define a retention period.
Best practices
Start with active work only.
Keep status names simple.
Archive old spreadsheet data instead of importing clutter.
Use the first week to refine required intake fields.