How to Move a Joomla Website to a New Server

Moving Joomla to a new server is a controlled restore followed by a traffic cutover. The safest migration keeps the old server intact until the destination is proven, transfers both files and database from a consistent point, updates only environment-specific settings, and tests the new server before DNS or proxy traffic changes.

Prepare a compatible destination

Confirm the new server supports the installed Joomla release and important extensions. Provision the required PHP version and modules, database service, HTTPS certificate, web-server configuration, storage, and resource limits. Create the destination database and credentials before the maintenance window.

Create a consistent source recovery point

  1. Back up the complete Joomla filesystem.
  2. Export the complete database, including extension tables.
  3. Record the backup time and Joomla version.
  4. For a busy site, use a maintenance window or another consistency method so late writes are not lost.

Keep the source server unchanged until the new server passes validation.

Transfer the Joomla filesystem and database

Copy or archive the entire Joomla installation into the new document root, including configuration.php, hidden server files where applicable, media, templates, overrides, and extension files. Import the database export into the destination database. Large sites are often more reliable to transfer as archives than as thousands of individual files.

Update configuration.php for the new server

Set the destination database host, database name, username, and password. Confirm the table prefix. Correct absolute log and temporary paths when the filesystem changed. In normal Joomla configurations, leave $live_site and cookie-domain settings empty unless there is a specific documented requirement.

Test the destination before switching traffic

  1. Use a hosts-file override, staging hostname, or controlled proxy route to reach the new server.
  2. Test frontend and Administrator access.
  3. Test SEF URLs, media, forms, login, email in safe mode, and critical extensions.
  4. Verify file permissions and writable directories.
  5. Review PHP and web-server logs.
  6. Confirm scheduled jobs will not run simultaneously on old and new servers.

Switch traffic with a rollback path

Update DNS or upstream routing only after the destination passes testing. Account for DNS caching and keep the old server available for a defined rollback period. Monitor errors, database writes, forms, authentication, email, and integrations after cutover.

When the move is stable, disable production jobs on the old server, secure or retire the old copy, and create a fresh full backup of the new environment.


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.

Open a Support Ticket