Sébastien Laframboise

Restore a WordPress site to a different hosting provider

Restore a WordPress site to a different hosting provider

When a host fails, shuts down its services, or becomes inaccessible, you need to get your site back online without turning the emergency into a makeshift migration. To restore WordPress on another host, start from a reliable backup, recreate the minimal environment, verify the site before the DNS switch, and keep a fallback option.

This procedure aims to keep the business running. It does not replace a planned migration, where you can compare offers and prepare every detail well in advance. Here, the priority is to restore a functional site with as little loss as possible.

Start by choosing the best available backup

Don’t automatically pick the most recent copy. First check its date, size, creation log, and location. A recent but incomplete backup won’t help you restore a stable site.

To rebuild a complete site, you need the site files and an export of its database. Media, the theme, plugins and uploaded files do not replace the content, settings, and accounts stored in the database.

Before you start, consult your verification of a complete and recent WordPress backup. .

If multiple copies exist, choose the one that offers the best balance of recency and integrity.

Determine what may have changed since the backup.

Record the time of the selected backup. Then list items possibly lost since then: orders, submitted forms, comments, registrations, page edits, or media added. This list will help you inform your team and resume operations after recovery.

Also keep the original backup intact. Always work from a copy. That way you can start over if an import fails or a setting on the fallback host causes issues.

Prepare the fallback host without putting the site live too quickly.

Create a separate hosting space, an empty database, and administrator access to the control panel. Then verify that the environment supports the PHP version required by the restored site. A version mismatch can prevent an older theme or plugin from working correctly.

The official guide Also prepare external elements the site depends on: HTTPS certificate, DNS access, email sending service, API key, remote storage, payment gateway, and analytics tools. You don’t necessarily have to reactivate everything before testing, but you should know what’s missing. Migrating WordPress.

confirms that moving to a new server requires transferring the files and the database. It also reminds that changing the address requires special attention to URL settings and stored data.

Restore the files and the database.

Use your host’s restore tool if your backup is compatible with it. Otherwise, upload the files to the target web space, then import the database into the database created for this recovery.

Then configure WordPress’s connection to this new database using the parameters provided by the host. This step must match exactly the database name, user, password, and database server of the new environment.

After the import, check that the expected tables are present and that the database size seems consistent with the backup. An import that finishes without errors can still be partial if a host control panel limit interrupted the process.

Test the restored copy before switching DNS.

Keep the public domain pointing to the old server as long as possible. Instead, test the restored copy using the temporary address provided by the host or a private preview method. Avoid letting visitors submit forms or place orders on two active copies.

If you keep the same domain and addresses, restoration usually requires fewer fixes. Still, inspect links, images, and redirects. The site address settings determine the URLs used by both the admin and the public site; WordPress shows them in the installation’s General Settings.

Perform a short, real functional check

  • Open the homepage, several key pages, and a few older posts.
  • Check the menus, search, images, downloads, and internal links.
  • Log in with an admin account, then confirm the essential roles.
  • Send a contact form to a monitored inbox.
  • Test sending and receiving a WordPress email.
  • For a shop, place a test order using your test payment method.
  • Check scheduled tasks, external integrations, and visible error messages.

A restoration trial in a controlled environment reduces surprises at the worst time. Also consult the article on how to test restoring a WordPress backup before an emergency to turn this checklist into regular maintenance.

Emails deserve separate attention. New hosting can require a different authentication method or block local sending. If needed, use your guide to choose a WordPress SMTP plugin and validate messages before returning forms to production.

Switch the DNS during a controlled window

When tests are successful, schedule a short cutover window. Record the current DNS value, the new server address, the planned time, and the person responsible. Temporarily disable sensitive actions on the old site if both environments might receive different data.

Then update the DNS records that point the domain to the new hosting. The TTL indicates how long a resolver can keep a record before requesting an update, as explained by Cloudflare in its guide on common DNS issues. Therefore, some visitors may reach the old server for a limited time.

Monitor the site from a private browser and a mobile device. Also check the HTTPS certificate, redirects, admin area, and forms. Document any anomalies with the time and affected page. You can then distinguish normal DNS caching from a real restoration failure.

Plan a rollback before declaring recovery complete

A rollback plan should be simple: keep the old hosting for an agreed period, document its DNS records, and know which data may diverge. If the new site fails on a critical function, you can redirect traffic to the old infrastructure while you fix the issue.

Finally, once the site is stable, create a new full backup from the fallback hosting. Update your access credentials, emergency contacts, and recovery procedure. Your next incident will then be a documented restoration, rather than a race against the clock.