A simple eCommerce migration is often perceived as a one-time technical task: move data, verify results, and go live. However, this process will involve much more work for businesses with complex pricing logic, historical customer data, and they are still live during the migration.

The story below is about a Shopware 5-to-WooCommerce migration for Simplifix Studio, a Bulgarian digital agency. The migration request was directly contacted by Simeon Nenov. 

Simeon was managing eCommerce projects for multiple clients, and he had previously collaborated with Next-Cart on another successful migration. This time, Simeon returned to Next-Cart and asked Jason Dinh, whom he had worked with, to continue handling his migration project.

What followed was a long-running, high-priority migration project. It extended deep into custom logic, database operations, and repeated synchronizations.

Keep reading!

Project background: A returning client with high expectations

Shopware 5 was nearing the end of its lifecycle at that time. Simplifix Studio, which runs its store on this platform, must decide on another platform to move to. WooCommerce was a proper choice for their business due to its flexibility, a broad plugin ecosystem, and long-term scalability.

On behalf of Complifix Studio, Simeon reached out to Next-Cart, and the project was immediately marked as high priority based on his clarifications and specific requirements:

• The store has a large historical dataset that needs to be moved.

• Business logic depended heavily on custom pricing and unit calculations.

• Customer data required ID continuity.

• SEO and logic credentials could not be disrupted.

• Multiple pre-launch and post-launch syncs were required to ensure the complex migration.

At the same time, the Shopware store needed to remain operational throughout the migration. Downtime or data inconsistencies were unacceptable.

Simeon didn’t ask for transactional migration alone; he sought a technical partner to adapt suitable tools, implement proper logic, and provide hands-on support throughout every phase of the transition.

Migration setup and initial execution attempt

The initial miration request covered all critical business data, including: 

• Products and categories

• Customers

• Orders and invoices

• DHL shipping labels

These migration entities were very common in normal migration. However, each one required careful handling to avoid breaking storefront functionality or backend workflows. Therefore, the migration was planned in stages instead of rushing into execution. This step ensured that data accuracy, relationships, and formatting would be preserved from the beginning.

To begin, KitConnect was installed on both the Shopware source store and the WooCommerce target store to create a secure environment.

At the customer’s request to add more products to the Shopware store, the migration timeline was temporarily paused to ensure no data was missed. Once the source data was finalized, the full migration was executed successfully.

After completion, the migration data was carefully reviewed and validated. Simeon confirmed that all products, customers, orders, and related data had been transferred accurately and were functioning as expected in WooCommerce.

Advanced customizations: Rebuilding business logic

What truly defined this story was the level of customization after the initial migration. The Shopware store actually implemented specific unit and pricing logic that did not directly map to WooCommerce’s default structure.

To address this, Jason systematically converted product units, such as milliliters to liters and grams to kilograms, while he and the team standardized unit price values to a consistent base.

This process required both backend adjustments and frontend validation, as well as a deep understanding of how migrated data behaves in a live WooCommerce environment.

Implementing UVP pricing and locale formatting

UVP (Unique Value Proposition) price was stored in a custom Shopware field, and Simeon asked to include it in the migration. This field was actually not supported by default in the migration logic. Jason needed to modify the migration tool to correctly extract and map UVP values into WooCommerce.

At the same time, locale formatting had to be addressed, as the store used comma-based decimal formatting rather than the dot-based format. Failing to adjust this would lead to pricing discrepancies and calculation errors. Being aware of this, Jason carefully apply according format rules across relevant fields. As a result, numerical accuracy and regional consistency throughout the storewas secured.

Preserving customer ID synchronization

One of the most demanding aspects of this migration project was aligning customer IDs between Shopware and WooCommerce. The custom customernumber field needed to remain consistent after migration.

This required database-level updates and skills to avoid ID conflicts. Though this step went well beyond standard migration processes, the team focused on preserving historical references, accounting workflows, and third-party integrations to keep full continuity of the WooCommerce customer database with the legacy Shopware system.

Incremental syncs for a live store

Rather than shutting down the source store for a single migration, the project implemented multiple incremental synchronizations: syncing new products, migrating customers and orders before launch, and performing a final sync right before going live.

The phased separation allowed the business to continue operating on Shopware while preparing WooCommerce in parallel. This approach helped reduce risk and ensured a smoother transition.

Maintaining SEO URLs and passwords

Preserving SEO performance was also critical for Simeon and his business. After the migration and further validation, existing Shopware SEO URLs were migrated and properly redirected. Search engine rankings and inbound traffic were maintained after launch.

In addition, customer passwords were successfully synchronized. Existing users could log in to the new WooCommerce store without resetting their credentials. This minimized friction and reduced unnecessary support requests after go-live.

Secure customer IBAN migration and additional field mapping

The process also involved migrating IBAN data that was not accessible via standard Shopware exports. To handle this, IBANs needed to be extracted from a Shopware database backup and carefully mapped to WooCommerce customer fields. 

Additional product fields were also mapped during the project. The Shopware field “Letzer Einkaufspreis (netto)” was transferred into WooCommerce’s MPN field with specific decimal formatting. As a result, internal remained usable for reporting and future integrations.

Clear explanations for requests outside the migration scope

During the project, several customer requests were discussed in depth. Each request reflected real operational needs. In the meantime, some fell outside the scope of a data migration. 

All limitations were carefully explained to Simeon to keep expectations aligned.

Order reminder and payment warning emails

Simeon requested migrating the custom order reminder and payment warning emails, including friendly reminders, payment notices, and first and final warnings. These workflows did exist in the original store, but they could not be migrated automatically. 

This was because such emails are not stored as transferable data in Shopware. In WooCommerce, reminder and payment emails were generated dynamically by the system and depended on the store’s internal configuration. In this circumstance, static templates that can be exported and imported didn’t work.

This request was identified as a configuration task rather than a migration one.

As an alternative, Jason recommended configuring WooCommerce native email templates or using reminder plugins designed for WooCommerce. 

Replacing product images with identical filenames

Another request of Simoen was to replace existing product images with new versions that used the same filenames but different formats, such as converting standard images to WebP.

This was not supported because the migration process treated images as media assets rather than simple file references. Images were imported into WordPress as new files, and the system couldn’t overwrite existing media. Additionally, the migration tool could not detect whether two images were ‘the same’ when they differed in format, size, or metadata.

The recommended solution was to manually update images where needed or to use a WordPress image optimization plugin.

Importing and assigning product attributes from Excel

The customer also requested that product attributes from an Excel file be applied to existing WooCommerce products.

In reality, the migration tool was designed for store-to-store data transfer, not for importing external files. Applying attributes from Excel would require custom parsing logic and rebuilding product-to-attribute relationships. Meanwhile, this carried a high risk of data inconsistencies and broken relationships for the already migrated WooCommerce store. 

Excel-based attribute assignment was considered part of manual store setup, not migration.

Jason recommended adding attributes manually in WooCommerce or using a WooCommerce CSV import plugin.

Migration scale and validation

Finally, each entity of the original Shopware 5 was successfully migrated, validated, and confirmed by the customer, including:

• 3 tax rules

• 7 manufacturers

• 49 categories

• 620 products

• 1,087 customers

• 5,904 orders

• 79 product reviews

• 1,000 coupons

Simeon repeatedly confirmed the accuracy of the data, correct pricing and unit logic, customer information, and successful SEO and password settings.

A migration was defined by expertise and trust

This migration store demonstrates the importance of a collaborative technician partnership. It goes through multiple migration stages, advanced customizations, database-level handling, and consistent communication. The project concluded with a fully validated WooCommerce store ready for long-term growth of Simplifix Studio.

For Next-Cart, this case highlights the value of expertise, experience, and flexibility in handling complex migrations. The result was not just a successful platform transfer but also the reinforcement of customer relationships with Simeon and his business.