WordPress Fleet Migration

Migrating a revenue-carrying publisher fleet is an exercise in not being noticed: readers and ad networks must see no interruption while every site changes servers, and the security posture that failed before has to be rebuilt along the way.

• •50+ sites with different plugin stacks, PHP requirements, and traffic profiles to move
• •Ad-funded traffic means downtime and slow pages translate directly into lost revenue
• •A history of security incidents demanded a hardened baseline, not just a faster server
• •No coherent backup or restore story existed across the portfolio
• •SSL and DNS management across dozens of domains had to become systematic

We sequenced the fleet by risk and traffic, rebuilt the platform baseline once as configuration, and applied it uniformly, so every site landed on the same hardened, cached, and monitored foundation.

• Audited every site for plugin conflicts and PHP compatibility before sequencing the batches
• Provisioned LiteSpeed servers tuned for WordPress with Redis object caching and OPcache
• Layered CloudFlare CDN and WAF with WordPress-specific rulesets in front of every property
• Automated daily encrypted backups with 30-day retention and one-click restore
• Cut over DNS in batches with per-site verification and immediate rollback paths