Flyway vs Liquibase in 2026: Which Should You Pick?
Table of Contents
Open Table of Contents
Brief
My goal is to make posts like this the SIMPLEST place on the internet to learn how to do things that caused me trouble. Every Spring service needs schema migrations, both major tools are fine, and yet the choice keeps generating meetings. This post ends the meeting: I evolved the same schema through the same 10 migrations in both Flyway and Liquibase — including the data migrations and the multi-step column split where tools actually differ — and compared what it’s like to live with each in 2026.
Both demo projects (each verifying its migrations against PostgreSQL 18 via Testcontainers) are at github.com/StevenPG/DemosAndArticleContent.
The answer up front, because you came here for it: default to Flyway; pick Liquibase when you need rollbacks or multi-database abstraction. The rest of the post is the evidence.
The Shared Scenario
Ten migrations, identical SQL where possible, covering the situations that actually occur in a service’s life:
| Step | Change | Why it’s in the test |
|---|---|---|
| 1–2 | customers, orders tables | baseline DDL |
| 3 | index on orders.customer_id | trivial change |
| 4 | add status column with default | additive change |
| 5 | backfill status by age | data migration |
| 6–8 | split name → first_name/last_name | expand/contract, 3 steps |
| 9 | reporting view | dependent object |
| 10 | total → total_cents | destructive change + view rebuild |
How Each Tool Thinks
Flyway is a filename convention. V1__create_customers.sql through V10__orders_total_to_cents.sql, applied in version order, checksummed into flyway_schema_history. The migration is the SQL file; there is nothing else to learn. Spring Boot autodetects db/migration/ and runs pending migrations at startup.
Liquibase is a changelog of changesets, each identified by author:id rather than position. The changelog can be XML/YAML/JSON or — the format I’d argue everyone should use — formatted SQL, which is plain SQL with structured comments:
--liquibase formatted sql
--changeset steve:004
ALTER TABLE orders ADD COLUMN status TEXT NOT NULL DEFAULT 'NEW';
--rollback ALTER TABLE orders DROP COLUMN status;A YAML master changelog includeAlls the directory and Spring Boot runs it at startup, recording each changeset in databasechangelog.
For the ten forward migrations, honestly: the experience is nearly identical. Same SQL, same startup behavior, same result (both demos assert the same final schema). The differences live in three places.
Difference 1: Rollback
That --rollback line is Liquibase’s headline feature. liquibase rollback-count 1 after step 10 puts the total column and the old view back, because I wrote down how. Flyway has undo migrations (U10__...sql) — but undo remains a paid Teams/Enterprise feature; Flyway OSS strictly rolls forward.
Three honest observations from actually exercising this in the demo:
- Rollback SQL is only as good as your discipline. Nothing validates that my
--rollbackblock actually inverts the change until you run it. Untested rollback is documentation, not capability. (Changeset 10’s rollback block is six statements long — writing it was a useful forcing function, and a reminder of why people give up on maintaining them.) - Data migrations don’t really roll back. Step 5’s backfill rollback restores statuses — but only because the transformation was trivially invertible. Step 8 (dropping the assembled
namecolumn) can only be approximately rolled back. Rollback is a DDL feature that data changes merely tolerate. - Roll-forward is the real strategy anyway. In CI/CD, the fix for a bad migration is the next migration — you can’t “unrun” a change that production traffic has already written against. Which is exactly Flyway’s philosophical position, and why its OSS tier gets away with not having undo.
So: if your org requires scripted rollbacks (regulated environments, DBA sign-off processes), Liquibase gives you real machinery for free. If “fix forward” is your culture, this difference evaporates.
Difference 2: Drift Detection
Someone hot-fixed an index directly on production. What does each tool tell you?
Flyway OSS: flyway validate checks that applied migrations match your files (checksums). It says nothing about objects created outside migrations — drift detection and schema diffing live in the paid tiers.
Liquibase OSS: liquibase diff compares two live databases and reports extra/missing/changed objects, and diff-changelog will even write the reconciling changeset for you:
liquibase diff \
--url=jdbc:postgresql://prod:5432/app \
--reference-url=jdbc:postgresql://staging:5432/appThis is the most under-advertised free-tier gap between the tools. If you inherit databases with a history of manual surgery, Liquibase’s diff alone can justify the choice.
Difference 3: The Abstraction Tax
Liquibase’s XML/YAML changesets (createTable, addColumn…) are database-portable and support preconditions and contexts — genuinely valuable if you ship one product to customers running Postgres, Oracle, and SQL Server. But if you run one database you control, the abstraction is pure tax: another syntax between you and the SQL, and anything interesting (generated columns, USING GIN, partition DDL) ends up in <sql> escape hatches anyway. Formatted SQL changelogs — as in the demo — dodge most of the tax while keeping rollback and diff. If you adopt Liquibase, adopt it in formatted SQL.
Flyway never had the abstraction, which is precisely why its learning curve is a filename.
What Changed Recently (Why “in 2026” Is in the Title)
Worth knowing before you commit either way:
- Flyway moved Postgres support (like other databases) into companion modules — you need
flyway-database-postgresqlalongsideflyway-core, the omission of which is now the #1 Flyway startup error on upgrade. - Liquibase deprecated a pile of legacy CLI names in 4.x (kebab-case commands like
rollback-countare current) and keeps investing indiff/policy checks as its differentiators. - Both remain first-class citizens in Spring Boot 4 — auto-config, health indicators, and Actuator endpoints (
/actuator/flyway,/actuator/liquibase) that list applied migrations at runtime. - Licensing reality: both OSS cores remain genuinely free; both companies monetize the ops features (undo, drift, checks, dashboards). Evaluate the free tier you’ll actually use, not the marketing page.
The Decision Table
| Your situation | Pick |
|---|---|
| Single database you control, fix-forward culture | Flyway — least machinery, filename-deep learning curve |
| Scripted, auditable rollbacks are mandatory | Liquibase (formatted SQL + --rollback) |
| You ship to customers on heterogeneous databases | Liquibase (XML/YAML abstraction earns its tax) |
| Inherited databases with manual-change history | Liquibase (diff / diff-changelog in OSS) |
| Team already knows one of them | That one — the gap doesn’t justify retraining |
| Greenfield Spring Boot service, no special constraints | Flyway — the boring default for a reason |
Summary
Run both through the same ten migrations and the forward path is a tie — plain SQL in, correct schema out, one databasechangelog table apart. The real differences are Liquibase’s free rollback machinery and drift diffing versus Flyway’s near-zero conceptual overhead. Match those against your org’s actual requirements (not aspirational ones — will anyone really test the rollback scripts?) and the decision takes five minutes.
Both projects — 10 migrations each, Testcontainers-verified against Postgres 18 — are at github.com/StevenPG/DemosAndArticleContent to use as starting templates. Like the Spring compatibility cheatsheet, I’ll revisit this comparison when the landscape moves.
Here’s their output just to have a look at the differences:
Flyway
2026-07-20T19:52:27.161 --- [flyway-demo] org.flywaydb.core.FlywayExecutor : Database: jdbc:postgresql://localhost:52839/test?loggerLevel=OFF (PostgreSQL 18.4)
2026-07-20T19:52:27.183 --- [flyway-demo] o.f.c.i.s.JdbcTableSchemaHistory : Schema history table "public"."flyway_schema_history" does not exist yet
2026-07-20T19:52:27.184 --- [flyway-demo] o.f.core.internal.command.DbValidate : Successfully validated 10 migrations (execution time 00:00.007s)
2026-07-20T19:52:27.196 --- [flyway-demo] o.f.c.i.s.JdbcTableSchemaHistory : Creating Schema History table "public"."flyway_schema_history" ...
2026-07-20T19:52:27.222 --- [flyway-demo] o.f.core.internal.command.DbMigrate : Current version of schema "public": << Empty Schema >>
2026-07-20T19:52:27.225 --- [flyway-demo] o.f.core.internal.command.DbMigrate : Migrating schema "public" to version "1 - create customers"
2026-07-20T19:52:27.236 --- [flyway-demo] o.f.core.internal.command.DbMigrate : Migrating schema "public" to version "2 - create orders"
2026-07-20T19:52:27.244 --- [flyway-demo] o.f.core.internal.command.DbMigrate : Migrating schema "public" to version "3 - index orders customer"
2026-07-20T19:52:27.250 --- [flyway-demo] o.f.core.internal.command.DbMigrate : Migrating schema "public" to version "4 - add order status"
2026-07-20T19:52:27.255 --- [flyway-demo] o.f.core.internal.command.DbMigrate : Migrating schema "public" to version "5 - backfill order status"
2026-07-20T19:52:27.260 --- [flyway-demo] o.f.core.internal.command.DbMigrate : Migrating schema "public" to version "6 - split customer name add columns"
2026-07-20T19:52:27.266 --- [flyway-demo] o.f.core.internal.command.DbMigrate : Migrating schema "public" to version "7 - split customer name migrate data"
2026-07-20T19:52:27.271 --- [flyway-demo] o.f.core.internal.command.DbMigrate : Migrating schema "public" to version "8 - split customer name contract"
2026-07-20T19:52:27.277 --- [flyway-demo] o.f.core.internal.command.DbMigrate : Migrating schema "public" to version "9 - create order summary view"
2026-07-20T19:52:27.284 --- [flyway-demo] o.f.core.internal.command.DbMigrate : Migrating schema "public" to version "10 - orders total to cents"
2026-07-20T19:52:27.292 --- [flyway-demo] o.f.core.internal.command.DbMigrate : Successfully applied 10 migrations to schema "public", now at version v10 (execution time 00:00.019s)Liquibase
2026-07-20T19:53:29.082 --- [liquibase-demo] liquibase.changelog : Reading resource: db/changelog/changes/001-create-customers.sql
2026-07-20T19:53:29.108 --- [liquibase-demo] liquibase.changelog : Creating database changelog table with name: public.databasechangelog
2026-07-20T19:53:29.126 --- [liquibase-demo] liquibase.changelog : Reading from public.databasechangelog
2026-07-20T19:53:29.128 --- [liquibase-demo] liquibase.changelog : Reading resource: db/changelog/changes/002-create-orders.sql
2026-07-20T19:53:29.130 --- [liquibase-demo] liquibase.changelog : Reading resource: db/changelog/changes/003-index-orders-customer.sql
2026-07-20T19:53:29.131 --- [liquibase-demo] liquibase.changelog : Reading resource: db/changelog/changes/004-add-order-status.sql
2026-07-20T19:53:29.132 --- [liquibase-demo] liquibase.changelog : Reading resource: db/changelog/changes/005-backfill-order-status.sql
2026-07-20T19:53:29.133 --- [liquibase-demo] liquibase.changelog : Reading resource: db/changelog/changes/006-split-customer-name-add-columns.sql
2026-07-20T19:53:29.134 --- [liquibase-demo] liquibase.changelog : Reading resource: db/changelog/changes/007-split-customer-name-migrate-data.sql
2026-07-20T19:53:29.135 --- [liquibase-demo] liquibase.changelog : Reading resource: db/changelog/changes/008-split-customer-name-contract.sql
2026-07-20T19:53:29.136 --- [liquibase-demo] liquibase.changelog : Reading resource: db/changelog/changes/009-create-order-summary-view.sql
2026-07-20T19:53:29.137 --- [liquibase-demo] liquibase.changelog : Reading resource: db/changelog/changes/010-orders-total-to-cents.sql
2026-07-20T19:53:29.149 --- [liquibase-demo] liquibase.snapshot : Creating snapshot
2026-07-20T19:53:29.201 --- [liquibase-demo] liquibase.lockservice : Successfully acquired change log lock
2026-07-20T19:53:29.203 --- [liquibase-demo] liquibase.command : Using deploymentId: 4591608844
2026-07-20T19:53:29.204 --- [liquibase-demo] liquibase.changelog : Reading from public.databasechangelog
2026-07-20T19:53:29.219 --- [liquibase-demo] liquibase.ui : Running Changeset: db/changelog/changes/001-create-customers.sql::001::steve
2026-07-20T19:53:29.230 --- [liquibase-demo] liquibase.changelog : Custom SQL executed
2026-07-20T19:53:29.232 --- [liquibase-demo] liquibase.changelog : ChangeSet db/changelog/changes/001-create-customers.sql::001::steve ran successfully in 11ms
2026-07-20T19:53:29.238 --- [liquibase-demo] liquibase.ui : Running Changeset: db/changelog/changes/002-create-orders.sql::002::steve
2026-07-20T19:53:29.243 --- [liquibase-demo] liquibase.changelog : Custom SQL executed
2026-07-20T19:53:29.243 --- [liquibase-demo] liquibase.changelog : ChangeSet db/changelog/changes/002-create-orders.sql::002::steve ran successfully in 5ms
2026-07-20T19:53:29.247 --- [liquibase-demo] liquibase.ui : Running Changeset: db/changelog/changes/003-index-orders-customer.sql::003::steve
2026-07-20T19:53:29.250 --- [liquibase-demo] liquibase.changelog : Custom SQL executed
2026-07-20T19:53:29.250 --- [liquibase-demo] liquibase.changelog : ChangeSet db/changelog/changes/003-index-orders-customer.sql::003::steve ran successfully in 3ms
2026-07-20T19:53:29.253 --- [liquibase-demo] liquibase.ui : Running Changeset: db/changelog/changes/004-add-order-status.sql::004::steve
2026-07-20T19:53:29.256 --- [liquibase-demo] liquibase.changelog : Custom SQL executed
2026-07-20T19:53:29.256 --- [liquibase-demo] liquibase.changelog : ChangeSet db/changelog/changes/004-add-order-status.sql::004::steve ran successfully in 3ms
2026-07-20T19:53:29.259 --- [liquibase-demo] liquibase.ui : Running Changeset: db/changelog/changes/005-backfill-order-status.sql::005::steve
2026-07-20T19:53:29.265 --- [liquibase-demo] liquibase.changelog : Custom SQL executed
2026-07-20T19:53:29.265 --- [liquibase-demo] liquibase.changelog : ChangeSet db/changelog/changes/005-backfill-order-status.sql::005::steve ran successfully in 6ms
2026-07-20T19:53:29.267 --- [liquibase-demo] liquibase.ui : Running Changeset: db/changelog/changes/006-split-customer-name-add-columns.sql::006::steve
2026-07-20T19:53:29.270 --- [liquibase-demo] liquibase.changelog : Custom SQL executed
2026-07-20T19:53:29.270 --- [liquibase-demo] liquibase.changelog : ChangeSet db/changelog/changes/006-split-customer-name-add-columns.sql::006::steve ran successfully in 3ms
2026-07-20T19:53:29.272 --- [liquibase-demo] liquibase.ui : Running Changeset: db/changelog/changes/007-split-customer-name-migrate-data.sql::007::steve
2026-07-20T19:53:29.275 --- [liquibase-demo] liquibase.changelog : Custom SQL executed
2026-07-20T19:53:29.276 --- [liquibase-demo] liquibase.changelog : ChangeSet db/changelog/changes/007-split-customer-name-migrate-data.sql::007::steve ran successfully in 3ms
2026-07-20T19:53:29.278 --- [liquibase-demo] liquibase.ui : Running Changeset: db/changelog/changes/008-split-customer-name-contract.sql::008::steve
2026-07-20T19:53:29.281 --- [liquibase-demo] liquibase.changelog : Custom SQL executed
2026-07-20T19:53:29.282 --- [liquibase-demo] liquibase.changelog : ChangeSet db/changelog/changes/008-split-customer-name-contract.sql::008::steve ran successfully in 4ms
2026-07-20T19:53:29.284 --- [liquibase-demo] liquibase.ui : Running Changeset: db/changelog/changes/009-create-order-summary-view.sql::009::steve
2026-07-20T19:53:29.288 --- [liquibase-demo] liquibase.changelog : Custom SQL executed
2026-07-20T19:53:29.289 --- [liquibase-demo] liquibase.changelog : ChangeSet db/changelog/changes/009-create-order-summary-view.sql::009::steve ran successfully in 5ms
2026-07-20T19:53:29.291 --- [liquibase-demo] liquibase.ui : Running Changeset: db/changelog/changes/010-orders-total-to-cents.sql::010::steve
2026-07-20T19:53:29.299 --- [liquibase-demo] liquibase.changelog : Custom SQL executed
2026-07-20T19:53:29.300 --- [liquibase-demo] liquibase.changelog : ChangeSet db/changelog/changes/010-orders-total-to-cents.sql::010::steve ran successfully in 9ms
2026-07-20T19:53:29.304 --- [liquibase-demo] liquibase.util : UPDATE SUMMARY
2026-07-20T19:53:29.305 --- [liquibase-demo] liquibase.util : Run: 10
2026-07-20T19:53:29.305 --- [liquibase-demo] liquibase.util : Previously run: 0
2026-07-20T19:53:29.305 --- [liquibase-demo] liquibase.util : Filtered out: 0
2026-07-20T19:53:29.305 --- [liquibase-demo] liquibase.util : -------------------------------
2026-07-20T19:53:29.305 --- [liquibase-demo] liquibase.util : Total change sets: 10
2026-07-20T19:53:29.305 --- [liquibase-demo] liquibase.util : Update summary generated
2026-07-20T19:53:29.307 --- [liquibase-demo] liquibase.command : Update command completed successfully.
2026-07-20T19:53:29.307 --- [liquibase-demo] liquibase.ui : Liquibase: Update has been successful. Rows affected: 0
2026-07-20T19:53:29.309 --- [liquibase-demo] liquibase.lockservice : Successfully released change log lock
2026-07-20T19:53:29.310 --- [liquibase-demo] liquibase.command : Command execution complete