Step-by-step Atlas walkthroughs
Database-specific Atlas guides
Wire Atlas into your pipeline
Integrate Atlas with any ORM
Roles, permissions, and policies as code
Lookup tables and reference data
Run via the Atlas Operator
Manage schemas via Terraform
End-to-end control and compliance
Block drift before and after deploys
Safe schema changes at machine speed
Apply modern CI/CD to schema changes
One migration tool to rule them all
Manage thousands of databases as one
flyway vs atlas
Atlas plans migrations automatically from your schema as code, lints them for unsafe changes, and imports your existing Flyway directory in one command.
Where Atlas and Flyway differ
Both tools apply versioned migrations reliably. The rows below cover what surrounds that: planning, validation, rollback, and operations.
Migration planning
Automatic. Atlas diffs the current state against your desired schema and writes the SQL, respecting your policies.
Manual SQL files. Diffing and script generation are available in the state-based Teams/Enterprise workflow.
Workflows
Versioned and declarative. Both run through the same deterministic planner.
Versioned. A state-based workflow is available in Teams/Enterprise editions via Schema Model diffing.
Rollback
atlas migrate down computes the revert plan from the live database, and handles partially applied migrations.
Optional undo scripts, written by hand. They assume the up migration fully succeeded.
Validation and linting
Built-in analyzers flag destructive changes, table locks, and incompatible changes, locally and in CI.
Not available.
Testing
Unit-style tests for schemas and data migrations, runnable locally and in CI.
Not available.
CI/CD integrations
Native GitHub, GitLab, Bitbucket, CircleCI, and Azure DevOps integrations with PR comments and merge gates.
CLI invocation from custom scripting or plugins.
Kubernetes and Terraform
Official Kubernetes Operator (AtlasSchema, AtlasMigration CRDs) and Terraform provider.
No official operator or provider.
Drift detection
Pre-apply drift check inside the pipeline, plus continuous monitoring with alerts.
Drift report as a separate command. No monitoring layer.
Security as code
Declarative roles, users, and grants with automatic diffing.
Manual GRANT and REVOKE statements in SQL scripts.
Bring your Flyway history with you
atlas migrate import converts an existing Flyway directory into Atlas format. Three steps take a project from Flyway to Atlas without rewriting its history.
Import your migration directory
V__ and R__ files convert to Atlas format with an atlas.sum checksum file. U__ undo files are skipped: Atlas computes down migrations dynamically.
Point Atlas at your database
One env block per real environment. Planning and validation run against an ephemeral dev container, not your targets.
Baseline and take over
The baseline flag marks migrations up to that version as already applied on the existing database. From here, atlas migrate diff plans new changes and atlas migrate apply ships them.
Keep your history. Change your workflow.
atlas migrate import converts an existing Flyway directory in one command. Start free, or schedule a demo to plan the rollout with your team.