A PRACTICAL WORKFLOW
From source file to reviewed copy.
Start with a copy of your product export. Keep the original nearby, and choose each transformation deliberately.
Open the CSV workspacePrepare a UTF-8 CSV.
Use a comma-separated CSV, up to 10 MB and 50,000 source records. The workspace does not read XLSX files.
In Excel, use Save As and choose CSV UTF-8 (Comma delimited). If your export uses another separator, create a comma-separated version before loading it.
Load the file and confirm the mapping.
Choose your source columns for the destination fields. Check each suggested match and confirm it yourself; a suggestion is not an applied mapping.
Download a mapping profile to reuse those choices later. Loading a profile brings back field mappings, not product data. Review it against the new file’s columns.
Inspect, then clean.
Use findings, search and pagination to review the file. Batch tools can clean whitespace, remove explicitly selected currency markers, normalize supported enum casing, and make your exact replacements.
Preview the affected cells before applying a batch change. Check the before-and-after trail, and use undo if a change is not what you intended.
Choose handles and image records explicitly.
Generate handles only when you choose to create new product handles. Existing handles are preserved. The tool does not guess a Latin spelling for non-Latin titles; enter the handle yourself when needed.
If a field contains multiple image URLs, explicitly choose to split them into image records. Review the resulting rows before export.
Download the right copy.
The source-preserving export contains all original columns with your applied edits. The Shopify-format export contains only the columns you mapped, with any explicitly selected image-record expansion.
Keep an audit JSON if you want a record of your changes. It excludes cell values by default; including them is a separate, explicit choice.
Review your destination import.
The tool cannot verify store state, category taxonomy, metafield values or live image availability. Review the destination platform’s import preview before proceeding.
Complete WooCommerce variable, variation, grouped and external product migrations are unsupported and block conversion. A clean file review does not guarantee a successful store import.