PROVIDER Β· The SQL-first database migration tool
Flyway
Flyway is the SQL-first migration tool where version numbers and checksums guarantee ordering and integrity, with CLI and Spring Boot integration bringing database changes under version control without a new DSL.
Pros
Cons
Product Information
Detailed Notes
Overview
Flyway was released in 2013 by the Boxfuse team and acquired by Redgate in 2019 as the simplest database migration tool, built around versioned SQL scripts such as V1__init.sql with a schema history table tracking applied versions and checksums preventing script tampering.
For Backend & Database work the value is zero abstraction with pure SQL, since no new DSL is needed and native SQL for the target database stays readable to DBAs, while the CLI, Java API, Maven and Gradle plugins, and Spring Boot integration make adoption quick for SQL-fluent teams.
The trade-off is abstraction level, because dialects are not auto-translated so the same scripts may need rewriting for another engine, rollback trails Liquibase with undo in the commercial edition and open source defaulting to forward-only migration, and parallel development needs conventions to avoid version clashes.
Core Strengths
- Pure SQL scripts need no new DSL and stay reviewable by DBAs
- Version numbers with checksums guarantee tamper-free scripts and controlled ordering
- Complete CLI, Java API, Maven and Gradle, and Spring Boot integration
- Supports MySQL, PostgreSQL, Oracle, SQL Server, ClickHouse, and many more
Product Ecosystem
Versioned migration
V-prefixed scripts run in version order while R-prefixed repeatables refresh views and procedures.
Validation and baseline
Checksums prevent edits to applied scripts and baseline starts an existing database at a version.
Integration
The flyway migrate CLI, Java API, Spring Boot startup migration, and pipeline steps.
Drawbacks
- No dialect translation, so switching engines often means rewriting scripts
- Open source is forward-only with weaker rollback than Liquibase
- Parallel development needs process conventions to avoid version conflicts
- Undo and some database support are commercial
Use Cases
- Fast adoption by SQL teams (β β β β β ) - No new syntax to learn
- Spring Boot startup migration (β β β β β ) - Runs at boot
- Consistent multi-environment deployment (β β β β ) - Versions and checksums guarantee order
- Scenarios needing automatic rollback (β β ) - Requires the commercial edition
Pricing
| Plan | Price | Scope |
|---|---|---|
| Community | $0 | Apache 2.0 with core migration |
| Teams | Annual subscription from about USD 600 | Undo and broader database support |
| Enterprise | Contract quoted | Governance, auditing, support |
The Community edition is free and covers most team migration needs, with Teams from about USD 600 annually adding undo and broader database support, and adoption cost mainly team conventions on naming and branching.
FAQ
-
Flyway or Liquibase? Flyway for pure SQL with DBA-centric teams, Liquibase for dialect abstraction, rollback, and richer context control.
-
What if a script is wrong? Applied scripts cannot be edited since checksums fail, so add a corrective version script and always back up before destructive changes.
-
Does it support rollback? Open source has no automatic undo, requiring manual reverse scripts or Flyway Teams undo, so design rollback scripts with backup strategy.