Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →The safest host change starts with a restorable copy of every part of your site: files, databases, email-related data, configuration, and DNS records. Create at least one archive you can retrieve without the old host, restore it on the new server, test the site privately, and only then change DNS. Keep the old account and a rollback copy until web traffic, email, and scheduled jobs are stable.
What a complete website backup must contain
A website is rarely just the files visible in a web directory. A reliable migration copy includes the application files and, when the site uses one, its database. The database may contain posts, pages, customer records, orders, accounts, settings, and sessions that do not exist in the file tree.
As an Amazon Associate I earn from qualifying purchases.
- Site files: application code, themes, plugins, uploaded media, images, documents, custom scripts, and server rules such as
.htaccess. - Database: content and configuration stored by WordPress, a forum, a shop, or another database-backed CMS.
- Configuration: environment files, connection details, PHP settings, cron definitions, redirect rules, and required extensions. Store sensitive configuration securely.
- Mail information: mailboxes, aliases, forwarding rules, autoresponders, and any mail archives that must move. A website archive does not automatically prove that mail data is included.
- DNS information: A, AAAA, CNAME, MX, TXT, CAA, and other custom records. DNS normally lives with the DNS provider, not inside the website directory.
- Certificates and external integrations: notes about SSL issuance, payment gateways, analytics, webhooks, API allowlists, and services restricted to the old server’s IP address.
For a WordPress site, copying only public_html (or its equivalent) can omit the database. Conversely, copying only a database omits themes, plugins, and uploads. Treat the site as a set of interdependent parts and verify that the destination can restore all of them.
Recommended Free Tools
1. Inventory the current account before making a copy
Write down what exists before you begin. This prevents a successful-looking transfer from silently losing a less visible dependency.
#1 Best Overall
- Easily store and access 2TB to content on the go with the Seagate Portable Drive, a USB external hard drive
- Designed to work with Windows or Mac computers, this external hard drive makes backup a snap just drag and drop
- To get set up, connect the portable hard drive to a computer for automatic recognition no software required
- This USB drive provides plug and play simplicity with the included 18 inch USB 3.0 cable
- The available storage capacity may vary.
Record the software and domains
- CMS name, version, PHP version, database engine and version, and enabled extensions.
- Every domain and subdomain, including parked domains and aliases.
- The document root for each domain and the database associated with each installation.
- WordPress multisite status, if applicable; a single-site migration workflow may refuse a network.
Record operational dependencies
- Scheduled jobs (cron tasks), queue workers, server-side scripts, and background imports.
- Redirects and rewrite rules in
.htaccessor web-server configuration. - SSL certificates, renewal method, and whether a certificate is issued by the host or an external service.
- External services that use the current IP address, callback URL, SMTP server, or firewall allowlist.
- All email accounts, aliases, forwarding addresses, autoresponders, and mailbox sizes.
Export DNS records
Copy the complete DNS zone or make a written record of every custom entry. Pay particular attention to MX records for mail, TXT records for SPF and domain verification, DKIM selectors, DMARC policy, CAA restrictions, and records for subdomains. A host migration service may not change DNS for you, and custom records can be missed during an otherwise complete account transfer.
2. Create a backup you can retrieve independently
Make the primary archive while the old site is still operating, then download or copy it somewhere the old host cannot erase. An archive that exists only inside the account you are about to cancel is not an independent backup.
Using a cPanel account backup
In cPanel, open Backup or Backup Wizard. A full account backup can include the home directory, databases, email configuration, and other account data supported by the host. The full-backup interface lets you choose a home-directory destination or a remote FTP or SCP destination. If you use a remote destination, confirm the remote path, credentials, and available space before starting.
cPanel warns that a full backup can fail when the account is near its quota. Check quota and free space first, and remove only disposable temporary files after confirming they are not needed. A full archive can be large and may take considerable time on an account containing videos or extensive mail.
Do not assume that creating the archive also proves that it can be restored. cPanel states: “You cannot automatically restore a full backup file in cPanel.” Automatic full-account restoration is available in WHM or through the hosting provider. Ask the new host, in writing, whether it will restore a full cPanel archive, which account types it accepts, and whether restoration assistance has limits or fees.
Rank #2
- Easily store and access 5TB of content on the go with the Seagate portable drive, a USB external hard Drive
- Designed to work with Windows or Mac computers, this external hard drive makes backup a snap just drag and drop
- To get set up, connect the portable hard drive to a computer for automatic recognition software required
- This USB drive provides plug and play simplicity with the included 18 inch USB 3.0 cable
- The available storage capacity may vary.
Download and verify the archive
- Wait for the control panel to report that the archive is complete.
- Download it to a computer or storage account that is independent of the old host.
- Check that the file exists, its size is plausible compared with the account’s disk usage, and the download completed without an error.
- Keep the original server-side copy until the downloaded copy has been checked.
- For a high-value site, make a second copy in a different location and restrict access because archives can contain passwords, private user data, and mail.
A file-size check is not a restore test, but it catches common zero-byte and truncated-download failures. If the host offers checksums, record the checksum and compare it after downloading.
Taking separate partial backups
If a full account archive is unavailable or too large, export the individual parts: download all site files, export each database, and separately document or export mail and DNS data. This approach requires a more careful inventory because it is easier to omit an alias, a second database, a hidden directory, or a scheduled task. Keep a dated manifest listing what was exported.
3. WordPress-specific option: an application migration archive
For a single WordPress installation, the Open Migration plugin listing documents an archive workflow that exports the database and wp-content, including themes, plugins, uploads, and other content stored there. The listing says its ZIP does not include wp-config.php or WordPress core files. It also states requirements of PHP 7.2 or newer, the ZipArchive extension, and sufficient disk space. Those are requirements and behaviors of that specific plugin, not a universal WordPress migration standard.
The listing says multisite networks are refused rather than migrated. Confirm compatibility before relying on this method, especially if the site uses a network, unusual database tables, very large media, or custom files outside wp-content.
Export from the old site
- Confirm the old site meets the plugin’s PHP and ZipArchive requirements.
- Install the plugin and create its export archive.
- Download the ZIP to independent storage and check its size and integrity.
- Keep a separate copy of
wp-config.phpand a note of the source database name, database user, table prefix, site URL, and active PHP version. Protect credentials as secrets.
Import on the new server
- Install a clean WordPress instance and the same migration plugin on the destination.
- Confirm the destination has enough disk space for the ZIP and extraction. A separate destination backup is prudent before an import that replaces content.
- Upload the exported archive and read the replacement warning carefully.
- Confirm the import. The documented workflow replaces destination content with the archive.
- Sign in with the source site’s user account after import, then save Settings → Permalinks to regenerate rewrite rules.
The plugin documents URL and path conversion. Test the site on its temporary address before using its Change Domain action. Its instructions warn that changing the domain too early can leave the site unreachable at both the temporary and real addresses.
Rank #3
- Easily store and access 1TB to content on the go with the Seagate Portable Drive, a USB external hard drive.Specific uses: Personal
- Designed to work with Windows or Mac computers, this external hard drive makes backup a snap just drag and drop. Reformatting may be required for Mac
- To get set up, connect the portable hard drive to a computer for automatic recognition no software required
- This USB drive provides plug and play simplicity with the included 18 inch USB 3.0 cable
- The available storage capacity may vary.
4. Prepare the new host before restoring
Compare the destination environment with the inventory. Check supported PHP and database versions, storage limits, process limits, SSL support, cron access, and whether the host can create the required databases and users. A destination that cannot run the source application’s versions or extensions is not ready for a restore.
Space for a cPanel archive
cPanel’s account restore guidance says to leave at least twice the archive file’s size free on the destination for extraction. For example, a 12 GB archive needs at least 24 GB of free space under that guidance, before allowing room for the restored account and future growth.
Choose the appropriate transfer path
When an operator has root access to both cPanel servers, cPanel recommends the WHM Transfer Tool for account transfers. Without root access, ask the provider to perform the supported restore or use the host’s documented import process. Clarify whether email, databases, custom DNS records, permissions, and SSL settings are included. Two-factor-authentication configuration is not transferred by the cPanel account-archive workflow, so plan to enroll it again on the destination.
5. Restore and repair the destination privately
Restore the archive before changing public DNS. If the destination is a different account or platform, create the databases and users first, upload files with the correct ownership and permissions, and update configuration values to the new database credentials. Do not publish credentials in tickets, screenshots, or shared documents.
Check common post-restore failures
- Database connection errors: verify database name, user, password, host, and permissions in the application’s configuration.
- Blank pages or 500 errors: inspect PHP and web-server error logs, then compare PHP versions and required extensions.
- 404 errors: confirm rewrite rules, file permissions, and that the web root points to the correct directory.
- Missing images or styles: check uploads, case-sensitive paths, absolute URLs, and file ownership.
- Redirect loops: review forced HTTPS rules, proxy settings, and old host redirects.
- Broken scheduled work: recreate cron jobs and verify their interpreter paths and environment variables.
Do not delete the source account while you diagnose these issues. A migration can appear successful on the home page while checkout, account login, forms, search, media, or background jobs remain broken.
Free tools Windows power users keep installed
One-click scans. No signup required.
Rank #4
- Easily store and access 4TB of content on the go with the Seagate Portable Drive, a USB external hard drive.Specific uses: Personal
- Designed to work with Windows or Mac computers, this external hard drive makes backup a snap just drag and drop
- To get set up, connect the portable hard drive to a computer for automatic recognition no software required
- This USB drive provides plug and play simplicity with the included 18 inch USB 3.0 cable
- The available storage capacity may vary.
6. Test the complete site without changing DNS
cPanel recommends verifying each website after migration and before changing DNS. Use the destination’s temporary URL when it works, or map the real domain to the new server’s IP address in your local hosts file. A hosts-file change affects only your computer, allowing realistic domain-based testing without sending public visitors to the new server. Remove the mapping after testing so your computer follows normal DNS again.
Use a repeatable test checklist
- Open the home page and representative pages for every content type.
- Test desktop and mobile layouts, images, downloads, search, and pagination.
- Submit contact, registration, comment, and other forms; confirm delivery and spam handling.
- Sign in, sign out, reset a password, and test role-based access where relevant.
- For a shop or membership site, test cart, checkout, payment callbacks, receipts, and account history in the appropriate safe mode.
- Check redirects, canonical URLs, HTTPS, robots rules, XML sitemaps, and analytics tags.
- Review application, PHP, database, and web-server logs while performing these actions.
- Confirm that cron tasks, webhooks, API callbacks, and outbound email use the destination settings.
For WordPress on a temporary address, follow the migration tool’s documented order: test first, point DNS to the destination, wait for the real domain to load there, and only then run the domain-change action if required. Changing the domain before the real DNS path works can make both addresses fail.
7. Plan the DNS cutover and email transition
DNS changes are not a substitute for a final content sync. Visitors may continue reaching the old server until resolvers update, so edits, orders, comments, and emails can arrive at two locations during the transition. Choose a quiet period, announce any editing freeze if the site changes frequently, and decide how you will reconcile final data.
TTL guidance
cPanel’s migration guidance recommends lowering DNS TTL to 300 seconds before migration and restoring it to 3600 seconds after completion. These are cPanel recommendations, not universal requirements; use the controls and limits of your authoritative DNS provider. Lowering TTL shortly before a change cannot instantly erase cached records whose previous TTL has not expired.
Preserve every required record
Before editing the zone, compare the destination records with your inventory. Preserve MX, SPF, DKIM, DMARC, CAA, verification TXT records, subdomain records, and any custom service endpoints. Changing only the website’s A record while accidentally deleting MX or DKIM entries can interrupt mail even when the web pages work.
8. Verify after DNS changes and keep rollback options
- Confirm the domain resolves to the new server from multiple networks or DNS-checking locations.
- Open the site over HTTPS and repeat the critical-path tests.
- Send and receive test messages for each important domain and mailbox; verify SPF, DKIM, and DMARC behavior.
- Watch logs, uptime, error rates, forms, payments, and scheduled jobs during the first operating period.
- Keep the old hosting service, the original archive, and the independent backup until the site and mail are stable. Do not cancel based on one successful page load.
- After verification, restore the normal DNS TTL and update documentation with the final server IPs, credentials location, and renewal dates.
Control-panel transfer or WordPress archive?
Neither approach is universally safer or faster. Choose according to platform, archive contents, and who can restore the result.
Quick Recap
| Consideration | cPanel account backup or transfer | WordPress migration plugin |
|---|---|---|
| Best fit | cPanel accounts needing an account-level archive or provider-assisted transfer. | Compatible single-site WordPress installations. |
| Typical contents | Account data supported by the host, potentially including files, databases, and mail configuration. | Documented export of the database and wp-content; the cited plugin excludes wp-config.php and WordPress core. |
| Restore access | Full automatic restoration is not available in the cPanel user interface; WHM or provider help may be required. | Import occurs inside WordPress and replaces destination content. |
| Key limits | Quota failures, extraction space, provider policies, and transfer permissions. | PHP 7.2+, ZipArchive, disk space, and no multisite support according to the cited listing. |
| What to verify | Email, custom DNS, permissions, SSL, 2FA re-enrollment, and restore support. | URL/path conversion, source login, permalinks, custom files, and a destination rollback copy. |
Failure modes that deserve a stop-and-fix response
- The archive is smaller than expected: compare it with account usage and confirm databases, uploads, and mail were included before proceeding.
- The host cannot restore the archive: pause the migration, obtain written provider instructions, or create a backup in the format the destination supports.
- The destination is nearly full: do not extract until the required free space is available; cPanel’s guidance calls for at least twice the archive size.
- Only some pages work: inspect rewrite rules, permissions, absolute links, and application logs.
- Mail stops after the web cutover: compare MX, SPF, DKIM, DMARC, and mailbox provisioning with the pre-migration inventory.
- Visitors see different versions: DNS caching or an unfinished final sync may be sending users to both servers. Keep the old site available and coordinate writes until traffic settles.
- WordPress breaks at both addresses: if a domain-change action was run before DNS pointed to the new server, restore the documented sequence from a destination backup or obtain host/plugin support.
A compact go/no-go checklist
Before the transfer
- Inventory domains, software, databases, mail, DNS, SSL, cron, redirects, and integrations.
- Create a complete archive and at least one independent copy.
- Confirm the archive size, download, storage security, and restore method.
- Lower TTL only if appropriate for your DNS provider and migration schedule.
Before DNS changes
- Restore the destination and resolve configuration errors.
- Test pages, media, forms, logins, transactions, redirects, HTTPS, logs, cron, and email.
- Verify all custom DNS records and destination mailboxes.
- Take a rollback copy of the restored destination.
After DNS changes
- Verify web resolution from multiple networks and test mail in both directions.
- Monitor the old and new servers for straggling traffic and data changes.
- Keep the old account and independent backups until stability is demonstrated.
- Restore normal TTL and document the final configuration.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
