20 Years of SQL Migration Tools Offer Six Design Lessons for NoSQL Migrators

A developer building a NoSQL-to-SQL migration tool in 2026 reviewed decades of design decisions behind established SQL tools like Flyway, Liquibase, and dbmate. Key lessons include using filename-based versioning for predictable execution order and halting all operations on failure rather than silently continuing, to protect production data. The review also highlights the value of writing a human-readable schema file after each migration, keeping the tool deliberately minimal to avoid platform creep, and requiring developers to write their own rollback scripts instead of relying on unsafe automatic undo logic. A final principle separates the migration changelog from the execution engine, ensuring proposed schema changes can be reviewed calmly in a file before any database is touched. The author notes that despite these patterns being open-source and battle-tested, NoSQL migration tools have largely been built from scratch without borrowing them.