Move a cPanel Website: Full Backups, Partial Restores and Testing

To move a cPanel website, first decide whether you need the entire hosting account or just one application. A full cPanel backup, a partial backup and a manual file transfer solve different problems. None should be restored over existing destination data without a reviewed plan.

Complimentary migration eligibility: InterServer provides migrations for web hosting plans only, limited to cPanel-to-cPanel and DirectAdmin-to-DirectAdmin. VPS and dedicated-server migrations are not offered. Cross-panel transfers and website-builder conversions are outside this service; the manual instructions below are for self-managed moves when the matching-panel web hosting requirements are not met.

Reviewed October 14, 2026. This guide applies to a source account that actually uses cPanel. Check the destination’s restore capabilities before exporting. A managed WordPress service, website builder or different control panel may require a different migration method.

Choose the appropriate method

• Full account: use a compatible cPanel account backup when the destination provider can restore it. This is generally the starting point for moving account-level data and settings, not for merging two existing accounts.
• Partial backup: export selected components when you understand what the destination must recreate separately. A home-directory archive does not replace a separate database export.
• One website: transfer its files, database and required configuration as an application migration. Include files outside the document root if the application needs them. Recreate hosting services separately.

For a move to InterServer, confirm the destination panel and scope through the InterServer migration support process. Do not assume the new service uses cPanel or can import a full cPanel archive.

Find the source account and provider instructions

This guide consolidates our former provider-specific cPanel-transfer walkthroughs. Their core backup and destination-restore procedure was the same. Use the provider references below for access details and export differences rather than relying on an old screenshot or a guessed login URL.

• A2 Hosting / hosting.com: check which panel your existing account uses. The current hosting.com cPanel backup guide covers full-account generation and authenticated download; a different Hosting Panel or managed product needs its own export method.
• GoDaddy: select the correct Web Hosting (cPanel) product in your account. Its Daily Backups account-export guide describes an additional option where available: choose the backup date, export the account and download after completion. Do not skip the database or home directory if you need both. Managed WordPress and website-builder products are outside this cPanel workflow.
• HostGator: its backup download guide distinguishes full cPanel archives from other backup products. Check plan, size and inode restrictions with the source provider before generation. Download the completed archive through authenticated access, not by moving it into the website directory.
• Liquid Web: its cPanel backup guide applies to a server running cPanel and requires that account’s login. It is not a backup workflow for every Liquid Web product.
• Namecheap: follow its cPanel backup documentation for the account export. Plan-specific AutoBackup options are distinct from the general Backup Wizard procedure below.
• Web Hosting Hub: use the Account Management Panel (AMP) for the correct account details. Its cPanel login guide explains where to find the temporary cPanel URL if the domain no longer points to that hosting. Use Web Hosting Hub’s account, not Namecheap’s.
• A Small Orange: its account-backup guide describes a home-directory full-backup export and separate database downloads. Use the provider dashboard for the correct account. Confirm a compatible full-account restore with the destination administrator rather than treating the ordinary home-directory restore as a full-account import.
• Arvixe: its manual cPanel backup guide describes the account backup and home-directory download. Confirm the actual panel and account before proceeding.

Use authenticated HTTPS access and verify the hostname and certificate. If the source uses a different panel or export system, stop and agree a compatible method with support. These references were checked during the editorial review; no provider dashboard was accessed or customer migration performed.

Create a full backup from the source account

The account owner does not need root access merely to generate a backup when the provider has enabled the feature. The privileged operation is a full-account restore. Missing backup tools or generation failures should be raised with the source provider.

1. Sign in through the provider’s authenticated HTTPS dashboard. Check that you are managing the correct source account.
2. Open Files > Backup Wizard > Back Up > Full Backup.
3. Choose Home Directory and the desired completion-notification option. Keep this location outside every public document root.
4. Start generation and wait for it to finish. Then use the authenticated interface’s download link to obtain the completed archive.

The cPanel Backup Wizard documentation describes this workflow. Interface labels and availability can vary with the installed version and provider configuration. The old screenshots were removed because they depicted a legacy interface, not a current walkthrough.

Review errors and available disk space before assuming that an archive is complete. Retain the original backup securely; do not publish it, email it to an unverified recipient or loosen filesystem permissions to make a web link work. Agree a private delivery method with the destination provider.

Restore the full account through the destination provider

A full archive is not restored through the ordinary cPanel account restore screen. Ask the destination provider or an authorized WHM administrator to handle it. Confirm the account mapping, software compatibility and any overwrite risk before the restore starts.

Backups are not interchangeable simply because they end in .tar.gz. Check that the archive is an actual supported account backup, not a manually compressed website directory. The provider should report restore warnings and any components that were skipped.

When partial backups are appropriate

The cPanel Backup interface offers separate home-directory, database, email-forwarder and filter downloads. Home-directory data can include mail files, but that is not the same as recreating working mailbox accounts and all server-side settings. Global filter exports do not include each mailbox user’s individual filters.

Keep a manifest of the components you selected. For a partial restore, select the matching component in Backup Wizard’s Restore screen and upload that component’s backup. Restore only to the agreed destination after protecting existing data. Check database users, grants and application credentials afterward; a database appearing in the panel is not enough to prove the application can use it.

Do not treat a partial backup as permission to lose DNS, mail or account configuration. If those components matter, arrange their migration explicitly or choose the full-account workflow.

If you migrate files and databases manually

Use an authenticated encrypted transfer method that both endpoints support, and include hidden files such as .htaccess. A directory copy can omit databases, scheduled tasks, external storage and application data outside that directory. Record those dependencies before copying anything.

Export each required database with a tool compatible with its engine and version. Import into the intended destination database, assign appropriate access and update the application’s connection settings. Never point a test copy at the production database just to make the connection error disappear.

For WordPress, keep the original hostname during migration where possible. A domain-name change is a separate task; naive text replacement in a SQL dump can damage serialized values. Do not combine unrelated URL changes with a hosting move unless they are part of the tested plan.

Test and cut over

• Preview the destination using the real hostname and an agreed hosts-file override or preview mechanism. An IP-only page is not a complete virtual-host or HTTPS test.
• Check files, application login, database-backed pages and important workflows. Disable real outbound jobs, payments and email while testing a separate copy.
• Verify mailboxes and routing separately if email is moving. Keep existing mail DNS intact when mail stays with another provider.
• Arrange a final synchronization or maintenance window for sites that receive new data. Reconcile changes before any rollback.
• Change only the DNS records required by the approved plan, monitor the result and retain the old service until verification is complete.

Use our website migration backup checklist for inventory, integrity checks and restore-test precautions. This guide was checked against current cPanel documentation; no customer account restore was performed as part of the review.