---
title: "Converge — shop carve-out & Shopware 5 maintenance"
description: "How nuonic cleanly carved the Converge online shop out of a shared Shopware 5 multi-shop instance — with data separation down to the database level — and has maintained and developed it independently on Shopware 5 ever since. Delivered with the nuonic F.O.C.U.S. framework."
canonical_url: "https://nuonic.de/en/case-studies/converge-focus"
---

<case-study-hero eyebrow="Case Study · F.O.C.U.S." image="/images/case-studies/converge-hero.png" imageAlt="Converge online shop — digital hardware for educational institutions on Shopware 5">

Shop carve-out. <span>



</span>



<span className="mono-hl">

Cleanly separating a shop from a shared instance.

</span>



<template v-slot:lead="">

How nuonic carved the online shop of [Converge](https://www.convergetp.de/) (formerly Gesellschaft für digitale Bildung) out of a historically grown multi-shop instance — with clean data separation down to the database level — and has maintained and developed it independently on Shopware 5 ever since. A case for our [Shopware support & maintenance](/en/shopware-agency/support), which keeps Shopware 5 running responsibly.

</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":"Converge (formerly Gesellschaft für digitale Bildung)"},{"label":"Industry","value":"IT for educational institutions"},{"label":"Platform","value":"Shopware 5"},{"label":"Project type","value":"Shop carve-out & ongoing maintenance"},{"label":"Timeframe","value":"Since late 2023 (ongoing)"},{"label":"Core","value":"Data separation down to database level"}]" :tags="["Shopware 5","Shopware Maintenance","Shop Carve-out","MySQL Cleanup","Docker Testing","Consent / GA4","Staging","SW 5.7 Update"]" label="Project at a glance">



</case-study-facts>

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

The Converge shop historically ran in a jointly operated Shopware 5 instance with other shops: shared database, shared plugins, shared configuration. What belonged together organizationally eventually didn't anymore — the shop needed its own instance. The [analysis](/en/services/consulting) showed how deep the entanglement went: customer data, orders, products, categories and customer groups of several shops in the same tables.

</case-study-section>

<case-study-section letter="O" name="Objectives" subtitle="Impact over features">

An independent, lean Shopware instance containing only its own data:

- **Only own data:** exclusively its own customers, orders and products.
- **Only needed extensions:** the plugins, payment and shipping methods actually in use.
- **Own tracking & consent:** a setup that belongs to the standalone shop — not to the old group.

</case-study-section>

<case-study-section letter="C" name="Constraints" subtitle="Making limits visible">

The hardest constraint was the database itself: Shopware 5 doesn't cleanly separate subshop data. On top of that:

- **Surgical data deletion:** every deletion of foreign customer and order data had to run via targeted, tested MySQL scripts, without damaging the shop's own data.
- **A grown plugin legacy** from the original instance.
- **Data-protection requirements:** foreign customer data must not remain in the new instance.
- **A shop system at end of life** that still has to carry operations reliably.

</case-study-section>

<case-study-callout title="Separation is precision work">

Every delete query was developed individually, tested locally in the Docker setup — **and only then executed.**

</case-study-callout>

<case-study-stats :stats="[{"value":"1 instance","label":"Cleanly carved out & independent"},{"value":"7 areas","label":"Data cleaned — customers to media"},{"value":"0 foreign data","label":"In the new instance"},{"value":"SW 5.7","label":"Update in live operations"}]">



</case-study-stats>

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

Separate first, then carry.

</case-study-heading>

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

Delivered step by step to the standards of our [Shopware development](/en/shopware-agency/development):

- **Shop identification:** mapping all data records to the shops of the shared instance — the basis for every further decision.
- **Data cleanup via MySQL:** targeted, tested delete queries for foreign customer data, orders, products, categories & shops, email logs, media and customer groups — developed and secured in the local Docker setup.
- **Plugin audit:** analysis of the inherited plugin stock, uninstalling what wasn't needed — with subsequent error testing.
- **Payment & shipping cleaned:** unnecessary payment and shipping methods removed, remaining ones reconfigured with their own credentials and fully tested.
- **Own tracking setup:** consent management (CMP), Google Tag Manager and GA4 newly set up for the standalone instance.
- **Template decluttered:** legacy from theme and plugin extensions of the original instance removed.

</case-study-section>

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

Since the separation, nuonic has looked after the standalone instance in a [Shopware support & maintenance model](/en/shopware-agency/support) — Shopware 5 deliberately keeps running here, operated responsibly:

- **Shopware 5.7 update** including core, store and custom plugins — with deployment and testing.
- **A dedicated staging instance** for risk-free changes.
- **Continuous optimizations:** manufacturer data on the product detail page, 404 handling, design adjustments.
- **Development is ongoing** — currently including the payment extension.

</case-study-section>

<case-study-callout title="Run Shopware 5 responsibly — and keep the path open">

Converge shows that a Shopware 5 shop at end of life doesn't have to be an emergency. We keep the instance stable and up to date through our [Shopware support & maintenance](/en/shopware-agency/support) (SW 5.7, staging, deployment). And because the shop now owns its own instance, its own data and its own tracking, Converge can decide independently — about hosting, roadmap, and one day about [moving to Shopware 6](/en/insights/shopware-6-migration-necessary).

</case-study-callout>

<case-study-callout title="Impact over activity">

Independence begins in the database. **A shop that owns its own instance, its own data and its own tracking can decide independently** — about its hosting, its roadmap, and one day about its next shop system.

</case-study-callout>

<case-study-facts :facts="[{"label":"Separation","value":"Carve-out from a multi-shop instance"},{"label":"Data hygiene","value":"MySQL cleanup, 7 data areas"},{"label":"Consolidation","value":"Plugins, payment, shipping, template"},{"label":"Tracking","value":"CMP, Tag Manager, GA4 standalone"},{"label":"Maintenance","value":"SW 5.7 update, staging, live operations"},{"label":"Model","value":"Ongoing maintenance since late 2023"}]" :tags="["Shopware Maintenance","Shop Carve-out","MySQL","Consent / GA4","Staging"]" label="Services at a glance">



</case-study-facts>

<focus-roles :roles="[{"title":"Strategist","items":["Separation concept & prioritization"]},{"title":"Architect","items":["Data model & instance setup"]},{"title":"Builder","items":["Scripts, cleanup, updates"]},{"title":"Operator","items":["Maintenance & continued development"]}]" label="The roles in the project">
<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" label="Contact" phone="+49 8141 828197-0">
<template v-slot:heading="">

Is your shop still tied to the old group? Let's talk about <span className="cta-hl">

impact

</span>

.

</template>

<template v-slot:body="">

nuonic Digital GmbH & Co. KG · Munich & Hamburg

</template>
</service-contact>