The 200,000-row export meets the 5,000-row import limit: a rite of passage for anyone who has migrated a mailing list, a CRM or a product catalogue. The fix is splitting — but naive splitting (chopping the file every N lines) produces parts that fail, because only the first one carries the header row the importer needs. Here is the way that works.
The two-minute flow
- Open Split CSV and drop the export — CSV or Excel both work.
- Set rows per part just under your platform's limit (importing at 5,000? use 4,900 — some platforms count the header).
- Keep "Repeat header in every part" ticked. This is what makes each part importable on its own.
- Download the ZIP: tidy files named part1, part2, … each a complete table.
SheetJS in your browser — customer data never crosses the network.
Finding the right rows-per-part
The error message usually tells you the cap; when it doesn't, the platform's import docs do. If neither helps, binary-search it: try 10,000 — fails; 5,000 — works; done. One habit worth keeping: make parts meaningfully smaller than the cap, because failed imports at row 4,999 of 5,000 waste far more time than a few extra files.
When the file needs reshaping too
Imports often want different columns, not just fewer rows. The Excel ↔ CSV ↔ JSON converter previews the table before you commit, and converts between formats when the importer insists on one. For a quick sanity check on what a part contains, its preview table beats opening forty files in Excel.