Skip to content

Migration

Bring your wholesale setup with you

Rebuilding a customer group structure by hand is the reason most stores stay on a plugin they have outgrown. The importer exists so that is not a reason.

How we handle your data

  • Preview before anything changes

    Every import runs as a dry run first and tells you exactly what it would create. Nothing is written until you confirm.

  • Safe to run twice

    The importer keeps a map of what it created. Re-running updates those records instead of duplicating them.

  • Your old plugin can stay off

    The importer reads the data where it lives — options, user meta, post meta — so the source plugin does not need to be active.

  • Nothing is written back

    It never modifies the source plugin’s data, so keeping it installed and deactivated is a perfectly good rollback plan.

  • It tells you what it could not map

    Anything with no equivalent is reported as a warning with the source record named, rather than silently dropped.

  • It is in the free plugin

    Migrating is not a Pro feature. You can move your data across and verify your pricing before you spend anything.

After the import

Two things worth doing before you switch the store over.

Check a price, then check it as the customer

Use the Price Explainer on a product you know the trade price of. It shows which rule won and which lost. Then use view-as-customer to browse the storefront as that buyer and confirm the shop, cart and checkout agree.

Read the warnings

Rule types with no direct equivalent are listed rather than approximated. There are usually only a handful, and they are quicker to re-create knowingly than to debug later.

Try it against a staging copy.

Install the free plugin, run the importer in preview mode, and see exactly what comes across before you commit to anything.

14-day money-back guarantee · 24-hour first response