---
title: "How to migrate a WordPress site to a new host (step by step)"
description: "Step-by-step guide to migrate a WordPress site to a new host or domain without losing anything: checklist, file or key migration and final checks."
url: https://migram.app/en/how-to-migrate-wordpress-site/
language: en-US
updated: 2026-11-16
translations:
  pt: https://migram.app/como-migrar-site-wordpress.md
  es: https://migram.app/es/como-migrar-sitio-wordpress.md
---

# How to migrate a WordPress site to a new host (step by step)

> The step-by-step way to move a WordPress site to a new host or domain without losing anything: preparation, migration by file or straight between servers, and what to check afterwards.

*Migration · 15/11/2026*

IN SHORT

- Migrating WordPress means moving **the files and the database** to the new server and **replacing the old addresses** with the new ones.
- The safest way: make a full backup in a single file, import it on the destination and only then point the domain.
- With Migram, you migrate by file or **straight between servers**, with no size limit and an automatic domain change.

Moving a WordPress site to a new host feels risky, but it always follows the same script: copy everything, take it to the new server, fix the addresses and check before you flip the switch. This guide walks through that script from start to finish, with two methods: by file and straight from one server to the other.

## What a migration involves

A WordPress site has two parts, and both have to reach the new server:

- **Files**: the `wp-content` folder, with uploaded images and documents, plugins and themes.
- **Database**: posts, pages, users, settings and the options of every plugin.

If the domain changes too, there is a third step: **replacing the addresses** stored in the database. The catch is serialized data, which stores the length of each piece of text. A plain search and replace breaks that data, so the replacement must be done by a tool that understands the format.

## Before you start: checklist

1. **Make a full backup** of the current site and keep a copy off the server.
2. **Check the PHP version** of the new server: use the same as today, or a newer one your plugins support.
3. **Check the disk space**: the new server needs room for the backup file and for the unpacked site.
4. **Install a clean WordPress** on the destination (most hosts do it in one click).
5. **Lower the DNS TTL** of the domain a day before, so the switch takes effect faster.
6. **Tell the people who edit the site**: anything published during the migration may be left out.

## Method 1: migration by file

This is the universal method: it works between any two servers, including from a local computer to a host.

1. On the current site, install [Migram](https://wordpress.org/plugins/migram/) (free) and open *Migram → Export*.
2. Choose what goes in the backup (the default is the whole site) and create the `.migram` file. Download it.
3. On the clean WordPress of the new server, install Migram and open *Migram → Import*.
4. Upload the `.migram` file. It is sent in parts, so your host’s upload limit doesn’t matter.
5. Confirm the import. When it ends, log in again with a username and password **from the imported site**: its users replace the old ones.

## Method 2: straight between servers, with a migration key

When both sites are online, there is no need to download and upload the file. The backup travels from one server to the other:

1. On the source site, create a backup in *Migram → Export*.
2. In *Migram → Backups*, create the **migration key** of that backup. It starts with `MIGRAM1.` and expires.
3. On the destination site, open *Migram → Import → Migrate from another site* and paste the key.
4. The destination downloads the backup straight from the source server and imports it.
5. When you are done, revoke the key in *Migram → Backups*: anyone with the key can download that backup.

It is the fastest way for large sites, because the file never goes through your computer.

## Changing the domain in the same migration

When you import on a different address, Migram updates the site address, folders and URLs in the content on its own, including inside serialized data and JSON. In the advanced export options you can also add your own replace rules, for example to switch a CDN address.

After a domain change, add a **301 redirect** from the old domain to the new one and report the move in Google Search Console (Change of Address tool), so you keep your search rankings.

## After the migration: what to check

- Open *Settings → Permalinks* and click *Save* to rebuild the address rules on the new server.
- Turn on **SSL** (https) on the new server and make sure there is no mixed content (images over http).
- Test forms, checkout and outgoing e-mail: many hosts require SMTP.
- Clear the site, server and CDN caches.
- Only then point the domain’s DNS to the new server, and keep the old one online for a few days.
- Set up automatic backups on the new server (see the [WordPress backup guide](/en/wordpress-backup-guide/)).

## Common problems and fixes

| Problem | Likely cause | Fix |
| --- | --- | --- |
| “The uploaded file exceeds the maximum upload size” | Host upload limit | Use a tool that uploads in parts, like Migram, or migrate with a key. |
| The import stops halfway | PHP timeout | Migram works in short steps that resume where they stopped; keep the page open. |
| Blank page or error 500 | PHP version not supported by a plugin | Change the PHP version in the hosting panel. |
| Inner pages return 404 | Address rules not rebuilt | Save the permalinks again. |
| Broken images or a security warning on the padlock | Old or http addresses | Check that the domain change ran and turn on https. |

## Frequently asked questions

### How long does it take to migrate a WordPress site?

For most sites, from a few minutes to half an hour. Media size and server speed matter most. DNS propagation can then take a few hours.

### Does the site go offline during the migration?

No. The old site keeps working while you prepare the new one. The switch happens when the DNS points to the new server. When restoring on the same server, Migram keeps the current site online until the very last moment.

### Do I need a paid plugin to migrate a large site?

No. Migram is free and has no size limit: uploads, downloads and migrations run in parts. The only limit is the server’s disk space.

### Can I migrate from a local WordPress to my host?

Yes. Export the `.migram` file on the local site and import it on the host. The local address is replaced by the domain automatically.

### Does Migram work with WordPress multisite?

Not yet. For now Migram is for regular installs, with one site per WordPress.
