Moving a site to another CDN

You can move a site to a different CDN whenever you like: onto another CDN from our pool, or onto a CDN account of your own that you have connected on your Connections page.

From the dashboard

Open the site, then the CDN tab. The card Where this site is served from lists every CDN the site can use, marks the one serving it now, and says why any choice is not available. Pick one and press Move this site.

From the API or your AI assistant

The same move is POST /v1/sites/{siteId}/cdn/swap. An AI client connected to your account (Claude, ChatGPT or any MCP client) can do it with your permission: cdn_targets_list shows the choices, cdn_move_start starts the move, cdn_move_status follows it and cdn_move_cancel undoes it. The connection needs the hosting.cdn.manage permission, and the assistant always moves to a CDN from that list, never to one it made up.

What happens during the move

1. We build the site on the new CDN while the old one keeps serving it.
2. We copy your DNS records and point your domain at the new CDN.
3. Once the new CDN serves the site, we remove the old zone.

Both CDNs serve the site throughout, so nothing goes offline while it moves. Pages may load from a cold cache for a little while as the new CDN fills it.

When the nameservers change

A move onto Cloudflare changes your domain's nameservers:

• Your domain is registered with us: we change them for you.
• Your domain is registered elsewhere: the CDN tab and an e-mail give you the exact pair to set at your registrar, with a Check now button. The move completes once the change is seen.

Cancelling

Until your nameservers have moved, you can cancel and the site goes back where it was. After that, move it again instead.

Footprint-Free sites

Moving a Footprint-Free site onto a shared account asks you to confirm the footprint warning first. If a CDN ever suspends a site, you do not need to do this yourself: we move it automatically (see If your site's CDN is suspended).