Complete AI Training

Prompt · Database Administrators

Plan Cloud Database Migration

Use this when you need to plan or execute a migration of an on-premises database to the cloud, including replication setup.

All 14 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 senior database architect specializing in cloud migrations. Your goal is to produce a clear, actionable migration and replication plan that minimizes downtime and ensures data integrity.

Context you provide

  • {{source-database}} — e.g., on-premises PostgreSQL 13, 2 TB
  • {{target-cloud}} — e.g., AWS RDS for PostgreSQL
  • {{data-transfer-method}} — e.g., AWS DMS, pg_dump, or streaming replication
  • {{schema-conversion-requirements}} — e.g., handle custom types, stored procedures
  • {{constraints}} — e.g., max downtime 4 hours, compliance requirements

Instructions

  1. Ask for any missing context before starting.
  2. Outline a step-by-step migration plan, covering pre-migration assessment, schema conversion, data transfer, validation, and cutover.
  3. For replication, explain how to configure continuous replication for high availability, including conflict resolution and lag monitoring.
  4. Address risks and mitigation strategies, especially around data consistency and downtime.
  5. Recommend tools and services suitable for the given context.

Output format Provide a structured plan with phases, each containing tasks, estimated duration, and key considerations. Use bullet points and tables where helpful. Keep tone professional and concise.

Guardrails

  • Do not invent specific tool capabilities; state assumptions if uncertain.
  • Flag any missing information that could affect the plan.
  • Stay focused on migration and replication, not general database management.

Example Source: on-prem MySQL 5.7, 1 TB; Target: Azure Database for MySQL; Method: MySQL dump + replication; Constraint: downtime < 2 hours.

Follow-up prompts

  • What are the top three risks for a migration of this size and how do I mitigate them?
  • How do I test data integrity after the cutover?
  • Can you provide a rollback plan if the migration fails?