Now accepting Q2 projects — limited slots available. Get started →
Espanol Portugues العربية 한국어 Francais Deutsch English 中文 日本語 繁體中文 Nederlands
Enterprise Migration
Multisite NetworksMulti-Tenant ArchitectureZero-Downtime Cutover

WordPress Multisite Migration to Next.js

Your WordPress Network Shares One Attack Surface Across Every Site

$1-2.5K/mo
WP Multisite Hosting
Typical managed hosting for 20-50 site networks
$45/mo
After Migration
Vercel + Supabase for same 50 sites
4-8wk
Migration Timeline
Typical WordPress Multisite to Next.js duration
95+
Lighthouse Score
Performance + accessibility target on every build
What WordPress Multisite Migration Actually Requires — And Why Most Agencies Won't Touch It

Your WordPress Multisite network runs 30+ subsites off one database, one plugin stack, one shared wp_users table. A migration pulls each subsite out — extracting content from prefixed tables like wp_2_posts and wp_3_options, remapping user capabilities stored as serialized arrays, rewriting every hardcoded media URL from /sites/[site-id]/ directories, and rebuilding the whole thing as isolated Next.js routes with per-location Supabase queries. Your team gets separate content stores, independent authentication, and zero shared plugin vulnerabilities. The old network had one entry point for attackers. Your new stack has none.

Onde os projetos falham

One plugin vulnerability on one subsite exposes all 30+ sites simultaneously That's not a hypothetical — 96% of WordPress exploits target plugins, and your entire network shares one attack surface. All it takes is one unpatched plugin on one subsite.
Prefixed database tables (wp_2_posts, wp_3_options) turn what should be a straightforward extraction into a multi-day operation Serialized data makes it worse — it contains hardcoded domain references, so a naive find-and-replace doesn't just miss things, it actively corrupts widget configs and option values.
The shared wp_users table with per-site capabilities (wp_2_capabilities, wp_3_capabilities) is its own headache You can't cleanly separate user access without remapping every capability key per subsite. There's no clean path — just careful, tedious work.
Media files live in /wp-content/uploads/sites/[site-id]/ with hardcoded URLs baked into the content itself Move or restructure any subsite and you break every image and file reference in that subsite overnight.
Domain-mapped subsites each need individual DNS changes, SSL certificates, and redirect rules Miss one domain during migration and you've handed that subsite's indexed pages and organic traffic to a 404 page.
Then there's the plugin problem The plugin that runs fine on your main site breaks on subsite #7 — and you can't update them independently. Network-activated plugins force every subsite onto the same version, so each update is a network-wide gamble.

Conformidade

Prefixed Table Extraction

We remap every wp_N_ prefixed table to clean schema structures in Supabase. Serialized data gets parsed properly — domain references rewritten without touching the serialization format itself.

Multi-Tenant Row-Level Security

Each former subsite gets its own location_id in Supabase, with RLS policies enforcing content isolation. No shared database, no cross-site data leaks. They're genuinely separate now.

Per-Site User Role Mapping

We extract per-subsite capabilities from the shared wp_users table and remap them to Supabase Auth roles. Each user ends up with the right permissions per location — a single login that actually knows where they're allowed to be.

Media URL Rewriting

Every media file from /wp-content/uploads/sites/[id]/ moves to CDN-optimized storage, and all content references get rewritten to the new paths with next/image optimization baked in.

Per-Domain Redirect Mapping

Every URL across every subsite — including domain-mapped custom domains — gets a 301 redirect to its new path. No orphaned URLs, no rankings quietly disappearing in the background.

Network-Wide Performance Audit

We benchmark each subsite's Core Web Vitals, page count, and plugin dependencies before migration starts. After launch, we verify 95+ Lighthouse scores across all locations. You get before-and-after numbers, not just a promise.

O que construímos

One plugin exploit hits all 30+ subsites simultaneously because network activation forces identical versions everywhere

Automated REST API extraction pulls posts, taxonomies, ACF fields, and meta from each subsite without manual exports

Prefixed database tables scatter your content across wp_2_posts, wp_3_options, wp_7_postmeta with no clean export path

Dynamic /locations/[slug] routes share brand components while serving isolated content from Supabase per-location queries

Shared wp_users table stores per-site capabilities as serialized keys that break on naive migration attempts

Normalized schema replaces wp_N_ prefix chaos with location_id foreign keys and actual relational structure

Media files live in /sites/[site-id]/ with hardcoded URLs baked into post content and widget configs

Custom admin interface manages content and users per location without WordPress core or plugin conflict risk

Domain-mapped subsites each require separate DNS, SSL, and redirect coordination or you lose indexed traffic overnight

Pre-rendered pages serve static HTML from edge nodes with zero PHP execution or database queries on page load

Network-wide plugin updates gamble every subsite's stability because you can't update subsites independently

Per-domain GSC properties and sitemap monitoring track indexing stabilization across every former subsite domain

Nosso processo

01

Network Audit

Start by mapping every subsite: URLs, content volume, active plugins, custom post types, domain mapping configuration, and user role distribution. You need to know exactly what shared functionality exists versus what's site-specific, and you need to flag every piece of serialized data that contains domain references before anything moves.
Week 1-2
02

Architecture Design

Then design the Next.js route structure, Supabase schema with location_id and RLS policies, shared component library, and per-location content models. The redirect strategy for every domain gets defined here too — before a single line of migration code runs.
Week 2-3
03

Content Export & Media Migration

Extract content via the WP REST API per subsite. Download media from each /sites/[id]/ directory. Export users with per-site capability mapping. Validate serialized data integrity at every step.
Week 3-5
04

Build & Import

Build the Next.js multi-tenant application with Supabase Auth, RLS, and the admin dashboard. Then batch import all content, rewrite all media URLs, and map users to Supabase Auth with the correct per-location roles assigned.
Week 5-10
05

Redirect Mapping & Launch

Implement 301 redirects for every URL across all subsites and domain-mapped domains. DNS cutover per domain. GSC property updates. Monitor indexing across all former subsites for 30 days post-launch — long enough to catch anything that wants to surface late.
Week 10-12
Next.jsSupabaseVercelWP REST APIRow-Level SecuritySupabase Auth

Perguntas frequentes

Why is WordPress Multisite migration harder than single-site migration?

Aqui está o que torna uma migração de Multisite genuinamente complexa: cada subsite tem suas próprias tabelas de banco de dados prefixadas (`wp_2_posts`, `wp_3_options`), mas todos compartilham uma única tabela `wp_users` com capacidades por site integradas. A mídia fica em diretórios separados `/sites/[id]/`. Dados serializados mantêm referências específicas de domínio espalhadas por todo o lugar. Extrair um subsite significa remapear todas as tabelas prefixadas, reescrever dados serializados sem corrupção, migrar caminhos de mídia e lidar com DNS por domínio — depois fazer tudo novamente para cada subsite na rede.

Can you migrate subsites with custom domains?

Para subsites mapeados por domínio, tratamos a transição de DNS por domínio, provisionamento de certificado SSL e implementação de redirecionamento 301 do domínio antigo para sua nova estrutura de caminho. Cada domínio personalizado obtém sua própria propriedade do Google Search Console atualizada e monitoramento de indexação dedicado. Coordenamos o tempo de transição para minimizar o tempo de inatividade em todos os domínios — escalonando quando faz sentido, agrupando quando não faz.

What happens to shared users across subsites?

WordPress Multisite armazena todos os usuários em uma única tabela `wp_users` com capacidades por site como `wp_2_capabilities` e `wp_3_capabilities`. Extraímos as funções por site de cada usuário, mapeamos para Supabase Auth e atribuímos permissões específicas de localização usando Row-Level Security. O resultado final: um único login com o nível de acesso correto por localização, sem que ninguém veja conteúdo que não deveria.

Will we lose SEO rankings during migration?

Construímos mapas de redirecionamento 301 para cada URL em todos os subsites, incluindo domínios personalizados mapeados. As propriedades do Google Search Console são configuradas por domínio com sitemaps atualizados enviados no dia do lançamento. Monitoramos a indexação por 30 dias após o lançamento em todos os subsites antigos para detectar qualquer coisa que escape. Vale notar: o salto de desempenho de HTML estático normalmente ajuda os rankings em vez de prejudicá-los.

How long does a WordPress Multisite migration take?

A linha do tempo escala com o tamanho da rede. Uma rede de 5–10 subsites geralmente leva 8–10 semanas. Redes na faixa de 25–50 subsites funcionam 12–16 semanas. Redes empresariais com 50+ subsites, mapeamento de domínio complexo e funcionalidade personalizada podem levar 16–24 semanas. A fase de auditoria define uma linha do tempo precisa para sua rede específica — os números acima são pontos de partida, não garantias.

What's the security improvement after migrating from WordPress Multisite?

Redes WordPress Multisite são alvos de alto valor precisamente porque uma vulnerabilidade de plugin afeta todos os subsites simultaneamente. Após a migração, seus sites são HTML estático pré-renderizado servido por um CDN — sem runtime PHP, sem banco de dados exposto à web, nada para um exploit de plugin aproveitar. A superfície de ataque cai essencialmente a zero. Sem mais alertas do Wordfence às 2 da manhã. Sem mais patches de emergência. Sem mais prender a respiração toda vez que uma atualização de plugin é lançada.

Multisite Migration from $15,000
Priced by network size. 30-day post-launch monitoring included.
See all packages →
Multi-Site Website PlatformWordPress to Next.js MigrationWordPress Multisite to Next.jsNext.js vs WordPressWordPress Multisite Is Not Multi-Site

Get Your Multisite Network Assessment

Tell us about your network. We'll deliver a migration plan and quote within 48 hours.

Get Your Network Assessment
Get in touch

Let's build
something together.

Whether it's a migration, a new build, or an SEO challenge — the Social Animal team would love to hear from you.

Get in touch →