HubSpot sample import files are working examples that show how spreadsheet columns can be structured before data is loaded into a HubSpot portal. They are useful for contacts, companies, deals and other CRM objects, but copying a template alone does not guarantee a clean import.
The important work is deciding what each row represents, which property identifies an existing record, how related records should be associated and who owns the resulting data. A sample file should therefore be treated as a mapping aid, not as a complete data model.
The safest approach is to select the correct sample structure, align it with the properties and business rules in your portal, test a small file, review the results and only then run the larger import. This reduces duplicates, incorrect associations and records that look complete but cannot support reliable reporting.
What HubSpot sample import files are designed to do
A HubSpot sample import file provides a reference layout for importing one or more CRM objects. It can help you understand expected column headings, record structure and the type of identifiers used to match or associate records.
Common examples cover contacts, companies, deals, tickets, products, calls, notes and other supported records. Some files represent one object, while others show how multiple objects can be loaded together. The correct choice depends on the business outcome, not simply on the file that contains the most columns.
A sample import file explains the shape of an import. It does not decide what your CRM data should mean.
Before editing a template, define the result you need. Are you creating new records, updating existing records, linking people to companies, moving open deals into a pipeline or establishing a starting dataset for reporting? Each objective affects the identifiers, required fields, associations and validation checks you need.
Choose the import structure based on the business state
HubSpot imports are easier to design when the target business state is explicit. A contact import may create people who should later be enrolled in marketing activity. A company import may establish account records for sales ownership. A deal import may represent active opportunities that must appear in a particular pipeline and stage.
These are not interchangeable uses of a spreadsheet. A record can be technically imported and still be operationally wrong if it has no owner, is placed in the wrong pipeline or is associated with the wrong company.
Use when the record set is independent
A single-object file is appropriate when you are creating or updating one type of record and associations are not part of the immediate task. Examples include importing a controlled list of contacts or updating company properties.
Use when relationships are part of the result
A multi-object file is useful when contacts, companies and deals need to be connected during the same process. It requires more careful identifier and association planning because an error can affect several records at once.
Use this decision rule: if the import is only successful when two or more records are connected, design and test the association logic before preparing the full file. Do not treat associations as a detail to resolve during the final upload.
What to check in contact, company and deal samples
Contacts
Contact files commonly include fields such as email address, name, phone number, lifecycle stage and owner. The most important question is how HubSpot should identify an existing person. If the purpose is to update records, use a reliable identifier and confirm that it is populated consistently.
Review whether blank values should leave existing CRM values unchanged, overwrite them or be excluded from the import. This matters when a source spreadsheet contains partial data. A contact file that contains only names and phone numbers may be acceptable for creating a limited dataset, but it may not be sufficient for segmentation, ownership or reporting.
Companies
Company files often contain company name, domain, location, industry, size and owner. Establish how organizations with similar names will be distinguished. A domain may help match a company, but it should be cleaned and reviewed rather than assumed to be accurate.
Also decide whether subsidiaries, business units and parent companies should be separate records. A sample file cannot answer that structural question. It only shows where the relevant properties can be placed.
Deals
Deal imports usually require a deal name, amount, close date, pipeline and deal stage. These values must reflect the pipelines and stages that exist in the destination portal. A stage label copied from another CRM may look reasonable in a spreadsheet but fail to represent the same business state in HubSpot.
Before importing deals, define what the date means, who owns the deal and whether the amount is stored in the correct currency and format. If historical deals are being loaded, distinguish closed business from active opportunities so that forecasts and reporting are not distorted.
Other objects
Templates for tickets, products, calls, notes and other objects should be reviewed in the same way. Identify the record, its required properties, its owner and its relationship to other records. Avoid importing activity or supporting data before the records it should relate to have been matched and validated.
A property is only useful when its value has a shared meaning. Importing a column called “status” without defining the allowed values can create data that is populated but not dependable.
How to prepare a HubSpot sample file
Keep the original source file, the edited import file and the final mapping notes. This creates an audit trail when someone later asks why a property changed or why an association was created.
Data checks that prevent common import problems
Most import failures are not caused by the existence of a spreadsheet. They are caused by ambiguity in the data or by assumptions about how the destination system will interpret it.
- Confirm that every column has one clear purpose.
- Remove merged cells, formulas, hidden rows and decorative formatting.
- Check that dates use one agreed format and represent the intended business event.
- Standardize phone numbers, domains, names and other matching fields.
- Compare dropdown and pipeline values with the values configured in the HubSpot portal.
- Identify duplicate source records before upload.
- Confirm owners, teams and required fields are available in the destination system.
- Separate test records from the production dataset.
Do not assume that a successful upload means the data is correct. Review records in HubSpot after the test. Check ownership, property values, associations, pipeline placement and reporting behavior. A technically accepted row can still create a misleading CRM record.
Associations require their own design decision
Associations connect records such as contacts to companies, deals to companies or deals to contacts. They should be planned separately from the property mapping because a record can have accurate fields and still be related to the wrong entity.
For example, imagine a source system contains two contacts with the same surname and a company spreadsheet contains several offices under one brand. Matching only on a display name creates avoidable ambiguity. A safer process uses stable identifiers, checks exceptions and sends unresolved rows to a review queue rather than guessing.
Association labels also matter when the relationship carries meaning. A contact may be a decision maker, billing contact or former employee. If those distinctions affect sales activity or reporting, they should be represented deliberately rather than left as an unnamed connection.
Association quality is part of data quality. A correct contact attached to the wrong company is still an incorrect CRM record.
Example: importing contacts, companies and deals together
Consider a hypothetical business moving active sales records into HubSpot. Its source file contains contacts, customer accounts and opportunities, but company names are not consistently written. The team should not begin by uploading every row.
First, it would clean and review company identifiers, decide which accounts are distinct, and map each source company to one destination record. Next, it would confirm which contacts belong to those companies and which deals are genuinely active. Finally, it would test a small set containing one ordinary account, one account with several contacts and one deal with an unusual value.
This sequence makes exceptions visible before they affect the full dataset. It also gives sales and operations teams a chance to agree on ownership, pipeline stages and reporting definitions before the CRM becomes the system of record.
When a sample file is not enough
A template is useful for a bounded import. It is not a substitute for CRM architecture, data governance or migration planning. Additional design work is usually needed when the source data includes multiple systems, conflicting definitions, historical records, complex associations or custom properties.
In those cases, the key questions are operational: which system is authoritative, who owns each property, which records should be retained, how will duplicates be resolved and what should happen when future imports arrive?
ConsultEvo approaches this work by clarifying the process and data rules before configuring the tooling. For broader CRM structure, pipeline design, integrations and reporting, see HubSpot consulting services or CRM consulting services.
How to maintain clean imports over time
A successful first import can still degrade if later files use different definitions. Maintain a short import standard that documents approved identifiers, property meanings, date and number formats, ownership rules, association logic and the review process for exceptions.
Assign an owner for the standard and require changes to be reviewed when the CRM structure changes. If imports are repeated, use a consistent file naming convention and retain the outcome of each test. Reporting should then be used as a control: if record counts, ownership or pipeline totals change unexpectedly, investigate the import rather than accepting the result as normal.
Automation can help with repeatable preparation, but it should follow clear decision logic. AI may assist with classification or cleanup when its job, review threshold and escalation path are defined. More tooling does not remove the need for accountable ownership.
Frequently asked questions
Where can I find HubSpot sample import files?
HubSpot provides sample import files through its current product documentation and import guidance. Select the sample that matches the object or combination of objects you need to load, then compare it with the properties configured in your own portal.
Should I use a single-object or multi-object HubSpot import?
Use a single-object import when records can be created or updated independently. Use a multi-object import when the result depends on creating relationships between contacts, companies, deals or other objects. Test association logic separately before importing the full dataset.
What should I check before importing a HubSpot spreadsheet?
Check identifiers, duplicate records, required properties, dates, numbers, dropdown values, owners, pipeline stages and association fields. Remove formulas and formatting that do not carry useful data, then test a representative sample.
Can HubSpot sample files be used for custom properties?
Yes, a sample file can provide the structure for adding custom property columns, but the property names, field types and allowed values must match the configuration in the destination HubSpot portal. Map and test custom fields before the full import.
How can I reduce duplicates during a HubSpot import?
Use a reliable identifier for matching existing records, clean the source values before upload and test updates with a small file. Review the resulting records and associations rather than relying only on the import completing successfully.
Need a safer HubSpot data import process?
If your import involves duplicate records, complex associations or unclear CRM ownership, ConsultEvo can help define the data rules, mapping and workflow before the upload.
