In theory, manual WordPress migration should be a breeze. All you have to do is export your existing database and then import it to the new host, in addition to transferring all of your files there and configuring everything to your liking. In reality, manual WordPress migration can get pretty messy, and that includes failed transfers and missing files.
If you want to spare yourself all that, there are plenty of migration tools, such as CMS2CMS, which allow you to simplify the migration process. CMS2CMS even enables you to see where your existing content will wind up on the new website, thank its Advanced Mapping feature. It also supports all major CMS platforms, such as WordPress, Joomla!, Wix, Squarespace, Drupal, Blogger, and many others.
However, while manual migration can be a pain, it does allow you to control every single aspect of the process. In order to help you avoid the most common problems, we share a few tips with you. Check them out.
- phpMyAdmin Time Out during Database Export/Import
While phpMyAdmin tool is useful, it does struggle with larger databases, and it will most likely time out at some point. The solution for this would be to install and use WP-CLI, which would allow you to simply use SSH commands. In order to back up your database, all you have to do is type:
EXPORT: wp db export for-transfer.sql
IMPORT: wp db import for-transfer.sql
- Files Taking Too Long to Download/Upload
If you have had your WordPress website for a while, you would be surprised by how much multimedia can pile up over the years. Downloading your files via FTP and then doing the same thing while uploading them to a new host can seem like a never-ending task. To speed it up, archive all of your files into one and transfer it. Then, you can download it to your new server. As mentioned before, you are going to need to install WP-CLI to do this.
- File Permission Issues
Although file transfer is easier than database migration, you still need to worry about file permissions, because they too get transferred. The problem is that file permissions can pose a potential security risk on your new host, which is why you might encounter an Internal Server Error. This means you will need to roll up your sleeves and fix the issue via FTP or SSH.
- Letting WordPress Know that the Website Location Has Changed
The location of your website is always saved inside the wp_options table and can easily be accessed via the Settings—>General option. Regardless of where you migrate your website to, WordPress will always look up the address from that particular table. In order to change the URL, add the following lines to the wp-config.php file:
- Missing User Activity Due to Propagation Time
At the end of the migration process, you will need to change the DNS of your website. The issue here is that there needs to be a propagation period, during which the records on DNS servers will be updated. However, you can cut it down by editing the DNS on the old server so that it points to a new domain.
As you can see, migrating your WordPress website to a new host doesn’t have to be a nightmare, as long as you prepare for the process. Using these tips will save you a ton of time and make the transfer a lot smoother. Give them a shot.
Audrey is a proactive journalist who likes to get knowledge, analyze and present fresh ideas. Her background and various interests determine her genuine passion for writing on edugeeksclub.com and other websites. Find her on Facebook and Twitter.