- Home
- Site
- Site Migration
- Bulk Migration
Bulk Migration
Bulk Migration moves every WordPress site from one hosting server onto a FlyWP server in a single run. You give FlyWP SSH access to your old server once, it finds the sites for you, and it copies them across one at a time while you watch the progress. Your old sites stay online the whole time, and nothing switches over until you say so.
If you only need to move one site, the existing single-site methods are simpler. Bulk Migration is for the case where you are leaving a host and want everything on it.
Supported sources
Section titled “Supported sources”| Source | Status |
|---|---|
| Cloudways | Available |
Support for more hosting providers is on the way.
Before you start
Section titled “Before you start”- Create your FlyWP server first. A bulk migration is started from the server you are migrating onto, so the destination has to exist before you begin. There is no step in the wizard for choosing one.
- Get SSH access to your old server: its public IP address, a username, and a password. On Cloudways, see Using Cloudways.
- Check you have room. The destination server needs enough free disk for every site you select, plus working space. FlyWP measures this for you before anything is copied.
How a bulk migration works
Section titled “How a bulk migration works”
The wizard runs in six steps. Two of them wait for you; the rest run on their own.
- Source: you pick the platform you are migrating from and enter its SSH details.
- Discovery: FlyWP connects to your old server, starts the migration agent on it, and lists every WordPress site it finds. Sites whose files are found but whose database cannot be read are excluded automatically, with the reason shown. This step then runs pre-flight checks against the destination server: that it has room (Destination storage), that the source is authorized on it (Source authorized on destination), and that the two servers can reach each other (Destination access verified). If these checks do not report within 10 minutes, the migration stops and nothing is copied.
- Confirm: you decide. Under the heading Review your migration, you see every site that was found, its size, and whether the selection fits the destination. Nothing has been copied at this point. Tick the sites you want and click Start Migration.
- Transfer: each selected site is copied and verified, one site at a time. Large sites take a while; the page shows which site is in progress and how far along it is, with counts for Queued, In progress, Ready to go live, and Failed.
- Going Live: you decide again. Once every site has been copied and verified, they wait. When you click Go Live, FlyWP stands each site up on the destination and serves it on a temporary test domain so you can check it before moving your real domain.
- Summary: what the run produced, with a link to your migrated sites and, if anything failed, a retry button.
Starting a bulk migration
Section titled “Starting a bulk migration”-
Log in to your FlyWP dashboard.
-
Open the server you want to migrate onto.
-
On the Sites tab, click Migrate.

-
In the Migrate Your Site window, choose Bulk Migration.
-
Pick your source platform, enter its SSH details, and click Discover Sites.
-
Follow the wizard through to Go Live.

What gets migrated
Section titled “What gets migrated”For each site, FlyWP copies the site’s files and its database, and carries over the PHP, WordPress, and database versions it was running on the old server.
The following are not migrated:
- Server-level configuration: cron jobs, custom server settings, and anything outside the site’s own directory.
- Email. Mail hosted on the old server does not move.
- DNS. Your domains keep pointing at the old host until you change them yourself.
Limits
Section titled “Limits”| Limit | Value |
|---|---|
| Migrations running at once, per team | 3 |
| Migrations per source server | 1 at a time, across all of FlyWP |
| Sites copied at once | 1 (sequential, not parallel) |
| Sites per migration | No fixed limit |
| Time allowed to find sites | 10 minutes |
| Time to confirm your sites after discovery | 72 hours |
| Time to click Go Live after the copy finishes | 7 days |
A migration that finishes with some sites failed stays available for retry for 2 hours. After that it is closed out and releases its hold on the source server, and you would need to start a new migration for the sites that failed.
If you leave a migration waiting at Confirm for more than 72 hours, or waiting at Go Live for more than 7 days, it is cancelled and cleaned up, and you would start a new one.
Only one migration can run against a given source server at a time, across all of FlyWP. This applies across all FlyWP accounts, so if anyone, in your team or another one, already has a migration running against the same IP address, yours will not start until theirs finishes.
Any member of the team that owns the destination server can start a bulk migration. FlyWP checks only team membership, with no separate plan or role requirement.
Destination storage
Section titled “Destination storage”At the Confirm step, FlyWP adds up what your selection actually needs and compares it against the destination’s free space. The estimate covers four things:
- Site data: the files and databases being copied.
- Working copy while each site goes live: temporary space for the largest single site.
- Docker and WordPress per site: roughly 600 MB for each site’s container and clean WordPress install.
- Free space kept in reserve: 5% of the payload, or 2 GB, whichever is larger, so the server is never filled to the last byte.

If the selection does not fit, Start Migration is disabled and you are told how much is needed against how much is free. Deselect some sites and run them as a second migration, or give the server more storage.
If FlyWP cannot measure the free space, or a site did not report its size, you will see a warning instead of a block: the migration is allowed to go ahead, but it may run out of room.
How it works under the hood
Section titled “How it works under the hood”You do not need any of this to run a migration, but it is useful to know what is happening on your servers.
- FlyWP connects to your source server over SSH and installs a small migration agent on it. The agent is what reads your sites and copies them.
- Your site data goes directly from your old server to your FlyWP server. It does not pass through FlyWP’s own infrastructure at any point.
- Your source server needs to be able to make outbound HTTPS connections, so the agent can report progress back.
- On the destination, FlyWP connects as the
flyuser using a temporary key created for that migration and removed afterwards. - The SSH credentials you enter are encrypted at rest and used only for that migration.
- When the migration settles, the agent is stopped and removed from your source server.
Using Cloudways
Section titled “Using Cloudways”Cloudways is the supported source today. To fill in the Source step:
- In the Cloudways dashboard, go to Servers, open your server, then Server Management and Master Credentials.
- Copy the public IP into Source Server IP. Use the public address, not a private or internal one.
- Copy the master username (it looks like
master_xxxx) into SSH Username, and the password into SSH Password. - Click Discover Sites.
If you enter a private or internal address, FlyWP stops straight away with This is not a public IP address. Use the public IP of your Cloudways server (Cloudways → Servers → Server Management → Master Credentials). It no longer waits for a connection to time out first.

Port 22 on the Cloudways server must be reachable, and its firewall must allow FlyWP through.
If something goes wrong
Section titled “If something goes wrong”Discovery fails. The wizard says why, and Start over takes you back to the first step:
| What you see | What to do |
|---|---|
| Could not reach your server | Check the IP is the public IP of your server, that port 22 is open, and that the server's firewall allows FlyWP through. Then try again. |
| Sign-in was refused | Check the SSH username and password, and that the IP belongs to your Cloudways server. |
| We could not start the migration | The problem is on FlyWP's side and our team is alerted. Try again later. |
| Discovery failed | Try again, and contact support if it repeats. |
A site fails during the copy or Go Live. The site shows a red notice saying what broke and what to do. You do not see the raw server error, but our team can: FlyWP keeps the stage and step the site failed at and the last 50 lines of the migration agent's log for 7 days, so support can look into it. When you contact support, give your server name and the site address.

Common notices:
- The destination server ran out of storage space while copying this site: add storage or resize the server, then retry.
- WordPress could not start on the new server: usually a plugin or theme that does not work on the new server. Fix it on the source site, then retry. The site is copied again from the source, so your fix comes across.
- Any other failure: retry the site, and contact support if it keeps happening.
Use the retry button on the summary to try again (see Managing your migrations). If a site is stuck with no progress for a long time, FlyWP's team is alerted automatically after about 30 minutes without any news from it.
Managing your migrations
Section titled “Managing your migrations”Click Migrations in the sidebar to see every bulk migration for your team, past and present.


- Resuming: click into any migration to return to the step it is on.
- Cancelling: a migration can be cancelled at any point before it finishes, from the Cancel Migration button in the wizard header. Sites that have already gone live stay live; the rest stop where they are.
- Retrying failures: if a migration finishes with some sites failed, a retry button appears on the summary, labelled with the number that need it, such as Retry 3 Failed Sites. A site that failed during the copy is copied again, picking up where it stopped. A site that failed at Go Live keeps its copy and only repeats Go Live, except when WordPress could not start, which is copied again from the source. Retried sites then wait for you to take them live. Sites that already migrated are left exactly as they are.
Next Steps
Section titled “Next Steps”Still stuck? How can we help?
View as Markdown