Website migration at scale: hundreds of sites
Website migration lessons from moving a large multi-site platform to new technology with a small team.

Moving one website is a project. Moving hundreds is a production line. Success depends on standardising the structure, keeping each site’s identity, documenting everything and checking every site before it goes live.
These lessons come from multi-site platform work.
Lesson 1: separate blueprints from templates
Use two layers. Blueprints are the fixed structure every site shares: page types, navigation patterns, URL rules, content models, tracking and SEO settings. They should be standardised and rarely change. Templates sit on top and control the look and feel, and they can vary much more.
Keeping these separate lets you migrate at scale without every site looking the same.
- Blueprint
- Template
Our view, scored out of 5.
Lesson 2: find common ground in look and feel
Most sites fall into a handful of styles: modern or traditional, light or dark, high-end or fast-moving. Build a small set of templates around those, so each site can pick the closest match. Finding that common ground early saves a huge amount of design and build time.
- Modern or traditional
- Light or dark theme
- High-end and spacious, or fast-moving and dense
- Image-led or text-led
Lesson 3: keep each site’s uniqueness
Templates and blueprints save time, but each website still needs its own identity. Understand why each site looks the way it does and what its audience expects. Carry over each site’s brand style — logo, colours, typography, imagery and tone — from the original, so it feels like an upgrade, not a replacement.
- Audit each site’s brand elements before migration
- Record logos, colours, fonts and imagery style per site
- Map each site to the template that fits its brand best
- Apply its brand tokens on top of the template
- Have the site owner confirm it still feels like theirs
Lesson 4: group sites into waves
Wave 1 (pilot)
- Simple sites: 8
- Medium sites: 2
- Complex sites: 0
- Total: 10
Wave 2
- Simple sites: 80
- Medium sites: 20
- Complex sites: 0
- Total: 100
Wave 3
- Simple sites: 60
- Medium sites: 50
- Complex sites: 10
- Total: 120
Wave 4
- Simple sites: 12
- Medium sites: 38
- Complex sites: 20
- Total: 70
Illustrative. Pilot with a few sites, then scale up simple sites before tackling complex ones.
Lesson 5: document everything
At scale, anything undocumented becomes a problem later. Document the blueprint, every template, each site’s brand settings and every configuration decision. Pay particular attention to tracking and SEO, because mistakes there are invisible until traffic drops.
- GA4 set up on every site, with all key events and conversions configured and tested
- Blog posts and content kept on the same URL strings wherever possible
- Any URL that must change mapped and redirected
- SEO reviewed ahead of time: titles, descriptions, headings, canonicals and structured data
- Every page checked for correct configuration before launch
- A record of each site’s settings, owners and integrations
Lesson 6: automate the repeatable
- Scripted content export and import
- Automated URL mapping and redirect generation
- Bulk image optimisation
- Automated checks for broken links, missing pages and accessibility
- Templates for launch emails and owner sign-off
Lesson 7: make site owners part of the process
- A clear timeline for each wave
- Simple content freeze rules
- A short review window with a checklist
- Training before go-live
- One place to raise issues
Lesson 8: use a go-live checklist for every site
Before any site goes live, run the same checklist. It turns hundreds of launches into a repeatable routine and catches problems while they’re easy to fix.
Brand and design
Content and URLs
SEO
Tracking
Launch
Spam check by Cloudflare
Lesson 9: estimate effort honestly
- 160
- 110
- 30
- 4
- 14
- 60
- 120
- Total hours
- 3,980
- Weeks needed
- 33
Add contingency for surprises in content and integrations.
How this looks in your industry
Illustrative examples
Closest to you
Education
A school network with 200+ sites
The problem: Each site had custom layouts.
What changed: Standardised to six templates and migrated in waves.
Result: The program finished on schedule.
Closest to you
Franchise
A franchise network
The problem: Feared every location site would look the same.
What changed: Used one blueprint with three templates and each location’s brand details carried over.
Result: Faster migration while each site kept its identity.
Closest to you
Government
A council with many microsites
The problem: A previous migration lost tracking and rankings.
What changed: Kept URLs, configured GA4 events and ran a go-live checklist on every site.
Result: Traffic and data carried over cleanly.
Common mistakes
- Mixing structure and styling in one template layer
- Letting every site become identical
- Too many custom layouts
- Changing URLs without redirects
- GA4 events not configured before launch
- No go-live checklist
Key takeaways
- Fix the structure in blueprints; vary the look in templates
- Find common ground in a few styles
- Keep each site’s own brand
- Document everything, especially GA4 and SEO
- Run a go-live checklist for every site
Frequently asked questions
What’s the difference between a blueprint and a template?
A blueprint is the fixed structure: page types, URLs, content models, tracking and SEO. A template is the look and feel applied on top.
How many templates do we need?
Usually a handful — enough to cover the main styles across your sites, such as modern and traditional, light and dark.
Should we clean up content before migrating?
Yes. Archive or remove pages with little traffic and no purpose before moving them.
How do we protect SEO across many sites?
Keep URLs the same where possible, redirect the rest, review SEO before launch and monitor each site in Search Console.
Your next step
Plan a migration that finishes on time
We plan and run large multi-site migrations with templates, automation and owner support.
Explore website migration