Prepare a database migration review plan

A migration review needs preconditions, expected changes and recovery considerations. The document should be built from the actual migration code and system constraints.

Use a reviewable project copy

Give the product or code teammate the relevant specification and a dedicated project folder or branch. Separate a proposed change from permission to release it. Request a diff or evidence table alongside the recommendation, and run checks that exercise the behavior in question. Generated code and test output still need review in the actual project environment.

Inputs for this workflow: Migration files, schema snapshot and the owner’s operational constraints.

Work through the task

1. Identify data changes and compatibility assumptions.
2. List validation and recovery evidence needed.

A brief you can adapt

Draft migration-review.md with affected tables, prerequisites, verification queries and unresolved risks. Do not execute the migration.

The filenames above are examples. Replace them with your actual inputs and destination before submitting the task.

Review the deliverable

Have the database owner review the plan and test it on a disposable representative copy.

Where this approach can fail

A rollback command may not restore lost data. Do not imply reversibility without evidence.

For the related desktop setup, see local folder.