# One-workflow migration, mapping and rollback checklist

Evidence class: Blank template. Owner page: /blog/the-work-after-the-call/

Use one copy for a defined client workflow. All fields are blank and all tasks are unchecked. This is a planning template, not an executed migration or proof of any tool's import support.

## Scope and owners

| Field | Your entry |
|---|---|
| Client/workflow reference | |
| Source setup and version | |
| Destination configuration and version | |
| Required customer result | |
| In-scope channels/actions/records | |
| Out-of-scope services that stay in place | |
| Decision and cutover owner | |
| Knowledge/source owner | |
| Record/action provider owner | |
| Staff handoff recipient | |
| Authorized test-data scope | |
| Planned cutover point/timezone | |

## Baseline and supported transfer

- [ ] Inventory knowledge, providers, permissions, triggers, scheduled work, records and human routes.
- [ ] Confirm the source's available export and destination's supported representation/import path.
- [ ] Preserve a baseline of relevant configuration and records with version/time and storage references.
- [ ] Identify pending work and authoritative identifiers before changing a route.
- [ ] Keep secret credentials in secure configuration; do not paste them into this checklist or shared exports.
- [ ] Record unsupported fields or operations as gaps and agree their disposition before transfer.

## Field and behavior mapping

Add rows as needed. A matching field name is not proof of equivalent meaning.

| Mapping ID | Object/behavior | Source field/key and meaning | Target field/key and meaning | Conversion/default/exclusion | Duplicate/reference rule | Owner | Comparison evidence/result |
|---|---|---|---|---|---|---|---|
| MM-01 | Customer identity and client scope | | | | | | |
| MM-02 | Requested/confirmed/error status | | | | | | |
| MM-03 | Date/time/timezone | | | | | | |
| MM-04 | Knowledge version and authority | | | | | | |
| MM-05 | Action permissions and provider reference | | | | | | |
| MM-06 | Human recipient and context | | | | | | |
| MM-07 | Trigger/scheduled-work ownership | | | | | | |

- [ ] Map required fields, references, defaults and explicit exclusions.
- [ ] Agree how existing/source identifiers link to target identifiers.
- [ ] Agree who resolves duplicates and unsupported representations.
- [ ] Keep agency and client scope explicit; review the intended and unauthorized actors.

## Compare before cutover

- [ ] Replay reviewed normal, missing-knowledge, conflict, failure and uncertain-action cases with authorized data.
- [ ] Compare authoritative action read-back, linked customer records, status and timezone.
- [ ] Reopen the result through the intended staff view.
- [ ] Verify handoff context and receipt at the agreed destination.
- [ ] Record expected/observed results separately; do not mark an unrun or uncertain case passed.
- [ ] Resolve material outcome, persistence, duplicate or permission failures before widening the move.

| Case/reference | Expected result | Source observation/evidence | Target observation/evidence | Gap/decision/owner |
|---|---|---|---|---|
| | | | | |
| | | | | |

## Cutover and duplicate prevention

- [ ] Name the single route allowed to create live actions.
- [ ] Pause/isolate competing triggers using the supported controls.
- [ ] Record the cutover point and reconcile pending/in-flight attempts.
- [ ] Inspect authoritative state before retrying an uncertain action.
- [ ] Confirm who reviews the first live outcomes and who can stop the move.

## Rollback and recovery

| Required decision | Your entry |
|---|---|
| Rollback trigger | |
| Decision owner and contact route | |
| Baseline/configuration reference | |
| Supported routing/configuration restoration steps | |
| Owner of records/actions created since cutover | |
| Authorized external cancellation/compensation path | |
| Customer-impact/handoff owner | |
| Recovery comparison evidence | |
| Outstanding items and next review | |

- [ ] Rehearse recovery in an authorized test scope.
- [ ] Confirm how post-cutover records and pending actions are reconciled.
- [ ] Confirm any compensating step separately; restoring configuration does not undo a booking or sent message.
- [ ] Read back the recovered state and record remaining work.
- [ ] Retain agreed evidence; remove only authorized test fixtures under the agreed cleanup process.

## Decision

| State | Mark one and record the owner/evidence |
|---|---|
| Not run / still being planned | |
| Compared with unresolved gaps | |
| Ready for the agreed bounded cutover | |
| Cut over; outcome review pending | |
| Recovered/rolled back; outstanding work recorded | |

This decision covers the specified workflow and configuration only. Expand scope after reviewing its actual outcomes.