I’ve manually trigger the proper db upgrade processes. You should be good to go now. The source of the issue is that the plugin files were newer than the database structure. Whatever method that was used to upgrade the plugin files did not trigger the db upgrade routine … you would see an admin notice when trying to visit one of the Connections admin pages notifying to proceed with the database update. When you used AIO WP Migration it moved the out of data database with the current plugin file. I probably worked just fine.
My thought is the disconnect started with the dev site. How was it created? Was it pulled from the live site then changes done before being pushed back to live? Or, was it an existing dev site which happened to have an older version of the Connections tables where the plugin file were updated to the current release and then push live?