Skip to content
English
  • There are no suggestions because the search field is empty.

Data Ingestion Studio Best Practices

Plan, prepare and deliver imports your teams can trust

Overview

Data Ingestion Studio gives you many ways to clean, match and deliver data. These best practices help teams use them consistently, so every import improves the CRM rather than adding clean-up work. Use this guide as a checklist for planning and reviewing imports.

Before you start

  • Agree the purpose of the import: new leads, updates to existing records, event follow-up or a one-off migration.
  • Confirm the target portal. Check the portal name and ID before every import.
  • Save portal defaults for properties, dates, locations, phones, notes and import modes first, so imports start consistently.
  • Ask for HubSpot record IDs, emails or company domains in source exports wherever possible. Identifiers are the best protection against duplicates.

Upload

  • Give each import a clear name, such as source, purpose and date. File names and segments use it.
  • Check the worksheet and header row in the preview before analysing.
  • Skip summary rows, notes above the header and columns you'll never use.
  • For files that grow over time, use Process rows after (file row number) to process only new rows.
  • In Excel files, recalculate and save formulas before uploading.

Prepare

  • Review the detected type, populated counts and samples for every column you plan to map.
  • Keep Treat NA, N/A, NULL and similar markers as empty on, unless a value such as NA is genuine.
  • Prefer exact replacements and letter case changes over manual edits to the source file, so decisions stay visible and repeatable.
  • Use email deduplication only when repeated emails truly represent the same single activity.
  • Combine address lines and split names before mapping.

Map

  • Map Record ID columns whenever they exist.
  • Use Don't overwrite for properties your team maintains manually, such as lifecycle stage or lead source.
  • Resolve every unmatched dropdown and owner value with a standard option, rather than adding near-duplicate options.
  • Create new properties only after checking whether a suitable one exists, and agree names with your HubSpot administrator.
  • Use Add column for values that apply to every record, such as campaign or lead source.

Details

  • Choose only the outputs you intend to import.
  • Turn on lookups for updates and recurring sources, so existing records receive their IDs.
  • Use Update only when an import should never create records.
  • Confirm date interpretation and time zone explicitly, especially for international or webinar files.
  • Use AI company matching only where it's approved by your organisation's data policies.

Review

  • Compare the import summary with the expected numbers before looking at individual rows.
  • Clear all errors, then check warnings for ambiguous contacts, unrecognised locations and invalid phones.
  • Preview the final files and open a few record links in HubSpot.
  • Skip rows deliberately, rather than leaving errors in place.
  • Apply changes and rerun before downloading or sharing.

Deliver

  • For manual imports, follow the import instructions exactly. Select the listed import modes and Don't overwrite properties.
  • Import companies before contacts, and contacts before notes.
  • Import each notes file only once.
  • For automated ingestion, read the Confirm screen carefully, especially the portal, counts and segments.
  • After delivery, check a sample of new and updated records, notes, event participation and segments.

Govern and collaborate

  • Grant portal access only to people who need it, and review access regularly.
  • Enable automated ingestion only for portals where review and confirmation responsibilities are agreed.
  • Release editing when you've finished, and share links rather than screenshots for reviews.
  • Keep diagnostics and issues files with your records of significant imports.

Why it matters

Consistent habits make imports predictable, auditable and easy to hand over. They protect the CRM from duplicates, overwritten values and inconsistent formats, which keeps reporting and automation trustworthy for every team using HubSpot.

What to do next

  • Turn this checklist into your team's import procedure.
  • Read Troubleshoot Data Ingestion Studio for help with common issues.