Behind every successful migration lie different complex layers: custom logic, platform limitations, and unique business rules. When these elements are overlooked, a technical migration can fail to deliver a functional store.
This case study explores how Next-Cart handled a sophisticated Magento (1)-to-WooCommerce migration. The client was Gijs van Woerdekom, founder of Woerdekom Webdesign in the Netherlands.
This is a multi-layered project. It involves custom product options, pricing inconsistencies, and feature gaps between the two platforms.
Through thorough customization and iterative refinement, the project ultimately delivered a fully functional WooCommerce store. The result not only mirrored the original Magento experience but also enabled a smooth go-live.
Understanding the project scope and business context
This project was carried out for one of Gijs’s clients, an online plant nursery operating on a well-established Magento store.
The dataset was substantial, consisting of 2 taxes, 106 categories, 1189 products, 1095 customers, and 2829 orders.
However, the true complexity of the project lay in how the data was structured and customized within Magento. Magento is known for its flexibility. The platform allows merchants to use third-party modules and custom configurations.
In this case, the customer’s store built custom product options and pricing logic on an external extension. These customizations decided how products were displayed and priced on the frontend. And it is essential to preserve them during migration.
The objective was to ensure that customers would feel the same way as the original Magento store.
The first red flag: Pricing inconsistencies in demo migration
As part of Next-Cart’s standard workflow, a demo migration was performed. It aimed to validate the transfer of data between platforms.
This early step revealed a major issue: product prices in WooCommerce did not match those on the Magento frontend.
With further investigation, the team discovered the root cause of the discrepancy lay in how Magento constructs pricing.
The Magento store did not rely solely on base product prices; instead, it used custom product options. These options influenced how the final price was presented.
Moreover, these options were managed via a third-party extension that introduced additional logic. It included a “View Mode” setting that controlled whether an option was visible on the frontend. As a result, the pricing customers saw was determined by both base values and selectively displayed option adjustments.
Meanwhile, the migration tool, in its default configuration, extracted all available options. It did not distinguish between visible and hidden ones. This led to incorrect pricing calculations and inconsistencies in the new WooCommerce store.
When one option becomes two: Variation mismatch
Alongside pricing issues, the deme migration also revealed discrepancies in product variations. Products with a single option in Magento were imported into WooCommerce with multiple variations.
This inconsistency was also tied to the same underlying customization. Magento stores both visible and hidden options in the backend. But the frontend only displayed those marked as visible. Meanwhile, the migration tools initially retrieved all options without filtering. WooCommerce ended up reflecting both visible and hidden options.
This created confusion not only in product structure but also for customers. Products appeared with extra variations in WooCommerce.
Custom job #1: Rebuilding product option logic
The Next-Cart team implemented a customization to replicate Magento’s frontend logic rather than its raw backend data.
The migration tool was modified to extract only those product options marked as visible. This helps align the data extraction process with the frontend display logic. WooCommerce would then reflect exactly what was seen in Magento.
At the same time, the team adjusted pricing calculations to match the original behavior. The migration tool was configured to ensure that variant pricing in WooCommerce corresponded to the prices in Magento.
These efforts restored data structure and pricing consistency that the demo migration missed.
Preparing for full migration: Clean slate strategy
To prepare for the full migration, the team decided to reset the WooCommerce environment, removing all previously imported data.
This step ensured a clean, controlled environment for the final migration. It helped minimize duplication, conflicts, or residual inconsistencies from earlier test runs. It also allowed the team to validate the migration results, ensuring all data originated from the finalized migration process.
In addition, at the client’s request, CMS pages were excluded from the migration. These pages had already been recreated manually in WordPress, so there was no need to import them from Magento. This streamlined the migration, helping the team focus on the core eCommerce data.
Post-migration reality: Platform differences surface
The full migration successfully transferred the store structure and core data. However, new challenges emerged due to inherent differences between Magento and WooCommerce.
One of those issues was product attributes that contained HTML content.
Magento uses HTML within attribute values to add formatting or links. WooCommerce, however, does not do it the same way. It displays the raw HTML code as plain text. This resulted in product pages displaying unformatted HTML strings. It detracted from the store’s overall presentation and usability.
To address this, an additional customization was introduced to clean attribute values during migration. HTML tags were removed, while the underlying text was preserved. This ensured that product information remained readable and consistent in the WooCommerce store.
Another bigger gap is the missing tier pricing functionality
In Magento, tier pricing is a standard feature. It allows merchants to define quantity-based discounts.
This functionality was essential for the client’s business as several products relied on tiered pricing structures to incentivize larger orders. It was critical to replicate this behavior in WooCommerce.
However, WooCommerce does not natively support tiered pricing. Therefore, a different approach was required.
Custom job #2: Bridging tier pricing with plugin integration
Next-Cart recommended integrating a third-party plugin to handle tiered pricing in WooCommerce.
However, installing the plugin alone was not sufficient. The migration process also needed to map Magento’s tier pricing data into the plugin’s format.
A second custom job was therefore implemented to handle this, enhancing the migration tool. It then extracted tiered pricing information from Magento, restructured it to meet the plugin’s requirements, and imported it into the WooCommerce environment.
This change affected product-level data, so it required remigrating products. Existing products in WooCommerce were removed. Then, the migration was executed again with the updated logic.
This extra step ensured that tier pricing was fully functional and aligned with the client’s business model.
SEO continuity: Preserving visibility across platforms
Despite the technical challenges, the migration of SEO data proceeded smoothly. Product titles, URLs, and meta descriptions were successfully transferred from Magento to WooCommerce.
The client had implemented an SEO plugin in WooCommerce. This allowed the migrated metadata to integrate seamlessly. The store, therefore, maintained its search engine visibility and did not lose valuable rankings.
Maintaining SEO continuity is often a critical concern in platform migrations. In this case, it was achieved without requiring additional intervention.
The final step: Delta migration for go-live precision
As the project approached its launch phase, the focus was to ensure data accuracy at go-live. Between the initial migration and the launch data, additional data was generated, including new orders, customers, and products.
But at this time, instead of another full migration, Next-Cart executed a delta migration. This step identified and transferred only the new or updated data, and left the previously migrated data intact.
The delta migration was carefully scheduled to align with the client’s timeline. The team accounted for the time zone difference between the Netherlands and Vietnam to ensure the final data sync occurred at the optimal time.
Finally, the client was able to launch the new WooCommerce store with complete, up-to-date data without downtime or data loss.
A successful launch and a satisfied client
The result was a fully functional WooCommerce store. It accurately reflected the original Magento store in both structure and behavior.
Product pricing was consistent, variations were correctly configured, and tier pricing functionality was preserved.
The store also maintained its SEO foundation and continuity in search performance.
The client’s feedback highlights both the technical success and the collaboration quality:
"Good, fast and clear communication. No strings attached. Custom solutions are also no problem. A perfect and correct migration, in my case Magento (1) to WooCommerce."
Final thoughts: Turning complexity into clarity
This Magento-to-WooCommerce migration illustrates how complex eCommerce systems can be successfully transferred. It was the right combination of technical expertise and strategic thinking.
Rather than a simple data transfer, Next-Cart approached this process as a translation of business logic from one platform to another. And every customization was aimed at preserving the store's functionality in practice.
The migrated store was a fully operational WooCommerce site that preserved the integrity of the original Magento experience.
In the end, this project is an example of a successful migration defined not by how quickly it is completed, but by how accurately the business behind it is carried forward.
