clyphox

What ever the issue with this plugin is I’ve just had to give up on it.
I had to do an emergency migration and its totally fudged all the posts up again, I’ve at least had success the old fasioned way:

mysqldump origdb > wp_orig.sql
cp wp_orig.sql wp_new.sql
perl -pi -e "s+old.domain.com+new.domain.com+g" wp_new.sql
perl -pi -e "s+/public/sites/oldpath+/public/sites/newpath+g" wp_new.sql
# assuming the destination DB and grants are ready just drop it and re_create it with the new variables
mysql -e "drop database newdb;"
mysql -e "CREATE DATABASE newdb DEFAULT CHARACTER SET utf8;"
mysql -uliveusername -plivepassword newdb <~/wp_new.sql

NB: the perl does a search/replace on a file..
I also use it on all files containing matches.. so hard-coded .xml files for some plugins for example sometimes need this.

To find a list of files that need changing:
find /path/to/search -type f -exec grep -l <string> {} \;

I may need to do some tests to verify if this is maybe related to different collation on the DB itself :/ <throws hands up in air>