Fix Import Errors

Overview¶

Import not working? This guide helps you identify and fix common import errors step by step.

How Import Validation Works¶

After uploading your file and mapping columns, Grovana validates your data:

1. Validation runs — Grovana checks each row for errors
2. Errors are highlighted — problematic rows appear in yellow
3. You can fix in-place — edit cells directly in the import UI
4. Or remove rows — skip problematic records entirely

Step-by-Step Troubleshooting¶

Step 1: Identify the Error Type¶

Click on a highlighted row to see the specific error message. Common error types:

Step 2: Fix the Error¶

Follow the specific instructions below for each error type.

Error: Duplicate Value¶

What You'll See¶

Rows with duplicate values are highlighted in yellow in the import UI before the import starts.

What It Means¶

A unique field (email, domain) either:

• Already exists in Grovana
• Appears twice in your file

How to Fix¶

Option 1: Edit the duplicate value

1. Click the cell with the error
2. Change to a unique value
3. Continue with import

Option 2: Remove the duplicate row

1. Click the X next to the row
2. The row will be skipped during import

Option 3: Let Grovana update the existing record

1. Ensure your file includes a unique identifier (email, domain, or id)
2. Map the unique identifier field
3. Grovana will update the existing record instead of creating a duplicate

How to Prevent This Error¶

Before importing:

1. Sort your spreadsheet by the unique field
2. Remove duplicate rows
3. Check if records already exist in Grovana

For more details: Uniqueness Constraints

Error: Invalid Format¶

What You'll See¶

The cell value is highlighted in yellow. Hover over it to see the error message:

{field name} is not a valid {field type}

What It Means¶

The data doesn't match the expected format for that field type.

How to Fix — By Field Type¶

Email¶

Problem: Invalid email format Solution: Use format [email protected]

❌ john.smith@
❌ john [email protected]
✓ [email protected]

Domain¶

Problem: Inconsistent format may cause duplicates Solution: Use https://domain.com format (recommended)

⚠️ acme.com         (valid, but not recommended)
⚠️ www.acme.com     (valid, but not recommended)
✅ https://acme.com  (recommended)

Date¶

Problem: Unrecognized date format Solution: Use YYYY-MM-DD format consistently throughout file

✓ 2024-03-15        (YYYY-MM-DD)
❌ 03/15/2024        (MM/DD/YYYY)
❌ 15/03/2024        (DD/MM/YYYY)

Phone¶

Problem: Missing required columns Solution: Include all phone columns

Boolean¶

Problem: Wrong boolean value Solution: Use uppercase TRUE or FALSE

❌ true
❌ yes
❌ 1
✓ TRUE
✓ FALSE

Select / Multi-Select¶

Problem: Value doesn't match existing options Solution: Use API names, not display labels

How to find API names:

1. Go to Settings → Data Model
2. Select the object and field
3. Enable Advanced mode (toggle at bottom right)
4. Use the API name (e.g., OPTION_1, not "Option 1")

❌ High Priority
✓ HIGH_PRIORITY

Currency¶

Problem: Missing amount or currency code Solution: Fill both columns

Number¶

Problem: Non-numeric characters Solution: Numbers only, period for decimals

❌ $1,234.56
❌ 1,234.56
✓ 1234.56

For complete format reference: Field Mapping

Error: Required Field Missing¶

What You'll See¶

The row is highlighted in yellow with the required field cell marked.

What It Means¶

A required field is empty for this row.

How to Fix¶

Option 1: Enter a value

1. Click the empty cell
2. Enter a value
3. Continue with import

Option 2: Remove the row

1. If you don't have the data, click X to skip the row

How to Prevent This Error¶

Before importing, identify required fields:

1. Go to Settings → Data Model
2. Select your object
3. Check which fields are marked as required

Error: Relation Not Found¶

What You'll See¶

This error appears after the import starts — the import fails with a message like:

Can't connect to company. No unique record found with condition: id = 7776ee49-f608-4a77-8cc8-6fe96ae1e43f

This means there is no Company in Grovana with that specific identifier.

What It Means¶

You're trying to link to a record that doesn't exist in Grovana.

How to Fix¶

Option 1: Import parent records first

1. Cancel the current import
2. Import the parent records (e.g., Companies)
3. Then import the child records (e.g., People)

Option 2: Fix the reference value

1. Check the reference value in your file
2. Ensure it exactly matches an existing record
3. Verify format: domains should be https://domain.com

Option 3: Remove the relation

1. Clear the cell to import without the relation
2. Add the relation manually later

How to Prevent This Error¶

1. Import in the correct order:

   • Companies first
   • People second (with company references)
   • Opportunities third

2. Verify reference values:

   • Export parent records to get exact identifiers
   • Use domain format https://domain.com
   • Check for typos and case sensitivity

For more details: Import Relations

Error: File Too Large¶

What You'll See¶

This error appears when uploading your file — the upload is blocked entirely:

Too many records. Up to 10000 allowed

You won't be able to proceed to the data review step until you reduce the file size.

What It Means¶

Your file has more than 10,000 records.

How to Fix¶

Option 1: Split into multiple files

1. Divide your data into files of 10,000 records or fewer
2. Import each file separately
3. Maintain import order (Companies before People)

Option 2: Ask for migration support Ask your administrator or implementation partner to plan a larger migration and verify the imported records.

Error: Field Not Recognized¶

What It Means¶

A column in your file can't be mapped because the field doesn't exist in Grovana.

How to Fix¶

1. Go to Settings → Data Model
2. Select the object you're importing
3. Click + Add field
4. Create the custom field with the appropriate type
5. Re-upload your file

Error: User Relation Empty¶

What It Means¶

You're trying to assign a record to a user (Owner, Assignee) but the relation isn't being mapped.

Common Causes¶

1. User hasn't accepted their invitation — the user doesn't exist in Grovana yet
2. Using user ID from old system — Grovana can't match IDs from another system
3. Wrong email format — the email doesn't match the user's Grovana account

How to Fix¶

1. Ensure all users have accepted their invitation to your Grovana workspace
2. Use the user's email address (not their name or old system ID)
3. Use the same email they used to join Grovana

Pre-Import Checklist¶

Avoid errors by checking these before importing:

File Requirements¶

Data Quality¶

Field Formats¶

Relations¶

Data Model¶

Still Having Issues?¶

If you've tried the above solutions:

1. Download the sample file — see the exact format Grovana expects
2. Export existing records — compare your file to working data
3. Test with a small batch — try 5-10 rows first
4. Check the reference articles:
   • Field Mapping
   • Uniqueness Constraints
   • Import Relations
   • Error Handling