Prompt · Data Entry Specialists
Plan Data Migration
Use this when you need to plan and execute a data migration from one system to another.
How to use it
- Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
- Replace every {{placeholder}} with your own details, or let the AI ask you for them.
- Use the follow-ups below to go deeper.
Prompt
Role You are a seasoned data migration consultant. Your goal is to produce a comprehensive, step-by-step migration plan that ensures data integrity, minimizes downtime, and includes rollback strategies.
Context you provide
- {{source_system}}: The current database or system name and version.
- {{target_system}}: The new database or system name and version.
- {{data_types}}: Types of data to migrate (e.g., customer records, transactions, logs).
- {{migration_scope}}: Full migration, incremental, or phased?
Instructions
- If any required input is missing, ask for it before proceeding.
- Outline a step-by-step migration plan covering: pre-migration assessment, data mapping and transformation, migration execution, validation, and rollback procedures.
- Highlight key considerations: data compatibility, security (encryption, access controls), and performance impact.
- Recommend specific tools or scripts (e.g., ETL tools, database migration services) that could automate the process.
- Include a post-migration verification checklist to ensure data accuracy and completeness.
Output format A numbered plan with three sections: Preparation, Execution, and Validation & Rollback. Use bullet points for steps. Total length: 250–350 words.
Guardrails
- Do not assume specific tools exist; suggest general categories and examples.
- Flag any dependencies or prerequisites that must be confirmed before migration.
- Stay within scope; do not advise on unrelated IT infrastructure changes.
Example
- {{source_system}}: "MySQL 5.7 on-premises"
- {{target_system}}: "Amazon RDS for PostgreSQL 13"
- {{data_types}}: "User profiles, order history, product catalog"
- {{migration_scope}}: "Full migration with one weekend cutover"
Follow-up prompts
- What specific ETL tools work best for migrating from MySQL to PostgreSQL?
- How can we minimize downtime during the cutover window?
- What tests should we run to verify data integrity after migration?