shopper / migrator

v1.0.0 2026-10-23 06:54 UTC

Requires

• php: ^8.3
• shopper/framework: ^3.0.0-rc.4
• spatie/laravel-package-tools: ^1.15

Requires (Dev)

• larastan/larastan: ^3.10
• laravel/pint: ^1.29
• mockery/mockery: ^1.6
• nunomaduro/collision: ^8.6
• orchestra/testbench: ^10.0|^11.0
• pestphp/pest: ^4.4
• pestphp/pest-plugin-laravel: ^4.1
• pestphp/pest-plugin-livewire: ^4.0

MIT

• Arthur Monney

• migration
• laravel
• e-commerce
• Shopper

Published on Packagist.org on 2026-10-23 07:14 UTC

README

Migrate your store from other e-commerce platforms to Shopper. The first supported source is WooCommerce, through its REST API: products, variations, options, categories, tags, images, prices and stock are imported into Shopper using the product import pipeline.

Installation

composer require shopper/migrator

Register the addon in your AppServiceProvider::register():

use Shopper\Facades\Shopper;
use Shopper\Migrator\MigratorAddon;

public function register(): void
{
    Shopper::addon(new MigratorAddon);
}

Then run the installer to apply the migrations and create the migrator.* permissions (they are granted to the administrator role):

php artisan shopper:migrator:install

The WooCommerce source then appears in the import modal on the products page, for any admin holding the migrator.create permission.

WooCommerce credentials

Generate read-only API keys in your WooCommerce admin under WooCommerce > Settings > Advanced > REST API, then paste the store URL, consumer key and consumer secret in the import panel. The store must be served over HTTPS.

By default the migrator refuses non-HTTPS store URLs and hosts on private/loopback networks (SSRF protection). For local development against a store on your own machine, allow it and skip certificate verification:

MIGRATOR_ALLOW_LOCAL_HOSTS=true
MIGRATOR_VERIFY_SSL=false

MIGRATOR_VERIFY_SSL is ignored in production — TLS verification is always enforced there.

Idempotency

Migrations are idempotent: products are matched by slug and variants by SKU, so running the migration again updates existing records instead of duplicating them.