Prepare XLS Source Data Files

Prepare XLS Source Data Files

When XLS is selected as the Source Platform, Next-Cart reads Product data from products.xls through File Upload. This Source option is handled through Custom Service. The included XLS file workflow migrates Products only unless additional entity handling has been explicitly approved and developed for the project.

Keep the workbook structure, worksheet identity, field names, and field order defined below. Change the Product values without rebuilding the workbook into a different layout.

An accepted upload can still produce 0/0

File acceptance confirms that the workbook was uploaded. It does not confirm that Product records were recognized. If the XLS structure does not match the required format, migration processing can still run while Product progress remains 0/0, meaning 0 Source records were scanned and 0 records were migrated to the Target Platform.

File scope

The XLS file structure below covers Products. Additional workbooks do not add Customers, Orders, or other entity types unless that handling has been explicitly included in the approved Custom Service scope and developed for the migration.

If the project requires additional entity types, non-standard fields, relationship reconstruction, or other custom logic, define those requirements before execution. Use Prepare Custom Service Requirements to document the additional work.

Download the sample workbook

Use the XLS Product sample as the starting workbook. An XLSX reference copy is also available for inspecting the same product worksheet and 43-column layout.

• Replace every sample record with your own Product data and preserve the worksheet, headers, and column order.
• The XLS Source setup expects products.xls. Keep the upload in XLS format; do not rename an .xlsx extension to .xls.
• Use the XLSX copy for reference; upload the XLS file for this Source setup.

Required XLS structure

Requirement	Required format
Source Platform	XLS
Migration Service	Custom Service
Included file scope	Products
Connection method	File Upload
Filename	products.xls
Workbook format	XLS (.xls)
Product worksheet	product
Record layout	One header row followed by one Product or Product-variant record per row
Columns	43, in the required order

The header row must contain these fields in this order:

product_id,sku,price,status,weight,length,width,height,manage_stock,qty,name,description,short_description,barcode,manufacturer,categories,images,option_name_1,option_value_1,option_name_2,option_value_2,option_name_3,option_value_3,attribute_name_1,attribute_value_1,attribute_name_2,attribute_value_2,attribute_name_3,attribute_value_3,attribute_name_4,attribute_value_4,attribute_name_5,attribute_value_5,attribute_name_6,attribute_value_6,attribute_name_7,attribute_value_7,attribute_name_8,attribute_value_8,attribute_name_9,attribute_value_9,created_at,updated_at

Do not rename the product worksheet, rename fields, remove fields, insert additional columns, or reorder the Product columns. Do not add title or note rows above the header.

Supported Product fields

Field group	Fields
Product identity, pricing, status, dimensions, stock, and content	product_id, sku, price, status, weight, length, width, height, manage_stock, qty, name, description, short_description, barcode, manufacturer, categories, images
Product options	option_name_1, option_value_1, option_name_2, option_value_2, option_name_3, option_value_3
Product attributes	attribute_name_1 through attribute_name_9, paired with attribute_value_1 through attribute_value_9
Timestamps	created_at, updated_at

Format Product records

• Use one worksheet row for each Product or Product-variant record.
• Variants of the same Product can use the same product_id with different sku and option values.
• Keep option and attribute name/value pairs aligned by their numeric suffix.
• Leave unused cells blank. Do not remove the corresponding columns.
• Keep multiple category entries in one categories cell, separated by commas, and use > for hierarchy where needed.
• Keep multiple image URLs in one images cell, separated by commas.
• Use numeric 0 or 1 values for status and manage_stock rather than text labels.
• Use YYYY-MM-DD HH:MM:SS for created_at and updated_at when timestamps are provided.

Prepare the workbook

1. Open products.xls and keep the Product table on the product worksheet.
2. Keep the required 43-field header row unchanged and in the exact order shown above.
3. Replace the Product values with the data that should be migrated.
4. Keep one Product or Product-variant record per row and leave unused fields blank.
5. Do not add merged headings, introductory rows, alternate field names, or extra columns to the Product table.
6. Save the workbook in XLS format with the filename products.xls.
7. Reopen the workbook and confirm that the worksheet, header, and records remain aligned.

Verify before upload

Check	Pass condition
Filename	products.xls
Workbook format	The file remains a valid .xls workbook.
Worksheet	The Product table remains on product.
Header	All 43 fields are present in the required order.
Record rows	Every Product or variant occupies one row under the header.
Empty values	Empty data remains in blank cells without removing columns.
Options and attributes	Each numbered name/value pair remains aligned.
Timestamps	Supplied timestamps use YYYY-MM-DD HH:MM:SS.

Store identity for file-based migrations

XLS does not require a Source Store URL. For a paid migration, the Target URL therefore locks when the Target setup provides one, Connect Stores is saved, and the migration advances to Configuration. Later migration activity can use another valid products.xls file, including one prepared from a different originating store, but it cannot replace a locked Target Store.

See Store URL Locking and Store Identity for the complete rule.

If Product progress is 0/0

A 0/0 Product result means Next-Cart did not recognize Product records from the uploaded workbook structure.

Check the filename, XLS format, product worksheet, header names, column order, and row alignment. Correct the workbook and upload it again. If all structural checks pass but Product progress remains 0/0, use Troubleshoot Connection Setup and provide the filename, a privacy-safe example row, and the migration result.

File Upload is migration input, not recurring synchronization

Selecting XLS provides a file-based Source for a migration. It does not create a recurring synchronization feed between the workbook and the Target Store. The included standard XLS workflow recognizes Products from products.xls when the required Next-Cart structure is used.

If the project needs scheduled imports, repeated external-feed processing, Customers, Orders, another data type, non-standard relationships, or business logic beyond the standard Product workbook structure, define that requirement through Custom Service.

Next Steps

Continue with Upload Source Data Files to prepare and validate the file for the Source connection.