Migration prerequisites checklist: identify what you have not checked

What you are answering

Have you tested a recent backup restore? Is an isolated staging copy available? Have you named the critical business flows and expected results? Is there a rollback decision point and route? Is an authorised owner responsible for the switch and acceptance? Select unknown when you have not verified a prerequisite rather than treating uncertainty as yes.

• A backup file alone is not a restore test.
• A staging copy must not silently send mail, charge cards or alter customer systems.
• Rollback must account for new writes, not only old code.

How to read the output

Each no or unknown response produces a prerequisite to resolve. If all five are yes, the output says you confirmed them; it does not independently verify them. There is no invented percentage score, estimated duration or assurance that the migration is safe. Compatibility, data integrity, capacity, security and live-change authority need their own checks.

• Do not schedule a production switch from this result alone.
• Keep the evidence for each yes answer in the actual migration brief.

Privacy and scope

The checklist accepts only prerequisite choices, not application files, logs or credentials. Its inspected implementation handles these choices in the browser and has no submission or storage path for them. Reset clears the displayed result; this is not a customer assessment retained by Synthetic Industry.

• Do not send passwords, dumps or private code through an enquiry.
• If requesting help, describe the unresolved prerequisite and desired outcome.

Prepare an actionable migration request

Send the source and target platform, included database/files and critical flow, plus which prerequisites remain unknown. Scope and price are agreed before private work. Customer account control and live approval remain separate from the software delivery route.