JobNimbus - Data Mapping

The following is a detailed listing of the data fields and how they map between JobNimbus and One Click.

There are 2 ways you can integrate between One Click and JobNimbus. One is as a "Contact" and the other is as a "Job". The mappings of each variety are listed in detail below.

Contact

When configured as a contact, the fields are mapped as follows:

User Object Linking

User

OCC Field: crm_id | SF Field: User.id
OCC Field: email | SF Field: User.email

Job Object

Job

OCC Field: customer_name | SF Field: Contact.first_name contact.last_name
OCC Field: name | SF Field: Contact.first_name contact.last_name
OCC Field: email | SF Field: Contact.email
OCC Field: lead_source | SF Field: Contact.source_name
OCC Field: metadata.job_nimbus_job_id | SF Field: NIL
OCC Field: metadata.job_nimbus_contact_id | SF Field: Contact.jnid
OCC Field: metadata.job_nimbus_user_id | SF Field: User.crm_id

Job Address

OCC Field: line_1 | SF Field: Contact.address_line1
OCC Field: line_2 | SF Field: Contact.address_line2
OCC Field: city | SF Field: Contact.city
OCC Field: state | SF Field: Contact.state_text
OCC Field: postal_code | SF Field: Contact.zip

Job Phone (Multiple records are created if available)

Job Phone

OCC Field: name | SF Field: Contact.primary.type
OCC Field: number | SF Field: Contact.primary.type

Job Appointments (Can be Multiple)

Appointment

OCC Field: summary | SF Field: JobTask.title
OCC Field: notes | SF Field: JobTask.description
OCC Field: start_time | SF Field: JobTask.date_start
OCC Field: end_time | SF Field: JobTask.date_end or start_time + 2 Hours and converted based on the company's time zone
OCC Field: metadata.job_nimbus_event_id | SF Field: JobTask.jnid

Job

The following is a detailed listing of the data fields and how they map between MarketSharp and One Click.