I like that Flyway uses plain SQL, so there’s no XML or YAML format to learn, and my existing SQL scripts became migrations almost unchanged. The script I test locally is the one that runs in production, and migrations apply in strict order. The schema history table shows which version each environment is on and exactly where a failed migration stopped. I also like that GitHub Actions applies migrations to staging and then production, so our environments stay aligned without anyone touching the database manually or me comparing tables by hand before a release. Review collected by and hosted on G2.com.

My main issue with Redgate Flyway is the gap between editions. Undo migrations and dry runs, which I’d expect in a production setup, only come with the paid tiers. After trying the free edition, it was difficult to convince our founders that Flyway offered a real safety net, so I still write rollback scripts by hand for risky changes. Review collected by and hosted on G2.com.