Possible problems when transferring a site to a new hosting

[subornaakter24]

Unforeseen complications are possible, some of them are easily fixed, while others cannot be solved, and all that remains is to try to minimize possible losses. Here are the types of problems that can happen:

The resource content has been completely lost.

Be sure to start the entire transfer process by manufacturing email list creating a backup copy, even using an old CMS. WordPress has a special plugin for this, and Drupal has an additional module.

You can get access data to the server control panel from the hoster and use it to perform backup copying without using the engines. To do this, go to Files, and then to the Backup Manager. Perform archiving and download copies of the database and files that are relevant at the time of the operation.

Check the correct operation of the copy by restoring it on the local server first. Involve the technical support service if there are problems. Do not transfer the site to a new hosting until you have a working copy of your web site.

The resource structure and URL have changed.

The understandable URLs most often change when switching to another engine (and when changing the site structure too), because different CMS generate different “URLs”.


It is very important that when transferring a site to a new hosting, the URLs are displayed correctly.

Redirects are difficult and take a long time to set up.

This is due to the URL change. And if your web resource is not very large, then performing page-by-page redirect setup will not be difficult, which cannot be said about the situation when the site has hundreds of pages. In this case, the process will take a lot of time and effort.

For example, the old engine issued the following URL for the section "Smartphones and phones" (where all phones, smartphones are collected): example-shop/catalog/phones/. And for each product position there was an address of this type: example-shop/catalog/phones/phone1.

If, when changing the engine, you have separate sections for phones and smartphones, then the product positions will have URLs of different types, for example, example-shop/catalog/phablets/phablet1 or example-shop/catalog/smartphone/smartphone1. Manual correction of redirects will be required in them.

The old and new engines have different functionality.

A simple example: you want to move a store from WordPress to OpenCart. The first platform has a good blog, while the second only has an "Articles" section. You will need to add a special module for blogs to OpenCart, attach a subdomain with a WordPress blog, etc. In addition, you will have to purchase and invent something else to expand the functionality and other components of the resource.

Design violation.

If the site design was initially formed according to a template, then when changing the engine it will not be saved. In fact, this is not such a problem, you will just have to pay a designer to recreate the desired look of the site, or look for a similar template.

Thus, if the old site no longer meets your requirements, weigh the pros and cons and start transferring the site to a new hosting.