Editorial contribution · business
Plan a software migration with a way back
Moving to new software while keeping data and work intact? Get a staged plan with checks, stopping criteria and a possible recovery path.
Published: · Version 1
A prompt to try
Plan this software migration: [CURRENT AND TARGET STATES]. Data model and interfaces: [DETAILS]. Availability and acceptable data loss: [REQUIREMENTS]. Technology and versions: [DETAILS]. First identify invariants, affected consumers and unknown dependencies. Ask about missing information that could affect the recovery path. Design a staged plan covering compatible expansion, data transfer, verification, switchover and later removal of old structures. For each step, describe the precondition, observable success signal and stopping criterion. Explicitly check whether writes made after the switchover will remain compatible with the old system. If reverting could lose data, describe a verifiable recovery strategy instead of making a blanket rollback promise. Provide a rehearsal plan with counts, samples, consistency checks and a recovery test. Do not execute a migration without a separate instruction or claim to have carried out tests.
Copy the text into your AI, fill in the placeholders and check the answer.
What you need
- Your own access to a suitable AI. Only add information you are comfortable sharing.
How to start
- Copy the prompt and paste it into your AI.
- Replace the placeholders and add any missing information.
- Check the answer and ask follow-up questions to adapt it to your situation.
RobinPrompt.BETA 0.1.9