Move a PBN in small, staggered batches, not all at once. Inventory every site, take your own backups, copy each site to the new host and check it there before you touch DNS, then switch name servers, confirm SSL and watch indexing for a week or two before moving the next batch. Done this way, a host change should look like routine site maintenance, not a network moving together.
Last updated: October 2026. Prices exclude tax and may change. We may earn a commission if you sign up through our links.
People switch PBN hosts for all sorts of reasons: a provider shuts down, prices rise, or an audit shows too many sites share one IP owner. The move itself is rarely what costs rankings. What costs rankings is downtime, broken pages, lost SSL, and dozens of sites changing infrastructure on the same afternoon. Here’s a process that avoids all four.
Step 1: What should you inventory before moving?
Build a spreadsheet before you do anything else. One row per domain, with:
- Current host, IP and IP owner
- Registrar and current name servers
- CMS (WordPress, static HTML, other) and PHP version if relevant
- Admin logins and any email accounts on the domain
- Number of indexed pages (a
site:search gives a rough figure) - Which money site or sites it links to
- Registrar renewal date
The inventory does two jobs. It’s your checklist during the move, and it’s a footprint audit. If the sheet shows 30 sites sharing one name server pair, you now know what the new setup needs to fix. Our Class C IP guide explains which hosting signals are worth checking.
Step 2: How should you back up PBN sites?
Take your own full backup of every site, even if the old host and the new one both offer backups. For WordPress, that’s the files (especially wp-content) and a database export. For static sites, the whole web root. Store copies somewhere that isn’t either host.
Check that a backup actually opens. A zip that won’t extract or an SQL dump that stops halfway is common, and you want to find out now rather than after the old account is cancelled.
Step 3: Should you let the new host migrate for you?
If it’s offered for free, usually yes. It saves time and the host’s staff do this daily. Both hosts on our shortlist include free migrations:
- LaunchCDN, best for large networks & CDN hosting, migrates any number of sites for free. Sites are served through Amazon CloudFront, Cloudflare or Bunny.net, with randomized name servers and clean SOA records.
- Bulk Buy Hosting, best for real shared-hosting IPs with cPanel, also migrates for free, placing each site in its own account on a different server at one of 10+ shared hosts.
Using both is best for maximum IP diversity, and the two are complementary: either one will migrate sites for free, so you can split a network between them as part of the move. Even with a managed migration, keep your own backups from Step 2.
Step 4: Why stagger the moves?
Because simultaneous changes are a pattern. If 60 domains change IP, name servers and SOA on the same day, anyone looking at DNS history can see a cluster that moved together. Spread the work out:
- Move in batches of a few sites, not the whole network.
- Leave several days to a couple of weeks between batches.
- Mix the batches. Don’t move all the sites that link to one money site together.
- If you’re splitting across two hosts, alternate which host each batch goes to.
Start with your least valuable sites. If something goes wrong with your process, you learn on a site that doesn’t matter much.
Step 5: How do you test a site before switching DNS?
Once a site is copied to the new host, check it before any visitor or crawler is sent there. The usual method is to point the domain at the new server on your own computer only, by editing your local hosts file, or to use a preview URL if the host gives one. Then check:
- The homepage and a sample of inner pages load without errors.
- Images, CSS and internal links work.
- Outbound links to money sites are intact and unchanged.
- You can log in to the admin area.
- robots.txt and any noindex settings are what you expect. A staging “discourage search engines” tick left on is a classic mistake.
Step 6: What’s the right way to switch DNS and name servers?
A day or two before the switch, lower the TTL on the domain’s DNS records if your current DNS allows it. That makes the change propagate faster. Then update name servers at the registrar (or the A record, depending on the new host’s setup).
Keep the old hosting live until the new site is confirmed working and propagation has settled, typically a few days. Some visitors and crawlers will still hit the old server during that window. Cancelling early creates downtime.
Use the new host’s name servers rather than a custom pair you reuse everywhere. Shared custom name servers are one of the easiest ways to link a network.
Step 7: How do you make sure SSL doesn’t break?
If a site was on HTTPS, it must stay on HTTPS from the first minute on the new host. An expired or missing certificate means browser warnings and crawl errors. Both LaunchCDN and Bulk Buy Hosting include free SSL, but certificates are often issued only after DNS points at the new server, so check each site shortly after switching:
- The padlock shows, with no warning.
- HTTP redirects to HTTPS.
- There are no mixed-content warnings from images or scripts loaded over HTTP.
Step 8: What should you check after the move?
Over the following one to two weeks, for each batch:
- Indexing. Repeat the
site:check and compare it to your inventory. A small wobble is normal. A big drop means something is wrong. - Search Console, if the site is verified there. Look for crawl errors and coverage changes. If you don’t use Search Console on PBN sites, don’t add it now just for the move.
- Uptime. A basic uptime monitor catches problems you’d otherwise miss.
- Money site rankings. Watch for movement, but give it time. Rankings often fluctuate after any change.
- Email. If the domain sends or receives mail, test it. MX records are easy to lose in a move.
Only start the next batch once the previous one looks stable.
What mistakes cause ranking losses after a move?
- Moving everything the same day. It’s the biggest footprint risk in the whole process.
- Cancelling the old host too early, leading to downtime during DNS propagation.
- Changing content at the same time. Move first, edit later, so you know which change caused what.
- Losing links. A broken plugin or missing post can silently remove the very link the site exists for.
- Recreating the old footprint on the new host: the same theme everywhere, the same analytics ID, the same custom name servers. A move is a chance to fix these. See our digital footprint guide.
- Blocking the wrong bots. A new CDN or firewall setting can block AI crawlers or even search engines. Our robots.txt for AI crawlers guide shows how to check.
How long does a PBN migration take?
The copying is quick. The waiting is what takes time. A 10-site network moved in a few batches might take a few weeks end to end. A 100-site network moved carefully can reasonably take a couple of months. That’s fine. Slow is the point.
If cost is part of the reason you’re moving, see how much a PBN costs, or compare the two hosts directly in our comparison table.
Frequently Asked Questions
Will moving my PBN to a new host hurt rankings?
Not if you avoid downtime, keep SSL working, leave content and links unchanged, and stagger the moves so sites do not all change infrastructure together.
How many PBN sites should I move at once?
A few at a time, with several days to a couple of weeks between batches. Moving the whole network on one day creates a visible pattern.
Do PBN hosts migrate sites for free?
Both LaunchCDN and Bulk Buy Hosting offer free migrations. LaunchCDN migrates any number of sites. Keep your own backups either way.
When can I cancel my old PBN hosting?
Only after each site is confirmed working on the new host and DNS propagation has settled, usually a few days after switching.