Joomla Migration Checklist: What to Verify Before and After a Site Move
Before the move: verify the recovery point
Create and verify a complete backup immediately before the migration. A Joomla site move requires both the website files and the database, so keep them as one dated recovery set. Record the source Joomla version, PHP and database environment, important extension versions, and current DNS values. Keep the source server intact until the destination has passed validation.
Before the move: verify destination compatibility
Confirm that the destination meets the technical requirements for the installed Joomla major version, including PHP, database server, required PHP modules, web-server support, and practical resource limits. Check third-party extension and template requirements as well. Do not discover an incompatible runtime only after production traffic has been moved.
During the move: verify files, database, and configuration
Transfer the complete Joomla filesystem and import the complete database, including extension tables. Preserve configuration.php, media, templates, overrides, custom code, and applicable hidden server files. Update configuration.php for the destination database host, name, username, and password, and correct absolute log and temporary paths when the filesystem location changed.
Before cutover: verify the destination privately
Test the destination before changing public traffic by using a hosts-file override, provider preview, temporary hostname, or another controlled method. Verify frontend and Administrator login, menus, articles, media, uploads, forms, search, SEF URLs, template output, extension pages, HTTPS, and Joomla/PHP/server logs. Keep live external integrations in test or disabled mode where appropriate.
Before cutover: verify routing and external dependencies
Check Apache .htaccess or Nginx routing for the new environment, including direct SEF requests and static files. Verify SMTP, outbound HTTPS, APIs, payment gateways in safe mode, webhooks, storage services, scheduled tasks or cron, DNS-dependent services, and IP allowlists. A server move can change public IP addresses and network policy even when Joomla itself is configured correctly.
At cutover: verify DNS and data consistency
Change only the DNS records required for the website and preserve unrelated mail, verification, and third-party service records. Account for DNS caching and TTL behavior. On sites that accept registrations, orders, submissions, or content changes, use a maintenance window, final synchronization, shared backend, or another deliberate strategy so old and new servers do not collect conflicting writes.
After the move: verify real traffic and keep rollback available
Confirm that public DNS resolves to the intended destination and that real HTTPS requests reach the new server. Retest frontend and Administrator access, SEF URLs, media, forms, login, email, scheduled tasks, APIs, and critical extension workflows. Monitor access, PHP, Joomla, and server error logs. Keep the old server available for the planned rollback period, then create a fresh destination backup and securely retire the old copy only after the migration is accepted.
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.