Upload Source Data Files

Upload Source Data Files

Complete, readable source exports allow Next-Cart to process file-based migration input for platforms that do not use direct API access.

Some platforms provide migration data through exported files instead of direct API access. In those cases, you prepare complete exports from the source store, keep the files organized, upload them through the Next-Cart interface, and verify that the files are readable before migration configuration continues.

Source data file upload is source-side only

Source data files are used only when the selected Source Platform supports or requires file-based input. Do not assume file upload replaces the required setup for the Target Platform.

Prerequisites

Before you upload source data files, confirm that:

• you are signed in to the Next-Cart account that owns the order and purchased migration;
• the order and purchased migration show the correct Source Platform and Target Platform;
• Next-Cart shows source data file upload for the selected Source Platform;
• you can sign in to the source store admin or reporting area;
• you have permission to export products, customers, orders, and other selected data;
• you know the required date range and data scope;
• you have enough local storage for the exported files;
• you have a secure location for temporary export files.

Common file types

The required file types depend on the Source Platform.

File type	Common use
CSV	Products, customers, orders, categories, reviews, coupons, or table exports.
XLSX	Reports, product lists, customer lists, or order exports from platforms that use spreadsheet output.
XML	Catalog, order, content, or platform-specific structured exports.
TXT	Tab-delimited reports, marketplace listings, or order reports.
ZIP	Bundled exports containing multiple files.
SQL or table exports	Platform-specific data exports or advanced support-assisted cases.

Use the format exported by the Source Platform or required by the platform-specific export guide. Do not convert files unless the guide or support team instructs you to do so.

Data types to prepare

Export all data types included in your migration scope and any platform-specific files required by the export guide.

Data area	What to prepare
Products	Product records, variants/options, SKUs, prices, inventory, images, attributes, brands, manufacturers, and related product details where supported.
Categories or collections	Category trees, collection assignments, product grouping data, and navigation-related source structures where exportable.
Customers	Customer records, emails, names, addresses, customer groups, companies, and contact details where supported.
Orders	Orders, order line items, order statuses, refunds, cancellations, discounts, taxes, shipping, and date ranges where supported.
Reviews and coupons	Product reviews, discount codes, coupon rules, and relationships where supported.
Content	Pages, posts, CMS content, blog exports, or platform-specific content files where supported.
Platform-specific files	Required tables, XML files, marketplace reports, image exports, or source backup files listed in the platform-specific guide.

Recommended export organization

Keep files grouped by platform and data type before uploading.

• Directorysource-exports/

  • Directoryproducts/

    • products.csv
    • product-variants.csv
    • product-images.csv
  • Directorycategories/

    • categories.csv
  • Directorycustomers/

    • customers.csv
    • customer-addresses.csv
  • Directoryorders/

    • orders.csv
    • order-items.csv
    • refunds.csv
  • Directorycontent/

    • pages.xml
    • blog-posts.xml
  • Directoryplatform-required-files/

    • required-file-1.xml
    • required-file-2.csv

The exact file names may differ by platform. Keep the original exported names when they are meaningful or required by the source export guide.

Prepare source data files

1. Confirm file upload is required

   Open the purchased service under Account → Migrations → My Migrations, select Start, and confirm that source data file upload is shown for the Source Platform.

2. Open the source store export area

   Sign in to the source store admin, reporting area, marketplace dashboard, or legacy export area.

3. Export products and catalog data

   Export products, categories, variants/options, images, brands, manufacturers, and catalog-related files where supported and required.

4. Export customers

   Export customer records, contact details, addresses, and customer groups where supported.

5. Export orders

   Export the full required order range. Include order line items, statuses, totals, taxes, discounts, shipping, refunds, and customer linkage where supported.

6. Export content and optional data

   Export reviews, coupons, pages, posts, metadata, or platform-specific content files when they are in scope and supported.

7. Check platform-specific requirements

   Review the export guide for the Source Platform. Some platforms require special files, table exports, XML files, report formats, or batched exports.

8. Organize the files

   Group files by data type and keep the original names when required. Do not remove required columns or rename required files.

9. Upload the files in Next-Cart

   Upload the files in the source data file upload area shown by Next-Cart. Match each file to the correct data type or platform requirement when fields are separated.

10. Verify the upload

    Confirm that each file appears in the interface, has the expected file size, and can be processed for connection verification or configuration.

What not to change in exported files

Avoid edits that can break relationships or prevent the files from being processed.

Do not change	Why it matters
Column headers	Headers may be used to identify fields and relationships.
Record IDs	IDs may connect products, customers, orders, categories, and line items.
Order numbers	Order numbers may be used for validation and support review.
Parent-child fields	Category, variant, bundle, or option relationships may depend on these values.
File encoding	Changing encoding can break special characters, names, addresses, or content.
Required file names	Some platform files may be identified by their original names.
Date formats	Changing dates can affect order ranges, filtering, or validation.

If you must change a file, keep a copy of the original export and document the reason for the change.

Expected result

After source data file preparation is complete:

• required files are exported from the source store;
• the files cover the intended data scope and date range;
• the files remain readable and structurally intact;
• platform-specific required files are included;
• the files are organized and uploaded in Next-Cart;
• the uploaded files are ready for verification and configuration.

Verify source data files

Check	Pass condition
File presence	Every required file for the selected Source Platform is included.
Data coverage	Products, customers, orders, and other selected data types are present where supported.
Date range	Orders and reports cover the intended migration period.
File format	Files use the required CSV, XLSX, XML, TXT, ZIP, or platform-specific format.
File integrity	Files open correctly without corruption, empty rows only, or unreadable characters.
Required fields	IDs, names, SKUs, emails, order numbers, line items, dates, and relationship fields are present where expected.
File size	Uploaded files appear complete and match the expected size or record count.
Original exports	Original unmodified files are preserved for support review if needed.

If the export is incomplete

Issue	What to check
Missing products	Confirm the export included all products, active/inactive status where relevant, variants/options, and catalog filters.
Missing customers	Confirm customer export permissions and whether customer data is included in orders instead of a standalone customer file.
Missing orders	Check date range, status filters, export limits, and whether orders must be exported in batches.
Missing line items	Confirm whether the platform has a separate line-item export or requires an export option such as detailed order rows.
Missing images	Check whether image URLs, image files, or image tables are exported separately.
Wrong file format	Re-export using the format required by the platform guide.
File too large	Split exports only if the platform guide supports batched exports. Keep all batches organized and complete.
File edited accidentally	Re-export the original file rather than trying to repair a damaged export.

Do not manually import remaining data into the target store

If the uploaded source files or Entity Points Plan do not cover all required data, resolve the export or plan issue before continuing. Manual imports can break relationships and make validation harder.

Security cleanup

After the files are uploaded and no longer needed locally:

• store original exports only in approved secure storage;
• remove temporary copies from shared computers;
• avoid emailing full customer or order exports unless support requests a secure transfer path;
• delete duplicate temporary files after verification;
• keep the original source exports until migration validation and support review are complete.

Next step

Situation	Go to
You need platform-specific export steps	Source Data Export Guides
You uploaded files and need to confirm readiness	Verify Platform Connections
Next-Cart shows API setup instead of file upload	Set Up an API Connection
Next-Cart shows KitConnect setup	Install KitConnect
The file upload or verification fails	Troubleshoot Connection Setup
File verification passes	Configure Your Migration