Can you migrate a whole network in one go

Yes, and on this platform it is the ordinary case rather than the exception. Send the current host details once and every account on it is moved, then each site is assigned an address out of your new allocation. A single Class C order can hold hundreds of addresses, so the size of the estate is rarely the constraint.

What changes when it is a network rather than a site

The copying is the same work repeated. What is genuinely different is that address assignment becomes a decision. Move one site and it goes on the address you have. Move forty and each one needs to land where you intended, because taking whatever address is next in the list is how an estate ends up with its most sensitive properties on adjacent blocks.

So the planning happens before the copying starts, not after. Decide the mapping, write it down outside the control panel, and migrate against that map.

A workable order for an estate move

1. Inventory first. Every domain, subdomain and mail account on the old host. Things that are not on the list do not get moved.
2. Plan the address mapping. Which site goes on which address, with the sensitive properties placed deliberately.
3. Lower record cache lifetimes across the estate a day or more ahead.
4. Migrate in batches rather than all at once. The first batch teaches you what is unusual about this particular estate.
5. Verify each batch before its delegation changes.
6. Cut over in the same batches, keeping the old host until the last one is settled.

Why batching beats a single sweep

A forty-site estate always contains three or four sites that are not like the others: an odd PHP requirement, a cron job nobody documented, a mail account somebody still uses. Discovering that on batch one costs you a small correction. Discovering it on all forty simultaneously costs you an afternoon of triage while sites are already switched.

Batches also keep the rollback cheap. At any point only one batch is in flight, and reverting one batch is a small operation.

Standing up new sites afterwards

If the estate runs WordPress, the panel can install across a list of domains in a single pass once the accounts exist, which is useful for the sites you are adding rather than moving. The caution from a fresh estate applies here too: a batch install produces identical sites, and identical is a footprint. Vary the visible parts deliberately afterwards.

Address planning is covered in IP Diversity, the per-site mechanics in Migration Basics, and if the estate is large enough to want its own machine, a dedicated server takes the same address blocks. To scope a specific move, contact us with the inventory.