I just checked the headings in your CSV, I’ll list here all items that have correspondents values on WooCommerce first and after talk about the items that requires some extra work with the CSV before importing.
I’ll give you some tips about the fields on WooCommerce, but please also check the docs about CSV Import schema in: https://github.com/woocommerce/woocommerce/wiki/Product-CSV-Import-Schema
—
See here a list with fields from Virtuemart and fields from WooCommerce:
product_sku
=> SKU
product_name
=> Name
product_s_desc
=> Short description
product_desc
=> Description
product_price
=> Regular price
product_publish
=> Published (note: accepts only 0
and 1
)
product_special
=> Is featured? (note: accepts only 0
and 1
)
—
Those requires some extra work, so I’m listing here to explain:
category_path
will match with “Categories” field, but you’ll probably need to format those before import, since WooCommerce will allow hierarchy and multiple categories like: Clothing > Tshirts
, you need to only list categories names.
Also you should merge product_full_image
and product_thumb_image
into just one column, also you can use comma to enter more than one image and import selecting the “Images” field, note that the first image will be always the product thumbnail that will show us on the store catalog and inside the product’s page.
By default WooCommerce doesn’t support manufacturer_id
and manufacturer_name
, but you could import those as meta data to just keep save on WooCommerce for future reference, and you also could display those meta data on WooCommerce too. So for it you could use “Import as meta data”.
Note that by default WooCommerce will generate related products for you, but there’s other options for related_products
, like “Upsells” products (shows up in the product’s page together to related products) and “Cross-sells” products (shows up in the cart), you can use SKUs for both of this options.
—
I checked the Virtuemart’s documentation, but since there’s no examples in that CSV I’m not sure about some headings from that CSV file, but I’ll try to guide you to find the best fit on WooCommerce.
Without any example is hard to say if product_availability
is just a status for the stock or it registers the stock quantity. So if it’s just product quantity, then select “Stock”, or use “In Stock?” to determine the stock status.
For product_tax
you could match with Tax status
(accepts taxable
, non-taxable
, and inherit
) or Tax class
.
Finally there’s some headings on that CSV related to measurements and weight: product_weight
, product_weight_uom
and product_lwh_uom
.
Two of those sounds like that are to define a “Units of measurement”, but on WooCommerce those settings are global, so before importing product_weight
I advise you to check what’s the unit used in your WooCommerce installation and try to convert in the CSV before.
Please let me know if it helps you.