.png?fit=max&auto=format&n=EQK5eX9kTD8NzWwA&q=85&s=878008bf159fcc4964d0c0d508b6e400)
Before importing, make sure the target pipeline and its stages already exist in Hoop. The import process matches opportunities to existing pipelines and stages by name — it does not create new ones automatically.
Required fields
Every opportunity import requires the following columns in your CSV:| Column | Description | Example |
|---|---|---|
| Contact Email or Phone | Used to associate the opportunity with a contact | jane@example.com |
| Pipeline | The exact name of the pipeline in Hoop | Sales Pipeline |
| Stage | The exact name of the stage within that pipeline | Qualified |
| Opportunity Name | A label for the opportunity | Jane Doe - Enterprise Plan |
Column mapping issues
During the import process, Hoop attempts to auto-map your CSV columns to opportunity fields. If the mapping is incorrect:Review the mapping screen
After uploading your CSV, Hoop displays a column mapping preview. Review each row to ensure the CSV column is mapped to the correct Hoop field.
Manually adjust mismatched columns
Use the dropdown next to each field to change the mapping. Common mismatches include “Company” mapping to “Opportunity Name” or “Value” mapping to “Phone.”
Date format errors
Hoop expects dates in one of the following formats:YYYY-MM-DD(recommended) — for example,2026-03-05MM/DD/YYYY— for example,03/05/2026DD/MM/YYYY— for example,05/03/2026
Import fails with 'invalid date' error
Import fails with 'invalid date' error
Open your CSV in a text editor (not Excel, which may reformat dates) and verify the date column values match one of the accepted formats. Remove any timestamps or timezone suffixes.
Dates are imported with the wrong day/month
Dates are imported with the wrong day/month
This typically occurs when using
DD/MM/YYYY format and Hoop interprets it as MM/DD/YYYY. Use the YYYY-MM-DD format to avoid ambiguity, or select the correct date format on the mapping screen.Pipeline and stage matching
The pipeline and stage names in your CSV must match exactly with the names configured in Hoop, including capitalization and spacing.- “Sales pipeline” will not match “Sales Pipeline” — capitalization matters
- “New Lead ” (with a trailing space) will not match “New Lead” — remove extra whitespace
- If a stage name exists in multiple pipelines, you must include the pipeline column so Hoop can resolve the correct one
Duplicate handling
By default, Hoop identifies duplicate opportunities by matching on contact email and pipeline. When a duplicate is found:- Update existing: The imported data overwrites the existing opportunity fields
- Skip duplicates: The row is ignored and no changes are made
- Create new: A new opportunity is created regardless of existing matches
If you are re-importing a file to correct errors, select Update existing to avoid creating duplicate opportunities in your pipeline.
File size and formatting limits
| Constraint | Limit |
|---|---|
| Maximum file size | 5 MB |
| Maximum rows per import | 10,000 |
| File format | .csv (UTF-8 encoded) |
| Delimiter | Comma only (not semicolons or tabs) |
After the import
Once your import completes:- Check the import summary for the count of created, updated, skipped, and failed records
- Navigate to the target pipeline and verify that opportunities appear in the correct stages
- Open a few individual opportunities to confirm that field data (value, status, custom fields) imported correctly
- If rows failed, download the error report from the import summary to identify and fix the specific issues