How to Move Joomla to a New Hosting Provider
Prepare the destination before copying anything
Confirm the new host meets the technical requirements for the Joomla version you are running, including PHP, database, required PHP modules, and web-server capabilities. Also inventory DNS, email, cron or scheduled jobs, SSL certificates, CDN settings, and external integrations that are tied to the old host.
Create a current complete backup
Take a verified backup of the Joomla files and database immediately before migration. Joomla's copying guidance treats a site copy as two coordinated operations: copying the files and copying the database. Preserve the source host unchanged until the destination has been tested and the migration is accepted.
Transfer the Joomla files
Copy the complete Joomla document root to the new hosting account while preserving directory structure and hidden files. A compressed archive transferred over SSH or a hosting file manager can be more reliable than moving thousands of individual files. Check failed transfers and correct destination ownership according to the new host's model.
Export and import the database
Export the source database and import it into a new database on the destination. Create the destination database user with the privileges Joomla requires. Keep the source dump unchanged as a recovery artifact, and do not assume the database name, username, password, or host will be identical on the new provider.
Update environment-specific configuration
Edit configuration.php for the destination database host, database name, username, password, and any changed log or temporary paths. Joomla's copying documentation specifically calls out these values. Keep live_site empty unless a documented configuration requires otherwise, and protect configuration.php after editing.
Test before changing public DNS
Use a provider preview mechanism, temporary hostname, local hosts-file override, or another controlled method to test the destination. Verify frontend and Administrator access, SEF URLs, HTTPS, media, forms, email in a safe test mode, extensions, scheduled tasks, file writes, and server logs before normal visitors arrive.
Switch traffic and keep a rollback window
Update DNS only after the new host passes testing. Account for DNS caching and avoid making conflicting content changes on both servers during the transition. Monitor important workflows, retain the old hosting copy for a defined rollback period, then secure or retire it 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.