How to Move Joomla to a New Domain
Moving Joomla to a new domain changes the public identity of the site and can affect DNS, HTTPS, redirects, cookies, integrations, and search-engine signals. Plan the hostname change separately from any server move, test the new domain before cutover, and keep the old domain working long enough to redirect existing URLs cleanly.
Identify exactly what the domain move changes
A domain move may keep the same server or happen together with a hosting migration. List the hostname, DNS, TLS certificate, document root, database, email, CDN, analytics, APIs, OAuth callbacks, webhooks, and extension licensing that may depend on the old domain. Separating these layers makes rollback much easier.
Back up the working site first
Create a current full filesystem and database backup before changing the public hostname. If files or database are also moving, keep them from the same recovery point. Preserve the old domain and working site until the new hostname is validated and redirects are operating correctly.
Configure the new hostname and HTTPS
Add the new domain to the hosting virtual host, control panel, reverse proxy, or CDN and point its document root at the intended Joomla files. Issue and test a valid TLS certificate before forcing HTTPS. Verify both the bare and www form if both are meant to resolve, and choose one canonical hostname.
Review Joomla and extension settings
Joomla normally does not require a hard-coded $live_site, so do not add one just because the domain changed. Review cookie settings only if they were explicitly customized. Check extensions for absolute URLs, domain restrictions, callback URLs, webhook endpoints, CORS rules, API allowlists, and license bindings.
Update old-domain references carefully
Search articles, Custom modules, template settings, CSS, JavaScript, email templates, structured data, feeds, sitemaps, analytics, and integrations for absolute old-domain URLs. Back up the database before bulk edits and change only confirmed fields; blind replacements can damage encoded or extension-specific data.
Redirect and verify the old URLs
After the new domain is fully tested, configure permanent redirects from old public URLs to their corresponding new URLs, preserving paths and query strings where appropriate. Test frontend and Administrator login, SEF routes, forms, email, media, APIs, webhooks, scheduled tasks, canonical URLs, sitemap URLs, and robots behavior. Monitor 404s and redirect chains after cutover.
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.