Bulk WordPress Migration For Agencies

Moving 20, 100, or 1,000 WordPress sites is an operations problem before it is a transfer problem. Agencies and hosting teams need a consistent inventory, scope rules, operator ownership, reusable destination profiles, per-job secrets, migration waves, exception queues, and proof that every site was tested.

Build The Fleet Inventory

Track the customer, source host, destination, domain mode, WordPress version, PHP version, files, database, multisite status, ecommerce or membership risk, DNS provider, mail provider, WAF, desired cutover window, and assigned operator. Detect facts from each install folder so self-reported software and size do not become the source of truth.

Group Sites Into Waves

• Wave 1: small brochure sites with standard WordPress, normal plugins, and straightforward DNS.
• Wave 2: larger media libraries, page builders, multilingual sites, and moderate databases.
• Wave 3: WooCommerce, memberships, multisite, high-write databases, strict WAFs, or limited source access.
• Exception queue: custom code, infected sites, broken databases, unsupported PHP, export-only hosts, and unclear ownership.

Reuse Endpoints Without Reusing Passwords

Save destination labels, hostnames, ports, usernames, paths, and preferred methods for the agency. Enter passwords, private keys, database credentials, and tokens for each migration. This keeps repeat work fast without turning the account into a permanent credential vault.

Standardize The Run

For each site, verify destination readiness, run source analysis, review the credit or agency-capacity estimate, start the direct transfer, inspect warnings, test through a preview route, run serialized-safe URL replacement, complete a final delta when needed, and then cut over DNS. Do not let a copied file count substitute for browser and log checks.

Use Seats For Constant Migration Work

Credit packs make sense for occasional customer moves. Operator seats and pooled monthly capacity make more sense when multiple agency employees continuously intake, run, troubleshoot, and report on migrations. Roles should separate administrators, operators, support, and billing while preserving an audit trail for credit grants, overrides, and customer authorization.

Report Exceptions, Not Just Success

A fleet dashboard should show sites awaiting access, ready to run, transferring, waiting for customer approval, blocked by WAF or runtime, ready for DNS, completed, and rolled back. Each handoff should include what moved, what changed, warnings, tests, DNS time, and credential-rotation reminders.

Start With A Repeatable Playbook

Use the agency migration workflow for intake through handoff, the WordPress guide for each application move, and the website migration checklist as the operator acceptance standard.