A plugin opened the door. A system did the rest.

Lupa textiles ran two shops that had grown side by side over the years — each with its own customers, its own terms, and separate maintenance. The system audit revealed that the actual business knowledge wasn't in any documentation, but in the legacy data itself: the B2B customer groups, for instance, were nowhere cleanly modeled and could only be reconstructed from the salutation field. The project began via an unusual route: our own store plugin Credit Limit for B2B & invoice purchase was already in use and became the door-opener for the full migration.

Not "rebuild two shops", but clearly defined goals before the first line of code:

• One platform instead of two building sites: consolidate both legacy shops onto a shared Shopware 6 base.
• Full data migration: move products, customers, orders, and the established SEO substance without any break.
• Digitize B2B processes that were previously safeguarded manually — from assortment control to order handover.
• A credit limit that enforces itself: invoice purchase without manual approval, hard-checked in the checkout.

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

• Legacy data as the only source: customer groups and terms existed only implicitly in the legacy data — migration here meant translating, not copying.
• Two separate data sets had to come together consistently in one platform.
• Assortment separation per dealer: each customer group may see only its approved assortment.
• A fixed ERP: orders must be handed over in a structured, automated way — no manual re-typing.

The migration wasn't pure data copying, but the translation of a grown business into a clean system — delivered to the standards of our Shopware development:

• Customer groups reconstructed from legacy data — out of the salutation field of the legacy records as the foundation for the entire B2B logic.
• Access control per customer group (AccessManager): each dealer sees only its approved assortment.
• XML order handover to the ERP — automated instead of re-typed, including UPS label generation.
• Credit Limit plugin extended for the project: limits per customer group, automatic reset aligned to the payment term, available limit visible in the top bar, and a hard block in the checkout.
• Data migration without breaks: products, customers, orders, and SEO URLs of both shops moved into one platform.
• Move to the client's hosting ahead of go-live — cleanly separated from live operations.

Go-live in summer 2025 — both legacy shops have run on a shared base ever since.

And this is where a project separates from a partnership. Since September 2025, nuonic has owned Shopware support & maintenance and the continued development of the consolidated platform — with a fixed release rhythm instead of ad-hoc firefighting:

• One maintained operation instead of two legacy shops drifting apart.
• Shopware 6.7 as an update epic in preparation — planned, not postponed.
• B2B logic as a living system: customer groups, assortment control, and credit limits grow with the business.
• Plugin feedback loop: project-specific extensions harden the store product for all customers.