Database Migration Strategies Overview
You'll learn how the three primary database migration strategies—lift-and-shift, replatform, and refactor—differ in complexity, risk, and cloud optimization.
Core Approaches Compared
When moving databases to the cloud, you face a fundamental choice: how much transformation should happen during migration?
Lift-and-Shift (Rehost)
Move your database "as-is" to cloud virtual machines. You're essentially relocating the same database software and configuration to cloud infrastructure. Fastest to execute, lowest initial risk, but you miss cloud-native benefits like auto-scaling or managed backups. Think of it like moving your furniture to a new house without buying anything new.
Replatform
Migrate to a cloud-managed database service (like RDS, Azure SQL, or Cloud SQL) while keeping the same database engine. You gain operational benefits—automated backups, patching, high availability—without rewriting application code. It's like moving into a furnished apartment: same lifestyle, less maintenance. Moderate complexity, better TCO than lift-and-shift.
Refactor/Re-architect
Redesign your database architecture to use cloud-native services—perhaps switching from Oracle to PostgreSQL, or adopting NoSQL services like DynamoDB. Requires schema changes and application code updates. Highest effort and risk, but maximizes cloud benefits: elasticity, cost efficiency, and modern features. This is a full renovation, not just a move.
Choosing Your Strategy
Your choice depends on timeline, budget, and long-term goals. Lift-and-shift gets you to the cloud quickly for urgent datacenter exits. Replatform balances speed with operational improvements. Refactor is for applications you'll run long-term where cloud optimization matters most.
Key Takeaway: Database migration strategies exist on a spectrum from quick-and-simple (lift-and-shift) to transformative (refactor), with replatform offering a middle ground that captures managed-service benefits without application rewrites.