Before you start
Confirm that you can sign in to WordPress, access the current site files and database, and edit the domain’s DNS. Check the current PHP version and make sure your cPanel plan has room for your site files, database and any email you plan to move.
Download a complete copy of the WordPress files and a database export. Save a copy outside both hosts. Export your current DNS records or note the web, mail and verification records you need to keep. For WooCommerce or another site that accepts new orders, schedule a short window for the final copy so recent activity makes it to the new site.
Copy the files and database to cPanel
- Open Domains in cPanel and confirm the domain’s document root. Upload and extract your files in that folder with File Manager, or use an authenticated file transfer. Include hidden files such as
.htaccesswhen they belong to the site. Store archives and SQL exports outside the public web folder. - In Manage My Databases, create a database and user, then grant that user the necessary database privileges. Import the SQL export into the new database with phpMyAdmin.
- Update the database name, username, password and host in
wp-config.phpto match the new account. Confirm the table prefix matches your imported database. Never share the configuration file or its credentials in a public link.
If the domain stays the same, keep the existing WordPress URLs. If the domain changes, update the WordPress Address and Site Address and use a WordPress-aware search-and-replace tool that handles serialized data. See the WordPress migration documentation.
Test your copy before you switch
Use a local hosts-file override to preview the production hostname on the new server from your computer. Check the homepage, a few posts or products, images, WordPress sign-in, permalinks, and key forms. If you are moving a store, check the cart and test checkout in your payment provider’s test mode.
A valid certificate may only become available once the domain points to the new host. Avoid signing in or submitting real customer data over an insecure preview. Remove the local override after testing so future checks use public DNS.
Point the domain to the new host and verify HTTPS
After the final copy, point the website’s DNS records to the new address using the values in your hosting account. Review the root domain and www, plus any IPv6 records. When changing nameservers, copy the full DNS zone first. Keep existing MX and email authentication records if mail stays with your current provider.
Once public DNS points to Fasting Host, check SSL/TLS Status in cPanel and verify that both the main domain and www open securely where configured. AutoSSL is available for eligible cPanel-hosted domains after validation. Read how AutoSSL works.
Give yourself time to verify the move
- Check the site from a second network. Test WordPress sign-in, forms, images and any redirected URLs, then clear the site cache if visitors see old content.
- If you are moving email, create the new cPanel mailboxes, copy existing mail and test incoming and outgoing delivery before retiring the old mail service.
- Keep the original hosting and a fresh backup until DNS, HTTPS and email work reliably. If something fails, compare both copies before directing visitors back so you preserve orders or edits that arrived after the switch.
For the database and file-transfer screens, see cPanel’s WordPress migration instructions.