Gatemi Store Migration FAQ and Troubleshooting

The progress bar does not move

The file is imported by a WP-Cron event once a minute, and WP-Cron only runs when somebody visits the site. On many shared hosts it is slow or switched off (DISABLE_WP_CRON without a server cron). Press Run the next batch now on WooCommerce → Store Migration — it imports the next 50 rows straight away, with the same code — and press it again as needed. For large files, ask your host for a real server cron calling wp-cron.php every minute.

Will my customers be emailed?

No. While a migration is open, WooCommerce's order and account emails and WordPress' password and new-user emails are switched off, and they come back on the moment the job finishes. This applies to both the scheduled runs and the Run the next batch now button. See How it works.

Can I run the same file again?

Yes — that is what it is for. Every record remembers its source id, so a second run updates the products, customers and coupons the first one made instead of duplicating them. Imported orders (full edition) are left untouched on a second run. Treat the first run as a rehearsal: check the result, fix the file, run it again.

Most of my Shopify rows were skipped

Shopify writes one row per variant, and only the first row of a product has a title. The others are skipped as "No name of its own — usually a variant line under the product above it." Each product is imported once, as a simple product. Variations are not imported as separate records.

My WooCommerce export starts with an invisible character

WooCommerce's own CSV exporter (and Excel's "CSV UTF-8") starts the file with an invisible byte-order mark. The plugin removes it from the first header, so the ID column is read and the rows are imported. (Versions before this fix skipped every row of such a file.)

What happens to the variations in my WooCommerce export?

A WooCommerce export lists each variation as its own row with its own name (for example Hoodie – Blue) and variation in its Type column. Those rows are skipped and counted as "A variation of the product above it"; the variable product itself is imported once, as a simple product. Variations are not imported as separate records.

Why are my products drafts?

Publish imported products straight away is off by default, because a migrated catalogue wants checking before it is for sale. Switch it on and run the file again to publish them, or publish them from Products in bulk. A product the old shop had hidden stays a draft either way.

The prices are wrong by a factor of a thousand

Check how the file writes money. The plugin reads 1.250,00 and 1,250.00 as 1250, and a single comma followed by exactly three digits (1,250) as a thousands separator. A price written 12,500 meaning twelve and a half will be read as 12500 — write it 12,50 or 12.50.

A customer already had an account on the new site

Their account is updated — billing name, email, phone, city and country, where the file has them — and never replaced. Their password, role and order history are left alone.

How do imported customers log in?

New accounts get a random password. Ask customers to use Lost your password? on the login page. The plugin sends no "set your password" email, deliberately.

Order lines are not linked to products — Full edition

A line is linked to a product only when the row's SKU matches a product already in the store. Import products first, then orders.

An order with several lines — Full edition

Every export writes an order with three products as three rows sharing its order number. The first row creates the order, with its total; each later row in the same migration adds its line to that order and is counted as updated. An order created by an earlier migration is left exactly as it is, so re-running the file adds no lines.

Does it work with HPOS?

Both editions declare compatibility with WooCommerce's order storage (HPOS). Full edition: an already-imported order is found through WooCommerce's own order query, so a second run of the same order file recognises its orders on an HPOS store and on the posts store alike, and creates nothing twice.

The uploaded file — where is it, and is it safe?

It is saved under a random name in wp-content/uploads/gmsm-imports/ (full edition) or wp-content/uploads/gmsmf-imports/ (free edition), with an empty index.html and a .htaccess that denies web access. On servers that ignore .htaccess (nginx), the random name is what keeps it private. With Delete the uploaded file when I am done with a migration on (the default), it is deleted when you press Done — clear this and start another, and on uninstall.

Moving from the free edition to the full edition

Install and activate the full edition; the free edition then stands down. Both use the same gmsm_settings option and the same _gmsm_source mark, so your settings carry over and the products and customers you already imported are recognised — re-running a product file updates them rather than duplicating them. An unfinished free-edition job is not carried over (each edition keeps its own job); finish it before switching, or start it again in the full edition.

What does uninstalling remove?

Deleting the plugin removes the current job, its uploaded file, and its cron event. The full edition also removes gmsm_settings, its licence state and its cached update data. The free edition removes gmsm_settings only when the full edition has never been licensed on the site.

Nothing that was imported is touched — no product, customer, order or coupon, and not the _gmsm_source mark on any of them, so a later migration can still recognise what is already there.

Shopping Cart
Scroll to Top