Restore or Move a Joomla Site to Another Domain or Server with QCBM

QCBM can use a verified Recovery Package to restore a Joomla site to a different domain, hosting account, server, or filesystem path. In the Recovery Runner, this is the Restore or move to this domain destination purpose.

A new-location recovery needs more than copying files: review the target database, Joomla environment settings, HTTPS, server-control files, and administrator access before you declare the move complete.

1. Prepare the New Destination

Create or identify the destination Joomla root, database, database user, DNS/domain access, and HTTPS configuration. Preserve any existing destination data that matters before you extract the Recovery Package.

Make sure the destination has enough free space for the package, staging, rollback state, and restored files.

2. Place the Package in the Exact Target Root

Extract the complete Recovery Package directly into the Joomla root you intend to use on the new server. The runner locks recovery to the physical directory containing qcbm-recover.php; that path cannot be changed in the browser.

3. Verify the Backup and Test the Destination

Open the destination, enter the package PIN, select Verify Backup, then select Test Locked Destination. Resolve missing files, checksum errors, path permissions, or disk-space problems before continuing.

4. Choose Restore or Move to This Domain

Under Destination purpose, select Restore or move to this domain. Enter or confirm the target domain shown in the runner.

New-location recovery deliberately uses more conservative destination-preservation choices than same-site recovery unless you explicitly select more destructive behavior.

5. Configure the Target Database

Enter the database host, port/socket, name, username, password, and Joomla table prefix appropriate to the new environment. Select a database strategy that matches the destination and then use Test Database.

Do not reuse old hosting database values merely because they were captured with the source Backup Set. A move commonly changes database hostnames, credentials, names, and permissions.

6. Review Joomla Environment Settings

Check Joomla site name, site online/offline state, Force HTTPS, timezone, cookie domain, and cookie path. The runner locks the temporary and log directories to paths under the new target root.

Advanced options also let you decide how to handle outgoing mail, cache, active sessions, the Joomla secret, and server-control files.

7. Pay Special Attention to .htaccess and Server-Control Files

A source .htaccess can contain domain redirects, subdirectory rules, PHP handlers, access controls, or paths that are unsafe on another server. For genuine cross-domain or cross-path recovery, QCBM quarantines environment-sensitive source .htaccess rather than blindly activating it.

If QCBM shows a Needs Attention notice after recovery, review the preserved source rules, test routing, and explicitly mark the item reviewed only after the destination behaves correctly.

8. Recover, Validate, and Finalize

Select Recover Site only after the locked root and database tests pass. After recovery, verify the frontend, administrator, login/logout, SEF URLs, redirects, uploads/downloads, extension routes, mail behavior, and other environment-sensitive functions.

Complete Confirm Installation, disable and clean up the runner files, download the Recovery Report, and then select Close.

Migration Checklist

  • Correct DNS/domain and HTTPS.
  • Package extracted in the intended target root.
  • Backup verification passed.
  • Target path test passed.
  • New database credentials and grants tested.
  • Cookie, HTTPS, tmp/log, mail, cache, and session settings reviewed.
  • Source server-control rules reviewed for the new environment.
  • Frontend and administrator validated before final cleanup.

Community Discussion

Want to compare workflows, share practical tips, or discuss how you use this QCBM feature? Visit the QC Backup Manager Community. For private support, bug reports, account-specific issues, or feature requests, use the QuantaCade support system.