How to Move Joomla to a New Domain
Separate the domain change from the site copy
A domain move may happen on the same server or together with a hosting migration. Identify which layers are actually changing: hostname, DNS, TLS certificate, document root, database, email, CDN, or application integrations. Keeping these changes explicit makes rollback and troubleshooting much easier.
Back up files and database before the move
Create a current complete backup before changing the public domain or configuration. If files or database are also moving, keep them from the same recovery point. Preserve the old site long enough to verify the new domain and to implement redirects for visitors and search engines.
Point the new domain at the Joomla installation
Configure the new domain in the hosting control panel, virtual host, reverse proxy, or CDN and issue a valid TLS certificate before forcing HTTPS. Make sure the new domain's document root points to the intended Joomla files and that PHP uses a version supported by the installed Joomla release.
Review Joomla and extension configuration
Joomla commonly works without a hard-coded live_site value, so do not add one merely because the domain changed. Review configuration.php, cookie settings, cache, log and tmp paths only where the environment requires it. Search extension settings for absolute URLs, callback addresses, webhook endpoints, licenses, CORS rules, or domain restrictions.
Update content and integrations that contain the old hostname
Check articles, Custom modules, template settings, CSS, JavaScript, email templates, structured data, analytics, feeds, sitemaps, payment systems, identity providers, and external services for absolute old-domain URLs. Back up the database before any bulk replacement and avoid blind replacements in encoded or extension-specific data.
Redirect the old domain deliberately
After the new domain is fully tested, configure permanent redirects from old public URLs to their corresponding new-domain URLs where appropriate. Preserve paths and query strings when they remain valid. Avoid sending every old URL to the home page, and keep the old domain and certificate active while redirects are required.
Validate the new canonical site
Test frontend and Administrator login, HTTPS, SEF URLs, forms, email, media, APIs, webhooks, scheduled tasks, and important extension workflows. Inspect canonical signals, internal links, sitemap URLs, robots behavior, and search-engine properties. Monitor 404s and redirect chains after traffic switches.
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.