Database migration tools record each schema change as a versioned step, so a team can rebuild or upgrade a database the same way in every environment.
This guide ranks them on what the first ninety days cost, the bill once governance is added, how cleanly you can leave, and whether a buyer can run the tool alone.
Vendors can pay for more visibility on this website, for example a higher place in a ranking or more room on a page. Commercial relationships can also affect which products we feature and how prominently. Every vendor link is marked the same, whatever the arrangement behind it. How that works.
In short
What database migration tools software does
A database migration tool stores schema changes as ordered or declared scripts, applies them to development, test and production databases, records which have run, and sometimes reverses them.
We ranked the 14 database migration tools on setup effort first, then total cost, then data export, then exit, then fit for the buyer. A challenger rule applies on top. Places 1 to 3 are kept for lesser-known vendors when the category has them; large brands rank from 4. Why those five, and why there is no score out of ten, is on the how we work page.
Schema-as-code CLI that plans, tests and applies database changes
Ranked #1 of 14 in Best Database Migration Tools in 2026.
Published pricingElsewhere
Atlas names PostgreSQL, MySQL, SQL Server, MariaDB, ClickHouse, Redshift, SQLite, Oracle, Snowflake and Databricks, a wider list than most tools here. Pro costs $9 per user per month for up to 50 seats; a pipeline costs $59 a month with two target databases, plus $39 for each extra one.
Argo CD, Terraform and a Kubernetes Operator are named integrations. It ranks first because every tier is priced openly, and the trade-off is the unstated licence.
What stands out
Schema as code
Per-seat Pro rates
Pipelines and monitoring
Where it costs you
The homepage states no open-source licence and restricts building competing products without written consent.
Pipelines and monitoring are priced per project and per database, so the bill grows with the size of the estate.
Pipeline use requires a Pro seat for every contributing developer.
Right for
Teams wanting declarative schemas with published rates across many engines
Wrong for
Buyers who need a stated licence or country of establishment
Not stated by the vendorPublished rates for Pro seats, pipelines and monitoring; Starter CLI is free to use; Enterprise on custom terms; Pro trial offered
Single migration binary and Go library using SQL files or Go functions
Ranked #2 of 14 in Best Database Migration Tools in 2026.
Open sourcePricing on requestElsewhere
Migrations come in two forms: SQL files marked with Up and Down annotations, or plain Go functions that can be built into the application through Go embed. Out-of-order migrations, data seeding and environment variable substitution in SQL are also listed.
It sits second because the whole bill is zero and the licence is stated, yet it gives a buyer nothing beyond the tool itself: no dashboard, no governance layer and no named owner.
What stands out
MIT licence
SQL or Go migrations
Embedded migrations
Where it costs you
The pages read name no owner, country or support offer, so help means the repository.
The README lists no paid plan, so there is no commercial support route to buy.
Changes are written by hand as SQL or Go, and the README names no governance or approval layer.
Right for
Go teams wanting plain migration files with no licence cost
Wrong for
Teams needing approval workflows, audit trails or vendor support
Not stated by the vendorOpen source under the MIT licence; the README lists no pricing or paid plans
Database change platform with a Community tier, hosted or on your servers
Ranked #3 of 14 in Best Database Migration Tools in 2026.
Free tierSelf-hostablePublished pricingElsewhere
Per-user billing makes Bytebase cheap for a small team and steeper for a large one, since Pro is charged for every user each month with a ceiling of ten database instances. The Community plan is a real way to try it, because 20 users and ten instances cost nothing.
Enterprise adds high availability, onboarding, premium SLA, a custom MSA and a HIPAA BAA, each without a price. Cloud, own servers or an offline install settle where it runs.
What stands out
Self-hostable
Per-user Pro billing
Community plan
Where it costs you
Pro stays at 10 database instances, so larger estates are pushed towards an Enterprise plan with no listed price.
How changes are written, reviewed or rolled back is not described on the pages read.
Pro lists no trial, and high availability, premium SLA and a HIPAA BAA are unpriced Enterprise add-ons.
Right for
Teams wanting a hosted or self-run change platform with per-user pricing
Wrong for
Estates beyond ten instances that need every price listed
Not stated by the vendorFree Community plan for up to 20 users and 10 instances; Pro billed monthly per user; Enterprise priced on contact with a 14-day trial
Declarative MySQL and MariaDB schema management from CREATE statements in a repo
Ranked #4 of 14 in Best Database Migration Tools in 2026.
Pricing on requestElsewhere
Instead of ordered migration files, Skeema compares the repository's CREATE statements with the live schema and generates the difference. Existing table definitions can be exported into the repo first, and linter rules can encode company policies.
A single push updates every named environment. It ranks fourth because it fits one engine family tightly, and the cost of that focus is that every other database is out of reach.
What stands out
MySQL and MariaDB only
Declarative diff and push
Configurable linter
Where it costs you
Only MySQL and MariaDB are supported, so a mixed estate needs a second tool.
The site shows no pricing, plans or support terms, only a contact link.
No country or address is shown, only a copyright line for Index Hint LLC.
Right for
MySQL or MariaDB shops preferring declarative schemas kept in version control
Wrong for
Estates running PostgreSQL, SQL Server or Oracle beside MySQL
Not stated by the vendorSite lists no prices or plans and offers a contact link only
Zero-downtime PostgreSQL migrations using an expand and contract workflow
Ranked #5 of 14 in Best Database Migration Tools in 2026.
Open sourcePricing on requestElsewhere
The expand and contract pattern adds new structures first, serves old and new schema versions side by side, and removes the old ones later. pgroll automates that sequence, backfills columns when required and can roll back straight away.
It ships as one cross-platform executable with no external dependencies and works with existing databases and managed services such as RDS and Aurora. The price of that safety is a narrow scope: one engine and one release pattern.
What stands out
PostgreSQL 14 or later
Expand and contract
Apache 2.0 licence
Where it costs you
It targets PostgreSQL 14.0 or later only, so other engines and older servers are excluded.
Two live schema versions mean the application has to work with both during a rollout.
The README names no owner, country or paid support.
Right for
Postgres teams that cannot take locks or downtime during releases
Wrong for
Mixed-engine estates or servers older than Postgres 14
Not stated by the vendorOpen source under Apache License 2.0; the README names no price
Database-native change management for framework-free projects and dependable deployments
Ranked #6 of 14 in Best Database Migration Tools in 2026.
Pricing on requestElsewhere
Sqitch is not tied to an ORM or application language, which suits projects where several services share one database. The site provides command references, tutorials and best-practice guides, and the community section gathers issues, a mailing list and the repository.
Because the homepage lists no database engines, no price and no licence, the evidence behind a purchase decision is thinner here than for the tools ranked above it.
What stands out
Framework-free
Database-native
Source on GitHub
Where it costs you
The homepage states no licence, so a legal review has to find it elsewhere.
No country or author is shown, and community help runs through issues and a mailing list.
The pages read list no supported databases, so engine coverage needs checking first.
Right for
Teams wanting migrations that stay independent of any one application framework
Wrong for
Buyers needing a stated licence, owner or paid support
Not stated by the vendorHomepage shows no prices or plans; binary and source downloads are offered
Plain SQL migrations inspired by Flyway, as a .NET library or CLI
Ranked #7 of 14 in Best Database Migration Tools in 2026.
Pricing on requestElsewhere
Evolve brings the database up to date every time the project runs, which fits teams that want migrations applied at application start-up instead of in a separate deploy step.
It reads plain SQL files, is offered as a library, a tool and a CLI, and covers seven engines including Cassandra. The author describes it as unfunded, so treat it as a dependency to review, not a supplier to rely on.
What stands out
Plain SQL scripts
Cassandra and CockroachDB
Sponsor-funded
Where it costs you
The page calls it a free-time project with no funding, so continuity rests on the author's spare time.
The page read gives neither a licence nor a price.
Support is requested through GitHub Sponsors rather than sold, and no country is given.
Right for
Teams on .NET wanting Flyway-style SQL scripts run when the application starts
Wrong for
Organisations that need contractual support or a named company
Not stated by the vendorNo price or licence stated; the author asks for support through GitHub Sponsors
Lightweight migration tool for SQLAlchemy projects written in Python
Ranked #8 of 14 in Best Database Migration Tools in 2026.
Pricing on requestElsewhere
Alembic tracks the current revision in an alembic_version table and moves with commands such as upgrade head and downgrade -1. Batch mode helps SQLite and other databases with limited ALTER support, and templates cover generic, pyproject, async and multidb setups.
Autogenerate drafts migrations from model differences, though a draft still needs review. Its reach stops where SQLAlchemy stops, which is why it sits mid-table for a general buyer.
What stands out
SQLAlchemy only
Autogenerate
Offline SQL scripts
Where it costs you
It assumes SQLAlchemy, so a project on another Python data layer gains little from it.
Older Python and SQLAlchemy releases fall outside what current versions support.
No country, vendor or support offer is stated, only a copyright line.
Right for
Python teams that already describe their schema through SQLAlchemy models
Wrong for
Polyglot teams wanting one tool for non-Python services
Not stated by the vendorRun by you as a Python library and CLI; the site shows no pricing
SQL query builder for JavaScript with built-in migration commands
Ranked #9 of 14 in Best Database Migration Tools in 2026.
Pricing on requestElsewhere
migrate:make creates a file, migrate:latest applies the batch, and migrate:rollback undoes it, with --all going back to the start. Transactions are on by default and can be disabled globally or for one migration.
Nine database targets are listed, including CockroachDB and Amazon Redshift. Beyond migrations, Knex is a query builder, so adopting its migration commands means taking the whole library into the project.
What stands out
JavaScript
Transactional migrations
Lock table
Where it costs you
Migrations belong to a query builder, so a team not using Knex adopts a library for a single feature.
A stuck lock has to be released by hand with migrate:unlock.
The pages read give no licence, price or country.
Right for
Node.js teams that already run their database queries through Knex
Wrong for
Non-JavaScript stacks or teams wanting a standalone migration product
Not stated by the vendorSite shows no pricing or plans; the homepage names no licence
Versioned migration tool for 50+ databases, published by Redgate
Ranked #10 of 14 in Best Database Migration Tools in 2026.
Open sourcePublished pricingElsewhere
Coverage is the draw: Oracle, SQL Server, MySQL, PostgreSQL, MariaDB, MongoDB, Snowflake, BigQuery, SQLite, DB2 LUW and SAP HANA are all named. It runs on Windows, macOS, Linux and Docker.
The catch is the edition split, since the Community edition targets individuals and education while Enterprise carries an unlisted price and a trial link without terms. A company buyer should ask Redgate what each edition includes before comparing.
What stands out
50+ databases
Apache-2.0 repository
Maven and Gradle
Where it costs you
Community targets individuals and education, so company teams land on Enterprise.
Enterprise shows no price, billing basis or limits, so its cost cannot be modelled in advance.
The README puts both editions outside the open source project, so the Apache licence does not cover what a company buys.
Right for
Teams on mixed or older database engines needing broad coverage
Wrong for
Buyers who must see a company price before talking to sales
Not stated by the vendorCommunity edition shown as free; Enterprise price not shown, with a trial page linked
Change automation and governance platform with database-count limits per plan
Ranked #11 of 14 in Best Database Migration Tools in 2026.
Pricing on requestElsewhere
The pricing page frames Liquibase around Change Automation, Change Governance and Change Intelligence, and caps each plan by database targets and database types.
Because no figure is shown and each plan includes a services package, the first ninety days cost consulting hours as well as licences. Role-based access arrives from Business upward. A trial page exists, but its terms are not described, so ask what it covers.
What stands out
70+ databases
Role-based access
Services package required
Where it costs you
A services engagement is compulsory on each plan, which adds cost beyond the licence.
Starter and Team cover one database type each, so a mixed estate must buy a higher tier.
Role-Based Access Control appears only on Business and Enterprise.
Right for
Large estates wanting change governance tied to ServiceNow or GitHub
Wrong for
Small teams wanting a visible price and no services package
Not stated by the vendorQuoted per plan across four tiers sized by database count; a trial page is linked without terms
Database release automation with Git integration and segregation of duties
Ranked #12 of 14 in Best Database Migration Tools in 2026.
Pricing on requestNorth America
Because the licence counts each managed deployment target as one connection, every extra environment raises the bill.
In return the governance list is the longest here: SSO and MFA, secrets vault integration, approval workflows, ITSM integrations and rollback validation. With no list price and no trial, setup begins with a sales call, and the first quote becomes your real price.
What stands out
Per-target licence
Approval workflows
Drift detection
Where it costs you
No list price or named plan is shown, so cost is known only after a sales conversation.
Environments multiply licences, because every deployment target is a separate connection.
The pricing page mentions no trial and offers only a demo.
Right for
Regulated teams needing approvals, audit trails and segregated duties in releases
Wrong for
Small teams wanting to start alone and see a price
United StatesQuoted by sales and licensed per managed deployment target; only a demo booking is offered
Migration commands built into Django, covering schema and data changes
Ranked #13 of 14 in Best Database Migration Tools in 2026.
Pricing on requestElsewhere
makemigrations drafts changes from models, migrate moves forward or back to a named point such as zero, sqlmigrate shows the SQL, and squashmigrations combines a long history, though a CircularDependencyError may need manual resolution.
Because it is bundled, nothing is bought and nothing is hosted. The cost is tying the process to one framework, and database behaviour varies: Oracle has no DDL transactions either.
What stands out
Squash and replay
RunPython data migrations
Framework-bundled
Where it costs you
Irreversible operations raise IrreversibleError when a rollback is attempted.
Historical models lack custom methods and save(), which limits what a data migration can do.
Old migrations reference code that must stay in the codebase.
Right for
Django projects wanting migration files generated from their model changes
Wrong for
Teams outside Django or running migrations from other services
Not stated by the vendorPart of the Django framework; no price or hosting, run against your own database
EF Core migrations generated from model snapshots for .NET projects
Ranked #14 of 14 in Best Database Migration Tools in 2026.
Pricing on requestElsewhere
The developer runs dotnet ef migrations add, then database update, and EF Core stores the result as source files next to the code. A history table means only new migrations run.
SQL Server, SQLite and Cosmos providers come from Microsoft, while Npgsql, Pomelo and others cover PostgreSQL and MySQL. It ranks last here because migrations are a feature of an ORM, and a team outside .NET gains nothing from it.
What stands out
NuGet packages
Migration bundles
Provider-dependent
Where it costs you
Providers from other parties are not all maintained by Microsoft's EF Core project, so support varies by database.
Upgrading to a new major release can stall until the other vendors ship matching providers.
The tools are called ideal for local development, with bundles or reviewed scripts advised for production releases.
Right for
Teams on .NET wanting migrations generated from their data model
Wrong for
Shops outside .NET or needing one vendor behind every database
Not stated by the vendorDistributed as NuGet packages; the pages read show no price
A database migration tool stores schema changes as ordered or declared scripts, applies them to development, test and production databases, records which have run, and sometimes reverses them. Feature lists look alike, so we would settle these points one at a time instead.
01
Work out how much a sales call is worth to you
11 vendors on this page sell by quote, while 3 publish a pricing model you can read today: Ariga Atlas, Bytebase, Flyway.
02
Ask which country the contract runs through
The 14 companies behind this list are established in 2 countries, by region Elsewhere 13, North America 1. Disclosure obligations attach to the company, so they travel with the vendor even when the servers stay at home.
03
Decide if open source matters
3 of these are open source: goose, pgroll, Flyway. Hosting one yourself trades a subscription for maintenance.
Database migration tools: versioned files or declared schemas
Two designs divide this market. goose, Alembic, Django Migrations and Flyway keep an ordered history of changes, each one a file that runs once and is recorded as applied. Skeema and Ariga Atlas instead hold the desired end state, then calculate the difference against a live database. Ordered files suit teams that review every statement and need data fixes between steps; declared schemas suit teams that want the repository to read like the schema itself.
Skeema keeps CREATE statements in a repo, while Atlas describes itself as Terraform for databases with each change planned and tested before deployment. Pick the design before comparing prices, because moving later means rewriting the history your tool trusts, and a half-way hybrid gives two sources of truth that drift apart.
Decide whether your team reviews ordered files or a declared end state
Ask how the tool records what has already been applied
Check whether data changes between schema steps are supported
Engine coverage: one database family or fifty
Coverage differs more than the marketing suggests. Skeema serves MySQL and MariaDB only, and pgroll serves PostgreSQL 14.0 or later only. Evolve lists seven engines, Knex.js nine and goose nine plus 'and more', while Flyway cites 50+ and Liquibase 70+. Alembic needs SQLAlchemy and Entity Framework relies on providers that usually break across major versions.
Narrow tools can do more for their engine, as pgroll does with expand and contract changes, but a company running PostgreSQL beside Oracle ends up buying two tools. List every engine you run today and the one you expect in two years, then strike any candidate that misses either. A tool tied to an application framework also fails for the services written in other languages.
List every engine and version you run now and plan to run
Check whether provider or driver versions track your upgrades
Count how many languages touch the database
Real price: seats, targets and services packages
Price models rarely match, so convert each to your own estate. Ariga Atlas charges per Pro user, plus rates per pipeline project and per monitored database. Bytebase bills Pro per user each month and caps it at ten instances. DBmaestro licenses each managed deployment target as one connection, so every extra environment adds a licence.
Liquibase caps database targets per plan, and every plan requires a Professional Services package, which belongs in the first-ninety-day total. Flyway Community is aimed at individuals and education, with Enterprise unpriced. goose, Sqitch, Alembic and Django Migrations show no price at all, which moves the cost into staff time. Build a three-year sheet that includes services, extra environments and seats for every contributing developer.
Count users, databases and environments before asking for quotes
Add services packages and onboarding to the licence total
Estimate staff hours for tools that show no price
Rolling back and leaving: what stays in your repository
Rollback behaviour varies and is often misunderstood. goose pairs each SQL change with a Down annotation, Knex.js offers migrate:rollback with an all option, and pgroll can roll back immediately during an expand and contract rollout. Django Migrations raises IrreversibleError when an operation cannot be reversed, and Entity Framework advises a bundle or reviewed SQL script for deployment.
DBmaestro lists rollback validation among its operations features. Exit is simplest when changes are plain SQL files in your own repository, as with goose, Evolve and Skeema, because another tool can read them. Platform tools such as Liquibase and Bytebase hold more state, so ask what you can export. Test one rollback on a copy of production before signing anything.
Run one rollback on a production copy during the trial
Ask which files and history you can export on leaving
Check whether irreversible operations are flagged beforehand
What goes wrong most often when buying database migration tools software
Choosing a tool for the engine you run today and finding the second database a year later has no support.
Comparing a per-user rate with a per-target licence without multiplying both by your real environments.
Treating autogenerated or declared diffs as safe without reading the SQL they will run.
Adopting an ORM's bundled migrations, then discovering the other services sharing the database cannot use them.
07
Frequently asked questions
8 answers
What is the best database migration tools in 2026?
First of 14 on this page is Ariga Atlas. Ariga Technologies sells Atlas as 'Terraform for databases': schemas live as code, and each change is planned and tested before deployment.
The Starter CLI has no seat limit, and the Pro, pipeline and monitoring rates are all listed. The homepage names no open-source licence and asks for written consent before anyone builds a competing product. Country and legal entity are not stated.
Which database migration tools publish their pricing?
3 of the 14, with the pricing model each one publishes:
Ariga Atlas: Published rates for Pro seats, pipelines and monitoring; Starter CLI is free to use; Enterprise on custom terms; Pro trial offered.
Bytebase: Free Community plan for up to 20 users and 10 instances; Pro billed monthly per user; Enterprise priced on contact with a 14-day trial.
Flyway: Community edition shown as free; Enterprise price not shown, with a trial page linked.
11 vendors do not print a price.
Is there a free database migration tool?
Bytebase offer a free tier or a free self-hosted edition.
Where are these database migration tool vendors established?
Across 2 countries (Elsewhere 13, North America 1):
Ariga Atlas: Not stated by the vendor.
goose: Not stated by the vendor.
Bytebase: Not stated by the vendor.
Skeema: Not stated by the vendor.
pgroll: Not stated by the vendor.
Sqitch: Not stated by the vendor.
Evolve: Not stated by the vendor.
Alembic: Not stated by the vendor.
Knex.js: Not stated by the vendor.
Flyway: Not stated by the vendor.
Liquibase: Not stated by the vendor.
DBmaestro: United States.
Django Migrations: Not stated by the vendor.
Entity Framework: Not stated by the vendor.
Which database migration tools are open source?
goose, pgroll, Flyway.
Which database migration tools can you host yourself?
Bytebase. The remaining 13 run only on the vendor's servers.
What should you use instead of Ariga Atlas?
The next in line are goose, aimed at Go teams wanting plain migration files with no licence cost, and Bytebase, aimed at teams wanting a hosted or self-run change platform with per-user pricing.
Who should not buy Ariga Atlas?
Buyers who need a stated licence or country of establishment. The homepage states no open-source licence and restricts building competing products without written consent..
Makers of database migration tools products can ask us to look at theirs. Say what it does and who uses it. We choose what to add, and nothing can be bought; see software advice for what a listing means.
