WPX Agency Onboarding Guide 2026: 200 Sites, One Migration Form Each

200 sites can mean 200 migration workflows

WPX says each website migration requires a separate migration form. If an agency intends to move dozens or hundreds of client sites, the administrative queue matters as much as the advertised site limit. Create a migration inventory before opening forms: source host, DNS, domain registrar, mailbox status, PHP version, special plugins, scheduled jobs, current traffic and launch priority. Move in batches rather than treating 200 sites as one change window.

The resource envelope is shared, not per site

Agency currently publishes **100GB RAM, 6 CPU cores and 300 PHP workers** for up to 200 sites. Those are account-level resources, not per-site guarantees. Simple equal-share arithmetic would average **0.5GB RAM and 1.5 PHP workers per site** at 200-site utilization. That is only a screening model: 190 cached brochure sites plus 10 dynamic stores can behave very differently from 200 similar blogs.

Backup retention helps—but restore operations still need process

WPX creates automatic daily backups on a separate server and retains them for **28 days**. At agency scale, recovery should be catalogued per site: which client needs a 1-hour RTO, which site can wait, which store requires off-platform exports, and who is authorized to request or approve restores. A provider backup system is valuable, but your agency still needs ownership, testing and communication procedures around it.

Managed hosting removes work, not all responsibility

WPX managed hosting includes server security, malware scanning/removal, backups, eligible migrations, support and one-time speed optimization. The customer still owns content, credentials, third-party code, SEO, advertising and business continuity choices. That boundary matters more at 200 sites because one weak plugin policy or credential practice can multiply across many clients.

One dashboard is the real operational value

WPX positions Agency as one dashboard for up to 200 client sites, with consolidated visibility, billing, email protection, temp URLs, caching and support. The strongest agency use case is standardization: common onboarding checklist, plugin policy, backup expectation, monitoring and client communication. The plan's economics become attractive when that standardization actually replaces scattered hosting/admin work.

Five-year pricing rewards utilization—but increases commitment

The current Agency cart shows **$599.99/month** or a **$399.99/month equivalent** when **$23,999.60** is prepaid for five years. At 200 sites, that is roughly $2/site/month before agency labor; at 100 sites it is about $4, and at 50 sites about $8. Those are utilization examples, not promises that every site fits the shared resource envelope. Test a representative client mix before committing five years.

What current reviews reinforce

Nicada Digital's 2026 agency-hosting guide emphasizes workflow and client-site management as key buying criteria, while Gaurav Tiwari and ProCritique both describe WPX's managed-service depth as the reason to pay above commodity shared hosting. For exact Agency limits and migration mechanics, WPX's current cart and knowledge base remain controlling.

**Bottom line:** WPX Agency can be cost-efficient at high utilization, but the real challenge is operational: one migration form per site, shared finite resources, standardized recovery and clear client ownership. Buy it when the dashboard and managed layer reduce agency labor—not simply because "200 sites" looks large.