Schema Migration Tools Compared
For the backend engineer deciding how a schema change gets from a design into production, and who has to write or generate the DDL.
On this page
DbSchema writes your migration scripts for you. You edit the schema model, DbSchema compares it with the target database, and it generates the migration script from the difference. You read that script before it runs on development, staging or production. That suits a team that designs the schema first. Liquibase and Flyway take the other approach: you write every change by hand, as a changelog or as numbered SQL files. DbSchema covers the unattended pipeline step too, with DbSchemaCLI and automation scripts.
One term first, because searches mix them up. Data migration moves records from one system to another. Schema migration changes the structure, and the data usually stays where it is. This page is about schema migration.
Pick the tool by where the change is written
Four questions separate the three tools:
- Can a change run unattended in a CI pipeline?
- Is the schema a diagram you edit?
- Can you edit the design with no database connection open?
- Can you compare the design against a live database?
Liquibase and Flyway are built around the first question. DbSchema answers the other three. For the pipeline step, DbSchema ships DbSchemaCLI and Groovy automation scripts. So the visual diff stays the review step, and the pipeline runs the rest.
Teams that like changelogs but want a visual diff can read Liquibase alternatives with a visual schema diff. If you are choosing a modeling tool as well, see the wider field of database design tools.
DbSchema is the only one of the three that draws the schema
The three tools split on one line: where the change is written. DbSchema starts from a visual model and generates the DDL from a comparison. Liquibase starts from a changelog you write. Flyway starts from SQL migration files that run in version order.
| DbSchema | Liquibase | Flyway | |
|---|---|---|---|
| Where the change is written | Diagram and model file | Changelog file | SQL migration file |
| Main interface | Desktop application | CLI, flow files, Java API | CLI, Flyway Desktop, Java API |
| Free edition | Community, no time limit | Open source | Community |
| Paid licensing | Per user, perpetual or monthly | Quote-only plans, sized by engines and targets | Enterprise |
| Drift review | Visual model-to-database diff | CLI inspection | check -drift, Enterprise only |
What to see: only DbSchema keeps the design as a diagram, and only DbSchema costs the same however many engines you use.
The diagram is where a new column is added. The migration script is a by-product of comparing that diagram with what is deployed. One per-user DbSchema licence covers every engine it supports. Adding a MongoDB cluster to a PostgreSQL estate adds a diagram to the same model, not a line to the contract. The free Community Edition has no time limit. It connects, reverse-engineers, draws diagrams and runs the SQL editor on all of those engines.

Liquibase applies changelogs you write yourself
Yes, Liquibase is a schema migration tool. You list every change in a text file called a changelog and keep it in source control. Each change in that file is a changeset. The update command deploys the changesets that have not run yet. According to the Liquibase documentation, you can write changelogs in SQL, XML, YAML or JSON.
Liquibase records what it has deployed in a DATABASECHANGELOG table inside the database. Since version 4.27.0, it also writes a DATABASECHANGELOGHISTORY table. Its documentation lists more than 60 supported databases across relational, NoSQL and graph engines.
Liquibase sells its paid plans by quote only
The paid product is Liquibase Secure, in four plans: Starter, Team, Business and Enterprise. None of them shows a price. Each has a "Get a Quote" button instead. The plans scale by database types and database targets, not by seats:
| Plan | Database types | Database targets |
|---|---|---|
| Starter | 1 | 250 |
| Team | 1 | 500 |
| Business | 2 | 750 |
| Enterprise | 4 | 2,000 |
What to see: a second database engine moves you up a plan, whatever the size of your team.
Starter is only for companies under 1 billion USD in annual revenue. The pricing page also says that every plan requires a Professional Services package. DbSchema is priced per user instead. The number of engines and databases you point it at does not change the bill.
Flyway runs SQL files in order, DbSchema compares a model
Flyway's model is plain. You write SQL migration files. Flyway scans the filesystem or the classpath and applies the pending files by version number. It records each one in a schema history table, so no file runs twice. Drift detection depends on the edition. Redgate documents the check -drift command as a Flyway Enterprise feature. It compares a target environment with a snapshot and can stop a deployment.
DbSchema takes the other route, and its drift review is in Pro, not in a top tier. You design tables, change data types and draw foreign keys in the .dbs model file. No live connection is open, so nothing reaches a server while the change is still under discussion. When the change is ready, you connect. DbSchema reads the current structure over JDBC and lists the differences object by object. Only then does a script exist. To compare two live environments instead, see finding schema drift between environments.
DbSchema sells Pro per user, perpetual or monthly
One installation edits diagrams for every supported engine. The model file commits straight into Git, with no cloud service involved. DbSchema is licensed per user, as a perpetual licence or a monthly subscription. The purchase page shows the prices in your currency, on separate tabs for Business, Personal, and Universities & Students.
On top of the free Community Edition, Pro adds schema synchronization, saving the model to a file, the documentation export, the Query Builder and relational data browsing.
Generate the script from a comparison, not by hand
In a code-first workflow, you write the file yourself. That is a versioned SQL migration for Flyway or a changeset for Liquibase. Then the CLI applies it. Getting the statements right is your job, including the constraint order on a table that other tables reference.
DbSchema replaces that drafting step with a comparison. You change the model and connect to the target. DbSchema reads the target's structure over JDBC and compares it with the model. It lists missing tables, altered columns, changed data types and index differences.
Generate the migration script in five steps
- Open the
.dbsmodel file and make the change on the diagram. This changes the model file only. - Connect over JDBC to the target development, staging or production database.
- Open Schema → Synchronize Model with Database and choose the target schema or catalog.
- Read the generated SQL statements in the Sync Dialog, and edit them there if you need to.
- Click Execute to apply the changes, then commit the script and the model file to Git.
Only step 5 touches the server. Everything before it happens in the model file and the dialog. DbSchema also exports database documentation from the same model, so the docs move with the migration. To split a generated script into safe and risky statements, see turning a schema diff into a safe migration script.

A migration script records how the schema changed
A migration script is an ordered set of DDL statements that moves a schema from one version to the next. It creates tables, alters columns, adds constraints and drops indexes. Kept in version control, it records how the database reached its current shape. A colleague can then rebuild that shape on a fresh environment without guessing.
A script touches a short list of objects: tables, their columns, the foreign keys between them, and the constraints and indexes that protect them. A schema comparison walks the same list. So a generated script and a hand-written one describe the same four things. The difference is that DbSchema derives the statements from two structures it has read. A foreign key you forgot to mention still shows up in the diff.

Run the script on staging before production
Promote the change through your environments. Apply and check the script on a local development database first. Then run it on staging, where the integration tests run. Run it on production last, inside a deployment window. Timing matters as much as correctness. A statement that rewrites a table takes as long as the table is big. Staging with realistic data volumes is where you find that out.
Before the production run, take a backup and confirm it restores. During the run, read the statements in the Sync Dialog and edit anything before you click Execute. DbSchema shows you the script instead of applying it silently. Afterwards, check that the structure matches the model and that the application still connects. Then commit the model file and the script together, so the next diff starts from what was deployed. For the wider category, see what a database migration tool does.
Download DbSchema at https://dbschema.com/download.html and reverse-engineer a database you already run. Change one column on the diagram, and read the migration script it generates before anything reaches the server. Schema synchronization is a Pro feature, and the 15-day trial includes it.
FAQ
What is the difference between data migration and schema migration?
Schema migration changes the structure and leaves the records alone. Data migration moves the records. DbSchema also handles moving a structure to another engine. Change the RDBMS field in Model → Model Properties, and DbSchema remaps the data types. A model designed for MySQL can then be created on PostgreSQL.
What databases does Flyway support?
Redgate publishes the list for each Flyway version. The installed version prints it with the flyway list-engines command, and -outputType=json gives a machine-readable list. One per-user DbSchema licence connects to every engine DbSchema supports. Its model-to-database review, a Pro feature, covers all of them.
What are the components of a database schema?
Tables, their columns, the foreign keys between them, and the constraints and indexes that protect them. DbSchema reads all four when it reverse-engineers a database. In Schema → Compare Model with Database, you give each difference one of three answers: update the model, push the change to the database, or skip it.
How much does Liquibase Starter cost?
Liquibase does not publish a price. Every plan, Starter included, is quote-only, and Starter is only for companies under 1 billion USD in revenue. DbSchema publishes its prices on the purchase page, with tabs for Business, Personal, and Universities & Students.
How does Liquibase know which changes it already applied?
Liquibase identifies a changeset by its author and id attributes plus the path of its changelog file. It runs each changeset once, unless the changeset carries runAlways or runOnChange. DbSchema answers the same question differently. It compares the model file with the live structure each time you synchronize.
Can I generate database migration scripts without writing SQL?
Yes. DbSchema writes the script from a comparison. It compares the .dbs model file with the target and generates DDL for the differences you select. For a schema you designed offline and never deployed, Schema → Create or Upgrade Schema in Database generates the whole DDL. It runs once you have read it. Schema synchronization is a Pro feature.
Sources
- DbSchema purchase page
- Liquibase documentation, "What is a changelog?" and "What is a changeset?", read 5 November 2026
- Liquibase documentation, supported databases, read 5 November 2026
- Liquibase Secure pricing page, read 5 November 2026
- Redgate Flyway documentation: migrations, getting started, check drift and list-engines, read 5 November 2026
Generate the migration script from your design
DbSchema compares your model with the target database and writes the DDL for the differences you select. You read every statement before it runs. Schema synchronization is a Pro feature; the free Community Edition connects, reverse-engineers the schema and draws the diagram.