This article addresses common mistakes after migrating a website from a competitor, either manually or automatically with the basic or expert mode migration tool.

In this article, you will learn:

• How to avoid problems with migration
• Common issues
• Frequently asked questions

The most common sources of site migration issues that you can avoid are:

• PHP differneces and missing modules
• Migrating the database and configuring the connection
• Blocked .htaccess commands
• File paths (open_basedir error)

If your website uses PHP (common with WordPress, Joomla, Drupal, …), check the configuration with the current provider and set it on the Webhosting you want to migrate to before performing the migration.

The PHP version is especially key. Make sure that the old and new Webhosting are using the same version of PHP.

Verify or change the Webhosting PHP version according to the instructions Webhosting – PHP configuration.

Next, check that the Webhosting parameters correspond to the requirements of the content management system or plugins. You can find parameters set by the service plan, which you cannot modify in the customer administration panel, on the Webhosting plan comparison page.

Before importing a database, make sure that your website supports the version of the database running on the Webhosting. You can find out by following the Webhosting – Database instructions.

If you use automatic migration, the system will attempt to update the configuration of the sites to the new database credentials.

After performing the migration itself, but before launching the site, make sure that the database is:

• successfully imported and
• configured on the website.

Check the .htaccess files if they do not contain prohibited commands from the list in the guide Webhosting – .htaccess.

To disable blocked commands, place the # at the beggining of the problematic line, e.g. #Options -MultiViews.

Incorrect file path settings usually lead to the open_basedir error.

With some content management systems, you may come across addresses in the database that contain the internal paths of the original web hosting service. For WEDOS hosting, a path may look like this: /data/web/virtuals/123456/virtual/www/domains/wds-test.eu.

Update these paths to the correct ones, or update them according to the instructions for the content management system or plugin.

Common issues with migrated websites include:

• The original website is displayed
• Website contains error messages
• Files aren’t loading

Issue: After the migration, the website is still displayed on the original hosting.

Cause: The most common cause is website content caching in the browser, or incorrect DNS settings.

Solution: Press Ctrl+Shift+R to reload the website without browser cache.

If the problem persists, perform a DNS check:

• Find out which DNS servers the domain is using and if the IP address changes of type A records (or AAAA if you are using one) directing to the new hosting have propagated. DNS record propagation usually takes tens of minutes to hours, DNS servers can take up to 48 hours.
• Check that you do not have the old IP address of the listed in your system’s hosts file.

Issue: The website works, but it shows errors that were not there on the original hosting.

Cause: Some web hosting servicess may have error display disabled, WEDOS Webhosting enbles error display by default.

Solution: We recommend fixing the errors according to the instructions of the website creator or content management system or plugin support. If the error cannot be fixed or the code that causes it can’t be shut down, you can turn off error display according to the Webhosting – PHP Configuration guide. However, we advise against this course of action.

Issue: Some files are not loaded, Errors 403 and 404 appear.

Solution: First, make sure that the files are properly migrated and that you are not loading them from inaccessible external sources.

In the case of Error 403, correct file permissions according to the instructions Webhosting – File Management.

If the original site only used HTTP and now you have HTTPS enabled, make sure the site loads all resources over this secure protocol, files with http:// addresses are blocked by https.

For more information about Errors 403 and 404, see the corresponding articles:

• Webhosting – Error 403: Forbidden
• Webhosting – Error 404: Not found

Question: Can you migrate the site and get it up and running for me?
Answer: Yes, we also offer a paid transfer service from competitors.