Skip to main content

How to Import Opportunities Using a Single CSV File

This article explains how to create or update Opportunities in Kyrios using a single CSV file by uploading, mapping, verifying, and monitoring a bulk import.

Updated over 3 months ago

Who This Is For / When to Use

This article is for users who need to bulk create or update Opportunities in Kyrios instead of entering them manually, such as during data migration, cleanup, or large pipeline updates.


What the Opportunity Import Does

The Opportunity import allows users to create new Opportunities, update existing Opportunities, or do both at once using a single CSV file, while maintaining data accuracy and pipeline structure.

This process supports large datasets, enforces required fields, and provides detailed success, warning, and error reporting after the import completes.


Required File Format and Limits

Opportunity imports require a properly formatted CSV file to process successfully.

File requirements

  • File type: .csv

  • Maximum file size: 30 MB

  • Header row required

  • One Opportunity per row

Important

  • Opportunity imports are not reversible

  • Deleted or overwritten data cannot be automatically restored


Required Fields for Creating Opportunities

When creating new Opportunities, the following fields are required:

  • Contact ID

  • Opportunity Name

  • Pipeline Name

If any required field is missing, that row will fail during import.


Required Fields for Updating Opportunities

When updating existing Opportunities, the following field is required:

  • Opportunity ID

Opportunity IDs can be retrieved by exporting Opportunities from the same Kyrios account.


Default Values Applied During Import

If optional fields are omitted, Kyrios applies the following defaults:

  • Stage: Defaults to the first stage in the selected pipeline

  • Opportunity Value: Defaults to 0

  • Status: Defaults to Open

  • Lost Reason: If a valid lost reason is provided, the status automatically updates to Lost


How to Retrieve Required IDs

Use exports to obtain the correct IDs before importing:

  • Opportunity ID, Pipeline Name, Stage Name: Export Opportunities

  • Contact ID: Export Contacts from the same Kyrios account


Supported Field Formatting

Fields must follow these formats to import correctly.

Date Fields

Accepted formats:

  • mm/dd/yyyy (10/28/2020)

  • yyyy/mm/dd (2020/10/28)

  • mm-dd-yyyy (10-28-2020)

  • yyyy-mm-dd (2020-10-28)

Multiple Select, Checkbox, List Fields

Accepted formats:

  • Value 1, Value 2, Value 3

  • Separators: comma ,, semicolon ;, or period .

Single Select / Radio Fields

Accepted format:

  • Value 1

Opportunity Owner

Accepted format:

  • FirstName LastName
    Example: Logan Paul

Tags

Accepted formats:

  • Tag1, Tag2, Tag3

  • Separators: comma ,, semicolon ;, or period .

Phone Numbers

  • E.164 format preferred: +11234567890

  • US formats also accepted: 123-456-7890, (123) 456-7890

Numeric Fields

Accepted formats:

  • 1.23, 1234, .123

Monetary Fields

Accepted formats:

  • 1234

  • 1,234.33

Opportunity Followers

Accepted format:

  • FirstName LastName, FirstName2 LastName2


Step 1: Start an Opportunity Import

Begin the import from the Opportunities section.

  1. Navigate to Opportunities

  2. Click Import from the top menu


Step 2: Upload the CSV File

Uploading the file prepares it for mapping and validation.

  1. Upload your CSV file

  2. Confirm the upload reaches 100%

  3. Select how to import:

    • Create Opportunities

    • Update Opportunities

    • Create and Update Opportunities


Step 3: Map CSV Columns to Kyrios Fields

Each column must be mapped to the correct Opportunity field.

  1. Review the mapping guide

  2. Map each CSV column to its corresponding field

  3. Confirm all required fields show as mapped

  4. Optionally enable Don’t update empty values to prevent overwriting existing data


Step 4: Verify and Start the Import

Verification confirms the import settings before execution.

  1. Review preferences and mappings

  2. Add optional tags to imported contacts if needed

  3. Click Start Bulk Import


Step 5: Monitor Import Progress

Imports can be tracked from the Bulk Actions page.

  • Status shows as Complete, In Progress, or Failed

  • Each import entry includes a Show Stats option


How to Review Import Statistics

The import statistics panel provides row-level results.

  1. Click Show Stats next to an import

  2. Review:

    • Total processed rows

    • Successful rows

    • Errors

    • Warnings

  3. Export results if needed


Understanding Errors and Warnings

Errors and warnings indicate how rows were processed.

  • Errors: Row failed and was not imported due to missing or invalid required data

  • Warnings: Row imported successfully, but some non-critical fields were skipped


Common Errors and How to Fix Them

Invalid Option for Dropdown or Multiselect Field

Cause: Value does not match available options
Fix: Update the CSV value to match an existing option or add the option before re-importing

Invalid Contact ID

Cause: Contact ID does not exist
Fix: Export Contacts to confirm valid IDs or remove the Contact ID if not required

Could Not Parse Date

Cause: Unsupported date format
Fix: Use one of the supported date formats listed above

Duplicate Unique Property Value

Cause: Duplicate value in a unique field
Fix: Remove duplicates or update existing records instead of creating new ones

Required Fields Missing

Cause: Mandatory fields not included
Fix: Add all required fields and re-import


Pro Tips

  • Enable Don’t update empty values to protect existing data

  • Test imports with a small file before running large imports

  • Use exports to ensure IDs and field values are correct

  • Break very large imports into smaller batches for easier error handling


FAQs

What happens if mandatory fields are missing?
Rows missing required fields fail and are not imported.

Can Opportunities be updated without an Opportunity ID?
No. An Opportunity ID is required to update existing Opportunities.

How do I fix dropdown or multiselect errors?
Ensure CSV values exactly match available options in Kyrios.

How should large imports be handled?
Split large files into smaller batches to simplify troubleshooting.

Did this answer your question?