Import Opportunities from CSV
Bring your pipeline into UpSight so opportunity coaching, reconciliation, and next-step tracking start from day one.
Use these templates to accelerate import setup and preserve clean mappings.
Current path: chat-assisted import via the Ops agent using importOpportunitiesFromTable after a spreadsheet parse.
This supports fast onboarding for pipeline data without requiring direct API payload construction.
| CSV Field | Format to Enter | Example |
|---|---|---|
opportunity_name | Free-text deal name | Acme Enterprise Expansion |
account | Company/account name text | Acme Inc |
amount, currency | Numeric amount + 3-letter currency | 125000, USD |
stage | Stage label text | Discovery |
close_date | ISO date (YYYY-MM-DD) | 2026-07-15 |
confidence / probability | 0-1 decimal or percentage | 0.65 or 65% |
next_step | Short action text | Schedule security review |
source | Lead source label | Inbound Demo |
crm_external_id | External deal ID | SFDC-OPP-1001 |
description | 1-2 sentence summary | Expansion across 3 departments |
forecast_category | Forecast bucket label | Commit |
contact_name/contact_email | Contact full name + email | Jane Chen / [email protected] |
owner | Owner full name or work email | Alex Morgan |
pipeline | Pipeline label text | Enterprise New Biz |
created_date | ISO date (YYYY-MM-DD) | 2026-04-20 |
Linking is best-effort
contact_name/contact_email and owner are matched against existing People and account users — no auto-create. Imports won't fail if a contact or owner isn't found; the opportunity just won't be pre-linked.
How updates and overwrites work
Current opportunity import path creates new opportunities and skips duplicate rows when crm_external_id already exists. It does not perform field-level upsert/overwrite like People import yet.
- Include
opportunity_namefor every row. - Include
crm_external_idto prevent duplicates. - Use consistent stage labels for clean kanban/pipeline reporting.
- Use ISO date format (
YYYY-MM-DD) for close dates.