Overview
This guide explains how to migrate a WordPress website from A2 Hosting to Neurax Host using a manual migration method. The process involves exporting website files and the WordPress database from A2 Hosting, then restoring them on Neurax Host.
This guide applies to WordPress websites hosted in an A2 Hosting cPanel environment.
Note: Neurax Host advertises free website migration assistance, and its Managed WordPress offering lists free WordPress site migration. Contact Neurax Host support to confirm eligibility and request assistance before starting the manual process.
Prerequisites
Before you begin, ensure you have:
- An active A2 Hosting account
- A WordPress website hosted on A2 Hosting
- An active Neurax Host account with cPanel access
- Access to your domain's DNS settings
- Sufficient disk space on your computer
- A recent backup of your website files and database
Phase 1: Export Website from A2 Hosting
Step 1: Access A2 Hosting cPanel
Purpose: Access the hosting account containing your WordPress website.
Instructions:
- Log in to your A2 Hosting account or Client Portal.
- Open your hosting service.
- Use the available option to log in to cPanel, if your hosting plan provides it.
Expected outcome: The cPanel dashboard opens.
Step 2: Open File Manager
Purpose: Access the website files stored on the server.
Instructions:
- In cPanel, navigate to the Files section.
- Click File Manager.
Expected outcome: File Manager opens.
Step 3: Locate the WordPress Installation
Purpose: Identify the correct website directory.
- Find the document root assigned to your domain. It may be
public_html, but the actual path can vary. - Open that directory.
- Verify that it contains WordPress files such as:
wp-adminwp-contentwp-includeswp-config.phpindex.php
Expected outcome: The correct WordPress installation directory is identified.
Step 4: Create a Website Backup Archive
Purpose: Create a downloadable backup of the website files.
- Select the files and folders inside the WordPress installation directory.
- Ensure hidden files, including
.htaccesswhere applicable, are included. - Click Compress.
- Select ZIP Archive.
- Enter a filename such as
backup.zip. - Create the archive.
Expected outcome: A ZIP archive containing the website files is created.
Step 5: Download the Website Backup
Purpose: Save the website files locally.
- Locate
backup.zip. - Select the file and click Download.
- Save it to your computer.
Expected outcome: The website backup is downloaded to your computer.
Step 6: Export the WordPress Database
Purpose: Create a backup of the WordPress database.
- Return to cPanel.
- Open phpMyAdmin under the Databases section, if available.
- Identify the database used by WordPress. Check
wp-config.phpfor the database name if necessary. - Verify the database tables. Their prefix may not be
wp_; check the$table_prefixvalue inwp-config.phprather than relying only on table names such aswp_posts. - Select the correct database and click Export.
- Choose:
- Method: Quick, if appropriate for the database size
- Format: SQL
- Click Go to download the export.
For large databases, use an export method suitable for the database size and the tools available on your hosting plan.
Expected outcome: A database backup, for example database.sql, is saved locally.
Step 7: Verify Downloaded Files
Ensure the following files are available on your computer:
backup.zipdatabase.sql
Keep both files safe until the migration has been completed and verified.
Expected outcome: The website files and database backup are ready for migration.
Phase 2: Import Website into Neurax Host
Step 8: Log in to Neurax Host cPanel
- Log in to your Neurax Host account.
- Open cPanel.
Expected outcome: The cPanel dashboard opens.
Step 9: Locate the Destination Document Root
- Open Domains in cPanel, if available.
- Verify the document root assigned to your domain.
- Open that directory in File Manager.
Do not assume the correct directory is always public_html.
Expected outcome: You have opened the correct destination directory.
Step 10: Upload and Extract Website Files
- Click Upload in File Manager.
- Upload
backup.zipto the correct document root. - Wait for the upload to finish.
- Select the archive and click Extract.
- Verify that
wp-admin,wp-content,wp-includes,wp-config.php, andindex.phpare directly inside the intended WordPress directory, not inside an unintended nested folder.
Expected outcome: The website files are restored in the correct location.
Step 11: Create a MySQL Database
- Open MySQL Databases in cPanel, if available.
- Create a new database.
- Record the full database name.
Expected outcome: A new database is created.
Step 12: Create a Database User
- Create a new MySQL database user.
- Generate a strong password.
- Save the username and password securely.
Expected outcome: A database user is created.
Step 13: Assign the User to the Database
- Add the new user to the new database.
- Grant the required privileges, typically ALL PRIVILEGES for a standard cPanel WordPress setup.
- Save the changes.
Expected outcome: The database user has the required access.
Step 14: Import the Database
- Open phpMyAdmin.
- Select the new destination database.
- Ensure the database is empty before importing, so existing tables do not cause duplicate-table or import conflicts.
- Click Import.
- Upload
database.sql. - Click Go.
- Check for import errors.
Expected outcome: The database imports successfully without errors.
Step 15: Update WordPress Configuration
Open wp-config.php in the destination WordPress directory and update the database settings using the actual credentials provided by Neurax Host.
Example:
define('DB_NAME', 'your_database_name');
define('DB_USER', 'your_database_user');
define('DB_PASSWORD', 'your_database_password');
define('DB_HOST', 'your_database_host');
Replace the example values with the correct details. Do not assume DB_HOST is localhost; confirm the actual database host with Neurax Host.
Save the file.
Expected outcome: WordPress is configured to connect to the destination database.
Step 16: Verify Domain and WordPress URLs
- Confirm that the domain is assigned to the correct document root.
- Verify the WordPress site URL and home URL.
- If the domain is changing, check whether old-domain references in the database need to be updated. Use a WordPress-aware search-and-replace method to avoid damaging serialized data.
- Confirm that important links and media references point to the intended domain.
Expected outcome: WordPress is configured to use the correct domain and website URLs.
Step 17: Test the Website Before Changing DNS
Where possible, test the migrated website before switching the domain's DNS to Neurax Host.
Verify that the destination files and database work correctly and that the website loads as expected using an appropriate preview or temporary testing method.
Expected outcome: Major migration issues are identified before the DNS switch.
Step 18: Update DNS If Required
If the domain still points to A2 Hosting, update DNS when you are ready to switch to Neurax Host.
Choose the appropriate method:
- Nameservers: Change the domain's nameservers to those provided by Neurax Host.
- A record: Point the domain's A record to the correct Neurax Host server IP.
These are alternative approaches; you do not normally need to change both.
If you change nameservers, make sure existing email DNS records, including MX records and applicable SPF, DKIM, and other required records, are preserved or recreated at the new DNS provider.
DNS propagation time varies and is not guaranteed to finish within 24–48 hours. Keep the A2 Hosting account active while the change takes effect and the new website is verified.
Expected outcome: The domain begins resolving to Neurax Host.
Step 19: Enable SSL and HTTPS
- Open SSL/TLS Status in cPanel, if available.
- Run AutoSSL if supported and needed.
- Verify that the SSL certificate is active and the website loads over HTTPS.
- Enable Force HTTPS Redirect only after the certificate is working correctly.
Expected outcome: The website loads securely over HTTPS.
Step 20: Test the Migrated Website
Before declaring the migration complete, verify that:
- The homepage and important pages load correctly.
- Images and media display properly.
- Menus, forms, plugins, and other essential features work.
- WordPress Admin is accessible at
https://yourdomain.com/wp-admin. - The database connection works without errors.
- WordPress URLs and internal links are correct.
- HTTPS works without certificate warnings.
- Email delivery works, if your domain uses email.
- Permalinks work correctly.
If needed, open Settings → Permalinks in WordPress Admin and click Save Changes to refresh permalink rules.
Expected outcome: The website passes the required functionality checks.
Migration Complete
The migration is complete only after the website pages, database connection, WordPress Admin login, forms, media, HTTPS, and other essential features have been tested successfully.
Keep your A2 Hosting account active until the migrated website is verified and DNS is resolving correctly. Once you have confirmed that the new website is working and you no longer need the old hosting environment, you can plan to cancel the old service.
After verifying the migration, delete the temporary ZIP archive from the Neurax Host server if it is no longer needed.
Need help? Contact Neurax Host support to ask about its free website migration assistance before attempting manual migration.
Troubleshooting
Error Establishing Database Connection
Verify the database name, username, password, host, and database-user permissions in wp-config.php.
Website Displays 404 Errors
Check the document root and rewrite configuration. In WordPress Admin, open Settings → Permalinks and click Save Changes if needed.
Images Are Missing
Verify that wp-content/uploads and the other required media files were migrated successfully.
Email Is Not Working
Check the domain's MX records and other required email DNS records. Confirm that changing nameservers did not remove existing email settings.
DNS Changes Not Working
Verify the nameservers and DNS records. Propagation time varies, so do not treat 24–48 hours as a guaranteed completion time.