From OpenCart 3 to WooCommerce without losing search visibility
An industrial tooling distributor had outgrown OpenCart. We inventoried every indexable URL, normalised the product data and rebuilt the store on WooCommerce — with the redirect plan reviewed before cutover.
The situation
The store had run on OpenCart 3 for years. It worked, in the sense that orders arrived, but every growth decision ran into the same wall: the catalogue could not be repriced in bulk, EU VAT rules had been patched by hand for several markets, and the custom modules had no remaining developer who understood them. Organic traffic was flat but valuable — a large set of indexable URLs built up over years, including category filters, product variants and buying guides.
The team had already postponed one migration. A previous agency proposed rebuilding the site but could not explain what would happen to the old URLs. For a business that earned most of its revenue from search, that was the whole risk.
Discovery: URLs before code
We started with three exports: a full crawl of the live site, Google Search Console performance data, and the internal list of products and customers. Every indexable URL was classified as keep, redirect or retire. Filter combinations that were never linked internally and generated no impressions were marked noindex rather than redirected; pages with impressions and links received explicit redirect targets.
The product catalogue was equally uneven. Attributes had been added over the years without a naming standard: “Voltage” and “Volt.”, “Material” and “material”, sizes stored as free text in some categories and as options in others. Mapping those values before import prevented a second cleanup project after launch.
Architecture decisions
The new build kept WooCommerce as the commerce engine and replaced the front end with custom templates. Three decisions mattered most:
- Retail and trade pricing became customer groups in WooCommerce, with tax display rules per group. The old store had hidden trade prices with CSS.
- Faceted navigation was rebuilt. Useful facets stay indexable; generated combinations are canonicalised and excluded from the sitemap, which keeps low-value URLs out of the crawl budget.
- Tax logic moved into validated EU rules for the core markets, with reverse-charge handling for business customers and clear gross/net display.
Migration mechanics
Products, variations, customers, address books, historical orders, reviews, SEO metadata and blog content moved to the new database. Attribute values were normalised before import, old media was matched to new attachments by checksum, and existing alt text was preserved. Staging ran on a copy of the production database with payments in sandbox mode.
Cutover happened in a low-traffic window after a full rehearsal. We kept the old store available behind a hosts-file override for a short fallback period, monitored 404s daily, and reviewed Search Console coverage through the first month.
Cutover and after
Organic sessions recovered to the previous baseline quickly, helped by redirect coverage that had been reviewed line by line and by Product schema that had been missing entirely. The client watched the crawl reports with us for the first month.
The team can now update prices and stock in bulk without a developer, and no custom module depends on a person who has left the business. The project ended with documentation for the redirect map, the attribute scheme and the tax rules — the parts that are hardest to reconstruct later.
What we would do differently
We would start the VAT audit earlier. The source data mixed gross and net pricing in two categories, which only surfaced during test checkout. We caught it before launch, but it compressed the QA window more than we would have liked.
Ready for a store that sells while you sleep?
Send us your current site or product list. You will receive a fixed-scope proposal, a 20-point audit and a realistic timeline within two business days.