Toby

Unfortunately I was advised against sharing the internal development build I received. The comment on the internal ticket from last month said that they were planning on getting the fix released in the next version of the plugin, which was due to come out at the end of last month. It looks like they missed this since the latest version is still last year.

I’ve been sent an internal, unreleased build of the plugin to test, which apparently includes a fix to my issue.
I’ll be testing this before the end of this week and reporting back to the ticket if it works.
I don’t know if I’m allowed to share it publicly, so I reccomend raising a ticket yourself and asking for a copy to test with.

Prashant from their support team was able to help me with this single transfer by sending me back a modified version of my archive file, and then it worked when I enabled the Legacy option.
However, I have many other sites to migrate in this way, so I’m trying to find out what he modified inside my archive, so that I can both apply it to my future MySQL > MariaDB migrations, but also post back here with the solution for others to use.
I haven’t had time to compare the DB exports just yet, but it may have been something in there that was modified.
It would also be nice to see the plugin updated to address or correct this issue or bug (if it is indeeed a bug or change that can be made to support these MySQL to MariaDB migrations), so that future exported archives don’t have this same issue.

@corylamleorg, perhaps you could chase up on ticket E4S-M1N-9Y3X I created? I haven’t heard anything since last Thursday. Thanks!