---
title: "Xucker — Replatforming from Shopware 5 to Shopware 6"
description: "Replatforming Xucker from Shopware 5 to Shopware 6 — and two years of continuous development after that. Delivered with the nuonic F.O.C.U.S. framework."
canonical_url: "https://nuonic.de/en/case-studies/xucker-focus"
last_updated: "2026-08-14T18:31:48.621Z"
---

<case-study-hero eyebrow="Case Study · F.O.C.U.S." image="/images/case-studies/xucker-hero.jpg" imageAlt="Xucker D2C shop on Shopware 6">

Xucker goes live. <span>



</span>



<span className="mono-hl">

A system that generates revenue.

</span>



<template v-slot:lead="">

Replatforming Xucker from Shopware 5 to Shopware 6 — and two years of continuous development after that. Delivered with the nuonic F.O.C.U.S. framework. Because go-live is not a success. It is where responsibility begins.

</template>
</case-study-hero>

<case-study-focus-strip :phases="[{"letter":"F","name":"Facts","tagline":"Reality over assumptions"},{"letter":"O","name":"Objectives","tagline":"Clarity before speed"},{"letter":"C","name":"Constraints","tagline":"The truth about systems"},{"letter":"U","name":"Execution","tagline":"Build, don't discuss"},{"letter":"S","name":"Scaling","tagline":"Growth is a system"}]">



</case-study-focus-strip>

<case-study-facts :facts="[{"label":"Client","value":"Xucker – sugar-free & sugar-reduced food"},{"label":"Industry","value":"Food / D2C E-Commerce"},{"label":"Starting point","value":"Shopware 5 (end of support)"},{"label":"Target platform","value":"Shopware 6"},{"label":"ERP","value":"SAP Business One (Sync4)"},{"label":"Delivery","value":"2022 – Go-live Nov. 2023"},{"label":"Continuous development","value":"Nov. 2023 – end of 2025"},{"label":"Services","value":"Replatforming · Plugins · Deployment · Maintenance"}]" :tags="["Shopware 6","SAP Business One","Sync4","Experience Worlds","Plugin Development","OpenSearch","Redis","Klaviyo","Mollie","BFSG","Server-Side Tracking","Deployment Pipeline"]" label="At a glance">



</case-study-facts>

<case-study-section letter="F" name="Facts" subtitle="Reality over assumptions">

Xucker stands for sugar-free and sugar-reduced food — a content-driven D2C shop with recipes, a magazine, and products that need explaining. The basis: Shopware 5 with end of support on the horizon, custom-grown commerce logic, and SEO substance built up over years. The [system audit](/en/services/consulting) showed: the platform wasn't limiting today's revenue, but every future decision.

</case-study-section>

<case-study-section letter="O" name="Objectives" subtitle="Clarity before speed">

Not "a new shop", but clearly defined goals before the first line of code:

- **A future-proof platform** before Shopware 5's end of support — via a [Shopware migration](/en/shopware-agency/migration) without loss of functionality.
- **Preserve the content worlds:** recipes, magazine, and storytelling as experience worlds — an upgrade, not a compromise.
- **Business logic as clean plugins** instead of core modifications — update-capable from day one.
- **Go-live without a break:** fully migrate customers, orders, reviews, and [SEO substance](/en/shopware-agency/seo).

</case-study-section>

<case-study-section letter="C" name="Constraints" subtitle="The truth about systems">

The critical conditions were named before implementation, not discovered during it:

- **Live operation** — the migration ran during full daily business.
- **Data from Shopware 5:** existing customers, order history, thousands of reviews.
- **Fixed system landscape:** SAP Business One as ERP (via Sync4), Trusted Shops, tracking setup.
- **Grown URL structure** — every lost URL is lost revenue.

</case-study-section>

<case-study-callout title="The decision formula behind every work item">

**Impact** on revenue, **commitment** to the deadline, **ownership** of the result. Projects don't fail because of technology, but because of unclear facts, goals, and limits. The framework forces clarity — before the first line of code.

</case-study-callout>

<case-study-stats :stats="[{"value":"591","label":"Total work items"},{"value":"9","label":"Custom plugins"},{"value":"54","label":"Releases in operation"},{"value":"3.5 yrs","label":"Partnership"}]">



</case-study-stats>

<case-study-heading eyebrow="Execution & Scaling">

Go-live is not a success. It is where responsibility begins.

</case-study-heading>

<case-study-section letter="U" name="Execution" subtitle="Build, don't discuss">

148 work items, structured into five epics: base setup, frontend & theme, backend & custom plugins, experience worlds, go-live & deployment. No endless concept phases — iterative delivery with a staging system and deployment pipeline from the very first work item.

- **9 custom plugins** instead of core hacks: minimum order quantities, direct debit payment, content teasers, product sliders, custom experience-world elements, and more — every requirement encapsulated and update-capable, following the standards of our [Shopware development](/en/shopware-agency/development).
- **Content migration with substance:** recipes, magazine, FAQs, and brand pages rebuilt as experience worlds — including rich snippets for recipes and reviews.
- **Data migration without a break:** existing customers, order history, and imported reviews from Shopware 5.
- **ERP integration secured:** SAP Business One via Sync4 — articles, stock, and orders in automatic sync, throughout the migration.

Go-live in November 2023 — during live operations, on schedule.

</case-study-section>

<case-study-section letter="S" name="Scaling" subtitle="Growth is a system">

And this is where a project becomes a partnership. After go-live, nuonic took full responsibility for [Shopware support & maintenance](/en/shopware-agency/support) and continuous development — 443 further work items, prioritized by data:

- **54 releases in two years** — continuous instead of big bang.
- **Shopware 6.5 → 6.6 → 6.7** — major updates without downtime in daily business.
- **BFSG accessibility implemented** before it became a risk — including legal requirements from the legal opinion.
- **Performance as a standing order:** search moved to OpenSearch; sessions, cache & cart offloaded to Redis.
- **Marketing stack expanded:** Klaviyo, server-side tracking, Mollie as payment provider, affiliate and marketplace integrations.

</case-study-section>

<case-study-callout title="Go-live is not a success. It is where responsibility begins.">

Two years later, the shop was running on a more current Shopware version than on day one — with **more features, better performance, and legal requirements fulfilled.**

</case-study-callout>

<case-study-facts :facts="[{"label":"Work items","value":"443 after go-live"},{"label":"Releases","value":"54 deployments"},{"label":"Shopware versions","value":"6.5 → 6.6 → 6.7"},{"label":"Compliance","value":"BFSG & legal opinion implemented"},{"label":"Risk","value":"0 big-bang risks"},{"label":"Model","value":"Full operations & development ownership"}]" :tags="["Release Management","Shopware 6.7","OpenSearch","Redis","Klaviyo","Mollie","BFSG","Server-Side Tracking"]" label="Numbers from two years of operation">



</case-study-facts>

<focus-roles :roles="[{"title":"Strategist","tagline":"Clarify facts, goals, and limits – before anything is built."},{"title":"Architect","tagline":"Update-capable structure – plugins instead of core hacks."},{"title":"Builder","tagline":"Deliver iteratively – with pipeline, staging, and review."},{"title":"Operator","tagline":"Own operations, updates, and continuous development."}]" label="Four roles, one team">
<template v-slot:heading="">

Four roles, from facts to scaling.

</template>

<template v-slot:intro="">

Responsibility across the full cycle — operationally tied to the phases, with no handoffs into the void.

</template>
</focus-roles>

<service-contact background="navy" ctaLabel="Let's talk impact →" ctaTo="/en/contact" image="/images/team/founders.jpg" imageAlt="Benedikt Rillox and Alex Jank, the founders of nuonic Digital" label="Contact" phone="+49 8141 828197-0">
<template v-slot:heading="">

Is your shop managing instead of growing? Let's talk about impact.

</template>

<template v-slot:body="">

nuonic Digital GmbH & Co. KG · Munich & Hamburg

</template>
</service-contact>