Shop carve-out. Cleanly separating a shop from a shared instance.

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 showed how deep the entanglement went: customer data, orders, products, categories and customer groups of several shops in the same tables.

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.

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.

Delivered step by step to the standards of our Shopware 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.

Since the separation, nuonic has looked after the standalone instance in a Shopware support & maintenance model — 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.