Is there a limit on file size?

Yes — up to about 100,000 rows per import run. Larger files are split into multiple separate imports.

What happens if there's an error in the file?

StoreChart shows a detailed error report before saving, including the row number and the problematic field, so it can be fixed in the source file and retried without ever writing the bad data to the system.

Can I export all my data back out to a file?

Yes — products, orders, customers, and inventory can be exported to a CSV file at any time, for backup, spreadsheet analysis, or transfer to another system.

What happens if I accidentally import the same file twice?

Products are matched by SKU and orders by order number, so a row that matches an existing record is flagged as a duplicate during validation instead of silently creating a second copy — it's safe to re-run an import after fixing errors without worrying about duplicating rows that already succeeded.

What's the best way to migrate a very large product catalog into StoreChart?

For catalogs approaching or exceeding roughly 100,000 rows, split the source file into several sequential import runs instead of one oversized file. Each run is validated and reported on independently, which makes it easier to isolate and fix errors without re-processing rows that already succeeded.

Can I import only a partial update, like just updating stock levels?

Yes. A file containing only the fields you want to update (for example, SKU and stock quantity) can be imported on its own, and StoreChart's column mapping only touches the fields present in that file, leaving every other field on the existing record untouched.

Data Import & Export

Import and Export Store Data via CSV and Excel

Upload a CSV or Excel file, map columns, and import products, orders, customers, or inventory with automated validation before saving.

Start Free View Demo

Move data between systems with a single file

Upload a CSV or Excel file, map the columns, and StoreChart validates everything before anything gets saved.

Import products, orders, customers, or inventory from a single CSV or Excel file.
Smart column mapping suggests an automatic match between file columns and system fields.
An error report is shown before saving to prevent bad data from ever reaching the system.
Especially useful for an initial migration from another platform or an existing spreadsheet.

How to import data in a few minutes

Three steps between uploading a file and having live data in the system.

Upload a file

Upload a CSV or XLSX file of up to about 100,000 rows, and choose whether you're importing products, orders, customers, or inventory.

Map the columns

StoreChart suggests an automatic match between the file's columns and system fields, and any column that wasn't matched correctly can be fixed manually.

Import and review the report

Before anything is saved, StoreChart runs validation and shows an error report, so issues can be fixed in the file and retried without touching existing data.

Fix and retry without touching existing data

Rows that fail validation can be corrected directly in the source file and re-uploaded, while rows that already passed validation stay untouched, so one bad row never forces a full re-import from scratch.

What unlocks with CSV import and export

Import
Import products, orders, customers, and inventory from CSV or XLSX files in a single run of up to about 100,000 rows.
Export
Export all existing StoreChart data to a CSV file for backup, reporting, or transfer to another system.
Smart mapping
The system automatically recognizes common column names and suggests a match to the relevant fields to shorten setup.
Validation
Every import goes through error checking and shows a detailed report before saving, preventing duplicate or invalid data.
Duplicate detection
Rows that match an existing record (by SKU for products, or order number for orders) are flagged during validation, so re-importing the same file twice doesn't silently create duplicate entries.
Migration-friendly export
A full export of existing StoreChart data can be generated as a starting template, making it easier to prepare a correctly formatted import file when moving data between two connected stores or systems.

The CSV import screen in StoreChart

The screen shows the automatically suggested column mapping and the file's error report before the final import is confirmed.

What should I know before a first-time migration into StoreChart via CSV?

CSV import is most commonly used the first week a store joins StoreChart, when historical products, customers, or order records need to move over from a spreadsheet, a legacy system, or a platform without a live integration. The process is designed around catching problems before they reach the database rather than after: after column mapping, every row is validated and a detailed report — including the row number and the exact field that failed — appears before anything is written, so the source file can be corrected and re-uploaded rather than leaving bad data mixed in with good data.

Duplicate handling matters most during migration, since it's common to accidentally run the same file twice or export overlapping date ranges from an old system. Products are matched by SKU and orders by order number, so a row that matches an existing record is flagged rather than silently creating a second copy — this makes it safe to re-run an import after fixing a handful of failed rows without worrying about duplicating the rows that already succeeded.

For stores with more than roughly 100,000 rows in a single category, the practical approach is splitting the source file into several sequential import runs rather than one oversized file, since each run is validated and reported on independently. Exporting existing StoreChart data to CSV works as the reverse direction of the same tool, and it's commonly used not just for backup, but to hand a clean, correctly formatted file to an accountant, or as a starting template when preparing the next migration. Because validation runs before any row is written, a large migration file with a handful of problem rows never blocks the rest of the import — only the flagged rows need correcting and re-uploading, while everything that already passed validation is saved on the first attempt.