Replacing a legacy CMS while preserving the complete editorial archive: for ÖKO-TEST, we built a custom editorial system, cleaned and migrated historical data, and supported the editorial team through the transition.
Two women working together in front of a laptop

ÖKO-TEST

Custom editorial system development for an independent consumer magazine

Project management Concept CMS development

Facts

Live since
2022
Collaboration since
2019
Services
  • Project management
  • Technical implementation
  • Consulting

Partner

ÖKO-TEST logo

Development Team

  • 4 Software Developers
  • 1 Project Manager

Technologies

Elixir (Phoenix) React Postgres Redis Adobe Interfaces

The starting point: replace the CMS, preserve the archive

ÖKO-TEST independently tests and evaluates products and services. Its editorial work combines research, test documentation, and publication. A new custom editorial system needed to replace the legacy CMS and preserve the historical data accumulated over years of publishing.

Our collaboration began in 2019; the new system went live in 2022. Alongside concept, consulting, and development, the work included preparing the archive for migration and helping the editorial team adopt the new workflows.

Legacy data
Migrated
Editorial tests
Created
Productivity
Increased

Replacing a legacy CMS and migrating the archive

When building the new editorial system for ÖKO-TEST, one of the main challenges was to replace the existing legacy system and migrate all historical data in its entirety. This process involved not only transferring large amounts of content, but also cleaning up and structurally preparing the many data formats that had accumulated over years of publishing. To ensure data quality and consistency, we performed a comprehensive plausibility check, identified potential sources of error, and systematically resolved duplicates and inconsistencies.

The transition: involve and train the editorial team

Beyond the technical work, carefully planned change management was crucial to a successful transition. We involved the editorial team early, set up regular feedback loops, and aligned user needs closely with the technical implementation. Through targeted training, test phases, and continuous support, we reduced reservations and made sure the new system was not only deployed but actively adopted in everyday work. The result was a smooth rollout that lays the foundation for more efficient editorial processes and a stable system landscape over the long term.

How we modernize legacy systems and migrate data
It's fun to familiarize yourself with such a complex system and continuously improve it — especially when you know that it's in use every day.
Mats Boyens Software Developer at naymspace

Planning to replace an existing system?

Tell us which workflows, data, and interfaces need to survive the transition. Together, we clarify the risks and what a technical assessment should cover before migration begins.

Portrait of Maike Thieme
Maike Thieme

Trusted by

  • OTTO
  • Porsche
  • Deutsche Bahn
  • Öko-Test

Please give us at least one way to reach you: email or phone.

By submitting you agree to our privacy policy. We only use your data to answer your request.