Those two tools were Transmit & WP Sync DB

I’m sure there are more efficient ways of doing this (tar or rsync commands) but I wanted to have some of the fine-grained control that comes with a GUI and that elude me when using the command line.

I don’t get to use Transmit enough on my Mac and that felt like reason enough to use it. Plus it’s nice to look at and the iOS version has been one of my favorite new apps for front-end work on an iPad (can’t wait for new Diet Coda).

I know Transmit can simultaneously transfer multiple files but I didn’t realize that when copying a folder (like the /wp-content folder) Transmit would treat it as one file and, therefore, download/upload each file within the folder in order, one by one. So a ⌘ + a later I’m dragging and dropping 3K+ files at a time, folder by folder.

It took some babysitting but it was super fast.

With all the media files transferred it was time to import the database from the old site to the new. I have used BackWPup Free before for this task. It downloads a .sql file for you to import to the new database using phpMyAdmin or similar. While looking for better tools to keep local, staging and production databases in sync I found WP Sync DB which appears to be a free fork (albeit slightly modified) of WP Migrate DB Pro. I wanted to give it a try and I was happy I used it here.

The Github page gives you all the instructions so I won’t repeat them. I chose to use the push method from the current live server to the new server. It ran for about 8 minutes. When I reloaded the new server everything looked identical to the old server.

Four years and 13GB with of website moved in about four hours of actual work time.