aioflare

Bulk Move Zone to Another Cloudflare Account

Bulk Move Zone lets you copy multiple domains from one Cloudflare account connected to aioflare into another. You choose what to copy (DNS records, page rules, security and performance settings), then aioflare creates or reuses zones in the target account and applies the selected configuration.

What is Bulk Move Zone?

Understand how zone copying between Cloudflare accounts works in aioflare

Bulk Move Zone is not an automatic registrar transfer. aioflare creates a matching zone in the target Cloudflare account (or reuses an existing one) and copies the data you select from the source zone. The original zone stays in the source account until you remove it yourself.

Copy, not delete

After a successful move, update name servers at your domain registrar to the new account's name servers when you are ready to switch traffic. Until then, the source zone can keep serving the domain.

Before you start

Requirements for a successful bulk move

  • At least two Cloudflare accounts added to aioflare (source and target).
  • Zones you want to move must exist in a source account you can access in aioflare.
  • The target account must be different from the source account for each zone.
  • Your plan defines how many zones you can move per bulk request; large jobs use the queue.

What can be copied

Optional copy targets you select in the move dialog

You enable each category independently. The zone shell is always created or reused in the target account even if all copy options are unchecked.

DNS records

Non-NS records are copied to the target zone. Duplicate records already present in the target are skipped.

Redirect rules

Active redirect rules from the source are recreated in the target, subject to the target zone's plan limits.

Security & performance settings

Editable zone settings from aioflare's Security and Performance tabs are applied to the target zone.

Zone settings include (when enabled)

  • SSL/TLS mode (including Automatic SSL/TLS), Always Use HTTPS, minimum TLS version, TLS 1.3
  • Security level / I'm Under Attack mode, Bot Fight Mode, WAF, browser integrity check, email obfuscation, hotlink protection, challenge TTL
  • Cache level, browser cache TTL, Always Online
  • HTTP/3, 0-RTT, WebSockets, Pseudo IPv4
  • Early Hints, Rocket Loader, Polish, image resizing, minify (CSS/HTML/JS)

What is not copied

Items that are read-only, deprecated, or not exposed via Cloudflare's public API

  • Brotli compression — always on in Cloudflare and not configurable via API
  • Removed or deprecated settings (for example Server-Side Excludes, Crawler Hints, legacy privacy pass)
  • HTTP/2 — managed by Cloudflare and not copied as a user setting

How to bulk move zones

Step-by-step workflow in the aioflare dashboard

  1. Open the Zones page

    Go to Zones and locate the domains you want to move.

  2. Select zones

    Click Select, then choose one or more zones. Use bulk actions from the floating toolbar.

  3. Open Move Zones

    Choose Bulk Move (or Move to Another Account) from the bulk actions menu.

  4. Pick target account and copy options

    Select the destination Cloudflare account. Enable DNS records, page rules, and/or zone settings as needed. Choose Skip or Overwrite if the zone name already exists in the target account.

  5. Confirm the move

    For more than three zones, aioflare queues the job. Choose client-side (browser) or server-side processing when prompted.

  6. Track progress

    Open the Queue page to monitor status. Server-side jobs continue even if you close the browser.

  7. Review results

    When the job completes, open the bulk move results view for per-zone status, name servers, DNS and rule counts, and optional JSON export.

  8. Update name servers

    At your registrar, point the domain to the name servers shown for the target account when you are ready to go live on the new account.

If the zone already exists in the target account

Conflict handling options

Skip

Leave the existing target zone unchanged and mark this domain as skipped in the results.

Overwrite

Use the existing target zone and copy the selected DNS, page rules, and settings into it.

Queue and batch limits

When bulk move uses the background queue

Moves of more than three zones are processed through aioflare's queue with rate limiting to stay within Cloudflare API limits. Your plan caps how many zones can be included in a single bulk move request.

  1. Submit the move from the dialog; large jobs open the processor choice modal.
  2. Server-side (recommended on supported plans): processing runs on aioflare infrastructure.
  3. Client-side: keep the browser tab open until the queue finishes.
  4. Completed jobs store encrypted results for the results modal and JSON export.

Client vs server processing

How to choose a processor for queued bulk moves

Server-side (recommended)

Runs on aioflare's queue worker. Ideal for many zones or full copy (DNS + rules + settings). Requires a paid plan with server queue and stored API credentials on the target account.

Client-side (browser)

Runs in your browser via the queue page. Suitable for smaller batches. Keep the tab active until completion.

After the move

What to do when copying finishes

A successful move means the target account has a zone with the copied configuration. Traffic does not switch automatically.

  • Copy name servers from the results modal for each domain.
  • Update your registrar when you want the domain to use the target Cloudflare account.
  • Optionally delete the zone from the source account after you verify the target zone.

Source zones are not removed

aioflare never deletes source zones as part of bulk move. Remove them manually only when you no longer need them.

Viewing results

Understanding the bulk move results modal

The results view lists each zone with status (moved, skipped, or failed), DNS and redirect rule counts, expandable name servers with copy buttons, and a JSON download you can use to inspect full result details when available from the queue.

Frequently asked questions

Common questions about bulk move zone

Does bulk move delete zones from the original account?
No. Zones remain in the source account until you delete them. Bulk move only copies configuration into the target account.
Do I have to change name servers immediately?
No. Change them at your registrar only when you want the domain to use the target Cloudflare account. Until then, the source zone can continue to serve traffic.
Why did my move go to the queue?
More than three zones in one request are processed asynchronously to avoid timeouts and respect Cloudflare API rate limits.
When should I use server-side processing?
For large batches or when you need to close the browser. Server-side requires a plan that supports server queue and API credentials stored for the target account.

See also: Bulk Zone Operations