HubSpot size problem
Split a HubSpot Import File Safely
Prepare a HubSpot import that exceeds the file or row limits for your subscription without losing headers or unique identifiers.
Use the matching tool
Split Large File
What the error actually means
HubSpot’s documented import limits differ by subscription, including file-size and row limits. A safe split preserves one header row, stable unique identifiers and the object associations required by the chosen import workflow.
Likely causes
- The file exceeds the account’s current size or per-file row limit.
- Several objects were flattened into one oversized table.
- Chunks do not repeat the header.
- The split removed identifiers required to associate records.
Association-safe chunks
Problem
Split rows and omit record IDs from later filesCorrect pattern
Each chunk retains the same header and the unique identifier used for updates or associationsA safe repair workflow
- 1Check the current limits for the actual HubSpot subscription.
- 2Choose a chunk size below both file and row thresholds.
- 3Preserve headers and all required unique identifiers.
- 4Import one chunk and review its result before queuing the remainder.
How to verify the result
A file that downloads successfully is not automatically a correct file. Check the result at both the structural and business-data levels:
- Each chunk meets the account limits.
- Headers and identifier columns are identical.
- Associations resolve to the intended records.
- Success and error counts reconcile across all chunks.
Read the deeper guides
Import CSV to HubSpot (Contacts & Companies)A complete guide to importing contacts, companies, and deals into HubSpot from CSV. Learn how to map properties, handle associations, and fix errors.How to Split Large CSV Files (3 Easy Methods)Split large CSV files that are too big for Excel. Learn how to divide CSV files by row count or column values. Handle files over 1 million rows.
Official references
Platform requirements and technical standards can change. These are the primary references used for this page.