Skip to content
English
Customer portal
Go to One Click Contractor
  • There are no suggestions because the search field is empty.

JobProgress Integration - Data Mapping

Overview of data field mapping between JobProgress and One Click Contractor

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

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: job.customer.first_name job.customer.last_name
  • OCC Field: name | SF Field: job.name OR customer_name if blank
  • OCC Field: email | SF Field: job.customer.email
  • OCC Field: lead_source | SF Field: NOT PROVIDED
  • OCC Field: metadata.jobprogress_job_id | SF Field: job.id
  • OCC Field: metadata.jobprogress_customer_id | SF Field: job.customer.id

Job Address

  • OCC Field: line_1 | SF Field: job.address.address
  • OCC Field: line_2 | SF Field: job.address.address_line_1
  • OCC Field: city | SF Field: job.address.city
  • OCC Field: state | SF Field: job.address.state.name
  • OCC Field: postal_code | SF Field: job.address.zip

Job Phone (Multiple records are created if available)

Job Phone

  • OCC Field: name | SF Field: Customer.Phones.label
  • OCC Field: number | SF Field: Customer.Phones.number

Job Appointments (Can be Multiple)

Appointment

  • OCC Field: summary | SF Field: Appointment.title
  • OCC Field: notes | SF Field: Appointment.description
  • OCC Field: start_time | SF Field: Appointment.start_date_time
  • OCC Field: end_time | SF Field: Appointment.end_date_time
  • OCC Field: metadata.jobprogress_customer_id | SF Field: Appointment.customer_id
  • OCC Field: metadata.jobprogress_user_id | SF Field: Appointment.user_id
  • OCC Field: metadata.jobprogress_job_id | SF Field: Appointment.jobs.data[0].id