What is the Salesforce Data Import Wizard row limit?

The Salesforce Data Import Wizard supports up to 50,000 records per CSV file. For larger exports, split the file into 50,000-row chunks and import each separately.

What is HubSpot's CSV import row limit?

HubSpot's contact and company import tool supports up to 100,000 rows per file. Files exceeding this limit will fail at upload or during processing.

Will field mapping work correctly if the header row is in every chunk?

Yes. Having the header row in every chunk is required for import wizards to map columns to the correct fields. Deliteful includes the original header automatically in every output file.

Does splitting affect data relationships like account-to-contact associations?

Splitting by row count is purely structural — no data values are modified. However, you should plan your migration load order carefully so parent records (e.g., accounts) are imported before child records (e.g., contacts) that reference them.

Can I use this for migrating to NetSuite or other ERP platforms?

Yes. Any platform that accepts CSV imports with a header row is compatible. Check your ERP's import documentation for its specific row or file size limit, then set that as your chunk size.

Split Migration CSVs to Fit Import Wizard Row Limits

Data migration projects stall when source CSV exports exceed the row limits of target system import wizards. The Salesforce Data Import Wizard caps at 50,000 rows per file; HubSpot's importer tops out at 100,000. When your CRM export or legacy database dump exceeds these thresholds, you cannot load it without splitting first.

Create free account

Migration projects have tight timelines, and a failed import at the load stage — caused by nothing more than an oversized file — wastes hours of preparation work. Most import wizards return an unhelpful error like 'file too large' or simply time out, leaving you to figure out the row limit through trial and error. Knowing your target system's cap and splitting to that exact limit before you start saves that debugging time entirely.

Deliteful splits your source CSV into fixed-row chunks with the original header row preserved in every output file. Target system importers — Salesforce, HubSpot, Zoho, NetSuite, and most ERP migration tools — require the header row to map fields correctly. Every chunk downloads numbered in sequence, so you can load them in order and track progress against your full record count.

How it works

1
Export your source system CSV
Pull the full record export from your legacy CRM, ERP, or database — contacts, accounts, transactions, or any object type.
2
Set the row limit for your target system
Use 50,000 for Salesforce Data Import Wizard, 100,000 for HubSpot, or check your target platform's documentation for its specific file limit.
3
Load each numbered chunk into the target system
Download the sequentially numbered output files and import them one at a time, verifying record counts after each batch.

Frequently asked questions

What is the Salesforce Data Import Wizard row limit?: The Salesforce Data Import Wizard supports up to 50,000 records per CSV file. For larger exports, split the file into 50,000-row chunks and import each separately.
What is HubSpot's CSV import row limit?: HubSpot's contact and company import tool supports up to 100,000 rows per file. Files exceeding this limit will fail at upload or during processing.
Will field mapping work correctly if the header row is in every chunk?: Yes. Having the header row in every chunk is required for import wizards to map columns to the correct fields. Deliteful includes the original header automatically in every output file.
Does splitting affect data relationships like account-to-contact associations?: Splitting by row count is purely structural — no data values are modified. However, you should plan your migration load order carefully so parent records (e.g., accounts) are imported before child records (e.g., contacts) that reference them.
Can I use this for migrating to NetSuite or other ERP platforms?: Yes. Any platform that accepts CSV imports with a header row is compatible. Check your ERP's import documentation for its specific row or file size limit, then set that as your chunk size.

Create your free Deliteful account with Google and split your migration CSV exports to fit your target system's import limits before your next load window.