Convert your Shopify products into a WooCommerce file

Where you start

Atelier Démo’s Shopify product export has 4 rows:

• a T-shirt in three sizes, S, M and L, on 3 rows: each size has its SKU (TSH-ATL-S…), its stock (12, 20 and 0) and its weight;
• a tote bag at 15.00, with a compare-at price of 18.00.

Shopify gives each size a SKU, but none to the T-shirt itself. WooCommerce, however, attaches each variation to its product through that product’s SKU: this is what the Converter will create.

What you will be able to do

• recognize a suggestion you should not confirm;
• find the parent SKU created for WooCommerce;
• check the variations in the written file.

Before you start

• Eloshon Converter installed on your computer: see the Download page.
• The products export of your Shopify store, as a CSV file: Export from Shopify.
• You do not need an Internet connection: the file is read and converted on your computer.

Step 1: Platforms

1. Open Eloshon Converter. On the home screen, click the New conversion button below the title.
2. Under Source platform, click Shopify.
3. Under Target platform, click WooCommerce.
4. Click Continue.

Step 2: File

1. Drag your CSV file onto the Drop a CSV, JSON or .eloshon file, or click to browse area, or click the area to choose it.
2. Read the card: File recognized · Shopify · products, with 4 rows.
3. Click Continue.

Step 3: Mapping

The To handle filter keeps 3 rows.

1. Read Variant Compare At Price: To check, with the reason Compare-at or sale price: please check. In Preview of converted rows, the tote bag has Regular price = 18 and Sale price = 15: Shopify’s compare-at price becomes WooCommerce’s regular price.
2. Read Variant Inventory Policy (To check) and Variant Inventory Tracker (Uncertain): their reason is Suggestion: confirm with Edit. Do not confirm them: an unconfirmed suggestion writes nothing, and each size’s stock already comes from Variant Inventory Qty.
3. Scroll down to the WooCommerce fields with no column card and read the Parent SKU generated block: the T-shirt will get a parent SKU.
4. In Preview of converted rows, under Edit the output file, check that Variant stock shows Quantities from the original file, otherwise choose that value.
5. Click Continue to review.

Step 4: Review

The counters show 2 products and 5 rows, and the problem list is empty: No problems detected.

1. Read the Good to know about this conversion card: 1 parent product SKU(s) created for WooCommerce, from the product’s reference or its title. WooCommerce attaches each variation to its product through this SKU. Variations keep their own SKU, or an empty SKU when your file gives none.
2. Read the Generated SKUs card: T-SHIRT-ATELIER, marked Generated, for the parent product.
3. Click Continue.

The Data with no match in WooCommerce card names 5 Shopify columns that have no place in the file, including Variant Inventory Policy and Gift Card.

Step 5: Export

1. Under Destination folder, keep the suggested folder (Documents, unless you changed it in Settings) or click Browse….
2. Under File name, keep the suggested name: your file’s name followed by _woocommerce.
3. Click Export.

The result

The Conversion complete screen lists the files written and their folder; Open folder opens that folder. The CSV file has 5 rows after the header:

• the T-shirt: Type = variable, SKU = T-SHIRT-ATELIER, Attribute 1 name = Taille, Attribute 1 value(s) = “S, M, L”;
• its 3 sizes: Type = variation, Parent = T-SHIRT-ATELIER, each with its SKU, its stock (12, 20, 0) and Regular price = 25;
• the tote bag: Type = simple, Regular price = 18, Sale price = 15;
• weights in kilograms, in Weight (kg) (0.18 for size S); the Shopify brand (Vendor) in Brands.

The file has no ID column: The ID column is removed (WooCommerce assigns its own IDs).

Messages you may see

• This file does not match the chosen source platform. The button next to the message picks the right source.
• Duplicate SKU “TSH-ATL-M”: the target may overwrite or reject this product. Towards WooCommerce, this is a blocking error: fix the SKU with Fix.
• Variant with no option value: repaired as a per-variant title. A size has no value in Option1 Value; this is a warning.
• If the file cannot be written to the chosen folder, the The conversion stopped window shows Unrecognized format., even though your file is recognized: choose another folder or another name.

Importing the file into WooCommerce

The Converter stops at the file: it does not connect to your store. The steps to import it into WooCommerce, based on WooCommerce’s official help, are in Import into WooCommerce. Eloshon has not tried this import in a real store: after the import, compare a few records with your old store.

Other ways to do it

• Some sizes stay on sale when they are out of stock in Shopify: the Converter does not read Variant Inventory Policy. At step 3, under Edit the output file, choose Quantities kept, selling beyond them (Shopify, WooCommerce); this choice applies to the whole file: every variation and every simple product gets Backorders allowed? = 1. It stays remembered for your next conversions to WooCommerce.
• You often convert files of the same shape: at step 3, Save as template keeps your choices, and Apply a template applies them next time. See Mapping templates.
• Your file is long: at step 5, tick the option that splits it into files of at most 500 rows. Each file repeats the header. Variations stay in the same file as their product.
• Your catalogue comes from a site read by Eloshon Scraper: choose Eloshon Scraper as the source and drop the job’s products.json file.