URL structure differences
Compare the actual BigCommerce product, category and content URLs with the proposed Shopify paths.
Product data export
Review the product export and map its fields, options, images and custom data to the Shopify catalogue.
Redirect planning
Include existing redirects and URL variants in the inventory, then test Shopify redirect restrictions before launch.
BigCommerce stores can use customised product and category URLs, so a matching-looking Shopify path is not proof that every address will stay the same. Start with the actual store and its existing redirects.
Inventory URLs and content
Crawl the live store and save its sitemaps and redirect list. Add landing pages from Search Console and analytics, including product, category, brand and blog pages. Record parameters, old URL variants and destination pages. Compare the inventory with Shopify’s actual product, collection, blog and page URLs.
For brand or category pages with useful content, decide how that content and the relevant products will appear on Shopify. Check filtered URLs individually: a query string or filtered path may not be eligible for the native redirect you expect. Do not assume a filter on the new store produces the same URL or indexation behaviour.
Map the catalogue
Export the product data available in BigCommerce and compare it with Shopify’s product CSV format. Record how each product, SKU, variant, option, image and custom field will transfer. Identify separate work for data not covered by your chosen export or import, including any price lists or custom fields. Keep a source copy and test a representative group before importing the full catalogue.
After import, compare products and variants against the source. Check inventory, price, images, descriptions, collections and availability on the intended sales channel. Confirm any custom integrations and customer or order history separately rather than assuming they transfer with products.
Redirects and launch checks
List old URLs from a site crawl, existing redirect rules, sitemaps and Search Console. Record the closest equivalent destination for each useful URL, including pages with external links. Keep unchanged URLs where they serve the same content. For a removed page with no close replacement, return a 404 or 410 rather than sending everyone to the home page.
Shopify redirects work only when the source URL is broken, and Shopify reserves certain paths. Its documentation lists /shop among prefixes that cannot be redirected. Query strings may not work as expected, and a .html URL cannot be redirected to the same path without the extension. Check each exception before committing to launch; agree a tested solution with your hosting or technical team. An app does not automatically bypass these restrictions.
Prepare the map and import eligible redirects using Shopify’s CSV template. Test on the Shopify domain where possible, then test the original URLs on the actual domain after DNS changes. Check the HTTP response, final destination and page content, including exceptions, and retain the results. A staging test alone cannot prove how the original domain will respond.
Before launch, check products, content, internal links, titles, descriptions, canonicals, sitemap and access settings. After launch, submit the new sitemap in Search Console, inspect important URLs, monitor indexing and search traffic, and investigate unexpected errors. Test checkout and analytics with an appropriate test order. Search results can fluctuate during a move; redirects and metadata do not guarantee rankings or a recovery date.
Where to go next
- Download the full migration checklist →
- Score your migration risk before committing to a timeline →
- Estimate how long the migration will take →
- Build the redirect map properly →
- Validate analytics after migration →
Quick answer
Prepare for a Shopify migration by recording old URLs, content and tracking before making changes.
What you will do
- Know which old URLs must be protected.
- Build redirects before launch pressure starts.
- Keep metadata, analytics and Search Console evidence available after the move.
- Reduce the risk of avoidable traffic loss.
What to check first
- Crawler export for the old site and Shopify staging site.
- Google Search Console page, query and indexing exports.
- GA4 annotations and landing-page reports.
- Shopify URL redirects.
- Redirect Mapping Sheet, Migration QA Checklist and Post-Migration Monitoring Sheet.
Work through it in this order
- Crawl the current site and export all indexable URLs.
- Export Search Console pages and queries for at least the last 16 months where available.
- Tag each old URL as protect, merge, replace, retire or investigate.
- Map protected URLs to the closest Shopify destination before launch.
- Copy or improve critical titles, descriptions, headings, content blocks and internal links.
- Test redirects, canonicals, sitemap output, robots rules and tracking on staging.
- Monitor Search Console, analytics and 404 logs for four weeks after launch.
Real-world notes
- Before launch, check that each old category URL has a suitable destination. Test the redirects after launch.
- Investigate tracking, redirects and internal links alongside Search Console data when traffic changes after a migration.
- Include blog URLs in the migration inventory and check their links and search traffic.
Final checks
- Old URL crawl saved.
- Search Console export saved.
- Top landing pages mapped.
- Redirects uploaded and tested.
- Metadata for priority pages reviewed.
- Analytics and conversion tracking checked.
- Post-launch monitoring owner assigned.
Watch-outs
- If the old site has faceted URLs indexed, decide which should become Shopify collections and which should be retired.
- If products are discontinued during migration, redirect only where the replacement is genuinely useful.
- If the domain also changes, follow the site-move guidance and monitor the transition.
Download the Migration Risk Kit or request an audit if organic revenue, product count or URL complexity is high.
Field questions
Will migrating from BigCommerce to Shopify hurt SEO?
Search performance can change during a move. Map changed URLs to relevant destinations, verify the new content and monitor Search Console. No migration method guarantees rankings.
How long does a BigCommerce to Shopify migration take?
The schedule depends on the catalogue, integrations, URL mapping and testing needed. Estimate it after reviewing the actual store.
Can BigCommerce product data be imported to Shopify?
Export the product data available in your BigCommerce store, map it to Shopify’s CSV format or another supported import method, and test a representative sample before the full import.