Shopware 5 to 6 Migration for a Complex Aviation eCommerce Platform with Custom Workflow Logic
Eisenschmidt needed more than a technical platform upgrade. The move from Shopware 5 to Shopware 6 had to preserve a complex aviation eCommerce model that included digital subscriptions, course-related workflows, customer-specific pricing, product-document handling, Pickware connectivity, and finance-sensitive order processes. BrandCrock supported the transition with structured migration delivery, custom Shopware development, workflow clarification, and operational stabilization.

Project Snapshot
Client:
Eisenschmidt
Platform:
Shopware 5 → Shopware 6
Industry:
Aviation eCommerce
License:
Shopware Evolve
Business Model:
B2C & B2B
Scope:
Migration, frontend and backend development, custom workflow plugins, theme alignment, daily sync, Pickware connectivity, SEO/on-page work, go-live, and operational stabilization
Complexity:
High-data migration, digital-product workflows, third-party course integration, customer-group pricing, finance-sensitive order handling, and plugin-heavy delivery
The Challenge
Eisenschmidt was not migrating a standard product shop. The project involved a large Shopware 5 environment with established workflows that extended far beyond normal catalog and checkout behavior.
The migration scope covered substantial historic data and a plugin-heavy setup. The supporting material references 700,000+ migration records, 10,000+ products including variants, 100,000+ customers, 500,000+ orders, 30+ plugins, Pickware, and Avendoo integration. At the same time, the target Shopware 6 shop had to preserve subscriptions, training products, pricing logic, ordering models, and finance-related handling that were already part of day-to-day operations.
Key challenges
- High-volume migration from Shopware 5 to Shopware 6
- 35 custom plugin developments/conversions in the original scope
- Renewable and non-renewable subscription logic
- Avendoo course activation workflows
- Customer-group-based pricing
- PDF datasheet handling on product pages
- ICAO collective ordering
- Daily synchronization between Shopware 5 and Shopware 6 before final transition
- Workflow clarity around vouchers, Vorkasse, invoicing, and dunning
- Additional Pickware-related complexity beyond the original estimate
What We Delivered
BrandCrock handled the project as a connected migration, redevelopment, and workflow platform build.
The Shopware 6 environment was set up as a new installation and developed across both frontend and backend layers. The storefront was aligned closely with the established Shopware 5 design, while additional theme work was carried out for sub-shop requirements. Payment, shipping, email templates, and invoice templates were also implemented as part of the broader delivery. The contract appendix explicitly covers migration, theme development, plugin/widget development, later version updates, remigration of new data, Pickware connectivity, SEO/on-page work, and go-live staging.
Beyond migration, BrandCrock developed custom functionality to preserve and improve key business workflows. This included digital subscription logic, Avendoo-based course activation, group-based discount pricing, daily SW5-to-SW6 data sync before go-live, PDF datasheet handling, and ICAO collective ordering. Supporting materials also show that the new platform was built with plugin continuity in mind, with multiple Shopware 5 plugins reviewed for Shopware 6 availability across areas such as DATEV, Pickware, Stripe, DHL, Doofinder, SAP OCI, and store locator functionality.
In parallel, finance-related workflow issues such as voucher handling, invoice timing, Vorkasse logic, and dunning behavior were reviewed, clarified, and documented so that migration progress also translated into smoother daily operations.
Implementation Highlights
01
Structured Shopware 5 to 6 migration
BrandCrock supported the move from Shopware 5 to Shopware 6 through structured migration delivery across frontend, backend, and shop setup, including remigration of new data generated during the project.
Outcome: Eisenschmidt gained a controlled transition path instead of a risky version upgrade.
02
Digital-product and subscription workflow development
Custom logic was developed for renewable and non-renewable subscriptions, including expiry handling, renewal logic, follow-up order generation, invoice generation, and customer-profile visibility. Avendoo course activation was also integrated so access began only when explicitly activated by the customer.
Outcome: digital products and training-related offerings could be managed in a way that matched the real business process.
03
Customer-specific pricing and specialized ordering logic
BrandCrock developed group-based discount functionality and a dedicated ICAO collective ordering workflow for quantity-driven purchasing scenarios.
Outcome: the shop better reflected aviation-specific ordering and pricing requirements.
04
Daily cross-version synchronization before go-live
To reduce data drift during transition, a custom process was developed to transfer newly created products, variants, images, customers, and orders from Shopware 5 to Shopware 6 before final cutover.
Outcome: the target system remained closer to live business reality during the migration phase.
05
Product-information and workflow stabilization
The project also included PDF datasheet handling for product pages and clarification of voucher, invoice, Vorkasse, and dunning workflows, supported by documentation and staging.
Outcome: the migrated platform became more usable not only technically, but operationally.
06
Theme development and Email Template customization
BrandCrock developed and customized the Shopware 6 storefront theme while also implementing transactional email and document templates
Outcome: the storefront gained a more consistent user experience, while email and document workflows became more structured and aligned with the platform design.
Outcome
The Eisenschmidt project delivered more than a successful migration. It created a more stable Shopware 6 foundation for an aviation eCommerce business with non-standard workflow requirements.
- Controlled Shopware 5 → 6 migration for a complex aviation eCommerce setup
- 972 contracted hours plus 265.5 additional hours approved for Pickware plugin development
- Preserved and improved digital-product workflows
- Better fit for customer-group pricing and specialized ordering logic
- Reduced transition risk through structured migration and daily sync
- Clearer handling of finance-sensitive order workflows
- Stronger basis for ongoing maintenance, plugin continuity, and future development
Planning a Shopware migration with custom workflows and operational complexity?
If your shop combines migration requirements with subscriptions, training products, specialized ordering, or finance-sensitive workflows, a structured technical review can reduce avoidable complexity before it affects go-live and daily operations.
