When a migration project involves legacy data and historical redirects, it requires higher stakes.
This case study tells the story of John Guthrie, from All Net Holdings (PTY) LTD in South Africa. His journey went through a WooCommerce-to-WooCommerce migration that required an out-of-the-box solution.
John had already worked with Next-Cart previously on a Magento multisite-to-WordPress migration that presented challenges. This time, he returned after six months for a new project. It was a significant signal of continued trust and confidence in Next-Cart service.
During the migration, the Next-Cart team filtered custom customers, optimized the entity limit, and preserved legacy Magento URL redirects. We did all of that while ensuring minimal data loss and maintaining site stability.
This is a story about careful listening, tailored engineering, and hands-on support that are vital in turning a complex migration into a successful outcome.
Project background: A WooCommerce store with a complex history
For this migration project, John was moving an existing WooCommerce store to a new WooCommerce site. The source site had thousands of WordPress users, but not all were actual customers. Also, historical data, including SEO-related URL redirects from the earlier Magento migration, needed to be retained.
The project was directly supported by Jason Dinh from the Next-Cart team, who worked closely with John to clarify his requirements and adjust the migration logic. He ensured the team produced final results that aligned with the customer's actual business.
The initial challenge: Distinguishing WordPress users from WooCommerce customers
When starting the project, John purchased a 5,000-entity migration plan, as he thought it was sufficient for this store. He based it on the WooCommerce customer number, which was 2,206. However, during the migration setup, the system detected 5,927 WordPress users.
This issue arose because WordPress stores all users, including administrators, editors, subscribers, and customers, in the same core user table. Therefore, by default, the migration tool counted every WordPress user as a customer. It inflated the total and made it appear that John needed a 10,000-entity plan.
John was clear that only actual WooCommerce customers should be migrated. He didn’t want to migrate thousands of non-purchasing WordPress users, which was unnecessary data in the new store; moreover, it would increase costs and complicate customer management.
From the migration technical perspective, this was an advanced configuration adjustment. It required a deep understanding of WooCommerce’s internal data structure and a customized approach.
Custom migration logic to filter actual WooCommerce customers
To address the issue, the Next-Cart team analyzed how WooCommerce distinguished customers from general WordPress users. WooCommerce maintained a lookup table that tracked real customer activity, while WordPress core tables didn’t do that.
Jason worked with the team to customize the migration logic to pull customer data exclusively from the WooCommerce customer lookup table. The system then integrated the data differently, ensuring that only customers who had engaged with the store were migrated.
Once the customization was applied, the migration tool detected approximately 1,378 valid WooCommerce customers, which fit well within the 5,000-entity limit John has chosen. This approach resolved the pricing concern and, more importantly, ensured that the migration scope reflected actual business requirements.
Expanding the scope beyond customers alone
After the customer-filtering issue was resolved, John clarified that the project involved much more than user data. He would like a complete WooCommerce migration, including products, categories, orders, images, descriptions, reviews, coupons, pages, and blog posts.
In other words, this was not a partial transfer. The customer required a complete replication of the existing store on the new WooCommerce store. These requirements were actually standard for most WooCommerce migrations.
However, John had an additional request that complicated matters. He needed to preserve the existing Next-Cart URL redirects created during an earlier Magento-to-WooCommerce migration.
Meanwhile, these redirects were already live, indexed by search engines. They were essential for maintaining SEO performance. Losing them would risk broken links, traffic, and ranking drops.
How Next-Cart preserved legacy Magento redirects
In John’s case, the redirects pointed old Magento URLS to their corresponding WooCommerce pages and had been in use for years.
Because this was a WooCommerce-to-WooCommerce migration, the legacy Magento redirects did not automatically transfer with standard entity migrations. They had to be handled separately to avoid data conflicts and ensure compatibility with the new store.
It meant the migration had to be sequenced. The main data migration needed to be completed first, followed by an update process to carry over the existing redirect rules.
Handling scale and server constraints
Once all requirements were confirmed, the migration was executed with the customized customer logic. Thousands of records were successfully transferred.
But, like many real-world migrations, the process was not entirely without friction. During execution, some errors related to server overload appeared in the migration logs. This was a common challenge when processing large datasets in resource-constrained environments.
In total, 3,507 orders were successfully migrated, with 8 reported as errors. John reviewed the results carefully and confirmed that the store’s overall data integrity remained intact. Given the scale of the migration, he accepted the loss of those few orders. It was nothing when the site appeared correct and functional.
However, to reduce further strain, the Next-Cart team recommended lowering the batch size to 1. This helped minimize server load and stabilize the migration process.
Final step: Manually migrate legacy redirects
After the main migration was completed, Jason manually ran an update process to migrate the existing Next-Cart redirects to the new WooCommerce site. While this final step was performed, John was advised not to rerun the migration to prevent data conflicts.
This step ensured that old Magento URLs continued to resolve correctly and preserve the SEO value.
Once the redirect update was completed, John verified the data on the target store. He found no further issues and confirmed the migration was totally complete.
Final outcome: A successful migration with precision
The project concluded with all critical objectives migrated, specifically:
-
93 categories
-
602 products
-
71 reviews
-
2,206 customers
-
3,507 orders
-
9 coupons
-
22 blog posts
-
14 pages
As per John’s initial expectations, only genuine WooCommerce customers were migrated, while excluding unnecessary WordPress users. Also, legacy Magento redirects were fully preserved.
A small number of order errors due to server limitations were transparently communicated to the customer and totally accepted.
Finally, the new WooCommerce store was fully operational, and the ticket was successfully closed.
Client Feedback
John’s final review reflected both satisfaction and renewed confidence:
“I am very impressed with Next-Cart, and I wish to thank them for their professional service. I had a complex migration of several sites from a Magento Multi-Store environment to separate WooCommerce stores.
The process took a few months as I was developing the sites and then migrating. Next-Cart were there all the way and were very patient with me.
Their solution is excellent, I was very happy with the end result and I will gladly recommend Next-Cart to any person needing to migrate their site to a new platform.”
Final thoughts when this case study ended
Not defined by volume, this WooCommerc-to-WooCommerce migration required precision and more:
-
Understanding the difference between general WordPress users and actual WooCommerce customers
-
Customizing migration logic at the database level
-
Respecting entity limits without compromising business needs
-
Managing server constraints
-
Preserving SEO legacy redirects from a different platform
In short, the successful migration was about understanding context, history, and the long-term impact, not just about pushing data from point A to point B.
For John Guthrie and All Net Holdings, this successful migration marked a sense of confidence in a complex, evolving eCommerce ecosystem.
For Next-Cart, it reinforced a core principle: No two migrations are the same, and the best solution is built around real-world needs, not assumptions.
