Gatemi Store Migration Accepted CSV Columns

Each source has a column map: for every field the plugin writes, a list of headers it will accept, tried in order. The first of them that is present and not empty on a row is used. Headers match ignoring case and spaces around them, so variant price and Variant Price both work.

Columns not listed here are ignored. A file does not need every column — only the one that identifies the record (marked identifies).

The file must be comma-separated, with one header row first. Quoted cells may contain commas and line breaks; there is no backslash escape (RFC 4180).

Shopify CSV export

Products

Field Headers read Notes
Source id (identifies) Handle Stored as shopify:<handle>
Name Title A row with no title is a variant line and is skipped
Description Body (HTML), Body HTML
SKU Variant SKU Set only when present
Regular price Variant Price
Sale price Variant Compare At Price Set only when above 0 and below the regular price
Stock Variant Inventory Qty Turns on stock management
Categories Type, Product Category Paths split on , and `
Published Published true, yes, 1… — see below

Each Shopify product imports as a simple product from its first row (the one with the title). Its variant rows are skipped and counted under "No name of its own — usually a variant line under the product above it."

Customers

Field Headers read Notes
Email (identifies) Email Must be a valid address; stored as shopify:<email>
First name First Name
Last name Last Name
Phone Phone Billing phone
City City Billing city
Country Country Code, Country First two letters, upper-cased

Orders — Full edition

One row is one order line. Rows sharing an order number are one order: the first creates it, and each later row in the same migration adds its line.

Field Headers read Notes
Order number (identifies) Name, Order ID e.g. #1001
Email Email Billing email; links the order to an account with it
Total Total Written as the order total
Tax Taxes
Shipping Shipping
Currency Currency First three letters, upper-cased
Status Fulfillment Status, Financial Status Mapped — see How it works
Date Created at, Paid at
SKU Lineitem sku Links the line to the product with this SKU
Quantity Lineitem quantity Empty means 1
Line name Lineitem name
Line price Lineitem price Per unit; the line total is price × quantity

Coupons — Full edition

Field Headers read Notes
Code (identifies) Code Lower-cased
Amount Value
Type Type Contains percent or % → percentage; anything else → fixed cart

WooCommerce CSV export

Products

Field Headers read Notes
Source id (identifies) ID, id Stored as woo:<id>
Name Name, post_title
Description Description, post_content
SKU SKU, sku
Regular price Regular price, regular_price
Sale price Sale price, sale_price Set only when above 0 and below the regular price
Stock Stock, stock_quantity
Categories Categories, category_ids Paths split on , and `
Published Published, post_status 1, publish… — see below

Customers

Field Headers read Notes
Email (identifies) Email, billing_email Must be a valid address; stored as woo:<email>
First name First name, billing_first_name
Last name Last name, billing_last_name
Phone Phone, billing_phone
City City, billing_city
Country Country, billing_country First two letters, upper-cased

Orders — Full edition

Field Headers read
Order number (identifies) Order Number, order_id, ID
Email Email, billing_email
Total Order Total, order_total
Tax Order Tax, order_tax
Shipping Shipping, order_shipping
Currency Currency, order_currency
Status Order Status, status
Date Order Date, date_created
SKU SKU, item_sku
Quantity Quantity, item_quantity
Line name Item Name, item_name
Line price Item Total, item_total

Coupons — Full edition

Field Headers read
Code (identifies) Code, code
Amount Amount, coupon_amount
Type Discount type, discount_type

Values

  • Published counts as published when the cell is true, yes, 1, publish, published, active or visible. Anything else is a draft. The product is published only if Publish imported products straight away is also on.
  • Money ignores currency symbols and reads 1.250,00, 1,250.00 and 1250 all as 1250, and 12,50 as 12.50.
  • Categories are created as needed. A path such as Kitchen > Kettles is a Kettles category inside Kitchen, and the product is filed under Kettles, as WooCommerce's own importer does.
  • Weight (full edition) is written in the shop's own weight unit: Shopify's Variant Grams and a WooCommerce Weight (kg), Weight (g), Weight (lbs) or Weight (oz) column are converted from the unit they name; a bare weight column is taken as already in the shop's unit.

What is not imported

Product images, variations as separate records (WooCommerce variation rows are skipped and counted), dimensions, product weight in the free edition, attributes, tags, customer addresses beyond city and country, order addresses, payment details, coupon restrictions and usage limits. Fill those in after the migration where you need them.

A worked example

A minimal Shopify product file:

Handle,Title,Variant SKU,Variant Price,Variant Compare At Price,Variant Inventory Qty,Type,Published
blue-kettle,Blue Kettle,KET-BLU,34.00,40.00,12,Kitchen,true
blue-kettle,,KET-BLU-L,38.00,,4,,

Imported with Publish… off, this creates one draft simple product Blue Kettle — SKU KET-BLU, regular price 34.00, no sale price (40.00 is above the price, so it is the old price, not a sale), stock 12, category Kitchen, source id shopify:blue-kettle — and skips one row as a variant line. Report: 1 created, 0 updated, 1 skipped. Run the same file again and it reads 0 created, 1 updated, 1 skipped.

Your own format — Full edition

A shop's own export can be added as a new source through the gmsm_sources filter; it then gets the same reader, resume and source-id rule. See the Developer reference.

Shopping Cart
Scroll to Top