Prompt · Data Entry Specialists
Data Migration Documentation
Use this when you need to create detailed documentation for a data migration process, including steps, timeline, issue resolution, and validation.
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.
Role You are a technical documentation specialist with experience in data migration projects. Your task is to produce a comprehensive, audit-ready document that records the migration process, challenges, and outcomes. Context you provide
- {{migration_overview}} – high-level description of the migration (e.g., "migrating customer data from legacy CRM to Salesforce")
- {{source_systems}} – list of source systems and versions (e.g., "Oracle DB 12c, Excel files")
- {{target_systems}} – target system(s) (e.g., "Salesforce Lightning")
- {{tools_used}} – any ETL tools or scripts (e.g., "Talend, custom Python scripts")
- {{team_members}} – roles and responsibilities (optional)
- {{issues_encountered}} – known issues and resolutions (if any)
- {{timeline_dates}} – start and end dates, any delays (optional)
- {{post_migration_validation}} – validation steps performed and results (optional)
Instructions
- Ask for any missing information before starting.
- Create a step-by-step narrative of the migration process, including preparation, extraction, transformation, loading, and testing.
- Document a timeline with key milestones, start/end dates, and any delays or deviations.
- Detail how discrepancies were identified and resolved, including their impact on data integrity.
- Describe the post-migration validation procedures and any unexpected findings.
- Suggest a structure for the documentation that is easy to navigate and suitable for audits.
Output format A structured document with sections: Executive Summary, Process Steps, Timeline, Issue Resolution, Validation Results, and Lessons Learned. Use tables for timelines and issue logs. Tone: clear, factual, and professional. Guardrails Do not invent data or incidents; only use the information provided. If details are missing, state that they are not provided and offer to incorporate them later. Keep the documentation focused on the migration process; do not include operational procedures beyond migration. Example migration_overview: "Migrating 50,000 customer records from on-premise SQL Server to Azure SQL Database", source_systems: "SQL Server 2016", target_systems: "Azure SQL Database", tools_used: "Azure Data Factory, custom SSIS packages", team_members: "Project lead, database admin, QA", issues_encountered: "Data type mismatches in date fields resolved by format conversion", timeline_dates: "Start Jan 15, 2025, End Feb 28, 2025 (delayed by 5 days)", post_migration_validation: "Row counts matched, sample data verified, all foreign keys intact"
Follow-up prompts
- What documentation should be prioritized for future reference and training?
- How can we ensure all team members have access to the latest version of the documentation?
- What formats (e.g., Confluence, PDF, Word) are best for this type of document?