**TL;DR.** Migrating from BigCommerce to Ordiko maps cleanly because both platforms are server-rendered with similar URL conventions. The biggest decisions are channel strategy (BC channels → Ordiko export feeds), B2B feature parity, and DNS cutover sequencing.

## Why BigCommerce merchants migrate

- Revenue caps: BC plans auto-upgrade when you hit $50k / $180k / $400k.
- Multi-storefront pricing: BC requires Pro ($399/mo). Ordiko includes unlimited stores at $19/mo.
- 2026 schema: BC's Product schema lacks `hasMerchantReturnPolicy` and `shippingDetails` natively.
- AI search readiness: no native llms.txt / Markdown twins on BC.
- React-native theming vs. Stencil templates.

## Step 1: Document BigCommerce setup

Inventory:

- Number of storefronts (if on Pro/Enterprise with Multi-Storefront).
- Channels (Amazon, Facebook, eBay, POS).
- Active payment gateways.
- Current SEO config (BC SEO settings, schema apps).
- Top 500 organic landing pages from GSC.
- Active themes (per storefront if applicable).

## Step 2: Export from BigCommerce

In the BC admin:

1. **Products → Export → Bulk Edit (.csv)** — include all attributes.
2. **Customers → Export**.
3. **Orders → Export** (optional, read-only post-import).
4. **Brands → Export**.
5. For media, use the GraphQL Storefront API or REST API to download product image URLs and sync to local.

Example REST API call for image listing:

```bash
curl -H "X-Auth-Token: $BC_TOKEN" \
  "https://api.bigcommerce.com/stores/$STORE_HASH/v3/catalog/products?include=images&limit=250" \
  > products_with_images.json
```

## Step 3: Provision Ordiko stores

If you ran BC Multi-Storefront with N storefronts:

1. Create one Ordiko account.
2. Create N stores in that account.
3. Each Ordiko store gets:
   - Its own slug, custom domain, and subdomain.
   - Its own locale set.
   - Its own SEO settings, robots, llms.txt, AI crawler policy.

Cost comparison: BC Pro Multi-Storefront = $399/mo for up to 5 stores. Ordiko Growth = $49/mo for unlimited stores.

## Step 4: Import catalog

For each storefront:

1. **Settings → Import → BigCommerce** in the Ordiko dashboard.
2. Upload BC's bulk-edit CSV and media archive.
3. The importer:
   - Maps BC option sets and variants to Ordiko variants.
   - Preserves slugs.
   - Imports brands as Ordiko brands.
   - Imports category trees with parent-child relationships intact.
   - Imports product images with original filenames as `alt`.

## Step 5: Configure redirects

| BigCommerce             | Ordiko              | 301 redirect needed? |
| ----------------------- | ------------------- | -------------------- |
| `/products/{slug}/`     | `/products/{slug}`  | Yes (trailing slash) |
| `/categories/{slug}/`   | `/categories/{slug}`| Yes                  |
| `/brands/{slug}/`       | `/brands/{slug}`    | Yes                  |
| `/pages/{slug}/`        | `/pages/{slug}`     | Yes                  |

Configure a wildcard redirect to strip trailing slashes:

```csv
from,to,status
/(.*)/,/$1,301
```

For deleted SKUs, write 410 entries. Ordiko's gone-paths layer handles HTTP 410 responses with vector-similarity recommendations.

## Step 6: Channel and feed strategy

BC's channel model (Amazon, Facebook, eBay, POS) maps to Ordiko's export feeds:

| BC Channel              | Ordiko equivalent                                 |
| ----------------------- | ------------------------------------------------- |
| Amazon channel          | Google Merchant + Amazon feed export              |
| Facebook channel        | Facebook product feed (built-in)                  |
| eBay channel            | Generic XML feed                                  |
| Instagram Shopping      | Facebook catalog (shared with Instagram)          |
| BC POS                  | Ordiko POS API (custom integration required)      |
| Pinterest               | Pinterest product feed (built-in)                 |

Configure feeds at **Settings → Feeds → New feed** per channel.

## Step 7: Set up 2026 Product schema

Same as the [Shopify migration guide](/guides/migrate-from-shopify-to-ordiko):

1. **Settings → SEO → Return Policy** at the store level.
2. **Settings → SEO → Shipping Policies** at the store level.
3. **Settings → SEO → AI Crawler Policy** (default: allow GPTBot, ClaudeBot, PerplexityBot on marketing routes; disallow on cart/account/checkout).

These render automatically on every PDP.

## Step 8: Run in parallel and QA

QA checklist per storefront:

- [ ] Home renders, hero image LCP ≤ 1.8s.
- [ ] PLP shows correct products with pagination.
- [ ] PDP renders with images, price, variants, brand, schema (validate with Rich Results Test).
- [ ] Brand pages render.
- [ ] Search works.
- [ ] Cart and checkout work with test card.
- [ ] Customer login works (with password reset).
- [ ] Multi-locale renders correctly per locale.
- [ ] Sitemap accessible at `/sitemap.xml`.
- [ ] llms.txt accessible.

## Step 9: Cutover DNS

1. Lower TTL on existing DNS to 300 seconds 24 hours before cutover.
2. Change A or CNAME records to point at Ordiko.
3. Within 1 hour of propagation:
   - Submit new `/sitemap.xml` in Google Search Console.
   - Submit in Bing Webmaster Tools.
   - Submit in Yandex Webmaster.

## Step 10: Monitor

For 72 hours, watch:

| Surface                                | What to monitor                       |
| -------------------------------------- | ------------------------------------- |
| GSC Pages → Errors                     | 404s, soft-404s, redirect chains      |
| GSC Performance → Clicks/Impressions   | ≤ 15% dip then recovery               |
| Bing Webmaster → IndexNow              | Pings logged                          |
| Ordiko → SEO → Web Vitals              | LCP/INP/CLS green                     |
| Ordiko → SEO → Redirects               | Add 301s for new 404s                  |

## FAQ

**Does BigCommerce multi-storefront translate cleanly to Ordiko?**
Yes. BC's Multi-Storefront (up to 5 on Pro) maps to Ordiko's unlimited multi-store. Each BC storefront becomes an independent Ordiko store with its own catalog, theme, domain, and SEO settings. Ordiko's model is simpler because there is no shared catalog channel concept — each store owns its catalog directly.

**Will I lose BC's revenue caps but pay more elsewhere?**
No. Ordiko has no revenue caps. Plans are flat: Starter $19/mo, Growth $49, Scale $149, Enterprise custom. There are also no per-transaction platform fees. Most BC merchants on Pro ($399/mo with $400k cap) drop to Ordiko Growth or Scale and save 50–70% monthly.

**How does Ordiko handle BC's B2B Edition features?**
Ordiko's enterprise tier includes B2B-style workflows: company accounts, purchase orders, tiered pricing, quote requests, and credit-line management. Coverage is narrower than BC's mature B2B Edition; evaluate against your specific workflow if B2B is core.

**Can I import my BC GraphQL Storefront API customizations?**
BC's Storefront API and Ordiko's tRPC API are different. Frontend customizations need re-implementation in Ordiko's React Server Component model. Backend logic in BC modules transfers to Ordiko Server Actions. Most teams find the React/TypeScript implementation faster to ship than the original BC code.