A large retail brand launches their new ecommerce platform.
The migration went perfectly. On time, on budget, no downtime. The CEO sent congratulations.
By June, organic revenue was down 34%. By September, they’d lost £4.2M in margin and couldn’t explain why to their board.
This is normal.
Website migrations fail commercially, not technically
Most organisations treat website and ecommerce migrations as technology projects. Success is defined by launch dates and technical specifications. Revenue is assumed to transfer automatically.
It doesn’t.
Revenue depends on search visibility, content integrity, journey continuity, and customer trust. These deteriorate silently during migrations, and damage takes 4-8 months to surface in revenue data. By then, recovery is slow and expensive.
What actually broke in that retail case:
340 high-value category pages lost their URL structure and ranking
Product schema markup was simplified, breaking rich results
Internal linking hierarchy was rebuilt from scratch, weakening page authority
18% of product content was truncated during migration to fit new templates
Mobile checkout flow added an extra step (0.4 seconds), increasing abandonment by 7%
Each issue was “minor” in isolation. Together, they cost £4.2M in six months.
Why migrations are managed incorrectly
When digital revenue performance is unclear, every decision feels risky. Investment slows. Transformation initiatives stall. Teams protect their budgets rather than collaborate on outcomes.
Most migrations follow this sequence:
Technology team selects platform and defines architecture
SEO team is brought in to create a redirect map
Content team is told to “fit content into new templates”
Launch happens on a technology-driven timeline
Revenue issues surface 90-120 days later when SEO rankings drop
The gap: No one owns commercial outcomes during the migration. Technology teams own delivery. Marketing teams own channels. Revenue performance falls between them.
What revenue-safe migrations look like
Organisations that protect revenue during migrations do five things differently:
Commercial ownership from day one One executive owns revenue performance throughout the migration. Not SEO performance. Not technical delivery. Revenue. They have authority to delay launch if commercial risk is unacceptable.
Content before technology Content, URL structure, and information architecture are designed first, then technology is configured to support them. Not the reverse.
. Journey mapping pre and post Every major customer journey is documented pre-migration, then tested post-migration before launch. Conversion rate, page load time, friction points, and exit rates are compared. Degradation is fixed before go-live.
SEO as a first-class concern SEO strategy (not just technical SEO) informs platform selection, URL structure, template design, content migration approach, and launch timing. Rankings are monitored weekly during migration, not after.
Staged launch with commercial validation Soft launch to 5-10% of traffic. Validate rankings, conversion, and revenue performance. Fix issues. Scale gradually. Don’t bet £50M in revenue on a single launch day.
The timeline that matters
Migration revenue risk follows a predictable pattern:
Weeks 1-4: Technical issues surface (broken pages, slow loads, checkout errors)
Weeks 4-12: SEO rankings begin shifting as Google re-crawls and re-evaluates
Weeks 12-20: Revenue impact becomes visible as ranking losses compound
Weeks 20-40: Recovery efforts begin, but rankings are slow to restore
Critical insight: By the time revenue impact is obvious (Week 12+), you’re already 3-4 months into recovery mode. The only way to protect revenue is to prevent ranking loss before it happens.
Migration Risk Self-Assessment
Answer honestly:
Does one person own revenue performance throughout your migration? (Not delivery, not SEO – revenue.)
Has your content and URL strategy been finalised before platform configuration?
Have you mapped and tested your top 10 customer journeys post-migration?
Is SEO strategy (not just technical SEO) informing your platform decisions?
Do you have authority to delay launch if commercial risk is unacceptable?
Three or more “no” answers? Your migration carries significant revenue risk. We can help with that, find out more about how our team successfully manages migrations for multi-lingual global websites.
Leave a Reply