How to Migrate from OpenCart to WooCommerce Without Losing SEO
A step-by-step OpenCart to WooCommerce migration plan: URL inventory, redirect mapping, data migration, testing, cutover and post-launch monitoring.
Migrations do not lose rankings by themselves. Careless migrations do — usually because nobody mapped the old URLs, the new templates changed canonical logic, or the site launched before the redirects were tested.
This is the process we use for OpenCart to WooCommerce moves, including the parts that happen before a line of code is written.
Phase 0: decide whether to migrate at all
A migration is expensive. Before committing, confirm that OpenCart cannot solve the actual problem. Sometimes the answer is an upgrade, a custom module and a performance sprint. If you need multilingual content workflows, a broader integration ecosystem or easier hiring, WooCommerce becomes the stronger case.
Phase 1: inventory everything
Crawl the live site
Use a crawler to collect every indexable URL: products, categories, manufacturers, information pages, blog posts, paginated listings and filter combinations that receive traffic. Export Search Console data for the last 12 months and identify URLs with impressions, clicks and backlinks.
Map data, not just pages
- Products and variations, including attributes and option values.
- Categories and their hierarchy.
- Customers, addresses and, if required, order history.
- Reviews and ratings.
- SEO metadata, descriptions and image alt text.
- URLs and their redirect destinations.
Flag the problem data early
Mixed tax display, duplicate SKUs, products with no category, images stored outside the media library, and languages stored as separate catalogues all surface during migration. Find them now, not during QA.
Phase 2: design the new architecture
Decide the URL pattern for products and categories, the taxonomy structure, and how filters will be handled. If the old URLs were keyword-rich and performing, preserve them where possible. If they were parameter URLs, build clean replacements and redirect the valuable ones.
Set canonical rules before development: paginated categories self-canonical, filtered URLs either indexable with unique content or noindexed, out-of-stock products kept live or redirected deliberately.
Phase 3: build the redirect map
Every old URL should have exactly one destination. The map should include:
- Product URL → product URL (same product).
- Product URL → category URL for discontinued items.
- Category and manufacturer URLs → equivalent new taxonomy.
- Paginated URLs → corresponding page or the category root.
- Information and blog pages → matching content.
- Filter URLs with traffic → closest useful category.
Use 301 redirects for permanent moves. Avoid redirect chains: point every old URL directly at the final destination. Test a sample of 100 redirects manually before launch.
Phase 4: migrate and test
Run the import on a staging copy with the same plugins and theme as production. Verify:
- Product counts, variations and prices match the source.
- Images load at the correct sizes and alt text is present.
- Categories contain the right products and no orphans remain.
- Customers can log in (or receive a password reset flow).
- Orders, taxes, shipping zones and payment methods work with real test transactions.
- Redirects fire correctly, with no loops or chains.
- Sitemaps generate valid URLs and exclude noindexed pages.
- Structured data validates.
Phase 5: cutover
Choose a low-traffic window. Put the old store in maintenance mode only for the DNS propagation period, not for days. Keep the old database and files available for rollback. After cutover:
- Verify HTTPS and canonical domain.
- Submit the new sitemap and remove the old one.
- Check robots.txt and that staging is not indexable.
- Test checkout end to end on mobile and desktop.
- Confirm analytics and conversion tracking fire correctly.
- Monitor server errors, 404s and redirect hits for 30 days.
Phase 6: protect what you earned
- Update internal links to final URLs.
- Update external backlinks where you control the source (directories, partner sites, profiles).
- Keep the redirect map live for at least 12 months — permanently for high-value URLs.
- Compare organic sessions, impressions and revenue weekly against the pre-migration baseline.
- Do not launch a redesign and a replatform on the same day if you can avoid it; separate the variables.
Realistic timeline
| Stage | Duration |
|---|---|
| Audit and inventory | 1–2 weeks |
| Architecture and design | 2–3 weeks |
| Data migration and build | 3–5 weeks |
| QA and redirect testing | 1–2 weeks |
| Cutover and monitoring | 30 days |
A 10-week plan for a mid-sized store is realistic. Promises of a two-week migration usually mean the redirect map is being written after launch.
Need a second opinion?
We have migrated stores from OpenCart 2.x, 3.x and 4.x with catalogues from 500 to 50,000 SKUs. Send your store URL and catalogue size and we will reply with a migration risk assessment — including what we would keep, what we would rebuild and how we would protect the URLs.