Initiation and Planning for CMS Transition

Summary
Ahlsell’s current CMS (EpiServer, now Optimizely) is outdated, heavily customized, and built on legacy .NET Framework. This has prevented version upgrades, locked us into a monolithic structure, and slowed down our ability to innovate. Migrating to a modern headless CMS is essential to remove blockers, accelerate development speed, and provide editors with a simpler, more sustainable content platform. This initiative ensures that future growth in e-commerce and digital experiences is not constrained by obsolete technology.

1. Current Situation and Challenges

• Legacy CMS (EpiServer/Optimizely): Running on an outdated version with no recent upgrades due to extensive customizations.

• Monolithic architecture: Tightly coupled CMS and e-commerce module create dependencies that hold back development.

• Technology stack: Large parts still rely on old .NET Framework, making it harder to recruit developers and increase delivery speed.

• Editorial pain points: Editors face inefficient workflows (e.g., menu handling, multiple content entry points).

• Upgrade risks: Customizations make upgrades costly and slow, preventing adoption of new features.

2. CMS Evaluation and Direction

• Strapi tested and discarded: Initially considered, but rejected due to compatibility issues and weak upgrade support.

• Directus under evaluation: Current candidate due to PostgreSQL alignment, schema control, and modern UI.

• Open choice: No final CMS has been selected; discovery pilots will determine the best fit.

3. Business Value and Enablers

• Accelerated development: Moving away from .NET Framework and Epi monolith will allow faster delivery cycles and shorter time-to-market.

• Future-proof technology: API-first, headless architecture ensures scalability and easier integration with other platforms.

• Reduced technical debt: Eliminates legacy dependencies that currently slow down upgrades and limit flexibility.

• Improved editorial efficiency: Editors focus on content creation, not layout or technical complexity.

• Sustainable operations: Simplified, modern CMS reduces long-term maintenance costs and operational risks.

4. Key Implementation Considerations

• Discovery-first: Validate new CMS with pilots (e.g., Swedish homepage) before broad rollout.

• Data migration: Plan and test article migration from EpiServer to new CMS.

• Parallel operation: Old and new CMS may run side by side during transition.

• Change management: Editors across countries must be onboarded and supported step by step.

5. Risks, Dependencies & Mitigations

• Uncertainty: Best CMS fit not yet determined.
  Mitigation: Test Directus and potentially other candidates via discovery pilots.

• Risk: Complex migration from EpiServer to new CMS.
  Mitigation: Start with limited pilots, validate migration tooling and process early.

• Dependency: Content producers and editors in multiple countries.
  Mitigation: Identify key stakeholders early, communicate clearly, and involve them iteratively.

• Issue: Adoption of new workflows by editors.
  Mitigation: Provide training, emphasize simplified processes, and gather feedback continuously.

6. Target State

A modern headless CMS that:

• Removes legacy EpiServer dependencies and monolithic constraints.

• Enables higher development speed and agility.

• Provides a clean, editor-friendly environment focused on content creation.

• Serves as a scalable, API-driven platform for future digital initiatives.