How to Move Joomla to a New Hosting Provider
Moving Joomla to a new hosting provider is a controlled migration of the complete site, not just a file copy. The safest process prepares a compatible destination, transfers a matched filesystem and database, tests the new host before public cutover, and keeps the old host available long enough to roll back if necessary.
Plan the hosting move before copying anything
Inventory the parts that will change: PHP and database versions, document root, DNS, TLS, mail delivery, scheduled jobs, CDN or proxy settings, and external integrations. Confirm the destination meets the requirements of the installed Joomla release and important extensions before beginning the transfer.
Create a consistent recovery point
Create a complete backup of the Joomla filesystem and database from the same point in time. For an active site, use a maintenance window or another method that prevents late writes from being lost. Keep the source hosting account unchanged until the destination has been accepted.
Transfer the files and database
Copy the complete Joomla document root, including intentional hidden files, media, templates, overrides, and extension files. Create a new destination database and user, import the matching database dump, and apply the ownership and permissions expected by the new provider. Do not point the new copy at the old production database.
Update environment-specific configuration
Edit configuration.php for the destination database host, database name, username, password, and any changed log or temporary filesystem paths. Keep $live_site empty in normal configurations unless there is a documented reason to set it. Review host-specific PHP settings and rewrite rules as well.
Test the destination before DNS cutover
Use a hosts-file override, temporary hostname, or provider preview method to reach the new server without sending normal visitors there. Test the frontend, /administrator, SEF URLs, HTTPS, media, forms, login, email in a safe mode, file uploads, critical extensions, and scheduled tasks. Review PHP and web-server logs for errors.
Switch traffic with a rollback path
Change DNS or upstream routing only after the destination passes testing. Avoid simultaneous content changes on both copies during propagation. Monitor forms, authentication, email, database writes, integrations, and error logs. Keep the old host available for a defined rollback period, then disable old scheduled jobs, secure or retire the old copy, and create a fresh backup on the new provider.
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.