Field Mapping

How Field Mapping Works¶

When you upload a file, Grovana analyzes your columns and attempts to match them to existing fields.

Automatic Mapping¶

Grovana tries to match columns based on:

• Column header names (exact or similar matches)
• Data type detection (dates, numbers, emails)
• Common field patterns

Manual Mapping Options¶

For each column, you can:

• Map to a field: Select the matching Grovana field from a dropdown
• Do not map: Skip the column entirely (data won't be imported)

Field Type Compatibility¶

All field types available in the Data Model are supported for import.

You can also import id values to either assign a specific ID to new records or update existing ones.

Data Format Requirements¶

Address Fields¶

Address is a nested field with multiple columns. Some can be left empty.

• Address / Address 1: Street address line 1
• Address / Address 2: Street address line 2
• Address / City: City name
• Address / State: State or province
• Address / Country: Country name
• Address / Post Code: Postal/ZIP code

Array Fields¶

Use the following format:

["value1","value2"]

Boolean Fields¶

Use TRUE or FALSE (uppercase) - not true or false

Currency Fields¶

Currency is a nested field with two columns that both must be filled:

• Amount / Amount: The numeric value (e.g., 1234.56)
• Amount / Currency: The currency code (e.g., USD, EUR)

Date Fields¶

Supported formats:

• YYYY-MM-DD (recommended)
• MM/DD/YYYY
• DD/MM/YYYY
• ISO 8601 format

Domain Fields¶

• It is recommended to use the format https://domain.com to avoid creating duplicates, as this is the format used for Companies created by the mailbox and calendar synchronizations
• A Domain Label and Domain URL can be filled: best practice is to fill domain.com in the label and https://domain.com in the url
• Domains must be unique within the Companies object
• Domains must be unique within the file to import

Email Fields¶

• Must be valid email format
• Emails must be unique within the People object
• Emails must be unique within the file to import
• For additional emails: use Emails / Primary Email for the main email, and Emails / Additional Emails with this format:

["[email protected]","[email protected]"]

ID Fields¶

Specifying an id during import is optional. Grovana auto-generates one if not provided.

Use cases for mapping an id column:

• Set a specific ID: Choose the UUID for newly created records
• Update existing records: Match against existing records to update them instead of creating duplicates. In that case, it is recommended to not map the other unique fields: mapping only one unique field ensures a smoother import.

JSON Fields¶

Use valid JSON format:

{"key":"value","key2":"value2"}

Links Fields¶

Similar to Domain fields:

• Fill both the label and URL columns: Links / Link URL and Links / Link Label
• Use full URL format: https://example.com
• For secondary links, use Links / Secondary Links column with this format:

[{"url":"https://grovana.ai","label":"Grovana"}]

Multi-Select Fields¶

Use the API names (not the display labels) in the following format:

["VALUE1","VALUE2"]

See here where to find the API names.

Number Fields¶

• Numbers only
• Decimals use period: 1234.56
• No thousands separators

Phone Fields¶

Phone is a nested field with multiple columns that must be filled

• Phones / Primary Phone Number: The phone number (e.g., 4159095555)
• Phones / Primary Phone Country Code: Country code (e.g., US)
• Phones / Primary Phone Calling Code: Dialing code (e.g., +1)

Rating Fields¶

Use the API name format: RATING_1, RATING_2, RATING_3, RATING_4, RATING_5

Relation Fields¶

Please see our dedicated article: Import Relations Between Objects

Select Fields¶

Use the API name of the option (not the display label):

VALUE1

See here where to find the API names.

Text Fields¶

• No special formatting required
• Leading/trailing spaces are trimmed

Finding API Names¶

For Select, Multi-Select, and Array fields with predefined options, you must use the API names, not the 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 the bottom right of the settings page)
4. View the API name for each option