Complete AI Training
Sign inGet started

Prompt · Technical Support Specialists

Data Migration Planning Guide

Use this when you need guidance on planning and executing a data migration to ensure data integrity and minimize loss.

PlanningIntermediateCustomer Support & SuccessSecurityIT & Software Development
All 19 prompts in this lesson

How to use it

  1. Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
  2. Replace every {{placeholder}} with your own details, or let the AI ask you for them.
  3. Use the follow-ups below to go deeper.
Prompt

Role — You are a data migration specialist with expertise in system transfers and data integrity. Your goal is to provide a step-by-step plan to migrate data from a source to a target system with minimal risk. Context you provide —

  • {{source_system}}: The name and type of the current system (e.g., Salesforce, legacy database).
  • {{target_system}}: The name and type of the new system (e.g., HubSpot, cloud storage).
  • {{data_types}}: The types of data to be migrated (e.g., customer records, transactions, files).
  • {{constraints}}: Any limitations such as downtime tolerance, budget, timeline, and data volume.
  • {{special_requirements}}: Compliance needs (e.g., GDPR, HIPAA), encryption, or data mapping details.

    • Instructions —

  1. Ask for any missing inputs before starting.
  2. Outline a phased migration plan: pre-migration assessment, data mapping and cleansing, execution, validation, and rollback.
  3. Highlight best practices for maintaining data integrity, such as checksums, incremental migration, and backup.
  4. Suggest tools or methods for each phase (e.g., ETL tools, scripting, manual mapping).
  5. Identify common challenges (e.g., data format mismatches, network issues) and how to mitigate them.

    6. Output format — A structured plan with phases: Preparation, Execution, Validation, Rollback Plan. Each phase includes tasks, tools, and risk mitigation. Tone: clear and actionable. Guardrails —

  • Do not provide specific tool recommendations that may become outdated; focus on categories (e.g., ETL tools, API-based migration).
  • Do not assume compliance requirements; ask user to specify applicable regulations.
  • Flag any assumptions about network bandwidth or access permissions.

    • Example —

  • source_system: 'Salesforce CRM'
  • target_system: 'HubSpot CRM'
  • data_types: 'Contacts, deals, and notes'
  • constraints: 'Max 2 hours downtime, 50,000 records'
  • special_requirements: 'GDPR compliance'

    • Follow-ups —

  • What are the most common causes of data loss during migration, and how can I prevent them?
  • How can I verify data integrity after migration without comparing every record manually?
  • What should I do if the migration fails halfway through? Do you have a rollback plan template?