**Version numbering** is clear and consistent. The product is easy to use, with an intuitive and easy-to-understand user interface. Integration with Azure DevOps is seamless, and performance is significantly better than SQL Source Control. The pricing provides an acceptable return on investment (ROI). The onboarding process was straightforward, and the support team has been excellent. We currently make limited use of the AI features, as we already have independent AI platforms in place. Review collected by and hosted on G2.com.

No major issues encountered at this time Review collected by and hosted on G2.com.

Redgate Flyway is a leading database migration tool that uses a “schema-as-code” approach to help manage database changes efficiently. It integrates smoothly with CI/CD pipelines to automate deployments from development through to production. Flyway also supports over 50 database management systems, helping ensure consistent and reliable database schema evolution across a wide range of environments. Review collected by and hosted on G2.com.

What I dislike about Redgate Flyway generally comes down to a few key areas that can slow development workflows and add unnecessary overhead.

First, the learning curve can feel quite steep, especially for teams that are new to migration-based database management. The documentation sometimes seems insufficient, which makes it harder to understand migrations and manage them effectively. As a result, developers can get frustrated and the ramp-up period can take longer than it should.

Another major drawback is the lack of certain features, particularly when important capabilities are limited to paid editions. This “paywall fatigue” comes from seeing functions that feel like they should be standard—such as undo migrations, dry runs, or more advanced reporting—locked behind higher-priced tiers. That can be difficult to justify, especially for smaller teams or projects working with tight budgets. Review collected by and hosted on G2.com.

What I really like about Redgate Flyway is how dead simple it is. There are no new languages to learn and no complicated setup—just plain SQL scripts. That makes it really easy to get started and to get the whole team on board.

It also plugs right into CI/CD pipelines like it was made for it. Deployments stay consistent, predictable, and smooth from development to production. And the migration tracking is an absolute lifesaver, because it helps prevent environments from drifting out of sync. Review collected by and hosted on G2.com.

It’s overly expensive. The UI can feel a bit laggy when working with large databases. It works well with legacy databases, but it should catch up with modern databases. Review collected by and hosted on G2.com.

What I like most about Redgate Flyway is how simple and developer friendly it is. It doesn’t require learning any new language or complex setup you can work directly with SQL scripts, which makes it very easy to get started and adopt within a team.

I also appreciate how seamlessly it fits into CI/CD pipelines. It brings a lot of structure and consistency to database deployments, ensuring that changes move smoothly from development to production without surprises. The built-in version control through migration tracking is another big plus, as it helps avoid issues like environments going out of sync. Review collected by and hosted on G2.com.

One thing I find a bit limiting about Redgate Flyway is its handling of rollbacks. Undoing changes isn’t always straightforward, especially in more complex scenarios, and some of the more advanced rollback capabilities are only available in the paid versions. Review collected by and hosted on G2.com.

I appreciate Redgate Flyway for its simple and reliable version control for database migrations. The seamless integration with CI/CD pipelines is a huge plus, as it automates deployments and ensures the same migrations have been applied consistently across all environments. Version control makes it easy to track and manage database changes. Moreover, the initial setup was straightforward due to clear documentation, making it relatively easy to integrate with our CI/CD pipelines. Review collected by and hosted on G2.com.

Initial setup and configuration was bit complex for new users and troubleshooting the migration issues could be improved to be straightforward with meaningful error messages to save time for users Review collected by and hosted on G2.com.

Initial setup and demos were performed by and with the Redgate Team, and they helped us all of the way.

Flyway helps our DBA team keep all databases up to date by using the Deploy functionality. It’s really simple to make a change in the development database and then apply that same change to customer databases.

We have integrated Flyway into our TFS pipelines flawlessly. This has removed the need of DBA intervention when another department wants to apply the latest database updates.

Once you have been trained in the available functionality, the performance of Flyway is outstanding. Its easy to see if there are any new updates to download before deployment, so you never miss a beat. Review collected by and hosted on G2.com.

There was a little issue in one of the newer updates. When launching Flyway after the update, it asked to convert the Toml file as a function had been deprecated. Once this was done, I received a licencing error which wasn't present before the conversion. Review collected by and hosted on G2.com.

Flyway was the missing piece for our one click deployment. We had pipelines for the code part of the release, but the database side continued to be our bottleneck as scripts were having to be run manually. Review collected by and hosted on G2.com.

There were several database objects that were not supported at the time that required cleanup on our side. Some of these were technical debt in the form of unused and orphaned database objects, but it did take time to track them all down and determine if they could be removed, or needed updating. I believe since then you can set Flyway to ignore certain database objects, so it is likely a non-issue moving forward. Review collected by and hosted on G2.com.

Flyway is great because it uses plain SQL scripts for versioning, making it incredibly easy for developers to learn and adopt.

It also ensures environment consistency by using a schema history table to track and automate migrations across your entire CI/CD pipeline. Review collected by and hosted on G2.com.

The "Paywall" Fatigue: Many features that used to be standard (or feel like they should be) are now locked behind Teams or Enterprise editions. For example, Undo migrations, dry runs, and certain advanced reporting tools require a paid license, which can be a tough sell for smaller teams. Review collected by and hosted on G2.com.

I like the simplicity of this tool. It uses plain SQL, which makes it very easy to work with and understand. At the same time, it also includes advanced features, such as drift detection, and it supports various database types. it supports integration of various databases. the performance is very good compared to some other tools i have used Review collected by and hosted on G2.com.

there are some features blocked by paywall and no built in undo functionality. hence need to manually rollback Review collected by and hosted on G2.com.

What I like most is that migrations are just plain, version-controlled SQL files. The V1__, V2__ naming makes the order of schema changes obvious, and running flyway migrate applies exactly what's pending, so every environment lands in the same state. It fits into a CI/CD pipeline with little effort, the schema history table gives a clear audit trail of what ran and when, and since it supports so many databases we didn't need a different tool per project. Being SQL-first keeps the learning curve low. Review collected by and hosted on G2.com.

The most useful features (undo/rollback, dry runs, drift detection) sit behind the paid Teams and Enterprise tiers, so the Community edition can feel bare-bones for a growing team. Initial configuration (flyway.conf, placeholders, per-environment settings) takes some trial and error, and the error output on a failed migration could be clearer about what went wrong. The desktop/UX side is also less polished than the command-line experience. Review collected by and hosted on G2.com.