Spreadsheet-to-workflow mapping
A fictional pilot mapping for a four-site rollout. It demonstrates field ownership and cutover controls, not an automated migration or product capability.
Scenario MS-031 · Juniper Dental (fictional). No real files or personal data are represented. The mapping is an instructional fixture and requires review against the actual source and destination systems.
Field mapping
Pilot scope: one synthetic job| Source field | Destination meaning | Rule / decision | Owner |
|---|---|---|---|
| Job ref | External reference | Preserve MS-031; do not treat as destination primary key | Data owner |
| Site | Site record | Split four named fictional sites into controlled child records | Operations lead |
| Status | Workflow stage | Map “waiting” only when the next owner and dependency are present | Process owner |
| Proof link | Artwork reference | Import metadata after access and retention review; no broken links accepted | Artwork owner |
| Notes | Structured exception / decision | Do not bulk-copy ambiguous notes; classify or retain read-only source | Job owner |
Pilot and cutover controls
No automatic release| Control | Completed example | Owner / state |
|---|---|---|
| Scope | One synthetic MS-031 job and four fictional site rows | Data owner · agreed |
| Reconciliation | 4 source sites = 4 destination sites; 12 source sign items = 12 destination items | Operations lead · matched |
| Exception | Three free-text notes need manual classification | Job owner · open |
| Rollback | Keep source read-only; delete only the disposable pilot records after exact-scope approval | Data owner · planned |
| Cutover | Not approved; attachment behaviour and permissions remain unknown | Migration owner · held |