**TL;DR.** Migrating from WooCommerce to Ordiko replaces your WordPress + hosting + plugin stack with a managed SaaS. Plan for catalog import (1–3 hours), redirect mapping (1 hour), and DNS cutover. Done correctly, SEO recovers in 1–4 weeks and operational cost drops 30–80%.

## Why WooCommerce merchants migrate

- TCO. Hosting + plugins + maintenance often exceeds Ordiko's flat fee.
- Performance. Plugin sprawl tanks Core Web Vitals; INP especially.
- Security. WordPress is the most-attacked CMS on the internet.
- 2026 schema. Achieving `hasMerchantReturnPolicy` on WooCommerce requires Yoast Premium + manual configuration or custom modules.
- AI search readiness. WooCommerce has no native llms.txt or Markdown twins.

## Step 1: Audit your WooCommerce surface

Catalog inventory:

```bash
# WP-CLI on the production server (read-only commands)
wp post list --post_type=product --format=csv > products_inventory.csv
wp term list product_cat --format=csv > categories.csv
wp option get yoast_seo_settings > yoast.json
```

SEO inventory:

- Yoast/Rank Math meta title and description per post (export via plugin).
- Current sitemap (`/sitemap_index.xml`).
- Active multilingual plugin (WPML, Polylang, or none) and its locale mapping.
- Active subscription plugin (WooCommerce Subscriptions, MemberPress) if any.
- Custom post types tied to commerce (testimonials, lookbooks).

Performance baseline:

- Run [PageSpeed Insights](https://pagespeed.web.dev) on home, PLP, PDP. Save the LCP/INP/CLS numbers.

## Step 2: Export the WooCommerce catalog

The default WooCommerce CSV exporter handles most cases:

1. WP Admin → Products → Export.
2. Choose: "All products", "Export all columns".
3. Download `wc-product-export.csv`.

For variable products with many variations, also export via WC Admin → Products → set view to "All", filter by `variation`, then export.

For taxonomies (categories, brands, attributes), use WP-CLI:

```bash
wp wc product_category list --format=csv > categories_export.csv
wp wc product_attribute list --format=csv > attributes.csv
```

For media, sync `/wp-content/uploads/` via SFTP.

## Step 3: Provision your Ordiko store

1. Sign up at [ordiko.shop](https://ordiko.shop).
2. Create a store: choose a slug (used for the default subdomain).
3. Configure locales (subset of 8 supported).
4. Pick an initial theme.
5. Connect your custom domain (you'll switch DNS in Step 9).

## Step 4: Import products and categories

In the Ordiko dashboard:

1. **Settings → Import → WooCommerce**.
2. Upload `wc-product-export.csv` and your media archive (zip of `/wp-content/uploads/`).
3. The importer:
   - Maps Woo variable products to Ordiko variants.
   - Preserves slugs.
   - Imports categories as Ordiko taxonomies, preserving the parent-child hierarchy.
   - Imports product images, deriving `alt` from filenames (improve later with the AI alt-text generator).
4. Monitor progress in real time; large imports (10k+ products) run as Trigger.dev background jobs and notify on completion.

## Step 5: Set up redirects

The WooCommerce → Ordiko URL conventions:

| WooCommerce              | Ordiko                |
| ------------------------ | --------------------- |
| `/product/{slug}`        | `/products/{slug}`    |
| `/product-category/{slug}` | `/categories/{slug}` |
| `/product-tag/{slug}`    | `/tags/{slug}`        |
| `/?p=123` (legacy)       | `/products/{slug}` (lookup-based) |

Configure wildcard 301s in `/seo/redirects`:

```csv
from,to,status
/product/(.*),/products/$1,301
/product-category/(.*),/categories/$1,301
/product-tag/(.*),/tags/$1,301
```

For deleted SKUs, write 410 entries. Ordiko's gone-paths layer turns those into HTTP 410 pages with vector-similarity-based recommendations.

## Step 6: Replicate SEO plugin settings

Yoast/Rank Math export their per-post meta titles and descriptions in the products CSV (Yoast columns are `yoast_wpseo_title` and `yoast_wpseo_metadesc`). The Ordiko importer reads these into the per-entity SEO editor.

2026 Product schema fields are configured once at the store level:

1. **Settings → SEO → Return Policy** (see [the Shopify migration guide](/guides/migrate-from-shopify-to-ordiko) for field reference).
2. **Settings → SEO → Shipping Policies**.
3. **Settings → SEO → AI Crawler Policy**.

These render on every PDP automatically.

## Step 7: Mirror hreflang

If you used WPML or Polylang:

1. Export the locale mapping (WPML → Tools → Export → XLIFF, or Polylang → Settings → Export).
2. Enable the matching locales in Ordiko.
3. Use `availableLocales` per-entity to flag partial translations.

## Step 8: Run parallel and QA

Run Ordiko on a subdomain (e.g. `new.example.com`) while WooCommerce continues at the production domain. QA checklist:

- [ ] Home page renders correctly.
- [ ] Category pages show paginated products.
- [ ] PDP renders with correct images, price, variants, schema (test with [Rich Results Test](https://search.google.com/test/rich-results)).
- [ ] Search returns relevant results.
- [ ] Cart and checkout work end-to-end with a test payment.
- [ ] Account login + order history loads.
- [ ] Multi-locale: each locale renders correctly with proper hreflang.

## Step 9: Cutover DNS

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

## Step 10: Monitor and recover

For 72 hours:

| Surface                                | What to do                          |
| -------------------------------------- | ----------------------------------- |
| GSC Pages → Excluded                   | Add 301s for any unexpected 404s    |
| GSC Performance → Clicks               | Confirm dip ≤ 15% then recovery     |
| Bing Webmaster → IndexNow              | Pings logged                        |
| Ordiko → SEO → Web Vitals              | LCP/INP/CLS green                   |
| Ordiko → SEO → Revalidation Events     | No errors                           |

## FAQ

**What WooCommerce plugins won't have direct equivalents in Ordiko?**
Ordiko ships subscriptions, multi-currency, advanced shipping, bookings (basic), gift cards, abandoned-cart recovery, and SEO as core features. WooCommerce extensions for unusual niches (LearnDash for LMS, BookingPress for appointments) don't have direct equivalents and may require external integrations or workflow changes.

**Can I keep my WordPress blog after migrating commerce to Ordiko?**
Yes — many merchants keep WordPress as a content CMS at /blog (subdirectory or subdomain) while Ordiko handles commerce. Configure your DNS to route /blog/* to WordPress and everything else to Ordiko. The trade-off: you maintain two stacks. Alternatively, migrate blog posts into Ordiko's MDX-based content collection for a single platform.

**How do I handle WooCommerce variable products?**
Ordiko's importer maps WooCommerce variable products to Ordiko variants with the same attribute structure (size, color, material, etc.). Each variation becomes an Ordiko variant with its own SKU, price, inventory, and optional images.

**Will I lose customer login credentials?**
Customer records import via CSV with hashed passwords. Customers receive a password-reset email on their next login attempt (WP and Ordiko use different password hash schemes). Loyalty points, store credit, and rewards-plugin data require custom mapping.