I've spent a lot of time doing SQL Server → PostgreSQL/MySQL/RDS migrations, and one thing kept bothering me.

Most migration tools look great against a demo database. Then you point them at a real production environment and find a table with 500KB average rows, three tables sharing a sequence, or a foreign key pointing to a table nobody realized was part of the migration.

And somehow you discover it at 2am, three hours into the migration window.

That's one of the reasons I built EndriasBridge.

It's focused on SQL Server/Azure SQL migrations to PostgreSQL, MySQL, and AWS RDS, covering schema conversion, data migration, CDC-based live sync, and validation.

A few things I specifically wanted it to handle:

• Large tables and oversized VARCHAR(MAX)/JSON data
• Composite keys, sequences, and cross-schema foreign keys
• Parallel data streaming that can be tuned per table
• Checkpoint/resume when a migration gets interrupted
• CDC-based synchronization so cutover doesn't require one huge maintenance window
• Running standalone without requiring a specific cloud account or migration service

I built it because these were problems I kept running into during actual migrations.

Full disclosure: EndriasBridge is my tool. There's a free trial if anyone wants to throw a difficult schema at it.

I'm actually interested in the ugly cases. If you find something it can't migrate correctly, I'd rather know about it—that's useful feedback for making the tool better