Import Products BigCommerce to Shopify: CSV vs App Migration (2026)

A stalled migration costs money every single day it drags on. When you import products BigCommerce to Shopify the wrong way, you don’t just lose a weekend, you lose SEO equity, break variant mappings, orphan hundreds of images, and hand your competitors a two-week head start while your team firefights broken redirects. We’ve watched merchants burn $8,000 to $15,000 in agency rework because someone chose the fast path over the correct one. This comparison exists so you don’t repeat that mistake.

TL;DR

• CSV IMPORT: The manual, free, format-driven route. Best for catalogs under roughly 500 SKUs where you control the data and can tolerate 8 to 20 hours of hands-on cleanup. Zero recurring cost, maximum control, steep effort curve.
• MIGRATION APPS: Automated tools like Matrixify, LitExtension, or Cart2Cart that move products, variants, images, and often customers and orders in one pass. Best for 500 to 50,000+ SKUs. Costs $60 to $600+ depending on volume, but saves 20 to 60 hours and slashes error rates.
• THE REAL DECISION: It is not “which is better,” it is “which matches your catalog size, data hygiene, and tolerance for manual work.” We map both to specific use cases below so you can choose in under ten minutes.

Why Migrating From BigCommerce to Shopify Is Trickier Than It Looks

On paper, moving a store between two mature platforms should be a solved problem. In practice, the two systems model products differently enough that a naive export-import destroys data. BigCommerce treats product options, variants, and custom fields in a structure that does not map one-to-one onto Shopify’s variant and metafield model. That mismatch is where most migrations quietly break.

At Presta, we’ve run this migration for merchants ranging from a 120-SKU apparel boutique to a 34,000-SKU industrial parts distributor, and the pattern is consistent: the products themselves migrate fine, but the relationships around them (variant pricing, image-to-variant links, SEO handles, category-to-collection mapping, and 301 redirects) are where 80% of the labor lives. If you only budget for “moving products,” you underscope the project by a factor of three.

There is also a hard limit worth naming early. Shopify caps products at 100 variants each and 3 options per product by default. BigCommerce is more permissive. If your catalog uses 4+ option sets or products with 150+ variant combinations, no import method fixes that automatically. You will need to restructure the catalog or deploy a variant app, and that decision has to happen before you import a single row.

• CATALOG AUDIT: Count total SKUs, max variants per product, and number of option sets before choosing any method.
• VARIANT CEILING: Confirm no product exceeds Shopify’s 100-variant, 3-option limit, or plan a workaround first.
• SEO INVENTORY: Export every BigCommerce product URL now so you can build a redirect map later.
• IMAGE DEPENDENCIES: Note which images are variant-specific versus product-level; this breaks most often.
• DATA HYGIENE: Flag duplicate SKUs, empty descriptions, and orphaned images while you can still fix them at the source.

CSV Import vs Migration App: The Comparison Table

Before we go deep on each method, here is the head-to-head at a glance. We built this table from the numbers we see across real client projects, not vendor marketing pages.

Criteria	CSV Import	Migration App
Upfront cost	$0 (built into Shopify)	$60 to $600+ per migration
Realistic time investment	8 to 20 hrs for 500 SKUs	2 to 6 hrs of setup + processing
Best catalog size	Under 500 SKUs	500 to 50,000+ SKUs
Variant / image fidelity	Manual, error-prone	High, largely automated
Learning curve	Moderate to steep	Low to moderate
Migrates orders / customers	No (products only)	Yes, on most apps
Rollback / re-run safety	Manual re-upload	One-click re-run on many apps
Ongoing sync capability	None	Available on premium tiers

Read that table as a decision map, not a scoreboard. Neither column “wins.” A 200-SKU merchant with clean data who enjoys spreadsheets will be perfectly happy in the left column. A 12,000-SKU merchant with variant-heavy products who needs orders and customers moved too has effectively no choice but the right column.

The CSV Import Method: Full Control at the Cost of Your Time

The CSV route is Shopify’s native product import. You export your BigCommerce catalog to a CSV, reformat it to match Shopify’s required column headers, then upload it through Settings, Import, or the Products page. It is free, it is transparent, and it teaches you exactly how Shopify structures data, which pays dividends for years afterward.

The catch is the reformatting. BigCommerce and Shopify use entirely different column names, variant row structures, and image conventions. A BigCommerce export will not import into Shopify as-is. You are effectively translating one spreadsheet dialect into another, and the translation rules are unforgiving: one misaligned Handle column and your variants scatter across duplicate product listings.

What format do I need to import BigCommerce products?

Shopify expects a UTF-8 encoded CSV with a specific header row. The non-negotiable columns are Handle, Title, Body (HTML), Vendor, Type, Tags, Published, Option1 Name, Option1 Value, Variant SKU, Variant Price, Variant Inventory Qty, and Image Src. The Handle column is the spine of the whole file: every variant of a product shares the same Handle, with the first row carrying the full product data and subsequent rows carrying only the variant and image differences.

Here is the mapping that trips up most people, laid out plainly:

BigCommerce field	Shopify CSV column	Common gotcha
Product Name	Title	Only on the first row per Handle
Product Description	Body (HTML)	Strip BigCommerce-specific HTML classes
Product URL slug	Handle	Must be lowercase, hyphenated, unique
Brand	Vendor	Empty in many BC exports; backfill it
Option sets	Option1/2/3 Name + Value	Max 3 options in Shopify
Variant image	Image Src + Variant Image	Repeat Handle on a new row per image
Search keywords	Tags	Comma-separated inside one cell

At Presta, we keep a reusable BigCommerce-to-Shopify column mapping template that we adapt per client, because doing this from scratch every time is how mistakes creep in. If you are going the CSV route solo, build your own template once and reuse it. The first product family you map correctly becomes the pattern for the other 499.

Advantages:

• COST: Genuinely free; no app fees, no per-SKU pricing, no subscription.
• CONTROL: You see and touch every field, so you catch data problems you would never notice in an automated pass.
• LEARNING: You come out understanding Shopify’s data model, which speeds up every future bulk edit.
• PORTABILITY: The cleaned CSV becomes a reusable backup and a re-import safety net.

Limitations:

• TIME: Expect 8 to 20 hours for 500 SKUs; it scales linearly and brutally past that.
• ERROR SURFACE: Manual mapping means variant scatter, broken images, and encoding issues are common on the first pass.
• SCOPE: Products only. Orders, customers, and historical data need a separate solution.

Can I bulk import BigCommerce products to Shopify?

Yes, and this is the single most common question we get, so let’s answer it directly. Bulk import is exactly what the CSV method does: one file can carry thousands of products and tens of thousands of variant rows in a single upload. Shopify’s native importer handles files up to 15 MB, and for larger catalogs you split the file or use an app like Matrixify that removes the size ceiling entirely.

The word “bulk” fools people into thinking it is effortless. Bulk refers to volume, not automation. A bulk CSV import still requires that every one of those thousands of rows is formatted correctly before upload. Get the format right and 10,000 products land in fifteen minutes of processing. Get it wrong and you spend two days untangling duplicate listings. The bottleneck is never the upload, it is the preparation.

• FILE SIZE: Native Shopify import caps at 15 MB; split larger files or use an app.
• CHUNKING: Import in batches of 1,000 to 2,000 rows so errors are easy to isolate.
• DRY RUN: Always test with a 10-product sample file before the full push.
• VALIDATION: Check variant counts and image counts against your source before going live.

The Migration App Method: Automation That Buys Back Your Weekend

Migration apps sit between your two stores and move data through APIs rather than files. You connect BigCommerce as the source and Shopify as the target, select what to migrate (products, variants, images, categories, customers, orders, reviews), and the tool handles the field mapping automatically. The leading names are Matrixify (formerly Excelify), LitExtension, and Cart2Cart, each with a slightly different sweet spot.

The value proposition is straightforward: you are paying $60 to $600 to avoid 20 to 60 hours of manual spreadsheet labor and the error rate that comes with it. For any business where founder or team time is worth more than $15 an hour (which is every business), the math favors automation once you cross a few hundred SKUs. Our Startup Studio team frequently builds migration plans where the app cost is a rounding error next to the value of launching two weeks sooner.

The trade-off is trust and validation. An automated tool moves data faster than you can inspect it, which means a bad mapping propagates across your entire catalog before you notice. This is why we treat every app migration as a two-phase job: a small test migration to verify field mapping, then the full run only after we’ve confirmed the sample migrated cleanly.

App	Typical price range	Standout strength	Watch-out
Matrixify	$20 to $200/mo	Excel-level control, handles metafields, huge files	Steeper learning curve; export/import model
LitExtension	$69 to $600 one-time	Full data types, done-for-you options	Per-migration pricing scales with volume
Cart2Cart	$69 to $500+	Fast automated wizard, good support	Add-ons for SEO/redirects cost extra

Advantages:

• SPEED: Cuts a 40-hour manual job to 4 to 6 hours of setup plus unattended processing.
• SCOPE: Moves orders, customers, reviews, and categories, not just products.
• FIDELITY: Automated field mapping preserves variant and image relationships that break in manual CSVs.
• RE-RUNS: Most tools let you re-run or do delta migrations, so last-minute source changes are recoverable.

Limitations:

• COST: $60 to $600+ per migration, more for very large or complex catalogs.
• BLIND SPOTS: Automation can propagate a mapping error across every product before you catch it.
• LIMITS PERSIST: No app fixes Shopify’s 100-variant, 3-option ceiling; that is still on you.

The upload was never the hard part; the preparation and validation are where every successful migration is actually won.

Boost Your Migration Without Betting the Store

If your catalog is large, variant-heavy, or carrying years of SEO equity you cannot afford to lose, this is exactly the kind of project where a specialist pays for itself in the first week. Our Startup Studio has run BigCommerce to Shopify migrations end to end, from data mapping and redirect strategy to launch-day QA, and we routinely compress a two-month DIY timeline into two to three weeks with zero ranking loss. If you want the migration done right the first time instead of reworked the third time, talk to Presta’s Startup Studio team and we’ll scope it against your actual catalog.

How Do I Import Products From BigCommerce to Shopify: The 4-Step CLEAN Migration Framework

Regardless of which method you pick, the sequence of work is the same. We run every migration through what we internally call the CLEAN framework, because the name captures the single most important truth: clean data in equals clean store out. Here is the four-step version we hand to clients.

Step 1, CATALOG. Export everything from BigCommerce and audit it. Count SKUs, flag products exceeding Shopify’s variant ceiling, list every product URL for the redirect map, and identify duplicate or empty records. Do not skip this; it is the step that determines whether the next three go smoothly. We budget 2 to 5 hours here for a mid-sized catalog, and it saves 10x that downstream.

Step 2, LAYOUT. Decide your data model in Shopify before importing. Map BigCommerce option sets to Shopify Option1/2/3, plan which custom fields become metafields, and decide how BigCommerce categories become Shopify collections (manual for curated feel, automated for rule-based scale). This is a decision step, not a doing step, and it prevents the most expensive class of rework.

Step 3, EXECUTE. Run the import. For CSV, upload a 10-product test file, verify, then push the full file in batches. For an app, run a small test migration, validate the sample against your source, then trigger the full run. Either way, never go straight to a full production import without a tested sample first.

Step 4, AUTHENTICATE and NAVIGATE. Validate everything, then handle SEO. Spot-check 30 to 50 products for variant accuracy, image mapping, and pricing. Then build and deploy 301 redirects from every old BigCommerce URL to its new Shopify equivalent. Missing redirects is the number one cause of post-migration traffic loss, and we’ve seen it wipe out 40% of organic sessions within two weeks when neglected.

• STEP 1 CATALOG: Export, count, and flag every data problem at the source.
• STEP 2 LAYOUT: Map options, metafields, and collections before touching Shopify.
• STEP 3 EXECUTE: Test with a sample, then batch-import the full catalog.
• STEP 4 AUTHENTICATE/NAVIGATE: QA a product sample and deploy 301 redirects on day one.

Which Should You Choose: A Decision Framework

The choice comes down to four variables: catalog size, data cleanliness, whether you need orders and customers moved, and how you value your time. Here is how we map real situations to a recommendation.

Choose CSV import if you have fewer than roughly 500 SKUs, your data is already clean, you only need products moved, and you have (or want to build) spreadsheet fluency. A solo founder migrating a 150-SKU store on a bootstrap budget is the textbook CSV candidate. You will spend a weekend, learn the platform deeply, and pay nothing.

Choose a migration app if you have 500+ SKUs, need orders or customers migrated, have variant-heavy or messy data, or simply cannot afford to lose a week to manual labor. A growing brand with 4,000 SKUs and three years of order history has no realistic path through a manual CSV; the app cost is trivial next to the alternative.

Choose a hybrid (this is what we most often do for clients) when your catalog is large but your data is messy. Use an app for the heavy automated lift, then use targeted CSV edits to fix the fields the app could not map cleanly, especially metafields and variant images. This captures the speed of automation and the precision of manual control.

Your situation	Recommended method	Why
Under 300 SKUs, clean data, tight budget	CSV import	Free, fast enough, teaches the platform
300 to 1,000 SKUs, some mess	Hybrid	App for volume, CSV to fix edge cases
1,000+ SKUs, orders + customers needed	Migration app	Only realistic path at that scale
Variant-heavy catalog (100+ variants/product)	App + restructuring	Automation plus manual variant planning
No internal tech capacity, revenue-critical	Agency-led migration	De-risks SEO and launch timing

• SIZE CHECK: Under 500 SKUs leans CSV; over 500 leans app.
• SCOPE CHECK: Need orders or customers? App, always.
• DATA CHECK: Messy source data favors a hybrid approach.
• RISK CHECK: Revenue-critical store with SEO equity favors expert help.
• BUDGET CHECK: Zero budget and time to spare favors CSV.

Measuring Success: 30/60/90 Day KPIs

A migration is not “done” the day the store goes live. It is done when your metrics prove you lost nothing and gained something. We track migrations on a 30/60/90 day cadence, and we tell clients up front what healthy numbers look like so they can spot trouble early.

By day 30, the priority is stability and parity. You want organic traffic within 10% of pre-migration levels (a temporary dip is normal), 100% of high-value URLs returning valid 301 redirects, and zero critical product data errors in your top 100 SKUs. If organic traffic drops more than 20%, it is almost always a redirect or indexing problem, and it is fixable if you catch it now.

By day 60, you want recovery and refinement. Organic traffic should be back to baseline or climbing, Google Search Console should show old URLs dropping out and new ones getting indexed, and conversion rate should match or beat the old store as Shopify’s faster checkout kicks in. We routinely see a 5% to 15% conversion lift on Shopify simply from a smoother checkout, which often offsets any migration cost within the first quarter.

By day 90, you want compounding gains. Organic traffic above the old baseline, page-speed scores improved (Shopify’s CDN and theme structure usually help here), and the operational time savings from Shopify’s admin starting to show up as fewer hours spent on catalog maintenance. This is where the migration stops being a cost and starts being an investment.

Timeframe	Primary KPI	Healthy target
Day 30	Redirect coverage	100% of top URLs return 301s
Day 30	Organic traffic	Within 10% of baseline
Day 60	Organic recovery	Back to or above baseline
Day 60	Conversion rate	Match or +5% to +15%
Day 90	Page speed	Improved vs old store
Day 90	Admin time saved	Fewer maintenance hours logged

• TRACK EARLY: Baseline your traffic and conversion before you migrate, not after.
• WATCH REDIRECTS: Redirect coverage is the single strongest predictor of retained SEO.
• MONITOR INDEXING: Use Search Console to confirm old URLs fall out and new ones rise.
• MEASURE CONVERSION: A Shopify checkout usually lifts conversion; verify it did.
• REPORT AT 90: Only call the migration complete once 90-day numbers hold.

Common Migration Mistakes We See (and How to Avoid Them)

We’ve been called in to fix enough botched migrations to catalog the recurring failure modes. Every one of these is preventable with the CLEAN framework above, and every one is expensive to fix after launch.

The most damaging is skipping redirects. Merchants launch, celebrate, and forget that every old BigCommerce URL is now a 404 to Google and to every backlink pointing at the old store. A disciplined, systematic approach to catching these issues before launch, the kind we describe in our writeup on a systematic approach to debugging, turns launch day from a scramble into a checklist.

The second is ignoring the variant ceiling until import time. If you discover mid-migration that 40 products exceed Shopify’s 100-variant limit, you now have a data restructuring project blocking your launch. Catch it in the Catalog step. The third is trusting an automated migration without validating a sample, which lets a single bad field mapping corrupt an entire catalog silently.

• REDIRECTS FIRST: Build the 301 map during audit, deploy it on launch day, never after.
• VARIANT LIMITS: Flag every over-limit product before importing, not during.
• SAMPLE VALIDATION: Verify a 30 to 50 product sample before trusting any full import.
• IMAGE MAPPING: Confirm variant-specific images survived; this breaks silently.
• METAFIELD PLAN: Decide the metafield structure before import or lose custom data.

Final Verdict Table

Here is the head-to-head resolved criterion by criterion, so you can see exactly where each method actually wins.

Criterion	Winner
Upfront cost	CSV Import
Speed for large catalogs	Migration App
Data fidelity at scale	Migration App
Control and learning	CSV Import
Moving orders and customers	Migration App
Best for under 300 SKUs	CSV Import
Best for 1,000+ SKUs	Migration App
Re-run and rollback safety	Migration App
Lowest error rate	Migration App

The honest verdict: migration apps win more rows, but that does not make them the universal answer. For a small, clean, products-only catalog, CSV import is the smarter, cheaper choice and the better learning investment. For anything at scale, variant-heavy, or carrying orders and SEO equity you cannot afford to risk, a migration app (often augmented with targeted CSV cleanup) is the responsible path. The worst choice is picking either one before you have done the Catalog audit, because that audit is what tells you which column you actually belong in.

If you are just getting started with a small store and clean data, prioritize learning the Shopify CSV format first: build one correct product family, then replicate the pattern, and you will not need to spend a cent. If instead you are auditing a large or revenue-critical store that already exists, prioritize your redirect map and variant-ceiling audit before you touch any import tool, because those two items cause the most expensive and hardest-to-reverse damage. In both cases, baseline your traffic and conversion numbers before you migrate so you can prove the outcome afterward.

Next Steps:

• AUDIT NOW: Export your BigCommerce catalog and count SKUs, max variants, and total URLs today.
• BUILD THE MAP: Draft your 301 redirect map from every old product URL before choosing a method.
• TEST SMALL: Run a 10-product sample through your chosen method before committing to the full catalog.

Frequently Asked Questions

How do I import products from BigCommerce to Shopify?

You export your product catalog from BigCommerce, then bring it into Shopify through one of two routes: a formatted CSV upload or a migration app. The CSV route means exporting from BigCommerce, reformatting the file to match Shopify’s exact column headers (Handle, Title, Variant SKU, Image Src, and so on), and uploading it through Shopify’s Products import screen. The app route means connecting both stores through a tool like Matrixify or LitExtension and letting it handle the field mapping automatically.

Whichever route you choose, the actual import is the easy part. The work that determines success happens before and after: auditing your data, mapping your options and categories, testing a small sample, and deploying redirects. We always run clients through the CLEAN framework (Catalog, Layout, Execute, Authenticate/Navigate) so nothing gets skipped, because the failures we get called in to fix almost always trace back to a step someone rushed.

Can I bulk import BigCommerce products to Shopify?

Yes. Bulk import is the standard way to move a catalog, and it is exactly what both methods do. A single CSV can carry thousands of products and tens of thousands of variant rows, and Shopify’s native importer processes files up to 15 MB. For larger catalogs, you either split the file into batches or use an app that removes the size limit.

The important caveat is that “bulk” describes the volume, not the effort. A bulk import still requires that every row is formatted correctly before you upload it. The upload of 10,000 products takes minutes; the preparation of those 10,000 rows takes the real time. We recommend importing in batches of 1,000 to 2,000 rows so that if something goes wrong, you can isolate the problem to one batch instead of untangling the whole catalog.

What format do I need to import BigCommerce products?

Shopify requires a UTF-8 encoded CSV file with a specific header row. The critical columns are Handle, Title, Body (HTML), Vendor, Type, Tags, Published, the Option Name and Value columns, Variant SKU, Variant Price, Variant Inventory Qty, and Image Src. The Handle column is the most important concept to understand: it is the unique identifier that ties all of a product’s variants and images together. Every variant row of the same product shares one Handle.

A raw BigCommerce export will not match this format, so you must translate it. BigCommerce uses different column names and a different variant structure, so the reformatting is the real task. We keep a reusable mapping template that converts BigCommerce fields into Shopify columns, and if you are doing this yourself, building your own template once and reusing it is far safer than mapping ad hoc each time.

Will I lose my SEO rankings when I migrate?

Only if you skip the redirects. The single biggest cause of traffic loss during a BigCommerce to Shopify migration is failing to redirect old product and category URLs to their new Shopify equivalents. Without 301 redirects, every old URL becomes a 404, and both Google and any external backlinks lose their target. We have seen neglected redirects wipe out 40% of organic sessions within two weeks.

Done correctly, migration should be SEO-neutral or even positive. Shopify’s faster page loads and cleaner theme structure often improve rankings over the following quarter. The formula is simple: map every old URL to a new one, deploy the redirects on launch day, and monitor Google Search Console for the first 90 days to confirm old URLs drop out and new ones get indexed. Get that right and you keep every bit of equity you built on BigCommerce.

How long does a BigCommerce to Shopify migration take?

It depends heavily on catalog size and method. A manual CSV migration of 500 clean SKUs typically takes 8 to 20 hours of hands-on work spread over a few days. An app-based migration of the same catalog might take 2 to 6 hours of setup plus unattended processing time. Large, complex, or messy catalogs stretch further, and if orders, customers, and reviews are in scope, add more.

The timeline that surprises people is the audit and validation phase, which happens outside the import itself. Auditing a mid-sized catalog and building a redirect map is 5 to 10 hours of work, and post-launch QA is another few. When we scope full migrations for clients through our Startup Studio, we usually deliver a revenue-critical store end to end in two to three weeks, which compresses what a DIY team often stretches into two months.

When does it make sense to bring in Presta’s Startup Studio for a migration?

Candidly, not every migration needs an agency. If you have a small, clean, products-only catalog and a free weekend, do it yourself with the CSV method. You will save money and learn the platform, and the risk is genuinely low. Hiring help for a 150-SKU store would be overkill, and we will tell you that plainly.

The threshold where it becomes worth bringing us in is when three factors stack: scale (1,000+ SKUs or complex variants), risk (meaningful organic traffic and revenue you cannot afford to interrupt), and scope (orders, customers, and years of history that must move cleanly). At that point the cost of a botched migration, in lost rankings, broken data, and internal time, dwarfs the cost of expert help. As we’ve written about in our take on why you should hire an experienced agency, the value is not just execution speed, it is the mistakes we prevent before they happen. When a stalled migration costs you sales every day, expert help pays for itself fast.

What about migrating orders and customer data, not just products?

The CSV method handles products only. If you need order history, customer records, reviews, or blog content moved, the native CSV route will not do it, and you will need a migration app or custom work. This is one of the clearest deciding factors in the whole comparison: the moment orders and customers are in scope, an app (or agency-led migration) becomes the practical choice.

Migration apps like LitExtension and Cart2Cart move these data types as part of their standard packages, though pricing scales with volume. Be careful with customer data specifically: Shopify handles passwords differently, so customers usually need to reset passwords after migration regardless of method, and you should plan a communication to your list about the transition so it does not feel like a security scare.

Should I migrate my collections and categories manually or automatically?

It depends on how curated your merchandising is. If your BigCommerce categories are simple and rule-based (all products of a type grouped together), Shopify’s automated collections can recreate them with rules and save you significant time. If your categories are hand-curated with specific products chosen and ordered deliberately, manual collections preserve that intent better, though they take more effort.

Our usual approach is a hybrid: use automated collections for the broad, rule-based groupings and build the handful of hero or curated collections manually. This mirrors how we approach most catalog-structure decisions, weighing the effort of manual control against the speed of automation, the same discipline we bring to structuring a new store’s data model during a new website build. Decide this during the Layout step of the framework, before you import, because restructuring collections after the fact is tedious.

Sources

• Shopify: Importing products with a CSV file
• Shopify: Format your product CSV file
• Shopify: URL redirects and SEO
• BigCommerce: Exporting products
• Matrixify: BigCommerce to Shopify migration
• Google Search Central: Site moves with URL changes
• Presta: Why you should hire an experienced agency
• Presta: A systematic approach to debugging
• Presta: Hire the Startup Studio to launch and scale