Mert Yaz?c?o?lu

The first one is actually easier and is the method that is intended to be used but your FTP server must be working properly.

The second one is an alternative method in which you trick WordPress Move to just make it generate the backup files.

I thought you already had backups of your current installation generated by WordPress Move.

Now, you have two options:

1) Letting WordPress Move handle the transfer of your backup files by properly configuring the plugin.

2) Transferring the backup files yourself.

For the first option, the server you are migrating to needs to have a working FTP server. If you have one running, enter the FTP details of the server you are migrating to, on the WordPress Move configuration page of your current WordPress installation. For the remote backup path, you need to enter the full path to the /wordpress-move/backup/ directory on the server you are migrating to, starting from the top directory that your FTP account has access to. If these sound complicated, follow the instructions on the next paragraph.

For the second option, fill in the configuration page of WordPress Move with incorrect data, so that WordPress Move stops asking you to fill in the fields on the configuration page. Once done, go to Migration Assistant and start the migration. It will be able to create backup files but will fail to connect the target server as we provided incorrect data. Go to Backup Manager and download the backup files by clicking on their names. Open your FTP client and connect to the server you want to migrate to. Then, upload your backup files to the /wp-content/plugins/wordpress-move/backup/ directory on your new server. Once you finish uploading them, you can use the Restore option of the Migration Assistant on the server you are migrating to, to finalize the migration operation.

You can upload your backup files to the /wp-content/plugins/wordpress-move/backup/ directory on your new server. Once you finish uploading them, you can use the Restore method to finalize the migration operation.

Yes, it is fully compatible with WordPress 3.5!

Thanks for reminding that, forgot to update that bit ??

That happens when you are not giving the right Remote Backup Path.

The path you are giving to should start from the highest directory that your FTP account has access to. The best way to figure it out if you do not know already, is using an FTP client (such as Filezilla), navigating to the /wordpress-move/backup/ directory and copying the full path that your FTP client shows.

As long as your servers and your domain name are configured appropriately, then yes, you can.

I believe either you solved the problem or rolled back.

Is it possible that you forgot to fill in the Change Domain Name (Optional) section on the migration page?

Not at all. Feel free to do whatever you want with it, as long as it conforms to the terms of GPLv2 or GPLv3 ??

Sorry for the late reply.

This is by far the best support request I have ever seen ??

As tofrugal said, looks like you did not wait for the file tree to load, so the plugin was unable to create file backups of the system. The reason you saw a blank screen is that WordPress is trying to load a theme that doesn’t exist on your new installation (because the plugin could not create file backups and transfer the files on the server you are migrating from).

Sincerely sorry for the late reply.

Happy to hear that you solved it. An interesting problem that should not have happened. Will definitely look into that!

Thanks for sharing your experience with us, much appreciated! ??

Sincerely sorry for the late reply.

The JS file tree is not capable of handling too many files. Will provide another option for installations that have too many files, in the upcoming releases.

Sorry for the late reply.

You can always add the following to the wp-config.php file if the URLs do not work as expected.

define( 'WP_HOME', 'https://www.nicolamalkin.com' );
define( 'WP_SITEURL', 'https://www.nicolamalkin.com' );

Sincerely sorry for the late reply.

One can always add the following to the wp-config.php file if the URLs do not work as expected.

define( 'WP_HOME', 'https://www.yourdomain.com' );
define( 'WP_SITEURL', 'https://www.yourdomain.com' );

Sorry for the late reply.

You are not supposed to create the backup folder, it already exists. The backup directory is inside the plugin directory which is /wp-content/plugins/wordpress-move/.

The error message could be more specific and helpful, will look into that.

Sorry for the late reply.

I think that might be the chunk size setting messing it up. Did you try altering that and trying again?