How to Move a Joomla Website to a New Server
Prepare the destination before moving data
Provision a server that supports the Joomla and PHP versions used by the site, along with the required database server and PHP extensions. Create the destination database and credentials, configure HTTPS and the virtual host, and confirm you can access logs and manage files before starting the production move.
Create a complete source backup
Back up both the Joomla files and database immediately before the move, using a consistent recovery point. Keep the original site intact until the destination has been validated. For a busy site, use a maintenance window or another consistency method so late database changes are not lost during transfer.
Transfer the complete Joomla filesystem
Copy or archive the full Joomla installation to the new document root, including configuration.php, hidden server files where applicable, media, templates, overrides, and extension files. Joomla's copying documentation notes that a compressed archive can be more reliable than transferring large numbers of individual files.
Export and import the database
Export the complete source database and import it into the new destination database. Include extension tables as well as Joomla core tables. Joomla's official copying guidance documents phpMyAdmin and command-line methods such as mysqldump and mysql for this step.
Update configuration.php for the new environment
Set the destination database host, database name, username, and password. Check absolute log and temporary paths and correct them when the server filesystem changed. Joomla's copying documentation recommends leaving live_site empty in normal configurations and also notes cookie_domain should normally be empty.
Test before changing production traffic
Use a hosts-file override, temporary hostname, staging URL, or another controlled method to test the destination. Verify frontend and Administrator access, SEF URLs, media, forms, email in safe mode, extensions, scheduled jobs, permissions, HTTPS, and server logs before directing normal visitors to it.
Switch traffic and monitor the new server
Update DNS or the upstream routing only after the destination passes testing. Keep the old server unchanged for a defined rollback period, monitor errors and important workflows, and account for DNS caching during the transition. After the move is stable, secure or retire the old copy and create a fresh destination backup.
Need More Help with Joomla?
Still having trouble? Open a support ticket with QuantaCade Support and we'll be happy to help where we can.
Support priority is given to QuantaCade products, services, and customers. However, we're also happy to assist fellow Joomla users with general Joomla questions and troubleshooting when possible.
QuantaCade is an independent Joomla extension developer and is not official Joomla support. Some issues involving third-party extensions, hosting environments, server configurations, or other systems outside our development control may be beyond what we're able to resolve.