Back to Posts List

Most Common Problems During Migration of WordPress

Share this article




Posted on November 14th, 2019 by Connie Benton in Guest Posts

WordPress migration

There is no doubt that WordPress is the most trusted CMS. It has a large community of developers, a variety of plugins, and a great potential for new features and SEO.

Why you may need to Migrate WordPress

Sometimes, a user needs to migrate their WordPress site to a new domain, hosting, or HTTPS address. Maybe the hosting provider does not meet all the user’s needs or standards like uptime, or pricing. 

Another thing is privacy. If you want to make your WordPress website private, but the policies of your old server provider do not fully correspond to your requirements, you may also opt for WordPress migration.

There may be one or many reasons, but it is always something pretty common.

The Most Common Issues Are Likely to Happen

It may seem that manual site migration is just a piece of cake, and nothing unexpected can occur while you are migrating all those files from the database and configuring them by your needs and liking. However, if you are not aware of possible issues and accidents, WordPress migration can turn into a total mess and chaos with all those file losses and failed transfers.

Even such an advanced migration tool as CMS2CMS will not help much in avoiding or controlling the common problems. That is why try to look through the following tips for possible issues and ways of solving them.

File Loss

The most frequent issue while migrating WordPress is losing files. This is rather frustrating because you will need to go back to some earlier version of the website if something goes wrong. In this case, you will have to spend extra time, cost, and effort to cope with the problem.

The essential tip on how to avoid file loss is to make a backup of the website before migrating it. Sometimes, the host makes backups automatically. If not, you can use some WordPress plugins, such as Duplicator or UpdraftPlus, which have been developed for this purpose.

You may also opt for a manual backup. Choose the home folder located in the file manager (usually, on the host website), and pick out the public_html file. The next step is compressing it to zip. Then, you will have to transfer this file to the place of storage (that may be either the hard drive or server). To export the whole database, use phpMyAdmin, and transfer it as well to the storage place.

Of course, after using your website for just a while, it becomes rather extended, so it may take ages to download the database on your computer. You may prefer to download the backup files to the new host instead. To save time and effort, you may also create a compressed archive in the form of one big file, and downloading will become much faster.

Images issues

It is also quite common that after completion of the migration process, you find out that the images do not appear in their right places or appear but are broken or distorted, or even they do not provide the correct linking. It means that something went wrong during the media file upload.

The bad news here is that you will need to upload the file once again from your computer or old server. Simple re-upload sometimes may do magic, and the broken images get fixed.

Permission Issues

The discrepancies are caused by the difference in terms and policies between the old and new hosts. That results in an error for some files which have been transferred. For example, if your former host permitted anyone of full access to specific files of your site, but the new host does not support such open permissions, the problem emerges after transferring such files.

Usually, you are allowed to change permissions on the new host. And you may opt for changing permissions on the old server as well by the new server requirements. After the policies have been changed, you can start transferring the file.

Location Issues

You may start thinking that you have just completed the migration process. However, the database you have migrated may still carry some details about the old server. That results in the downtime during migration because the URLs have not been changed, and they lead visitors to your former hosting. It means that the visitors will see nothing but a 404 error.

Make sure whether WordPress knows that you have changed the website location so that the redirection issue could not occur. To control the WordPress awareness of the new location, check the settings. You will have to go to General Setting to examine the URLs for the domain name. If they display different names, change them, and insert new details in the wp-config.php file.

Activity Loss

It happens that the previous visitors’ comments or other activities are lost during the time of propagation at the final step of the DNS change. The propagation time is the period in which all the DNS servers in the world need to update records about domain names. During this time, all the activities are not recorded, so they are lost.

To decrease the activity loss, you will need to diminish the propagation time. To achieve that, you can work with the DNS Zone on the old host to direct every record to the new one. In this case, even if visitors are referred to the old server, they will be led to the new IP address with the right content.

Conclusion

It is impossible to describe all the problems that you may come across during WordPress migration. You can easily find all the essential information about them and the ways of their solution by further research.

To conclude, it is worth saying that migrating the WordPress website to a new host is not rocket science. You can make this process much easier if you are prepared for possible issues beforehand. You can make this transfer a lot smoother by using these tips.

Connie Benton

Connie is a chief content writer, guest contributor, and enthusiastic blogger who helps B2B companies reach their audiences more effectively. With an emphasis on organic traffic and conversion, she takes big ideas and turns them into highly practical content that keeps readers hooked.

comments powered by Disqus