Your Umbraco Site Costs £18K/Year to Host What Vercel Runs for £240

Why Umbraco Teams Are Moving to Next.js

Umbraco has earned its reputation. It's open-source, flexible, and deeply embedded in the .NET ecosystem. Over 16,900 companies run on it, with the UK accounting for roughly 31% of that install base. The recent v17 LTS release proves the project is alive and well.

But here's the uncomfortable part: most Umbraco sites are still server-rendered Razor views sitting behind IIS or Azure App Service. The frontend's tightly coupled to the .NET backend. Page speed suffers. Hiring gets harder every year as the talent pool shifts toward React and TypeScript. And your editorial team is stuck with a publishing workflow that was designed for a monolithic architecture -- because it is one.

Next.js solves these problems without making you throw away everything you've built. Since v12, Umbraco's Content Delivery API has enabled genuine headless mode. You can keep the Umbraco backend and bolt a Next.js frontend onto it. Or make a clean break and migrate content to a purpose-built headless CMS like Sanity or Payload.

We're a UK-based agency. We know the Umbraco ecosystem intimately because it's everywhere here. We also know when it's time to move on.

The Real Pain Points With Umbraco

Performance Bottlenecks

Umbraco's default rendering pipeline produces server-rendered HTML on every request unless you layer aggressive caching on top. Even with output caching, TTFB on Azure App Service typically lands between 800ms and 2.5 seconds depending on hosting tier and database performance. Mobile Lighthouse scores for typical Umbraco sites sit between 45 and 65 -- well below Google's Core Web Vitals thresholds.

Frontend Developer Experience

Razor views work, but they're limiting. No component-based architecture. No hot module replacement. No design system tooling like Storybook. Junior and mid-level developers increasingly come from React backgrounds and find the Razor/C# templating layer genuinely frustrating. Recruitment becomes the bottleneck.

Hosting Costs and Complexity

Running Umbraco properly means managing Windows servers, SQL Server databases, and often Azure Blob Storage for media. Monthly hosting costs for a production-grade setup typically run £150 to £500+ depending on traffic. Compare that to a static or ISR-based Next.js site deployed to Vercel or Cloudflare Pages -- it's not close.

Scaling Limitations

Umbraco doesn't scale horizontally without significant effort. Load balancing requires careful configuration of distributed cache and database synchronisation. A CDN-first approach with Next.js eliminates most of that complexity entirely.

Content Modelling Rigidity

Umbraco's Document Types are powerful, but they're tightly coupled to the rendering layer. Reusing content across channels -- mobile apps, kiosks, third-party platforms -- requires custom API work that the Content Delivery API only partially addresses.

Two Migration Paths: Choose What Fits

Option A: Umbraco Backend + Next.js Frontend

This is the low-risk path. Your content team keeps using Umbraco's familiar backoffice. Document Types, content nodes, media library -- all of it stays exactly where it is. We build a Next.js frontend that consumes the Content Delivery API introduced in v12+.

This approach works well when:

• Your editorial team is deeply invested in Umbraco's workflow
• You have complex Document Types with nested content and block editors
• You want to de-risk the migration by changing one layer at a time
• Your .NET team can continue maintaining the backend

We map each Document Type to a corresponding React component. Razor views become typed Next.js page templates. Grid layouts and Block List editors get converted to composable React components with TypeScript interfaces generated from your Umbraco schema.

Option B: Full Migration to Sanity or Payload CMS

This is the clean-break path. We extract all content from Umbraco, transform it, and load it into a modern headless CMS. Sanity gives you real-time collaborative editing and a flexible schema system. Payload CMS is open-source, self-hosted, and built on Node.js -- a natural companion to Next.js.

This approach makes sense when:

• Your Umbraco instance is outdated (pre-v10) and upgrading is expensive
• You want to eliminate .NET hosting entirely
• You need structured content that serves multiple channels
• Your team wants a unified JavaScript/TypeScript stack

We write custom migration scripts that map Document Types to CMS content models, preserve relationships between content nodes, and handle media asset migration with proper URL redirection.

Our Migration Process

1. Discovery and Audit (Week 1-2)

We audit your Umbraco instance: version, Document Types, templates, custom controllers, media volume, third-party integrations, existing URL structure. We benchmark current performance and flag SEO-critical pages.

2. Architecture Decision (Week 2)

Based on the audit, we recommend Option A or Option B with a detailed rationale. We define the tech stack, hosting strategy, and content model mapping.

3. Content Model Mapping (Week 2-3)

Every Document Type gets mapped to either a React component (Option A) or a CMS content model (Option B). We document this in a shared schema reference that both developers and content editors can review.

4. Frontend Build (Week 3-6)

Razor views become React components. We build the design system in a component library, create page templates, and wire up data fetching via either the Umbraco Content Delivery API or your new headless CMS.

5. Content Migration (Week 5-7, Option B only)

Custom ETL scripts extract content from Umbraco's database, transform it to match the new schema, and load it into the target CMS. We validate every content node, relationship, and media asset.

6. SEO Preservation and Launch (Week 7-8)

This is where migrations succeed or fail. We implement a complete redirect map covering every URL. XML sitemaps are regenerated. Structured data is ported. We verify canonical tags, meta descriptions, and Open Graph data page by page. Screaming Frog crawls run pre- and post-launch to catch any gaps.

For a deeper comparison of Umbraco and Next.js approaches, we've published a detailed technical breakdown.

SEO Preservation Strategy

SEO is a first-class concern throughout the migration -- not something we bolt on at the end:

• Full 301 redirect mapping from every Umbraco URL to its Next.js equivalent
• Preservation of internal link structure -- no orphaned pages
• Metadata migration -- page titles, descriptions, OG images carried over programmatically
• Structured data ported and validated against Google's Rich Results Test
• Performance gains that directly improve Core Web Vitals rankings
• Post-launch monitoring with Search Console and Ahrefs for 90 days

Timeline and Investment

A typical Umbraco to Next.js migration for a mid-sized site (50-200 pages) takes 6-10 weeks depending on complexity and which migration path you take.

• Option A (Headless Umbraco + Next.js): £15,000 – £35,000
• Option B (Full migration to Sanity/Payload): £20,000 – £50,000

Larger sites -- complex integrations, multi-language setups, e-commerce -- will land at the higher end. We scope every project with a fixed-price proposal after the discovery phase. No surprises mid-project.

Why Work With Social Animal

We're UK-based, so we understand the Umbraco market better than most. We've worked directly with .NET teams, migrated Razor codebases, and dealt with the specific quirks of Umbraco's content architecture first-hand. We also build production Next.js applications every day -- it's our core capability.

Your Umbraco site served you well. Let's make sure the next platform serves you better.