---
title: "Success factors when switching to a headless cms | Ergosign GmbH"
description: "Learn about the advantages of hybrid content migration and how this approach can successfully migrate numerous content pages."
canonical_url: "https://www.ergosign.de/en/insights/blog/swd-hybrid-content-migration"
locale: en
meta:
  "og:description": "Learn about the advantages of hybrid content migration and how this approach can successfully migrate numerous content pages."
  "og:title": "Success factors when switching to a headless cms"
  "twitter:description": "Learn about the advantages of hybrid content migration and how this approach can successfully migrate numerous content pages."
  "twitter:title": "Success factors when switching to a headless cms"
---

> Index of every page on this site: [llms.txt](https://www.ergosign.de/llms.txt)

# **Hybrid content migration:** Key success factors when moving to a headless CMS

![Ein Mann und zwei Frauen sitzen an einem Tisch, vor ihnen steht ein Laptop. Der Mann klatscht lächelnd mit der Frau links von ihm ab, während die andere Frau rechts von ihm ebenfalls lächelt.](https://a.storyblok.com/f/180740/1920x1150/786e6c8e8f/swd_hybride-migration_header.jpg/m/3840x1792/smart)

## Scalable content migration: Best practices for moving to a **headless CMS**

*In the* [*first part of our content series*](https://www.ergosign.de/en/insights/blog/swd-headless-cms)*, we dove into the basics of a successful content migration from a traditional monolithic to a headless CMS with the Stadtwerke Düsseldorf example.*

The migration of content to a headless CMS is a crucial step towards a digital experience platform (DXP). But how do you proceed when the existing system comprises several hundred content pages, of which the majority needs to be migrated to the new system?

Our loyal client, Stadtwerke Düsseldorf, also faced this question. In the second part of this content series, we dive deeper into the migration process using the example of their online magazine.

## **Structure** instead of chaos

Migrating hundreds of pages to a new CMS

### Automated vs manual migration

Initially, we weighed the pros and cons of automated and manual migration. The biggest advantage of **automated migration** is clear: it saves editors time and effort. However, a disadvantage is also evident. If content elements are not displayed as intended, this often becomes apparent only later in the migration process. "Dead" and broken links or non-search engine optimized content must be addressed and adjusted later – identifying and optimizing these can be time-consuming.

On the other hand, **manual migration** offers full control and typically results in a lower error rate. Editors can revise content during migration: by optimizing headlines, rewriting text according to SEO recommendations, or incorporating more suitable imagery. All of this is not a problem when migrating manually. However, this approach entails a significant time investment for the editors. Before content can be migrated step by step, everyone involved must first be trained with the new CMS.

### The best of both worlds — Hybrid migration of the online magazine

Since we migrated numerous pages with varying requirements for Stadtwerke Düsseldorf, we opted for a combination of automated and manual migration. The hybrid approach combines the respective advantages: where appropriate, less complex content, which varies little, is migrated automatically. This saves time, which can be used to manually transfer and optimize complex content.

We started with the migration of the online magazine of Stadtwerke Düsseldorf. Every month, the magazine provides customers with exciting articles on local pride, life, innovation, leisure, mobility, work, and much more. With nearly 500 content pages and a variety of different and nested components such as text, headline, image, and video, the magazine posed a challenge for hybrid migration. We initially developed a new frontend concept that considers SEO recommendations, and prototyped it in Figma. Naturally, we also took into account the requirements of digital accessibility for Stadtwerke Düsseldorf's magazine.

Digital accessibility for an optimal customer experience was considered from the beginning and throughout the remaining content migration.

After developing the components, we began with the automated migration, transferring the framework of the magazine: structures, page titles, and metadata. The Stadtwerke Düsseldorf team was trained by us in using the CMS Storyblok, followed by manual content migration. Our team at Ergosign also actively assisted, if support was needed. This way, the entire online magazine could be transferred efficiently to the new CMS and was simultaneously optimized.

![Screenshot der Startseite des Online-Magazins der Stadtwerke Düsseldorf](https://a.storyblok.com/f/180740/3444x1814/a1caef2fc3/swd_magazin_screen.png/m/3200x0)

*Das migrierte Magazin der Stadtwerke Düsseldorf*

## **Quality** in focus

Beyond the Launch: Continuous Support and the Content Migration Success Checklist.

### Continuous support and quality assurance

A successful content migration requires not only careful planning and implementation, but also continuous support and quality assurance. Before and during the migration, we conducted training sessions for the Stadtwerke Düsseldorf team and ensured that the team was familiar with the new CMS. The transition to Storyblok was made easy due to its high usability and intuitive editing in the backend, especially through the visual editor. After the migration, we tested the migrated articles for errors and set up URL redirects where necessary to ensure a smooth customer experience.

### Checklist: Success factors for successful hybrid content migration

**Careful planning:**  
Thorough analysis and planning are crucial to understanding the scope of the migration, identifying potential challenges, and establishing a clear timeline.

**Evaluation of automated and manual migration:**  
A precise assessment of the pros and cons of automated and manual migration enables finding the right balance between efficiency and control.

**Development of a new frontend concept:**  
Developing a new frontend concept that considers the requirements of the new CMS and SEO recommendations lays the foundation for successful migration and content optimization**.**

**Training and support for the team:**  
Comprehensive training of the team in using the new CMS is essential to ensure that all stakeholders are familiar with the new tools and processes.

**Continuous support and quality assurance:**  
Ongoing support during the migration process and thorough quality assurance ensure that potential issues are quickly identified and resolved to ensure a smooth customer experience.

**Usability of the new CMS:**  
Choosing a CMS with high usability and intuitive operation facilitates the transition for the team and helps increase the efficiency of the migration.

**Testing and troubleshooting:**  
Testing the migrated content for errors and setting up URL redirects are crucial in ensuring customers receive a consistent and error-free user experience.

**Clear communication and collaboration:**  
Open communication and effective collaboration among all stakeholders are crucial for the success of the migration.

At Ergosign, we believe that no content migration is like any other. Therefore, we approach each project tailored to the customer.

Start today with the individual migration of your content!

![Tobias Zapp](https://a.storyblok.com/f/180740/1920x1920/4db980b94d/tobias-zapp.jpg/m/360x360)

### Tobias Zapp

Head of DXP

[+49 681 95 98 20 0](<tel:+49 681 95 98 20 0>)

[projects@ergosign.de](mailto:projects@ergosign.de)

[LinkedIn Dieser Link führt zu einer externen Seite](https://www.linkedin.com/in/tobias-zapp)

## Relevant **Insights & News**

[![Zwei Personen betrachten in einer modernen Galerie eine Skulptur aus bunten Blöcken und Kabeln, die ein Netzwerk darstellt.](<https://a.storyblok.com/f/180740/1920x1080/eec80a7f28/composable-dxp-header.jpg/m/640x426/smart/filters:quality(50)>)<h3>Composable DXP vs. Monolith: Wann Modularität sich rechnet </h3>](https://www.ergosign.de/en/insights/blog/composable-dxp-vs-monolith) [<h3>Digital Accessibility at Yippie </h3>](https://www.ergosign.de/en/insights/blog/digital-accessibility-at-yippie) [![Gruppe von Personen bei der Zusammenarbeit im Büro – sie besprechen Ideen und nutzen Haftnotizen auf einem Whiteboard.](<https://a.storyblok.com/f/180740/5472x3648/e003e95ec5/dxp-pakete-header.jpg/m/640x426/smart/filters:quality(50)>)<h3>Tailored DXP Solutions for Every Digital Ambition </h3>](https://www.ergosign.de/en/insights/blog/optimized-customer-experience-with-dxp) [![Ein Mann steht mit Mikrofon auf einer Bühne und hält einen Vortrag.](<https://a.storyblok.com/f/180740/2880x1920/a5ebe716c4/dx-conf-zuerich_header_joon.jpg/m/640x426/smart/filters:quality(50)>)<h3>Digital Experience Conference 2025 Zurich </h3>](https://www.ergosign.de/en/insights/blog/digital-experience-conference-2025-zurich)

[Go to more news and insights](https://www.ergosign.de/en/insights?tag=0dcc91ca-ec56-4f4d-88c8-00104b31f0e8&tag=3d8be810-ad70-45a8-ab16-961aedb774b1&tag=c9d2705d-29b6-45af-8c77-a0fd0264b99e)

```json
{"@context":"https://schema.org","@graph":[{"@id":"https://www.ergosign.de/#website","@type":"WebSite","inLanguage":"en","name":"Ergosign GmbH","url":"https://www.ergosign.de/","publisher":{"@id":"https://www.ergosign.de/#identity"},"translationOfWork":{"@id":"https://www.ergosign.de/#website"}},{"@id":"https://www.ergosign.de/en/insights/blog/swd-hybrid-content-migration#webpage","@type":"WebPage","dateModified":"2026-10-14T11:26:48.508Z","datePublished":"2024-05-02T00:00:00.000Z","description":"Learn about the advantages of hybrid content migration and how this approach can successfully migrate numerous content pages.","name":"Success factors when switching to a headless cms","url":"https://www.ergosign.de/en/insights/blog/swd-hybrid-content-migration","breadcrumb":{"@id":"https://www.ergosign.de/en/insights/blog/swd-hybrid-content-migration#breadcrumb"},"isPartOf":{"@id":"https://www.ergosign.de/#website"},"potentialAction":[{"@type":"ReadAction","target":["https://www.ergosign.de/en/insights/blog/swd-hybrid-content-migration"]}],"primaryImageOfPage":{"@id":"https://www.ergosign.de/#logo"}},{"@id":"https://www.ergosign.de/#identity","@type":"Organization","name":"Ergosign GmbH","url":"https://www.ergosign.de","logo":{"@id":"https://www.ergosign.de/#logo"}},{"@id":"https://www.ergosign.de/#/schema/organization/#ergosign-organization","@type":"Organization","name":"Ergosign GmbH","url":"https://www.ergosign.de","logo":{"@type":"ImageObject","url":"https://www.ergosign.de/logo.png"}},{"@id":"https://www.ergosign.de/en/insights/blog/swd-hybrid-content-migration#article","@type":"Article","dateModified":"2026-10-14T11:26:48.508Z","datePublished":"2024-05-02T00:00:00.000Z","headline":"Hybrid Content Migration: Success Factors when Moving to a Headless CMS","inLanguage":"en","thumbnailUrl":"https://a.storyblok.com/f/180740/1920x1150/786e6c8e8f/swd_hybride-migration_header.jpg","author":[{"@id":"https://www.ergosign.de/#/schema/person/1"},{"@id":"https://www.ergosign.de/#/schema/person/2"}],"image":{"@id":"https://www.ergosign.de/#/schema/image/1"},"isPartOf":{"@id":"https://www.ergosign.de/en/insights/blog/swd-hybrid-content-migration#webpage"},"mainEntityOfPage":{"@id":"https://www.ergosign.de/en/insights/blog/swd-hybrid-content-migration#webpage"},"publisher":{"@id":"https://www.ergosign.de/#/schema/organization/#ergosign-organization"}},{"@id":"https://www.ergosign.de/en/insights/blog/swd-hybrid-content-migration#breadcrumb","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","name":"Home","item":"https://www.ergosign.de/en","position":1},{"@type":"ListItem","name":"Blog","item":"https://www.ergosign.de/en/insights/blog","position":2},{"@type":"ListItem","name":"SWD hybrid content migration","item":"https://www.ergosign.de/en/insights/blog/swd-hybrid-content-migration","position":3}]},{"@id":"https://www.ergosign.de/#/schema/person/1","@type":"Person","name":"Alina Dier"},{"@id":"https://www.ergosign.de/#/schema/person/2","@type":"Person","name":"Christian Grasmück"},{"@id":"https://www.ergosign.de/#logo","@type":"ImageObject","caption":"Ergosign GmbH","contentUrl":"https://www.ergosign.de/logo.png","inLanguage":"en","url":"https://www.ergosign.de/logo.png"},{"@id":"https://www.ergosign.de/#/schema/image/1","@type":"ImageObject","contentUrl":"https://a.storyblok.com/f/180740/1920x1150/786e6c8e8f/swd_hybride-migration_header.jpg","inLanguage":"en","url":"https://a.storyblok.com/f/180740/1920x1150/786e6c8e8f/swd_hybride-migration_header.jpg"}]}
```

## Sitemap

See the full [sitemap](https://www.ergosign.de/sitemap.md) for all pages.
