# Hypothetical worked migration plan: one callback workflow

Evidence class: Hypothetical worked example; not an executed test or customer result. Owner page: /blog/the-work-after-the-call/

This is a filled planning example. No migration, provider action, access test, cutover or rollback has been executed. All outcome observations remain untested. Names and identifiers describe a fictional workshop, not a customer.

## Scope and owners

| Field | Example entry |
|---|---|
| Client/workflow reference | EXAMPLE-WORKSHOP / after-hours callback intake |
| Source setup and version | Hypothetical source configuration A |
| Destination configuration and version | Hypothetical candidate configuration B; support not yet qualified |
| Required result | Final corrected callback request readable by reception in the correct client's queue |
| In scope | One intake route, public policy answers, callback request, staff handoff |
| Out of scope | Confirmed bookings, payments, other locations and ordinary daytime intake |
| Decision and cutover owner | Example role: agency delivery lead; client manager approves service change |
| Knowledge owner | Example role: workshop service manager |
| Record/action provider owner | Example role: client account administrator |
| Handoff recipient | Example role: workshop receptionist |
| Authorized test-data scope | Synthetic phone ending 0102 and fictional request EX-REQ-01 only |
| Planned cutover | After controlled acceptance, in an agreed local business timezone; no actual time scheduled |

## Inventory and transfer decisions

- Intake trigger: identify the route and how to pause new intake. Verify that timers, workers and provider retries are also controlled.
- Credentials: client administrator authorizes the intended destination through its supported process. No secret is stored in this file.
- Sources: compare approved policy version A with the extracted representation. The manager approves any changed answer.
- Configuration: preserve instructions and field mappings as a reviewed baseline. A copied prompt alone is insufficient.
- Pending jobs: list each waiting, retrying and uncertain item before routing changes. One system or named person owns completion.
- External actions: reconcile any request that may already have saved. Preserve its original action identity.

These are planned checks. An inventory does not prove a tool can export or import the required state.

## Field and behavior mapping

| Mapping | Source meaning | Candidate meaning | Conversion or exclusion | Duplicate rule | Owner | Evidence still needed |
|---|---|---|---|---|---|---|
| MM-01 | Client and request IDs | Same client and request references | Preserve opaque IDs; do not merge by email alone | Same request retains identity | Agency evaluator | Allowed and denied client checks |
| MM-02 | Request collected | Requested, not confirmed | No conversion to booked | Repeated request does not create a new action | Client manager | Staff-view status comparison |
| MM-03 | Preferred time in local business timezone | Same requested local time and explicit zone | Resolve ambiguous dates before write | Preserve request identity | Agency evaluator | Controlled date conversion check |
| MM-04 | Approved public policy A | Approved public policy A | Exclude private account material | Withdrawn source stays ineligible | Service manager | Source and retrieval comparison |
| MM-05 | Create reception request | Same permitted operation only | No booking or payment authority | Reconcile uncertain original write | Provider account owner | Actual endpoint and saved-result check |
| MM-06 | Reception receives final details | Same receiving role and context | Carry final corrected phone ending 0102 | Receipt checked separately from send | Receptionist | Controlled receipt and context check |
| MM-07 | Old worker owns pending item EX-PENDING-01 | Old worker finishes it; candidate does not replay it | New intake switches only after owner decision | One continuing writer per item | Cutover lead | Queue inventory and ownership record |

## Compare before cutover

| Case | Expected result | Source observation | Candidate observation | Decision |
|---|---|---|---|---|
| Corrected callback number | Final phone ending 0102 in receiving queue | Not run | Not run | Hold live routing until compared |
| Preferred time only | Requested status, no booking confirmation | Not run | Not run | Verify wording and saved state |
| Destination timeout after possible write | Unknown until original outcome reconciled | Not run | Not run | Assign recovery owner; no blind replay |
| Repeated delivery | Same intended action, no unintended duplicate | Not run | Not run | Verify actual contract and retention |
| Wrong-client actor | Denied view and change | Not run | Not run | Required permission check |
| Unavailable policy answer | Clear limit and named human route | Not run | Not run | Check staff receipt and context |

## Cutover decision and rollback

Cutover is not approved in this example. The agency lead first collects the agreed source/candidate observations; the client manager checks that reception can use the result. Missing records, incorrect client scope or an unavailable exception route prevent cutover.

The cutover plan assigns new intake to one route and keeps existing pending jobs with their recorded owner. It records the last source request and first candidate request so staff can reconcile the boundary.

For rollback, restore the agreed intake route and configuration after authorization. Reconcile candidate-created records and uncertain actions separately. A routing change does not undo a record, booking or message. Any compensation follows the destination's authorized process and records its accepted or unresolved result.

The rollback rehearsal and its observation record are still required. Keeping the old configuration is only preparation.

## After the change

Compare the agreed observation window with the baseline, including exceptions and staff correction work. Record remaining work, its owner and the decision to continue or return. Do not turn this example into a claim that Vora has imported, persisted or recovered this workflow.

[Read the migration method](/blog/move-one-workflow-first/) · [Use the blank checklist](/resources/migration-checklist.md) · [Prepare an evaluation](/help/).