← All migrations

Migration Guide

Migrate from Easify Product Options
to Product Variants.

An honest read on whether the switch fits your store, what stays the same, what changes, the concrete migration path — and the case for staying put if that's actually the right call.

The honest case

Why move from Easify Product Options?

Easify and Product Variants solve different problems entirely — Easify adds storefront-side custom options (engraving, file upload, custom dimensions); Product Variants is an admin-side bulk variant editor. Stores moving from Easify to Product Variants usually do so because they realised they need bulk catalogue editing more than storefront options — or they're composing both tools rather than swapping. The honest framing: this isn't a replacement, it's adding the missing layer.

What stays the same

  • Easify Product Options stays installed if you need storefront-side customer customisation — Product Variants doesn't replace it.
  • Your Shopify theme, products, customers, and orders are unchanged.
  • Your other Shopify Apps continue working with both tools.
  • Your existing customisation flows in Easify continue running.

What changes

  • You add admin-side bulk catalogue editing (pricing, inventory, SKUs, templates) — Easify doesn't cover this.
  • Preview-and-commit diff view for high-stakes catalogue work.
  • Reusable variant templates — apply standard SKU structure across new products.
  • Multi-location inventory editing in bulk across configured warehouses.

Migration path

The concrete steps.

  1. 1

    Install Product Variants alongside Easify

    Different problems entirely. Free tier on Product Variants. Both compose cleanly.

  2. 2

    Audit your bulk-catalogue needs

    Pricing updates? Inventory sync? SKU template reuse? Those are Product Variants jobs.

  3. 3

    Build a variant template matching your standard SKU structure

    Re-applies on new product launches; Easify's storefront options sit on top.

  4. 4

    Test the composition: Easify drives the storefront customisation UX; Product Variants edits the underlying SKU prices

    No conflicts — Easify reads from the SKU model Product Variants edits.

  5. 5

    Run both deliberately

    Easify for what customers see; Product Variants for what admins edit. Different surfaces.

When NOT to switch

If you don't need bulk catalogue editing (your catalogue is small, your pricing rarely changes, you have no SKU template reuse), don't add Product Variants for the sake of it. The combination earns its keep when your catalogue grows past the point where one-at-a-time SKU editing is practical.

FAQ

About the migration.

Going deeper

More on Product Variants.

Ready to migrate?

Free to install. Try Product Variants alongside Easify Product Options and migrate page-by-page on your timeline.