GraftportPlatformsPricingGuidesLog inBook a call

Platform migrations

BigCommerce to Shopify, redirects in place from day one.

Move products, customers and order history off BigCommerce. Built for stores that have outgrown BC's storefront limits.

MagentoShopifyBigCommerceWooCommerce
Book a migration reviewHave an invitation code?

What comes across

01
Products & variants
Including BC's complex options, flattened to Shopify variants and metafields
02
Categories to collections
Tree preserved as nested smart collections
03
Customers
Profile, address book, customer groups mapped to tags
04
Orders
Full history with payment and shipping breakdowns
05
Gift cards
Outstanding balances move across as Shopify gift cards
06
301 redirects
Every old BC URL preserved as a redirect
07
Pages
Static pages and web content intact

Where this one gets sharp

The things that catch teams out on this platform, said plainly before you sign anything.

Options vs variants

BC's product options are richer than Shopify variants. We flatten what we can and store the rest as metafields, with a per-product report of what changed.

Bulk pricing rules

BC's tiered customer pricing maps to Shopify volume discounts where possible. Anything more bespoke needs an app on the destination side.

API token, not admin login

Connect via a BC store API token with read access. No need to share an admin password.

Channels are not Markets

Regional storefronts map to Shopify Markets. Separate sales channels like Amazon need re-setting up natively.

FAQ

BigCommerce questions.

Something not covered? hello@graftport.com reaches a person, not a queue.

Will my BC channels become Shopify Markets?

Where the channel is just a regional storefront, yes. Where it's a separate sales channel like Amazon, those need to be re-set up natively in Shopify, with the catalogue we migrate.

What about BC subscriptions?

BC's subscription product needs replacing with a Shopify subscription app. The customer and order data we migrate is compatible, but the subscription engine itself is not portable.

Can I re-run a migration without creating duplicates?

Yes. Every record is tracked by its source identity, so anything already loaded is skipped on the next run. Re-run on go-live night without a single duplicate ending up in your store.

What happens if a mapping is wrong?

Re-edit the mapping, dry-run it, then re-load. Mappings are versioned, so you can revert to any prior version with one click.

Where does my data live?

EU-hosted infrastructure with strict access boundaries per account. Source store credentials are encrypted at rest, and we wipe everything cleanly on request.

How does pricing actually work?

Pricing is quoted case by case so the plan matches the source platforms, brand count, and re-run cadence of your migration. Tell us what you're moving on the pricing page and we'll come back with numbers within one business day.

Outgrown BigCommerce?

Twenty minutes, your data, an honest answer about scope and timeline.

Book a call