How to Migrate a WordPress Website from HostPapa to Neurax Host

Overview

This guide explains how to migrate a WordPress website from HostPapa to Neurax Host using a manual migration method. The process involves backing up website files and the WordPress database, transferring them to Neurax Host, configuring WordPress, and testing the website before switching DNS.

This guide uses a sample WordPress installation hosted on HostPapa. The steps may vary depending on the website’s size, configuration, and hosting environment.

Prerequisites

Before you begin, ensure you have:

• An active HostPapa hosting account.
• A WordPress website hosted on HostPapa.
• An active Neurax Host hosting account with cPanel access.
• Access to your domain’s DNS settings.
• Access to the existing WordPress admin dashboard, if available.
• Sufficient storage space for website files and database backups.
• The ability to create a database and database user on Neurax Host.
• Your current WordPress, PHP, email, and DNS configuration details, where applicable.

Important: Do not cancel your HostPapa hosting account or delete the original website before migration and testing are complete. Keep a separate copy of both the website files and database.

Phase 1: Back Up and Export the Website from HostPapa

Step 1: Access HostPapa cPanel

Purpose: Open the hosting control panel to manage website files and databases.

Instructions:

1. Log in to your HostPapa account.
2. Open the hosting dashboard.
3. Locate and launch cPanel, if it is included with your hosting service.

Expected outcome: You can access the hosting control panel.

Step 2: Locate the WordPress Installation

Purpose: Identify the correct website directory before creating a backup.

Instructions:

1. Open File Manager in cPanel.

2. Locate the directory associated with your WordPress domain.

3. Do not assume the website is always located in public_html. Check the domain’s configured document root.

4. Verify that the directory contains WordPress files such as:

   • wp-admin
   • wp-content
   • wp-includes
   • wp-config.php
   • index.php

5. Enable the display of hidden files, if necessary, to check for files such as .htaccess.

Expected outcome: You have identified the correct WordPress installation directory, including relevant hidden files.

Step 3: Create a Backup of Website Files

Purpose: Create a copy of the WordPress files before migration.

Instructions:

1. Open the verified WordPress installation directory.
2. Select the website files and folders, including hidden files where relevant.
3. Use the Compress or Archive option if available.
4. Choose ZIP format.
5. Give the archive a recognizable name, such as wordpress-backup.zip.
6. Start the compression process.

Expected outcome: A ZIP archive containing the selected website files is created.

Important: Confirm that the archive includes the necessary WordPress files, themes, plugins, uploads, and hidden configuration files. A website file archive does not necessarily contain the WordPress database.

Step 4: Download and Verify the File Backup

Purpose: Store a copy of the website files outside the hosting account.

Instructions:

1. Locate the ZIP archive in File Manager.
2. Download it to your computer.
3. Check that the downloaded file exists and has a plausible file size.
4. If possible, inspect the archive to confirm that it contains the expected WordPress files and folders.

Expected outcome: You have a local copy of the website files.

Step 5: Export the WordPress Database

Purpose: Back up the database containing WordPress posts, pages, settings, users, and other website content.

Instructions:

1. Open cPanel.
2. Launch phpMyAdmin, if available.
3. Identify the database used by the WordPress installation. Check the database name in wp-config.php if necessary.
4. Select the correct database in phpMyAdmin.
5. Choose Export.
6. Select Quick export and SQL format if suitable for the database.
7. Start the export.

Expected outcome: A database backup, such as database.sql, is downloaded to your computer.

Important: Keep the SQL file separate from the website ZIP archive. Protect both backups because they may contain sensitive website data.

Step 6: Record Existing Website Settings

Purpose: Preserve important configuration details for testing and troubleshooting.

Before proceeding, record the following where applicable:

• WordPress site URL and home URL.
• Current PHP version and relevant PHP extensions.
• Active themes and plugins.
• Permalink settings.
• Existing DNS records, including website and email records.
• Email configuration and any external services connected to the website.

If the website uses an online store, membership system, booking platform, or frequently updated content, plan how to preserve changes made during migration.

Expected outcome: You have the backups and configuration details needed to restore and verify the website.

Phase 2: Prepare the Neurax Host Destination

Step 7: Log in to Neurax Host cPanel

Purpose: Access the destination hosting account.

Instructions:

1. Log in to your Neurax Host hosting account.
2. Open cPanel using the access method provided for your service.

Expected outcome: The Neurax Host cPanel dashboard opens.

Step 8: Verify the Domain and Document Root

Purpose: Confirm where the website files must be placed.

Instructions:

1. Open the Domains section in cPanel, if available.
2. Locate your domain or add it if the hosting plan supports the required configuration.
3. Check the document root assigned to the domain.
4. Record the actual directory path shown by cPanel.
5. Confirm that the domain is associated with the intended hosting account.

Expected outcome: You know the correct destination directory for the WordPress installation.

Important: Do not assume the document root is always public_html. The correct path depends on the domain and hosting configuration.

Step 9: Upload the Website Backup

Purpose: Transfer the backed-up website files to Neurax Host.

Instructions:

1. Open File Manager in Neurax Host cPanel.
2. Navigate to the verified document root.
3. Select Upload.
4. Upload the ZIP archive saved on your computer.
5. Wait for the upload to finish.
6. Verify that the archive appears in the destination directory.

For large websites, browser uploads may fail because of file-size limits, timeouts, or connection interruptions. If that happens, use a supported SFTP method or contact Neurax Host support for an alternative.

Expected outcome: The website archive is present in the correct destination directory.

Step 10: Extract the Website Files

Purpose: Restore the WordPress files to the destination directory.

Instructions:

1. Select the uploaded ZIP archive.
2. Choose Extract, if the option is available.
3. Extract the files into the verified document root.
4. Confirm that the WordPress files appear directly in the intended website directory.

For example, if the document root is public_html, the expected structure is:

• public_html/wp-admin
• public_html/wp-content
• public_html/wp-includes
• public_html/wp-config.php
• public_html/index.php

Expected outcome: The WordPress files are in the correct directory.

Warning: Avoid an unintended nested structure such as public_html/public_html/wp-admin. The correct structure depends on the actual document root configured for your domain.

Phase 3: Create the Destination Database and User

Step 11: Create a New Database

Purpose: Create a database for the migrated WordPress website.

Instructions:

1. In cPanel, open the database management tool available on your account, such as Manage My Databases or MySQL Databases.
2. Find the option to create a new database.
3. Enter a database name.
4. Create the database.
5. Record its full name, including any account prefix displayed by cPanel.

Expected outcome: The new database is available for the WordPress import.

Step 12: Create a Database User

Purpose: Create a user that WordPress can use to connect to the database.

Instructions:

1. Open the database management tool.
2. Locate the option to create a database user.
3. Enter a username.
4. Generate a strong, unique password.
5. Create the user.
6. Save the database username and password securely.

Expected outcome: A database user has been created.

Step 13: Assign the User to the Database

Purpose: Grant WordPress the required database permissions.

Instructions:

1. Locate the option to add a user to a database.
2. Select the database user.
3. Select the new WordPress database.
4. Add the user to the database.
5. Grant the privileges required for WordPress to operate. In a standard cPanel WordPress setup, this commonly means selecting ALL PRIVILEGES for the specific WordPress database.
6. Save the changes.

Expected outcome: The database user has the necessary permissions for the WordPress database.

Security note: Grant privileges only on the intended database, not on unrelated databases.

Step 14: Import the HostPapa Database Backup

Purpose: Restore the database exported from HostPapa.

Instructions:

1. Open phpMyAdmin on Neurax Host, if available.
2. Select the new database created in Step 11.
3. Choose Import.
4. Select the SQL file exported from HostPapa, such as database.sql.
5. Start the import.
6. Wait for the process to finish and check the result.

Expected outcome: The WordPress database is imported into the new Neurax Host database.

If the import fails, check the selected database, SQL file integrity, and any upload or import size limits. For a large database, contact support for an appropriate import method.

Phase 4: Configure WordPress on Neurax Host

Step 15: Update wp-config.php

Purpose: Configure WordPress to connect to the new database.

Instructions:

1. Open File Manager.
2. Navigate to the actual WordPress document root.
3. Locate wp-config.php.
4. Create a copy before editing it.
5. Open the file for editing.
6. Locate the database configuration entries and update them with the values created on Neurax Host.

Example:

define('DB_NAME', 'YOUR_DATABASE_NAME');
define('DB_USER', 'YOUR_DATABASE_USERNAME');
define('DB_PASSWORD', 'YOUR_DATABASE_PASSWORD');
define('DB_HOST', 'YOUR_VERIFIED_DATABASE_HOST');

7. Replace each placeholder with the actual value supplied or confirmed for your Neurax Host account.
8. Save the file.

Important: Do not assume DB_HOST is always localhost. Verify the correct database hostname from your Neurax Host configuration or support team.

Expected outcome: WordPress is configured to use the destination database.

Step 16: Check WordPress Site URLs

Purpose: Ensure WordPress uses the correct website address after migration.

Instructions:

1. Identify the current siteurl and home values in the WordPress database.
2. Compare them with the intended website domain and protocol.
3. If the domain is changing, update the relevant WordPress URLs carefully.
4. If the website uses a search-and-replace operation to update old URLs, use a WordPress-compatible tool that handles serialized data correctly.
5. Back up the database before making URL changes.
6. Check theme settings, plugin settings, and media links for references to the old domain.

Expected outcome: WordPress is configured to use the intended website URL.

Important: Do not perform a simple unrestricted text replacement directly in the database. Incorrect replacements can damage serialized WordPress data or plugin settings.

Phase 5: Test the Website Before Switching DNS

Step 17: Test the Website on the Destination Hosting

Purpose: Confirm that the migrated website works on Neurax Host before directing visitors to it.

Instructions:

1. Use a supported preview or staging method if available.
2. If no preview URL is provided, ask Neurax Host support about available testing options. Another option, where appropriate, is to use a local hosts-file entry to test the destination server from your own computer.
3. Confirm that the test method directs requests to Neurax Host without changing public DNS prematurely.
4. Test the homepage, important pages, navigation, images, forms, and login.
5. Check for database connection errors, missing files, PHP errors, and broken links.
6. Verify that the site uses the intended domain and that internal links and media URLs work.
7. Review logs for errors where available.

Expected outcome: The destination website passes the necessary functionality checks before the DNS switch.

Important: A temporary URL is not guaranteed to be available. Confirm the supported testing method with Neurax Host before relying on one.

Step 18: Verify WordPress Admin Access

Purpose: Confirm that the WordPress backend works on the destination server.

Instructions:

1. Open the WordPress admin URL using your intended domain or the supported preview method.
2. Log in with your existing WordPress credentials.
3. Confirm that the dashboard opens.
4. Check plugins, themes, settings, and media.
5. Test important administrative functions.

Expected outcome: You can access and use the WordPress dashboard on the destination hosting.

Step 19: Check Email and External Services

Purpose: Prevent migration-related interruptions to connected services.

Instructions:

1. Confirm whether email is hosted with HostPapa, Neurax Host, or a separate provider.
2. If email is hosted separately, preserve the existing MX, SPF, DKIM, and DMARC records as required.
3. If mailboxes or messages need to move, arrange a separate email migration. Moving WordPress files and the database does not automatically migrate email.
4. Test contact forms, SMTP delivery, payment gateways, booking systems, analytics, and other integrations used by the website.

Expected outcome: The website and its connected services are ready for the DNS change.

Phase 6: Switch DNS to Neurax Host

Step 20: Update the Domain's DNS Records

Purpose: Direct visitors to the migrated website on Neurax Host.

Instructions:

1. Identify where the domain's DNS is managed.
2. Obtain the correct nameserver or DNS record values from Neurax Host.
3. Choose the appropriate method:
   • Update nameservers if you intend to move DNS management and have accounted for all existing records.
   • Update the website's relevant A or other required records if DNS will remain with the current provider.
4. Before making changes, save a copy of the existing DNS records.
5. Check email and other service records carefully before changing nameservers.
6. Apply the DNS changes and monitor the domain's resolution.
7. Keep the original HostPapa website and hosting available while the DNS change takes effect.

Expected outcome: The domain begins directing visitors to the Neurax Host website.

Important: DNS changes do not take effect everywhere immediately. The time required varies depending on TTL values, DNS caching, and the providers involved. There is no guaranteed fixed propagation time.

Phase 7: Enable HTTPS and Complete Verification

Step 21: Verify SSL and HTTPS

Purpose: Ensure the website can load securely over HTTPS.

Instructions:

1. Confirm that the domain points to the intended Neurax Host server.
2. Open the SSL/TLS Status section in cPanel, if available.
3. Check whether a valid SSL certificate is installed for the domain.
4. Follow the available certificate-provisioning instructions, or contact Neurax Host support if the certificate is missing or invalid.
5. Once HTTPS works correctly, enable Force HTTPS Redirect if the option is available, or configure a suitable redirect.
6. Test the homepage and important pages over HTTPS.
7. Check for mixed-content warnings caused by resources still loading over HTTP.

Expected outcome: The website loads securely over HTTPS without certificate errors.

Important: Do not enable a forced HTTPS redirect before confirming that the certificate is valid and HTTPS works.

Step 22: Complete the Final Website Checks

Verify the following after the DNS switch:

• Homepage and important pages load.
• WordPress admin login works.
• Images, CSS, and JavaScript load correctly.
• Navigation and permalinks work.
• Contact forms and email notifications work.
• Plugins and themes operate as expected.
• Database errors are absent.
• HTTPS works without certificate or mixed-content warnings.
• Online payments, bookings, or other critical functions work, if applicable.
• DNS and email records remain correct.

For websites that receive orders, bookings, memberships, or frequent content updates, check whether any new data was added to the old site during migration. If necessary, synchronize those changes before considering the migration complete.

Expected outcome: The migrated website is operating correctly on Neurax Host.

Troubleshooting Guide

1. ZIP File Upload Fails

Symptoms:

• The upload stops before completion.
• The browser reports an error.
• The file does not appear in File Manager.

Possible causes:

• Unstable internet connection.
• Browser timeout.
• File-size or hosting limits.
• Insufficient disk space.

Solutions:

• Retry the upload using a stable connection.
• Confirm available disk space and upload limits.
• Use a supported SFTP method for large files, or contact Neurax Host support.

2. ZIP File Extracts into Another Folder

Symptom: The files appear in a nested directory, such as public_html/public_html/wp-admin, when the actual document root is public_html.

Solution:

• Check the configured document root.
• Move the WordPress files into the correct directory if necessary.
• Confirm that wp-admin, wp-content, wp-includes, and wp-config.php are in the intended WordPress installation directory.

3. Error Establishing a Database Connection

Possible cause: The database name, username, password, hostname, or permissions are incorrect.

Solution:

• Verify DB_NAME, DB_USER, and DB_PASSWORD in wp-config.php.
• Confirm the correct database hostname with Neurax Host.
• Ensure the database user has the required privileges.
• Check that the database import completed successfully.

4. SQL Import Fails

Possible causes:

• The wrong database is selected.
• The SQL file is incomplete or corrupted.
• The database exceeds the import limits.
• The database contains an import error.

Solutions:

• Confirm that the destination database is selected.
• Check the SQL backup and re-export the database from HostPapa if necessary.
• For large databases, use a supported alternative import method or contact Neurax Host support.

5. Website Opens but Styling or Images Are Missing

Possible causes:

• Files were not fully copied.
• The wp-content/uploads directory is missing or incomplete.
• URLs still reference the old domain.
• File permissions or resource paths are incorrect.

Solutions:

• Verify that the necessary files and folders exist in the destination installation.
• Check wp-content/uploads.
• Review the browser console and website logs for missing resources.
• Check and safely update old URLs where necessary.

6. Website Pages Return 404 Errors

Possible causes:

• Permalink rewrite rules need to be regenerated.
• The .htaccess file is missing or incorrect.
• The domain points to the wrong document root.
• The destination server does not support the required rewrite configuration.

Solutions:

1. Verify the domain's document root.
2. Back up .htaccess before editing it.
3. Log in to WordPress admin, if available.
4. Open Settings → Permalinks.
5. Click Save Changes without changing the settings.
6. Test the affected pages again.

If the problem continues, check the server configuration or contact support.

7. WordPress Admin Login Does Not Work

Possible causes:

• Incorrect credentials.
• An incomplete database import.
• A plugin conflict.
• A domain or cookie configuration issue.

Solutions:

• Verify the username and password.
• Confirm that the database imported correctly.
• Check the WordPress site URL settings.
• Review logs and investigate plugin conflicts if needed.

8. Domain Opens the Old Hosting Website

Possible cause: DNS changes have not fully taken effect, or the DNS records still point to HostPapa.

Solutions:

• Verify the nameservers and relevant DNS records.
• Confirm the correct destination IP or DNS values with Neurax Host.
• Check the domain's DNS resolution from different networks.
• Allow for DNS caching; the time required varies.
• Keep the original hosting available until the destination is verified.

9. HTTPS Is Not Working

Possible causes:

• The DNS record points to the wrong server.
• The SSL certificate is missing, invalid, or not yet provisioned.
• The domain is not covered by the certificate.

Solutions:

• Verify DNS first.
• Check the certificate status in cPanel, if available.
• Follow the available SSL instructions or contact Neurax Host support.
• Enable forced HTTPS redirection only after HTTPS is working.

10. Blank White Screen or WordPress Error

Possible causes:

• A plugin or theme conflict.
• An incompatible PHP version or extension.
• A PHP error or incomplete file transfer.

Solutions:

• Check available PHP and server error logs.
• Confirm that the website uses a PHP version supported by WordPress, the active theme, and required plugins.
• Back up the website before disabling plugins or changing files.
• If a plugin conflict is suspected, temporarily disable the relevant plugin using a safe method, then test and re-enable plugins as appropriate.
• Avoid displaying PHP errors publicly on a live website.

Frequently Asked Questions (FAQs)

Q1. Can I migrate a website without changing the domain's DNS first?

Yes. You can transfer the files and database and test the destination before switching public DNS. Use a preview or staging method supported by Neurax Host, or consider a local hosts-file configuration where appropriate. A temporary URL is not guaranteed to be available.

Q2. Will migration delete my HostPapa website?

No. Copying the files and database to Neurax Host does not automatically delete the original website. Keep the original hosting and backups until the new website has been tested and verified.

Q3. How long does WordPress migration take?

The time varies depending on website size, database size, internet speed, hosting limits, configuration, and the complexity of the website. Large websites and sites with online orders or frequently changing content may require additional time for testing and data synchronization.

Q4. Do I need coding knowledge to migrate WordPress?

Not necessarily. Many manual migrations can be completed using File Manager, phpMyAdmin, and WordPress settings. However, database errors, URL changes, DNS configuration, or server-specific issues may require technical assistance.

Q5. Can I migrate only the files without the database?

A standard WordPress website generally requires both its files and its database. The files contain WordPress core, themes, plugins, and media, while the database stores content, settings, users, and other information.

Q6. Which files are important for WordPress migration?

Important items typically include:

• wp-admin
• wp-content
• wp-includes
• wp-config.php
• index.php
• .htaccess, if used

Also check for hidden files and any additional files required by the website. The database must be exported separately unless your backup method explicitly includes it.

Q7. Why must wp-config.php be updated?

The destination hosting account may use different database credentials or a different database hostname. Updating the configuration allows WordPress to connect to the destination database.

Q8. Can I use the same database name on Neurax Host?

You can use the same database name only if the destination hosting account allows it. cPanel may add an account prefix, and database names must be unique within the relevant environment. Use the full database name shown by Neurax Host.

Q9. Can I delete the ZIP backup after migration?

Keep the original backups until the migrated website has been tested and you have confirmed that you can recover it if necessary. Afterward, you may remove unnecessary archives from the hosting account to save space, but retain a secure backup copy.

Q10. How do I verify that migration succeeded?

Check that:

• The homepage and important pages load.
• WordPress admin works.
• Images, styling, and navigation display correctly.
• Forms and other essential features work.
• The database connection is successful.
• HTTPS works correctly.
• The website uses the intended domain and destination hosting.

Q11. Does changing DNS move the website immediately?

No. DNS changes can take different amounts of time to become visible because of TTL values and caching. The timing varies, so do not rely on a fixed 24–48-hour guarantee.

Q12. What should I do before starting the migration?

Before starting:

1. Create a complete website file backup, including relevant hidden files.
2. Export the WordPress database separately.
3. Save copies of important DNS and email records.
4. Record the current WordPress URLs and relevant settings.
5. Check the destination document root and database requirements.
6. Plan how to test the website before switching DNS.
7. Keep the original hosting available until the migration is verified.