Last updated:
Wortmann Group: Tamaris Shopware 5 to Shopware 6 Migration Under a Five-Month Deadline
Embedded Shopware engineering and dedicated QA capacity enabled the migration from Shopware 5 to Shopware 6 within five months, without expanding the client's permanent team. AI-assisted QA reduced actual QA effort by 25% against the original estimate.
Project Summary
Wortmann Group needed to move the Tamaris ecommerce storefront from Shopware 5 to Shopware 6 within five months, but its existing engineering team could not add the required capacity through permanent hiring. The timeline did not allow for recruitment or a lengthy external onboarding process.
Elogic Commerce embedded two certified Shopware developers and a QA engineer into Wortmann Group’s existing team to accelerate the replatforming. The client retained architectural and product ownership while Elogic Commerce supplied the specialist Shopware engineering and QA capacity needed to meet the deadline. The team was onboarded into the client’s environment in under three days and delivered the migration over four months, followed by a dedicated month of production stabilization.
Elogic Commerce incorporated AI-assisted engineering practices into the development and QA workflow, with technical and production decisions remaining under human engineering oversight. The agreed QA scope was completed using 25% fewer hours than originally estimated, while test strategy, risk assessment and release decisions remained under QA ownership. The migration went live inside the five-month window.
Key Outcomes
5
months from start to production, including a dedicated month of stabilization.
25%
fewer QA hours than originally estimated, while completing the agreed QA scope.
< 3
days to onboard the embedded team into the client's environment.
maintained
regression coverage alongside development rather than compressed into the final stage of the migration.
About the Client
The Tamaris online store was running on Shopware 5 prior to this migration.
Wortmann Group is a German footwear manufacturer, wholesaler and retailer, founded in Detmold in 1967 and the company behind Tamaris, one of its flagship footwear brands. The group trades in more than 70 markets. Tamaris is the storefront this migration covered.
Business Challenge
01
A platform transition already decided
Wortmann Group needed to move Tamaris from Shopware 5 to Shopware 6. This was not a version upgrade: Shopware 6 introduced a redesigned architecture, so functionality had to be adapted rather than transferred. The platform decision was made; the problem was execution.
02
An urgent delivery requirement
The migration carried a timeline that could not be met by the client’s existing team alone, and could not wait for recruitment.
03
Integration into an existing engineering organization
Any external capacity had to work within the client’s development environment, architecture, processes and team structure rather than establishing a separate delivery track.
04
Migration risk under time pressure
The transition had to reach production without compromising ecommerce functionality, customer experience or regression coverage.
05
QA coverage that could not be traded away for speed
Compressing a migration timeline usually means compressing testing. On a replatforming, that is where the risk concentrates.
Why Elogic Commerce Was Brought In
Wortmann Group had already decided to migrate from Shopware 5 to Shopware 6. The constraint was execution: the migration had to reach production within five months, and the internal team could not add permanent engineering capacity quickly enough.
Elogic Commerce supplied the missing capacity as an embedded team of two certified Shopware developers and one QA engineer. The specialists joined the client’s existing environment rather than establishing a separate delivery track, allowing Wortmann Group to retain architectural and product ownership while adding the Shopware and QA capacity the migration required.
The QA role was deliberately staffed alongside development. On a time-critical replatforming, testing cannot become the final buffer in the schedule; regression coverage has to progress with the migration.
Elogic Commerce's Contribution
Certified Shopware engineering
Two certified Shopware developers contributed to the Shopware 6 migration as part of the client’s internal team. Their work covered:
- Shopware 6 architecture and configuration. Adapting the platform architecture to support the client’s B2B commerce requirements and multiple business models.
- B2B commerce functionality. Customer-specific catalogs, pricing, permissions, ordering rules and other account-level business logic.
- Custom Shopware development. Extending Shopware where standard platform capabilities did not meet the requirements.
- Data and catalog migration. Migration and validation of products, customer data, pricing structures and other commerce data.
- Integration development. Building and maintaining the interfaces required to synchronize commerce data with the surrounding business systems.
- Performance and scalability optimization. Addressing bottlenecks carried over from the previous implementation and optimizing application and database behavior.
- Deployment and production readiness. Environment configuration, release preparation, cutover and post-launch stabilization.
Embedded team extension
Elogic Commerce’s developers and QA engineer joined Wortmann Group’s team for the duration of the replatforming, working inside the client’s environment and to the client’s processes rather than running a parallel delivery track. Work was allocated within the client’s own planning, and architectural and product decisions stayed with Wortmann Group throughout.
Dedicated QA
A QA engineer joined the team and took responsibility for QA through the replatforming, owning test strategy, risk assessment, acceptance criteria, defect prioritization and release readiness. On a replatforming with this much B2B business logic, regression coverage across commerce workflows was a substantial share of the total effort, which is why QA was staffed as a dedicated role rather than absorbed into development capacity.
AI-assisted QA
AI assistance was applied to the repetitive, high-volume parts of the QA workstream: generating and refining test scenarios and test cases from requirements and implemented functionality, building regression coverage for repetitive commerce flows, preparing test data and variations, organizing test results, logs and defect information, surfacing edge cases that warranted additional regression coverage, and automating repetitive validation tasks where appropriate.
The QA engineer remained responsible for test strategy, risk assessment, acceptance criteria, interpretation of results, defect prioritization, and the decision on whether functionality was ready for UAT and release. AI accelerated the preparation and analysis around those decisions rather than making them.
AI-assisted QA reduced the effort required for the agreed QA scope by 25% against the original estimate, measured as actual hours against estimated hours, while test strategy, risk assessment, defect prioritization and release decisions remained under the QA engineer’s control.
Migration Approach
The migration was delivered through parallel engineering, migration and QA workstreams over four months, followed by a dedicated month of production stabilization. This allowed the team to maintain development velocity without postponing testing until the end of the project. The sequence covered requirements and technical assessment, Shopware 6 architecture, implementation and customization, data and integration migration, continuous QA and regression testing, UAT, production cutover, and stabilization and optimization.
The main technical challenges were:
Shopware 6 has a fundamentally different architecture, so existing business logic could not simply be transferred. Custom functionality had to be redesigned and reimplemented.
Customer-specific catalogs, pricing, permissions, ordering rules and other account-level requirements had to be supported without creating an overly complex customization layer.
Products, customer records, pricing structures and their relationships had to be transferred while preserving data integrity and business-critical dependencies.
Existing interfaces with the surrounding enterprise systems had to be adapted or rebuilt for Shopware 6 while maintaining reliable data synchronization.
The legacy Shopware 5 implementation had accumulated significant business logic, creating application and database bottlenecks, which made the migration an opportunity to optimize performance and scalability.
Critical B2B and ecommerce workflows had to be validated continuously rather than at the end of the migration.
The launch had to happen without disrupting active ecommerce operations, requiring data validation, release preparation, UAT, cutover planning and post-launch stabilization.
Results & Delivery Impact
Delivery
The Shopware 5 to Shopware 6 migration reached production within the agreed five-month window, including one month of stabilization.
Capacity
Two certified Shopware developers and one QA engineer supplemented the internal team without requiring permanent hiring, and without Wortmann Group giving up architectural or product ownership.
Onboarding
The embedded specialists became operational inside the client's environment in under three days.
QA efficiency
The agreed QA scope required 25% fewer hours than originally estimated, with test strategy, risk assessment, defect prioritization and release readiness remaining under the QA engineer's ownership.
Risk control
Regression coverage progressed alongside development rather than being deferred to the end of the migration.
What This Project Demonstrates
01
Shopware 6 migration expertise
02
Shopware 5 to Shopware 6 migration experience
03
Certified Shopware engineering
04
Embedded ecommerce engineering and team extension
05
Dedicated QA through a time-sensitive migration
06
AI-assisted engineering under human oversight
07
Engineering delivery under urgent timelines
08
Measurable migration delivery and QA efficiency
09
B2B commerce architecture on Shopware 6, including customer-specific catalogs, pricing and permissions
When This Solution Is a Good Fit
01
You already have an internal engineering team and a technical owner.02
The platform decision has been made and the constraint is execution, not strategy.03
You need Shopware specialists quickly, on a compressed timeline.04
You want to retain architectural and product ownership.05
You need dedicated QA alongside development capacity.06
You want to accelerate delivery without outsourcing engineering ownership.Need Shopware Expertise for an Urgent Migration?
Elogic Commerce provides certified Shopware developers and QA specialists who can embed into existing ecommerce teams, support Shopware 5 to Shopware 6 migrations, and add delivery capacity when a fixed migration date cannot wait for permanent hiring. Talk to Elogic Commerce about your migration.