BigCommerce to Shopify: Catalogue, Custom Fields and Integrations

Direct answer: moving from BigCommerce to Shopify involves mapping both data and store functionality before choosing an import method. The platforms can deliver similar commercial outcomes through different models. Copying every field, extension and integration without reviewing its purpose can reproduce complexity that the migration was meant to eliminate.

Establish the business case before choosing a migration tool

Start by distinguishing measurable goals from assumptions. Reducing catalogue maintenance, simplifying integrations or improving theme flexibility are goals that can be tested. Statements such as “Shopify will definitely make this store faster” or “conversion rates will automatically improve” are not migration requirements or reliable forecasts.

Record why the move is being considered, which operations cannot be interrupted and what evidence would count as success. A store with several connected systems may need a compatibility assessment before anyone exports its first product.

Shopify publishes a BigCommerce migration overview covering data transfer, SEO and launch considerations. Use it to structure the investigation, but validate each step against the actual source store.

Map the catalogue, variants and custom fields

Inventory product identifiers, SKUs, option combinations, prices, inventory, images, categories and custom fields. Give every source field an explicit destination: native product attribute, purchasable variant, metafield, metaobject, collection or information deliberately retained in a separate system.

These choices depend on how the information is used. A custom field used internally by an operations team may not need to appear on a product page. A product attribute used to filter a category must instead support the intended storefront filtering experience.

Do not assume that BigCommerce categories and Shopify collections share identical behaviour or URLs. Separate the data transformation from the decisions about navigation and search.

Run a representative pilot import before attempting the entire catalogue. Reconcile product and variant counts, SKU relationships, prices, image associations and availability. Shopify's product CSV documentation describes dependencies between its fields: a successful upload alone does not demonstrate that the resulting catalogue is correct.

Decide what happens to customers, reviews and loyalty data

Customer profiles and order history require their own migration plan. Available export methods, supported import formats and the intended customer account experience must be checked independently.

Do not treat customer passwords as ordinary records that can simply be copied into a new platform. Define the first-login journey, account communication and tests for legitimate customer access.

Reviews, loyalty points and wishlists often live in particular applications rather than in the core commerce platform. Determine whether those providers support a reliable export and whether an appropriate destination exists. Where they do not, document the gap instead of promising that a standard CSV will preserve everything.

Marketing consent also needs provenance. Importing a contact record does not create permission for new marketing messages. Preserve the meaning and evidence of existing preferences in accordance with the applicable consent rules.

Audit integrations and remove unnecessary features

List every important function: discounts, catalogue feeds, B2B purchasing rules, advanced search, shipping services, ERP synchronisation, warehouse updates and automated customer messages. For each one, identify the actual business need and the current owner of its data.

Some requirements may be supported natively; others may need an app or an integration. Some existing extensions are no longer useful and should not be carried into the new store at all. Prefer a small, observable integration to several overlapping processes whose update order is unclear.

For inventory and orders, decide which system is authoritative. If an ERP sets prices or a warehouse system controls stock, define the direction of each update, failure handling and reconciliation rules before launch.

A feature inventory should test behaviours, not merely compare app names. The old extension's code does not have to survive; the necessary merchant or customer outcome does.

Preserve relevant URLs and search continuity

BigCommerce and Shopify may use different routes for products, categories, editorial content and other pages. Export an inventory of valuable existing URLs, especially those with organic visibility, incoming links or important internal references.

For each priority URL, assign a relevant destination and record the expected response. Test permanent redirects, unexpected 404s, redirect chains, canonical links, internal navigation and sitemap entries. A redirect to an unrelated homepage is not a substitute for a meaningful destination.

Google Search Central's site-move documentation recommends planning URL mappings and monitoring the old and new sites during a move. The Shopify migration URL testing guide explains how to turn that mapping into test cases.

Test the complete purchasing journey

A catalogue that looks complete inside the admin is not enough. Test search, filters, product pages, variant selection, promotions, taxes, shipping rates, checkout, payment, confirmation messages, customer accounts and refund workflows.

At least one end-to-end test order should reach every essential downstream system, including fulfilment or warehouse software where applicable. Include negative cases such as a failed synchronisation, an unavailable variant or a promotional rule that should not apply.

A checkout misconfiguration can prevent orders even if the import report is entirely green. Acceptance must cover what a customer can actually buy, not just what the system claims to have imported.

Build a keep, replace, redesign or remove register

The migration should produce a decision record for each business-critical capability rather than an automatic list of equivalent apps.

BigCommerce capability Target behaviour to test Possible decision
Filtering by a custom product field Appropriate Shopify collection and filter results Redesign
Recurring discount rule Correct eligibility, dates and calculation Keep or replace
Custom transactional email Correct trigger, content and delivery Replace
Order export to a warehouse Reliable transmission and recovery on failure Keep the outcome
Unused legacy extension No necessary business process is lost Remove

Each row needs an owner, an acceptance test and an explicit result. “Keep” means preserving the required behaviour, not replicating the implementation line for line.

A regression that catalogue checks will miss

Consider a hypothetical BigCommerce store that labels certain orders for an external logistics platform. After the migration, products, totals and checkout might all look correct while those orders never reach the warehouse.

Testing only product records cannot detect that failure. Follow a sample order all the way to the receiving system, inspect its status and verify what happens when the first transmission fails. The same principle applies to finance exports, fraud controls and customer notifications.

These are illustrative scenarios, not case studies or claims about a client project.

Monitor operations after switching platforms

After go-live, compare 404 errors, redirect behaviour, product data, feed health, stock movements, orders and analytics anomalies against a recorded pre-migration baseline. Keep an issue register with severity, owner and resolution status.

The product and variant migration guide covers detailed catalogue reconciliation. For a source-specific feasibility review, the Shopify migration service is delivered directly by Francesco Guiducci.

The best migration is not the one that reproduces the greatest number of BigCommerce settings. It is the one that preserves necessary customer and operational behaviours, removes avoidable complexity and passes explicit tests before and after launch.

Sources cited in this article

Official documentation and external references linked in the text. Shopify features change: always check against the current version.

Topic: Migrations and platform choice · BigCommerce migration, custom fields, ecommerce integrations

How to cite this article

Guiducci, F. (2026). BigCommerce to Shopify: Catalogue, Custom Fields and Integrations. IFG Digital. Last updated 16 November 2026. https://ifgdigital.com/en/ifgwebdesign/ecommerce/blog/bigcommerce-to-shopify-migration-data-apps-integrations/

With your consent, Google Analytics 4 measures visits and interactions. With both categories enabled, it also uses Google click identifiers to attribute requests to Google Ads. Marketing also enables Meta Pixel for page views and WhatsApp clicks. Google and Meta do not receive form entries, messages or contact details. Google remarketing and ad personalisation stay off. You can refuse or withdraw from the footer. With Marketing enabled, the OpenAI pixel measures visits and may detect contact details from forms and send them as hashes with advertising identifiers.