15 WordPress Sites > Zero-Downtime Migration

Migrating 15 Portals at Scale Without a Single Second of Downtime

When your organic traffic is your revenue, declining search rankings aren't a technical inconvenience — they're a business crisis. Iberion needed to migrate 15 monolithic WordPress sites to a modern architecture that passed Google's Core Web Vitals thresholds, without disrupting service to 150M+ monthly visitors. We built a reusable headless architecture that could be deployed once and replicated across every portal — turning a 15x problem into a one-time engineering investment.

Pain Points

Google's Core Web Vitals update turned Iberion's legacy WordPress infrastructure from a maintenance headache into an active revenue threat. Failing LCP and CLS scores meant declining search rankings — and for a media business built on organic traffic, that meant losing the visitors that fund the entire operation. Fifteen separate monolithic WordPress installations compounded the problem: each portal had its own codebase, its own performance profile, and its own editorial workflow. Portal-by-portal optimization was impractical at this scale.

Challenge

Iberion couldn't afford a slow, sequential rebuild — search rankings were already declining across multiple properties. But migrating 15 high-traffic portals without any downtime for 150M+ monthly visitors demanded an approach that balanced speed with precision. The architecture had to pass Google's Core Web Vitals thresholds, preserve URL structures and SEO equity during cutover, maintain ad tech integrations critical to revenue, and sustain editorial workflows without interruption.

Solution

We migrated all 15 monolithic WordPress sites to a centralized headless architecture, using DNS-level cutover with parallel environments to maintain zero downtime throughout:

- Frontend: Next.js with ISR (Incremental Static Regeneration) for performance-optimized rendering. Server-side rendering for dynamic content, static generation for high-traffic pages, and edge caching via Vercel for sub-second global delivery.
- CMS: Enterprise Contentful with structured content models migrated from WordPress via automated migration scripts. Editorial teams transitioned to the new CMS without content freezes — both systems ran in parallel during cutover.
- Hosting: Vercel with edge network distribution. At 150M+ monthly visits, CDN configuration, cache invalidation strategy, and edge function placement were critical to sustaining performance at scale.
- SEO Preservation: Full URL structure mapping, 301 redirect chains, canonical URL handling, and structured data migration to protect existing search equity during the transition.
- Architecture: A shared Next.js codebase with portal-specific configuration — the first portal took 2-3 months to build and validate, subsequent portals deployed in 2-4 weeks each using the established architecture and content model.

Engagement model: Dedicated engineering team with Vercel Partner support. First portal delivered in 2-3 months; remaining portals rolled out on an accelerated timeline using the reusable architecture. Zero editorial downtime throughout.

Outcome

Every portal now passes Google's Core Web Vitals thresholds with a 30% average LCP improvement. Search rankings stabilized and organic traffic recovered across all 15 properties. Editorial teams publish faster through Contentful's structured workflows. The shared architecture means performance improvements and bug fixes propagate across all portals simultaneously. And 18+ months post-engagement, continuous monitoring has recorded zero performance regressions across any of the 15 portals.