HubSpot Deal Import template.

What's inside — the exact file

This is the complete template, not a sample. The rows are worked examples — replace them with your data (and delete them before any platform import).

What this template is for

Deal imports rebuild your pipeline in HubSpot — from a legacy CRM, a sales spreadsheet, or a billing export. The hard part isn't the deals; it's the associations, which is why this template carries Associated Contact Email and Associated Company Domain columns so every deal lands attached to the right records instead of floating unmoored.

The example rows model deals across different pipelines and stages, because the most common import failure is stage names that don't exactly match your portal's pipeline configuration.

How to use it, step by step

1. Set up pipelines and stages before importing. Deal Stage values must match your HubSpot pipeline stages exactly. Build (or rename) pipelines first, then make the spreadsheet match — not the other way around.
2. Map old stages to new honestly. Legacy CRM stages rarely correspond one-to-one. Collapse them deliberately ('Negotiation' + 'Verbal Commit' → 'Contract Sent') and write the mapping down — this is your mini field-mapping exercise.
3. Fill association columns from clean keys. Associated Contact Email and Associated Company Domain must match records already in HubSpot — which is why deals import last, after companies and contacts.
4. Format amounts and dates plainly. Amount: plain numbers, no symbols. Close Date: a consistent format (YYYY-MM-DD is safest). Open deals need expected close dates; closed deals need real ones, or your historical reporting lies.
5. Import and verify the pipeline view. Contacts → Import, choose Deals. Then open each pipeline's board view: correct stages, sane amounts, associations present on a sample of ten.
6. Rebuild forecasts and reports last. Once deals verify, point dashboards and forecasts at the imported pipeline. Historical win-rate reporting is only as honest as the stage mapping you wrote in step two.

What each column means

Common mistakes to avoid

• Importing deals before contacts and companies exist, so association columns match nothing and every deal imports orphaned.
• Stage names that almost match ('Closed Won' vs 'Closed won') — the match is exact, and near-misses either fail or dump deals into the wrong stage.
• Importing dead deals as open because the legacy CRM never closed them — pre-close them in the spreadsheet or your new pipeline starts life bloated.
• Forgetting Close Date on closed deals, which lands them all in the import month and wrecks every historical revenue chart.

Questions, answered

Do imported closed deals affect my reports?

Yes — closed-won deals with amounts and close dates flow straight into revenue reporting, which is exactly what you want if the dates are real and a mess if they defaulted to import day. Verify close dates before, not after.

Can one deal associate to multiple contacts?

The import attaches the association columns you provide — typically one contact and one company per row. Additional associations can be added in the UI, via workflows, or with a follow-up association import if your source data has them.

Should historical deals migrate at all?

Two honest options: import 12–24 months of closed deals for trend reporting, or start clean and keep history in the old system's export. Importing five years of half-maintained deals gets you five years of half-true reports — decide what you'll actually use.

This is a Market Disrupt worksheet, not a vendor file. Import-format templates follow each platform's documented layout as of July 2026 — platforms evolve, so validate against current documentation before a large import.