Introduction: why migration needs a careful hand

Replatforming an ecommerce store is a complex technical project at the best of times. For UK CBD retailers in 2026 it brings added layers: Certificates of Analysis (COAs) must remain discoverable for customers and compliance checks, age‑verification workflows must stay intact, and SEO gains built over months or years are fragile during a move. This guide takes a calm, practical approach: we explain the common causes of migration failures and provide a clear step‑by‑step plan to move product listings without losing COA access, age‑verification or search rankings.

Problem statement

When a CBD retailer replatforms, the chief risks are:

• Loss of search visibility because indexed URLs change or redirects are incomplete.
• Broken COA links or missing product documents that damage customer trust and third‑party checks.
• Disabled age‑verification or compliance apps that block checkout or create friction.
• Gaps in analytics, pixels or tag manager data that make it hard to compare pre‑ and post‑migration performance.

Common causes of migration failure

• Incomplete URL mapping — pages are recreated with new paths but no 301 redirect from the old, indexed URL.
• Missing metadata — titles, meta descriptions and structured data (schema) aren’t migrated, reducing click‑through and SERP presence.
• COAs treated as peripheral — certificates or lab PDFs left on the old host or not linked as product assets, causing 404s.
• Age‑verification and third‑party apps not reconnected — verification gates fail, blocking conversions.
• Lack of testing and backups — one live cutover with no rollback plan.

Solutions — step‑by‑step migration playbook

1. Pre‑migration discovery and baseline

• Export your indexed URLs from Google Search Console and combine them with a full crawl (Screaming Frog, Sitebulb or similar) to identify every product, category and content URL that must be mapped. This is a recommended SEO migration practice — don’t rely on memory.
• Create a pre‑migration baseline of organic traffic, conversions, and keyword rankings so you can compare post‑launch metrics.

2. Build a complete URL redirect map and plan 301s

For every indexed page, specify the new destination URL and implement a 301 redirect. Proper redirects can preserve an estimated 90–95% of rankings if done correctly; the mapping must be exhaustive. Store the map in a simple CSV (old_url,new_url) for import or reference.

3. Migrate products, SKUs and metadata using specialised tools

Use migration tools or platform APIs that preserve variant SKUs, images and metadata. Examples include LitExtension, Cart2Cart, Matrixify or native platform APIs. These help move products, customers and orders while keeping variant-specific data intact. Make sure titles, meta descriptions and structured data (product schema) are transferred or re-created.

4. Treat COAs as first‑class product assets

Treat Certificates of Analysis as linked product documents. Options:

• Rehost COAs on the new platform’s media library and update product links.
• Keep COAs on a dedicated secure CDN and implement redirects from old COA URLs to the new ones.
• Where PDFs will move, implement 301s from old PDF URLs to new PDF locations so bookmarks and third‑party checks keep working.

Make this part of your URL mapping — COA links count as indexed assets.

5. Run at least two full test migrations on staging

• Create a staging environment that mirrors the live store and run a complete migration twice: once to validate workflows and a second time to test fixes.
• Validate data integrity: SKUs, prices, stock, images, metadata, and linked documents like COAs.
• Keep versioned, encrypted backups of both source and target stores so you can roll back quickly if anything fails.

6. Re‑establish and test age‑verification and compliance flows

Before cutover, reconnect and validate every third‑party compliance app and age‑verification flow in staging. Test edge cases — returning customers, guest checkout, and mobile browsers. Ensure any server‑side checks, cookies or session handshakes used by vendors are properly configured for the new domain.

7. Reconnect analytics, pixels and tag managers

Reinstall or reconfigure Google Analytics, Google Tag Manager, Facebook/Meta pixels and any affiliate scripts on staging and then on production. Validate event continuity (add‑to‑cart, purchase events) so conversion data remains reliable across platforms.

8. Launch checklist and cutover

• Switch DNS only once you are confident in staging migrations.
• Deploy your 301 redirects immediately on the new host or via the CDN.
• Verify robots.txt and sitemap.xml reflect the new structure and submit the sitemap to Google Search Console.
• Communicate with customers: brief notice on website and email about a short maintenance window and reassurance that COAs and order history remain available.

9. Post‑launch monitoring

• Verify 301s by sampling the redirect map and using a crawler to confirm no 404s for old, indexed URLs.
• Crawl the new site and compare traffic and rankings with your pre‑migration baseline daily for the first two weeks, then weekly for a month.
• Watch COA links and the age‑verification funnel specifically — a single broken compliance check can block purchases and damage trust.
• Be ready to push quick fixes and iterate redirect rules if unexpected patterns arise.

Practical examples and product asset notes

Different product types require slightly different checks. For high‑strength oils or lab‑sensitive items make sure PDFs are attached to the product page and visible via the product template. For example, an oil like Wylde Natural Cold‑Pressed Drops 1000mg CBD Oil 10ml needs its batch COAs and metadata preserved intact. The same goes for treats such as Wylde CBD Gummy Bears (30 x 10mg), vape liquids like CanaVape Blue Dream Complete CBD E‑liquid 1800mg, or concentrated tinctures such as CBD Living Tincture 4500mg (0% THC). Each product should include a migrated COA link and correct product schema.

Prevention tips — keep future migrations simple

• Maintain a canonical URL strategy and avoid frequent URL renames.
• Store COAs centrally (CDN or a dedicated /docs/ host) and reference them by stable URLs.
• Document integrations, API keys and vendor accounts so age‑verification, payment and analytics tools can be reconnected quickly.
• Keep a living redirect map even after launch — retire old redirects only after traffic has dropped to near zero.

Conclusion

Replatforming a UK CBD store needn’t be disruptive. With disciplined discovery, a complete URL redirect map (implementing 301s for every indexed page), specialised migration tools, rigorous staging tests, and a clear post‑launch monitoring plan, you can preserve SEO, keep COAs accessible, and ensure age‑verification and analytics remain uninterrupted. Plan carefully, test often, keep backups encrypted and versioned, and communicate with customers — those steps will safeguard revenue and reputation through the transition.