Knowledgebase

Customers commonly migrate a website when changing hosting providers, upgrading services, moving between hosting platforms or consolidating website services. A careful migration helps reduce downtime, broken pages, email disruption and other service issues.

Important: Apexhost services are generally self-managed unless a separate management arrangement applies. Customers are responsible for managing website files, databases, DNS records, application settings and related service configuration within their hosting environment.

A website is usually made up of files and, in many cases, one or more databases. The files may include HTML pages, PHP scripts, images, themes, plugins, style sheets and application code. The database may store content, settings, user accounts, product information or other application data.

A successful website migration also depends on the hosting platform. Linux hosting is generally used for WordPress, PHP, MySQL and many open-source applications. Windows hosting is generally used for websites or applications that rely on Microsoft technologies such as ASP.NET or MSSQL. Moving a website between Linux and Windows hosting may require more than a simple copy because the application may not be compatible with the new environment.

DNS, or Domain Name System, also plays an important role in a website migration. DNS records tell internet users where the website and related services are hosted. If DNS is updated incorrectly, the website may stop loading or email services may be affected.

Note: A domain transfer is not the same as a website migration. Moving a domain between registrars does not automatically move website files, databases, DNS zones or email services.

Before starting a website migration, make sure you have the following:

* Access to the correct Apexhost Client Area account.

* Access to the current hosting account or server where the website is presently hosted.

* Permission to manage the website, domain and DNS settings on behalf of the owner or organisation.

* A current backup of the website files and any related databases.

* Login details for the relevant control panel, such as cPanel or SolidCP, where applicable.

* A clear understanding of whether the website requires Linux hosting or Windows hosting.

* Any SSL certificate, DNS and third-party service details connected to the website.

Warning: Do not cancel the old hosting service before the website migration has been completed, tested and confirmed as working on the new service. Cancelling too early may remove access to files, databases or DNS information needed for the move.

Every website migration is slightly different, but the process usually follows these stages:

1. Review the current website and identify what needs to be moved, including files, databases, DNS records, SSL certificates and application settings.

2. Confirm that the new Apexhost hosting service is suitable for the website’s technical requirements.

3. Create a full backup of the existing website and database before making any changes.

4. Upload or restore the website files to the new hosting environment.

5. Create or restore the required database and update any database connection settings used by the website.

6. Test the website on the new hosting service before changing live DNS where possible.

7. Update the domain’s DNS settings or nameservers so traffic points to the new hosting service.

8. Allow time for DNS propagation and re-test the website after the changes become visible.

9. Confirm that SSL, forms, logins, plugins, scripts and third-party integrations are working correctly.

10. Keep the old hosting active until you are satisfied that the migration is complete and stable.

* Website files such as themes, plugins, media and application code.

* Databases used by WordPress, custom applications or eCommerce systems.

* DNS records for the website and connected services.

* SSL certificate configuration.

* Cron jobs, scheduled tasks or application-specific settings.

* Email-related DNS records such as MX, SPF, DKIM and DMARC if they are linked to the domain.

* Test the website carefully after migration, including forms, contact pages, admin logins, shopping carts and media files.

* If the website uses a content management system such as WordPress, confirm that file paths, URLs and database details are correct after the move.

* If the website is changing between Linux and Windows hosting, confirm application compatibility before migration.

* Keep a copy of the old DNS records before making changes, especially if email or other third-party services also use the domain.

* DNS changes can take time to propagate. During this period, some visitors may reach the old hosting environment while others reach the new one.

* If your domain uses external email hosting, make sure website-related DNS changes do not remove or overwrite the email provider’s required records.

[Screenshot: Apexhost Client Area hosting service page]

[Screenshot: Login to Control Panel button on the service details page]

This can happen if DNS is not pointing to the new hosting service, the files were not uploaded correctly, or the website configuration is still referencing the old environment. Check the DNS settings, confirm the website files are present and review application configuration files such as database connection settings.

This usually means the database was not imported correctly, the database user does not have the required permissions, or the website configuration is using incorrect database details. Recheck the database name, username, password and server settings used by the website.

This is often caused by DNS propagation. After DNS changes, internet providers and devices may take time to refresh cached records. Allow time for propagation and test again later.

This can happen if DNS records were changed without preserving the existing MX and related email records. Review the current DNS zone and confirm that the required email records are still present and correct.

Check the technical requirements of your website or ask your developer. WordPress, PHP and MySQL websites usually use Linux hosting. ASP.NET and MSSQL websites usually require Windows hosting.

Not always. A website migration moves the website and related hosting configuration. A domain transfer is a separate process that changes the domain registrar.

It may be possible to reduce or avoid noticeable downtime if the migration is planned carefully and DNS is changed only after the new site has been tested. However, some disruption can still occur depending on the application, DNS timing and migration method.

Yes, provided the hosting service is suitable for the site’s requirements and the files, database and configuration are moved correctly.

Sometimes, but not every website is compatible with both platforms. Confirm the application requirements before changing platforms.

* Website Hosting Explained (Getting Started)

* Choosing the Right Hosting (Getting Started)

* Linux Hosting (Web Hosting)

* Windows Hosting (Web Hosting)

* Managing Services (Apexhost - Client Area)

* Managing Domains (Apexhost - Client Area)

* Domain Transfers (Domains)

* Logging In (Apexhost - Client Area)

If you require further assistance, please contact Apexhost Support at support@apexhost.com.au.