The database migration feature in Bitbucket should provide a "dry run" option and perform a simulated migration from the source to the target database listing all table that could potentially causing any issues during the actual migration.

At this moment the database migration for a large database takes a long time for a 40gb database it takes up to 20 hours to complete, and if any table has any data that the migration is not able to parse or fix, it will fail the migration, rolling back to the source database.

This is very frustrating, because after failing the only option available is to check the logs for that particular error and attempt the migration once again, only for it to fail again after 20 hours on another table.

Having a "dry run" would give an admin the information to check all the tables that could be of any concern, making the task of troubleshooting and fixing it way easier for admins and DBAs.