WorkflowFor DevelopersDatabases & Data Engineering

Data Warehouse Migration Plan.

When planning a data warehouse migration that must preserve data integrity and cannot afford significant downtime.

ChatGPT Β· Claude Β· GeminiΒ·AdvancedΒ·~1950 tokens
Curated by the AIPP team
Last updated 14 May 2026 Β· v3
data-warehouse-migration-plan-4.md Β· 1950 words
You are a senior {{role}} brought in to help a developer or tech professional complete a {{use_case}} task.

# Context
- Pack: Developers & Tech Professionals
- Category: Databases & Data Engineering
- Use case: Data Warehouse Migration Plan
- Source task:
  - I need to migrate data from {{source_legacy_database_on_premise_warehouse_old_vendor}} to {{target_snowflake_bigquery_redshift_new_schema}}.
  - Step 1: Assessment: audit the source data (volume, quality, dependencies, undocumented business logic in queries).
  - Step 2: Migration Design: choose migration approach (big bang vs. incremental), data transformation rules, and cutover strategy.
  - Step 3: Validation: design a validation framework to verify data integrity after migration.
  - Step 4: Rollback Plan: how to revert if the migration fails.

# Goal
Source data audit, migration design with cutover strategy, data integrity validation framework, and a rollback plan.

# Constraints
- Treat this as a sequential workflow where each step builds on the previous step.
- Keep every step clearly labeled and easy to run separately if needed.
- Avoid generic filler, vague advice, and unsupported claims.
- Make the output specific, practical, and ready to use.

# Output
Source data audit, migration design with cutover strategy, data integrity validation framework, and a rollback plan.

The variables to fill in

PlaceholderWhat to put thereExample
{{role}}Roledata migration specialist
{{use_case}}Your specific valuedata warehouse migration plan
{{source_legacy_database_on_premise_warehouse_old_vendor}}Source legacy database on premise warehouse old vendorSOURCE
{{target_snowflake_bigquery_redshift_new_schema}}Target snowflake bigquery redshift new schemaTARGET

How to customize this prompt

  1. Replace each {{double-curly}} with your real context.
  2. Adjust the constraints section to match your tone β€” formal, casual, blunt.
  3. If the engagement is recurring, change the duration line to mention milestones rather than days.
  4. Run it in your tool of choice. The output should be ready to paste with at most one small edit.

When to use

When planning a data warehouse migration that must preserve data integrity and cannot afford significant downtime.

PRO TIP

Migrate the metadata (schemas, views, stored procedures) before the data β€” every undocumented stored procedure is a surprise waiting to ruin your timeline.

Related prompts

Structured

Technical Problem Debugger

Debug this problem systematically. Identify the root cause, explain why it is happening, provide the fix, and explain how to prevent it in future.

Structured

System Design Advisor

Design the high-level architecture for this system. Cover components, data flow, scaling strategy, and key design decisions.

Structured

No-Code Tool Selector

Recommend the best no-code or low-code tool stack for the stated goal, with implementation guidance.

Structured

Data Analysis Prompt

Design the complete analysis approach for the stated question. Include the analytical method, the steps to execute it, and the format for presenting findings.

β˜… THIS PROMPT IS IN A PACK

The Developer Toolkit Pack

250 technical prompts for code review, documentation, architecture planning, debugging, test writing, API design, and career growth β€” built by developers for developers.

Browse more prompts β†’