← Back to Blog
December 19, 2024•14 min read

Database Migration Strategies for Zero-Downtime Deployments

DatabaseMigrationsDevOpsZero-Downtime

Database migrations are risky—a bad migration can bring down production. This guide covers strategies for making schema changes safely, without downtime or data loss.

Backward-Compatible Changes

Always make migrations backward-compatible when possible. Add columns as nullable first, populate data, then make them required in a separate migration. This allows old code to continue working while new code uses new fields.

-- Step 1: Add nullable column
ALTER TABLE users ADD COLUMN phone VARCHAR(20) NULL;

-- Step 2: Populate data (in application code)
UPDATE users SET phone = ... WHERE phone IS NULL;

-- Step 3: Make required (after deployment)
ALTER TABLE users ALTER COLUMN phone SET NOT NULL;

Feature Flags

Use feature flags to control when new database features are used. Deploy schema changes first, then enable features gradually. This provides a safety net if issues arise.

Rollback Strategies

Every migration must have a down script. Even if you never use it, writing the rollback script forces you to think through the migration carefully.

Design migrations to be reversible. Keep down migrations simple, or maintain a separate rollback script. Test migrations on staging that mirrors production data volumes.

Key Takeaways

  • Always make schema changes backward-compatible before switching application code — deploy the new column first, update the app, then remove the old column in a separate migration.
  • Use feature flags to decouple schema availability from feature activation, giving you fine-grained control over rollout and a fast kill switch if problems appear.
  • Test migrations on a staging environment that mirrors production data volume precisely — a migration that takes 2 seconds on 10,000 rows may require a maintenance window on 10 million rows.
  • Use tools like Prisma Migrate, Flyway, or Liquibase to version-control your migrations alongside your application code so every deploy includes the correct schema changes.
  • Back up your database immediately before applying destructive migrations, even in CI/CD pipelines — automated backups before migrating are a production non-negotiable.

Ready to Ship Your SaaS?

Stop writing the same boilerplate code. Browse our production-ready SaaS templates — each includes authentication, Stripe billing, database setup, and deployment configs so you can launch in days instead of months.

Check out our straightforward pricing, see how we compare to ShipFast and MakerKit, or read the documentation to understand exactly what you get. Questions? Learn about our team and mission, or catch up on our engineering blog.