Hire developers

Headless CMS Migration Services

Headless CMS migration agency for sites leaving WordPress, Drupal, AEM or Sitecore. We own the plan, the import and the 301 map, so rankings hold.

30 min · No commitment · Free

We are a headless CMS migration agency. We take sites that rank well and are hard to change off WordPress, Drupal, AEM or Sitecore, move the content into a headless CMS and rebuild the frontend. We own the whole project: the audit, the content model, the import scripts, the URL and 301 map, the cutover and the weeks after launch, so search traffic survives the switch. We also run frontend rewrites, framework upgrades and hosting moves when they come with the same risks.

This page covers how we run a migration as a project with a fixed scope. If you want to add a developer to your own team instead, see how to hire headless CMS developers. If you are replatforming a live site on any stack and want the full process with deliverables, read our website migration agency page. If you are still deciding whether to go headless at all, start with headless CMS development.

Which migrations do we run?

CMS replatforms

This is most of our work. A team has outgrown WordPress plugins, Drupal modules or an AEM licence, and editors wait on developers to publish. We move the content into Payload, Strapi, Sanity, Contentful or Storyblok and rebuild the frontend, usually in Next.js. The content model gets designed first. Import scripts come after it.

Frontend rewrites

Sometimes the CMS is fine and the frontend is the problem: a PHP theme that renders every page on request, or a single page app that search engines struggle to index. We rebuild the frontend with static generation or incremental regeneration and keep the CMS behind it. Headless WordPress is the common case: WordPress stays as the editing backend and only the frontend is rebuilt.

Framework upgrades

Vue 2 and Nuxt 2 have reached end of life, and Drupal 7 has too. Next.js apps on the Pages Router keep running but miss newer features. An upgrade looks like routine maintenance, yet it often touches routing, data fetching and rendering, so it needs the same URL checks as a replatform.

Hosting moves

A move to a new host with the same CMS and the same files is a job for the new host’s transfer service, and we say so. We take hosting moves when they come with a rebuild: a frontend moving to a CDN, a self-hosted CMS moving into containers, or a site leaving a managed platform plan.

Where are you moving from?

FromToOur page
WordPressPayload, Strapi, Sanity, Contentful or StoryblokWordPress to headless CMS migration
WordPress, keeping it as backendNext.js frontend over WPGraphQL or the REST APIHeadless WordPress development
Drupal 7 or an older DrupalA current Drupal version, or a headless CMSDrupal migration services
AEM on premises or 6.xAEM as a Cloud Service, or a headless CMSAdobe Experience Manager migration
Sitecore XPA headless CMS, or Sitecore XM CloudSitecore XM Cloud and headless work
Server-rendered or SPA frontendNext.js or Astro with static generationNext.js development
Any platform, new domain or URLsSame content, new structureSEO-safe website migration

Two comparisons help before you commit to a route: WordPress vs headless CMS for teams on WordPress, and AEM vs headless CMS for teams paying for Adobe.

How does a migration run?

Every project follows the same seven steps. Each ends with a sign-off from a named person on your side.

  1. Audit. We crawl the site, export traffic and rankings from analytics and Search Console, and list every template, content type, plugin and integration. This becomes the baseline we measure against.
  2. Content model mapping. Each old content type is mapped field by field to the new schema. Fields nobody uses are dropped here, not after launch.
  3. URL and 301 map. Every old URL gets a target: keep, redirect or retire. We keep URLs that earn traffic and give the rest one-hop 301s.
  4. Content migration scripts. We write import code against the old database or API, run it on a copy of production data, and produce a diff report for editors. Nobody copies content by hand.
  5. Parallel run. The old site stays live while the new one runs on staging with real content. Editors try their usual publishing tasks there, and we crawl it against the old site.
  6. Cutover. A short content freeze, a final import, then a DNS or routing switch in a planned window, with a written rollback plan.
  7. Post-launch watch. We track Search Console coverage, server logs, rankings and conversions against the baseline and fix gaps as they show up.

The headless CMS migration checklist lists the same gates if you plan to run the project in house.

How do we protect SEO during a migration?

Keeping a URL is safer than redirecting it. Where a URL must change, it gets a one-hop redirect that lives in version control and is tested against a crawl of the old site. Links inside body copy are rewritten to the new URLs, so the site does not send its own visitors through redirects.

Titles, descriptions, canonicals, structured data and hreflang come over template by template, and a crawl diff compares them with the old site before launch. Analytics tags, events and conversion goals go into the QA plan, because they break without anyone noticing.

We also measure Core Web Vitals before and after. A migration that makes pages slower has failed, whatever the CMS.

How to choose a headless CMS migration agency

Most migration agencies can build a new site. Fewer can move a ranking site without losing traffic. Ask these questions before you sign with anyone, us included.

  • Do they start with an audit and a baseline? A quote given before anyone has crawled the site and read Search Console is a guess. Ask what they will measure before and after launch.
  • Who writes the URL and 301 map, and when? It should exist before any template is built, live in version control and be tested against a crawl of the old site.
  • Is content moved by scripts or by hand? Import code that can run again after a fix, with a diff report for editors, is the only way to move thousands of pages and their media reliably.
  • Can they show the content model first? The new schema decides how editors work for years. Ask to see a field by field mapping from your old content types.
  • What is the rollback plan? A cutover without a written way back is a bet. Ask how long a rollback takes and who decides to use it.
  • How long do they stay after launch? Coverage drops and broken redirects show up in the weeks after cutover, not on launch day. Ask who watches Search Console and logs, and for how long.
  • Have they moved a site like yours? Ask for a migration with a similar platform, page count and number of languages, and for the numbers before and after.

What drives the risk and the cost?

We do not publish a price list, because two sites with the same page count can need very different work. Every project is scoped after a short audit and quoted as a fixed scope. These are the drivers we look at.

DriverWhy it matters
TemplatesEach template is a frontend component to build and a set of fields to map
Content modelCustom fields, page builder markup and shortcodes take the most import work
Changed URLsEvery changed URL needs a redirect, a test and a place in the watch list
LanguagesEach locale adds hreflang, routing and review cycles
IntegrationsForms, CRM, search, analytics and single sign-on each need rewiring and testing
Design changesA redesign done during the move adds scope and makes traffic changes hard to read
Sign-off speedThe content freeze date and how fast decisions come back set the end date

The biggest single risk is changing too much at once. We keep the URLs, the structure and the design where we can, move the platform, and leave improvements for after the new site has proved itself.

Proof from recent migrations

Drupal 7 to Next.js and Payload for a European enterprise healthtech organization. The site carried over 1,200 content nodes across four languages and had to leave Drupal 7 before its end of life. A TypeScript pipeline pulled every node through the Drupal REST API with checksum validation, and locale-aware routing kept the URL structure and hreflang tags. LCP went from 4.3s to 1.5s, editor publish time fell by about 50%, and there were 0 SEO ranking regressions at cutover. Read the Drupal replatform case.

WordPress to Payload for a US-based Series-B fintech. Roughly 40 custom plugins sat on the old site, and every copy change needed a developer review. All existing permalink structures were carried forward, and compliance approvals moved into the CMS. Time to publish fell by about 65%, LCP dropped from 4.2s to 1.4s, and organic traffic held through cutover. See the fintech replatform case.

Start with an audit

Send us the site, the platform you have in mind and your launch window. We crawl it, record a baseline and come back with a fixed scope, a dated plan and the risks we see. Book a migration assessment.

Services

Migration Services

Process

Hiring Developers Process

  1. 01

    Quick call

    We’ll schedule a call and understand your requirements and devs you need to hire.

  2. 02

    First candidates

    Get selected candidates who have been thoroughly evaluated in just a few days.

  3. 03

    Select

    Get a list of devs who match the best. You select the developers you like.

  4. 04

    Interview

    We contact selected devs in 48 hours. You interview & choose the best one.

Ready to ship?

Hire experienced Migration Specialist now for Your Needs!

Hire Migration Specialist to get the right specialists that will cater to the needs of your project fast.

30 min · Free · No commitment

Case studies

Real products
we shipped

From AI-powered platforms to fintech and consumer apps — work that's live, used, and producing results.

Our clients

Our Clients

Brands and teams we've helped ship, scale and modernise their digital products.

30+ Active clients
12 Industries
18 Countries
95% Repeat business

Migration services FAQ

Which CMS should we migrate to?

Pick the target after the audit, not before it. Payload suits a TypeScript team that wants the schema in its own repo. Strapi suits teams that want to model content in an admin panel. Sanity, Contentful and Storyblok are hosted options for teams that do not want to run a CMS server. The content model and the editors' daily work decide it.

Can a migration run without downtime?

Yes, in most cases. The old site keeps serving visitors while we build and import into the new one, and both run side by side until the new site passes its checks. Cutover is a DNS or routing switch in a planned window, with a written rollback plan. Editors pause publishing only for the short freeze before the final import.

Do you migrate into Drupal and AEM, or only away from them?

Both. Most of our work moves sites off WordPress, Drupal, AEM or Sitecore to a headless CMS. We also run Drupal version upgrades and moves to AEM as a Cloud Service when a team wants to stay on its platform. The Drupal and AEM migration pages cover those routes and the traps of each platform.

How is a migration priced?

We scope it after a short audit and quote a fixed scope with named deliverables. The price follows the number of templates, the content model, how many URLs change, the number of languages, the integrations and whether the design changes. Page count alone says little. Two sites with the same number of pages can need very different amounts of work.

Should we redesign the site during the migration?

Usually not. A redesign changes templates, URLs and copy at the same moment the platform changes, so when traffic dips nobody can tell which change caused it. We migrate first, keep the current design and structure, prove that rankings held, and then redesign on the new stack, where design changes are cheaper to ship.

Testimonials

What our clients say

Direct feedback from teams we've shipped with.

HTML CSS Hugo +5

Alpina tech did a good job during the discovery phase of our project

4.9 / 5
J
John C. Delivery Manager Headless CMS rebuild and frontend integration
Strapi Next.js React +9

I had the opportunity to work with Alpina Tech and the experience was very positive. He successfully achieved the goals set, demonstrating talent and commitment at every stage of the work. Moreover, he was always attentive to my instructions and consistently available, which greatly facilitated communication and the de...

5.0 / 5
M
Michael A. Delivery Manager Rebuild Strapi Cloud CMS, migrate content, and integrate with Next.js frontend (Render)
Next.js React JavaScript +5

Alpina Tech is not only a very talented dev, but he's a fantastic partner who has a rich business acumen and is quick to complete anything you throw at him. He knocked out work in a single day that I wasn't expecting for a week. Will definitely work with him again.

5.0 / 5
D
David R. Technical Project Manager Fix Netlify Functions & Assessment Tool for Next.js Website
React Native React Node.js +7

Alpina Tech always responded promptly and got a lot done in the limited environment we had. If things weren’t clear, he’d message and make sure he has the scope right. I highly recommend him for full stack development.

5.0 / 5
J
James K. Technical Project Manager React Native + Node.js Developer for Collectibles App with GPT-4 Integration
UX/UI Design Figma Landing Pages +4

I had the opportunity to work with Alpina Tech on the design of several landing pages and a UI kit, and I couldn’t be happier with the results. He managed to deliver high-quality designs in a very short time. The landing pages were beautifully crafted, and the UI kit was exactly what we needed to streamline the project...

5.0 / 5
R
Robert N. Delivery Manager UX/UI design for landing + UI kit
React.js React Next.js +12

Working with Alpina Tech on a headless CMS project built with Strapi, Node.js, and Next.js was a great experience. His deep understanding of modern frontend frameworks, API development, and server-side rendering (SSR) ensured a smooth and efficient development process. Alpina Tech showcased excellent React.js and Next....

5.0 / 5
W
William P. Project Manager React Developer Needed for Headless CMS with Strapi, Shadcn, and TypeScript
Swift SwiftUI UIKit +8

We worked with Alpina Tech, a top-tier Apple ecosystem developer specializing in Swift, SwiftUI, UIKit, and Combine. Delivered a seamless, high-performance app with Core Data, iCloud Sync, AVKit, MapKit, and Push Notifications. Optimized for iOS, watchOS, and macOS, ensuring smooth performance and App Store compliance....

5.0 / 5
D
Daniel O. Delivery Manager Develop iOS mobile app
JAMstack Hugo Next.js +10

I hired Alpina Tech to build a custom Hugo website. He was a pleasure to work with. He took the time to understand exactly what I wanted at the beginning of the project, and he then proposed a much better way of achieving that. He communicated regularly, provided clear and timely updates, offered ongoing support with m...

5.0 / 5
M
Matthew M. Project Manager Installing a custom theme for Hugo website
Next.js React Sanity +7

Alpina Tech was incredibly helpful and a pleasure to work with! He not only assisted with improving the SEO of my startup but also fixed a challenging Sanity bug with great patience and professionalism. His expertise and attention to detail were invaluable, and he did an excellent job overall. Highly recommended!

4.9 / 5
A
Anthony L. Technical Project Manager SEO Technical Expert for Next.js & Sanity.io Blog Integration
UI/UX Design Figma Web Design +3

I had the pleasure of working with Alpina Tech on the UI/UX design for my public website, and I am extremely impressed with his work. He significantly expanded and improved upon the original design I already had, seamlessly integrating enhancements that perfectly matched the existing style. His ability to develop great...

5.0 / 5
B
Brian D. Delivery Manager UI/UX Designer for AI Startup
Jekyll JAMstack HTML +5

Working with Alpina Tech was a great experience. He is knowledgeable and delivers high-quality work. The agency boasts a wide range of talent, making it a good choice for various projects. Communication was consistently excellent, and Alpina Tech ensured that every aspect of the project worked as expected. The work was...

5.0 / 5
K
Kevin F. Project Manager Web Developer Needed to Convert Figma Landing Page Design to Jekyll Static Site
UI/UX Design Figma Landing Pages +4

Alpina Tech and the team have completed the design quickly and it looks great. They are very responsive and were able to quickly make adjustments that I have requested.

5.0 / 5
L
Lauren E. Delivery Manager Landing page and public site pages design
iOS Swift SwiftUI +3

Alpina Tech is awesome, he fixed a complicated bug on VPN iOS app in two hours.

5.0 / 5
R
Rachel Y. Technical Project Manager ASAP iOS Developer Swift/SwiftUI (Fix VPN Mobile App)
Hugo JAMstack HTML +3

Alpina Tech did an excellent job guiding us through the process and helping us achieve our project goals.

5.0 / 5
B
Brandon A. Project Manager hugo site work
GitHub Pages HTML CSS +4

Alpina Tech helped us launch a research project website. Thank you for being available on short notice!

5.0 / 5
E
Eric B. Delivery Manager Fix github.io page issue
Technical SEO Web Strategy Management

I had the pleasure of working with Alpina Tech on leadership and technical projects. The team is highly motivated, strategically minded, and has exceptional technical SEO expertise. Their approach significantly boosted our digital presence. I highly recommend Alpina Tech for engineering and leadership-driven projects –...

5.0 / 5
S
Steven T. CEO AT CLAWBUSTER GAME PROVIDER Leadership & Technical SEO Optimization
HTML CSS JavaScript +4

Alpina Tech demonstrates all the right qualities of a strong development team – deep frontend expertise, great communication, and a proactive work attitude. A reliable partner for any technical project.

5.0 / 5
S
Scott M. Delivery Manager Frontend Development & Collaboration
Web Development Frontend HTML +3

Alpina Tech is a very professional and reliable team. Working together on web projects was extremely successful. The team showed strong technical knowledge and excellent organizational skills.

5.0 / 5
J
Jonathan N. Business Analyst - Playtech Web Development Collaboration

Keep exploring

More on Migration

Our team

The team you'll actually work with

We pair deep technical expertise with the kind of ownership you'd expect from your own in-house crew.

  • Same team from discovery to launch
  • Daily standups, Slack, and full transparency
  • Senior-only engineering, design, and QA
  • Long-term collaboration, not staffing
10+ years in the field
EU-based UTC+0 → UTC+3
Senior-only no juniors
Alpina Tech Team

Book a session

Let's just
{ Make it together! }

Learn how our services can improve your business processes, customer experience, and drive growth.

Schedule a meeting

Get a lightning-fast, SEO-optimized, high-performance web app for:

  • SaaS platforms
  • Marketplaces
  • Marketing websites
  • News portals
  • Catalogs & listings

Meeting agenda

  1. 01 Define goals & product scope
  2. 02 Quick technical SEO check-up
  3. 03 Outline your development roadmap
30 min
Web conferencing details provided upon confirmation.

Meet our team

Team member 1Team member 2Team member 3Team member 4Team member 5Team member 6

Success!

Form was sent to our team. We will contact you soon.

Get Your Estimate

Tell us about your project and we'll get back to you with an estimate.

Your Name
Solutions
Contact Email
Estimated Budget
Attach File