The only required piece of data to get a Terminus Hub instance up-and-running is the Account data itself. If customers can provide a list of Accounts, with the outlined fields, the Terminus Technical Consultant team can create an Account Hub instance. 

For our list-based Hub configuration, optional data can be provided which will fill in the additional columns and reporting capabilities within an Account Hub instance.


Object File Requirements

  • Each object is contained in it’s own .csv file.
    • File naming convention should reflect exactly what the data it contains (ie. Account.csv, Opportunity.csv, etc)
  • Each file contains the mandatory fields in the correct data type. Mandatory fields include: 
    • Account Name
    • Account Domain/URL
    • Account ID
  • Custom fields to be used in filters and columns are also contained in each record. These may include:
    • Account Segments (Industries/Verticals, Company Size, etc.)
    • Account Tiers
    • Some customers may also have the option to provide details on opportunities/deals, contact, and campaign response data  
  • Unique ID fields of records will be consistent between data file uploads. For example:
    • 18 Character ID for Salesforce
    • 36 Character ID for Dynamics365
  • Each record ingested from the file will be treated as its own record. Terminus will not deduplicate this data after ingesting it into the Account Hub.
  • Character Encoding should be UTF-8


Mandatory Object


Accounts

  • Required Fields + Type:
    • Account/Company ID -> VARCHAR(36)
    • Account Name -> VARCHAR(255)
    • Website -> VARCHAR(255)
  • Recommended Fields + Type:
    • Owner ID -> VARCHAR(36) *If sending us a User object
    • Owner Email -> VARCHAR(255)
    • Owner Name -> VARCHAR(255)
    • Last Activity -> DATETIME
    • Parent Account ID -> VARCHAR(36)
    • Account Type VARCHAR(255)
    • Industry VARCHAR(255)
    • Tier VARCHAR(255)
    • Country VARCHAR(255)
    • Region VARCHAR(255)
    • Territory VARCHAR(255)


Optional Objects that Provide Additional Value


Opportunities

  • Required Fields + Type:
    • Opportunity ID -> VARCHAR(36)
    • Account ID -> VARCHAR(36)
    • Name -> VARCHAR(120)
    • Closed -> CHAR(1)
    • Won -> CHAR(1)
    • Close Date -> DATETIME
    • Created Date -> DATETIME
  • Recommended Fields + Type:
    • Amount -> DECIMAL(12,4)
    • Stage -> VARCHAR(40)
    • Opportunity Type  -> VARCHAR(40)


Contacts

  • Required Fields + Type:
    • Contact ID -> VARCHAR(36)
    • Full Name -> VARCHAR(121)
    • Email -> VARCHAR(80)
    • Account ID -> VARCHAR(36)
    • Created Date -> DATETIME
  • Recommended Fields + Type:
    • Title -> VARCHAR(128)


Leads

  • Required Fields + Type:
    • Lead ID -> VARCHAR(36)
    • Full Name -> VARCHAR(121)
    • Email -> VARCHAR(80)
    • Converted Account ID -> VARCHAR(36)
    • Converted Contact ID -> VARCHAR(36)
    • Created Date -> DATETIME
  • Recommended Fields + Type:
    • Title -> VARCHAR(128)
    • Company -> VARCHAR(255)


Campaigns

  • Required Fields + Type:
    • Campaign ID -> VARCHAR(36)
    • Campaign Name -> VARCHAR(80)
    • Start Date -> DATETIME
    • Created Date -> DATETIME
    • Type -> VARCHAR(40)
  • Recommended Fields + Type:
    • Parent Campaign ID -> VARCHAR(36)


Campaign Responses (Marketing Activities)

  • Required Fields + Type:
    • Response ID -> VARCHAR(36)
    • Campaign ID -> VARCHAR(36)
    • Lead ID -> VARCHAR(36)
    • Contact ID -> VARCHAR(36)
    • Responded -> CHAR(1)
    • Response Date -> DATETIME
    • Created Date -> DATETIME


Sales Activity

  • Required Fields + Type:
    • Activity ID -> VARCHAR(36)
    • User ID -> VARCHAR(36)
    • Lead/Contact ID -> VARCHAR(36)
    • Type -> VARCHAR(40)
    • Created Date  -> DATETIME
    • Subject -> VARCHAR(255)


Users

  • Required Fields + Type:
    • User ID -> VARCHAR(36)
    • Full Name -> VARCHAR(121)
    • Email -> VARCHAR(80)

Database Relationship Visual

image2.png

Was this article helpful?
1 out of 1 found this helpful

Comments

0 comments

Please sign in to leave a comment.