Skip to main content

​
Requirements: Read First

1
Column names must appear as written below
2
Contact Type must be one of the following: account, contact, lead, or prospect
3
One one employee name (Relationship Manager) can be associated with each contact row

​
Required fields

  • contact_id (String) OR  email (String) - Unique identifier for contact; should be a consistent value across imports used to identify a contact. The import needs to be able to identify duplicate names by using either the Contact ID or Email as a way to identify the contact. For example, if there are multiple contacts named John Smith, a unique email address or Contact ID is required to accurately differentiate them.
    • Contact ID: Assigned via a CRM as a way to uniquely identify a contact
    • Examples: 12345, camoag@example.com
  • name (String) - Contact name

​
Optional fields

  • email (String) - Contact email (optional only if a contact id is used)
  • contact_type (String) - Contact type. Defaults to ‘contact’
    • Must be one of: account, contact, lead, or prospect
  • date_of_birth (String) - YYYYMMDD date of birth. Used if actual date of birth is known
    • Examples: 19800101
  • approximate_date_of_birth (String) - YYYYMMDD approximate date of birth. Used to approximate age, dynamically as time goes on
    • Examples: 19800101
  • network_id (String) - See documentation on Networking. Used to group contacts under the same network
    • Examples: 12345
  • network_name (String) - See documentation on Networking. Used as the network name, either in conjunction with network_id above or used as network name should this contact be chosen as the network primary contact
    • Examples: Acme Seed Company
  • market_segments (String) - Names of marketing segments associated with the contact. If more than one, values should be pipe delimited (”|”)
    • Examples:
      • Resolute Defenders
      • Resolute Defenders|Innovators|Young Beginning Farmer
  • products (String) - List of product names associated with the contact. If more than one, values should be pipe delimited (”|”)
    • Examples:
      • Real Estate Loans
      • Real Estate Loans|Crop Insurance
      • Seed|Fertilizer
  • product_ids (String) - List of product IDs associated with the contact. If more than one, values should be pipe delimited (”|”). These can be thought of as external product IDs, SKUs, codes, etc. Note: only use one of either products or product_ids; if using these, must use our product import to assure these exist in the system.
    • Examples:
      • 1234xyz
      • 1234xyz|5678def
      • 12345678
Phone numbers
  • primary_phone (String) - Contact primary phone number. Any formatting or extra spaces will be removed in favor of consistent platform formatting
    • Examples: 5551234567, (555) 123 4567
  • secondary_phone (String) - Contact secondary phone number. Any formatting or extra spaces will be removed in favor of consistent platform formatting
    • Examples: 5551234567, (555) 123 4567
  • home_phone (String) - Contact home phone number. Any formatting or extra spaces will be removed in favor of consistent platform formatting
    • Examples: 5551234567, (555) 123 4567
  • mobile_phone (String) - Contact mobile phone number. Any formatting or extra spaces will be removed in favor of consistent platform formatting
    • Examples: 5551234567, (555) 123 4567
  • business_phone (String) - Contact business phone number. Any formatting or extra spaces will be removed in favor of consistent platform formatting
    • Examples: 5551234567, (555) 123 4567
Addresses Addresses should be provided either broken out by address components or a single address string (e.g. “123 Main St, Anytown, IL, 12345”), but not both. Billing
  • billing_address (String) - Contact billing address, as single line
    • Examples: 123 Main St, Anytown, IL, 12345
OR 
  • billing_address_line_1 (String) - Contact billing address line one
    • Examples: 123 Main St
  • billing_address_line_2 (String) - Contact billing address line two
    • Examples: Suite 400
  • billing_address_city (String) - Contact billing address city
    • Examples: Anytown
  • billing_address_state (String) - Contact billing address state
    • Examples: IL
  • billing_address_zipcode (String) - Contact billing address zipcode
    • Examples: 12345
Shipping
  • shipping_address (String) - Contact shipping address, as single line
    • Examples: 123 Main St, Anytown, IL, 12345
OR 
  • shipping_address_line_1 (String) - Contact shipping address line one
    • Examples: 123 Main St
  • shipping_address_line_2 (String) - Contact shipping address line two
    • Examples: Suite 400
  • shipping_address_city (String) - Contact shipping address city
    • Examples: Anytown
  • shipping_address_state (String) - Contact shipping address state
    • Examples: IL
  • shipping_address_zipcode (String) - Contact shipping address zipcode
    • Examples: 12345
Primary
  • primary_address (String) - Contact primary address, as single line
    • Examples: 123 Main St, Anytown, IL, 12345
OR 
  • primary_address_line_1 (String) - Contact primary address line one
    • Examples: 123 Main St
  • primary_address_line_2 (String) - Contact primary address line two
    • Examples: Suite 400
  • primary_address_city (String) - Contact primary address city
    • Examples: Anytown
  • primary_address_state (String) - Contact primary address state
    • Examples: IL
  • primary_address_zipcode (String) - Contact primary address zipcode
    • Examples: 12345
Relationship Manager
  • employee_email (String) - Email of employee relationship/account manager of contact
  • employee_id (String) - Unique ID of employee relationship/account manager of contact. Employee emails must all have identical employee IDs
    • Examples: 12345
  • employee_name (String) - Employee relationship/account manager name of contact
    • Examples: John Sales
Last modified on May 22, 2026