Migrate Umbraco to Next.js Headless CMS

Why Leave Umbraco's Monolithic Architecture

Umbraco served the .NET ecosystem well for years. But if you're running a self-hosted instance or paying for Umbraco Heartcore, you're probably dealing with problems that compound over time:

• Server-side .NET rendering bottlenecks that tank your Lighthouse scores on mobile
• Windows Server or Azure App Service hosting costs that balloon as traffic scales
• Coupled frontend templates (Razor views) that force every change through .NET developers
• Slow build and deploy cycles tied to IIS restarts and .NET compilation
• Core Web Vitals failures — LCP above 2.5s, poor TTFB from dynamic page generation

Umbraco isn't broken. It's just architecturally stuck in a paradigm that modern web performance has moved past. Your content editors deserve a great backoffice experience. Your users deserve sub-second page loads. You can have both.

What a Next.js Headless Stack Actually Gets You

Moving to Next.js with a headless CMS backend isn't a lateral move — it's a genuine architectural leap. Here's what actually changes:

Edge-First Delivery

Next.js with Incremental Static Regeneration (ISR) pre-renders pages at build time and serves them from edge nodes globally. Your TTFB drops from 1.2-2.5 seconds to under 300 milliseconds. That's not a benchmark fantasy — that's what we measure on every migration we ship.

Decoupled Frontend Freedom

Your frontend team writes React and TypeScript. No more Razor syntax. No more C# models leaking into presentation logic. Component libraries like ShadCN UI, Radix, or your own design system slot in cleanly. Storybook for component development. Tailwind for styling. Modern tooling, modern velocity.

Hosting Cost Collapse

A self-hosted Umbraco instance typically runs $200-500/month on Azure or a dedicated Windows server. The same site on Vercel or Cloudflare Pages costs $20-100/month — sometimes less. Static assets on a CDN don't need application servers. You pay for bandwidth, not compute.

Core Web Vitals That Actually Pass

Google's page experience signals aren't optional anymore. ISR and SSG eliminate render-blocking server processing. The Next.js Image component handles lazy loading, format negotiation, and responsive sizing automatically. We routinely hit 95-100 on Lighthouse mobile after migration.

Heartcore vs. Self-Hosted: Different Starting Points, Same Destination

We handle both migration paths.

From Umbraco Heartcore

Heartcore already exposes a Content Delivery API, so the backend lift is minimal. We map your existing content types, configure API access, and build the Next.js frontend against Heartcore's REST endpoints. Your editors keep the Umbraco backoffice they already know. The frontend just gets dramatically faster.

The main win here is cost: you can stay on Heartcore as your content backend if the pricing works, or migrate content to a more cost-effective headless CMS like Sanity, Contentful, or Strapi.

From Self-Hosted Umbraco

Self-hosted migrations are more involved. We enable the Delivery API on your Umbraco instance (available since Umbraco 12+), configure webhook-driven ISR for real-time content updates, and build the Next.js frontend from scratch.

The webhook flow works like this:

1. Editor publishes content in Umbraco backoffice
2. Umbraco fires a POST to a Next.js webhook endpoint with the content path and HMAC signature
3. Next.js verifies the signature and calls revalidatePath() to purge the ISR cache
4. The next visitor gets a freshly generated page — everyone else gets the cached version

This gives editors near-instant publish-to-live cycles without rebuilding the entire site.

Full .NET Escape Option

If you want to decommission the Umbraco backend entirely, we migrate your content to a modern headless CMS — Sanity for structured content flexibility, Contentful for enterprise workflows, or Payload CMS for self-hosted open source. Your .NET servers go offline permanently.

Our Migration Process

We've refined this into a repeatable, low-risk process:

Phase 1: Audit and Architecture (Week 1)

We run Lighthouse audits on your current Umbraco site, map every content type and relationship, catalog URL structures for SEO preservation, and identify integration points (forms, search, e-commerce, authentication).

Deliverable: Migration architecture document with content model mapping, tech stack recommendation, and risk assessment.

Phase 2: Proof of Concept (Weeks 2-3)

We build a working POC — typically your homepage and one content-heavy template — connected to either your existing Umbraco API or the target headless CMS. This validates the architecture, proves the performance gains, and gives stakeholders something real to evaluate.

Phase 3: Full Build (Weeks 4-8)

Component library buildout in Next.js. All page templates. Content migration scripting (automated, not manual). Form integrations. Search implementation. Preview mode for editors. Analytics reconnection.

Phase 4: SEO Preservation and Launch (Weeks 9-10)

This is where migrations succeed or fail. We implement:

• 1:1 URL mapping with 301 redirects for any changed paths
• XML sitemap generation via Next.js
• Structured data (JSON-LD) for all page types
• Canonical tags and meta tag parity
• Google Search Console monitoring pre and post-launch
• Crawl testing with Screaming Frog to catch broken links before they hit production

We don't launch until crawl parity is confirmed. Zero indexation loss is the standard, not the goal.

SEO Preservation Strategy

SEO is the highest-risk part of any CMS migration. Here's how we eliminate that risk:

Every URL on your current Umbraco site gets cataloged. We build a redirect map that handles path changes, trailing slashes, case sensitivity differences, and query parameter variations. Internal links get updated in content during migration.

We set up rank tracking on your top 50 pages before launch. Post-launch, we monitor daily for 30 days. If anything drops, we diagnose and fix within 24 hours.

The performance improvements from Next.js typically produce a positive SEO impact within 4-6 weeks — better Core Web Vitals scores lead to better rankings, not just maintained ones.

Timeline and Investment

Typical Umbraco-to-Next.js migrations run 8-12 weeks depending on site complexity:

• Small sites (under 50 pages, simple content model): 6-8 weeks, $15,000-$25,000
• Mid-size sites (50-500 pages, multiple content types, integrations): 8-12 weeks, $25,000-$50,000
• Enterprise sites (500+ pages, personalization, multi-language, complex workflows): 12-16 weeks, $50,000-$100,000+

These include content migration, frontend build, SEO preservation, and 30 days of post-launch support. Hosting cost savings typically offset 30-50% of the migration investment within the first year.

Who Handles This

This migration service is led by Aryan Shah at Social Animal. We've built headless architectures for teams escaping WordPress, Drupal, Sitecore, and Umbraco. The .NET-to-modern-stack migration is one we know cold.

If you're tired of paying for Windows servers, waiting on .NET builds, and watching your Core Web Vitals fail — let's talk specifics about your site.