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

Understanding OCC, CRM, and CompanyCam Integration Conflicts

This article explains why integration conflicts can occur when using One Click Contractor (OCC), a CRM, and CompanyCam together. It outlines the root cause of circular job creation, the supported configuration options, and the recommended best practice to avoid data sync issues.

Article Introduction

When One Click Contractor is connected to both a CRM and CompanyCam, integration conflicts can occur if more than one system is responsible for creating jobs or projects. This is a common scenario and is usually caused by circular logic between systems.

At the core of the issue is job creation ownership. If a CRM creates a job in OCC and that same CRM also creates a project directly in CompanyCam, OCC has no reliable way to determine how data should flow between systems. As a result, OCC cannot consistently send data to or receive data from CompanyCam, leading to broken or incomplete integrations.

Supported Configuration Options

There are two primary ways customers attempt to use OCC, a CRM, and CompanyCam together:

Option 1: CRM → OCC → CompanyCam (Supported with limitations)

  • The CRM creates the job in OCC

  • OCC creates the project in CompanyCam

This configuration avoids circular job creation and allows OCC to manage the connection with CompanyCam.

Tradeoff: CompanyCam does not communicate directly with the CRM. Any updates from CompanyCam flow only through OCC.

Option 2: CRM + OCC + CompanyCam all creating jobs (Not supported)

  • The CRM creates jobs in OCC

  • The CRM also creates projects in CompanyCam

This setup creates circular logic and breaks the data flow. OCC cannot determine which system is the source of truth, making reliable syncing impossible.

Recommended Best Practice

In most cases, the recommended approach is to not connect CompanyCam to OCC at all when a CRM is already in use.

This allows:

  • The CRM to remain the single source of truth

  • OCC and CompanyCam to both send data independently to the CRM

  • Fewer sync conflicts and edge cases

  • Clear ownership of job and project data

This configuration provides the most stability and predictability for customers using multiple platforms.

Key Takeaway

When multiple systems are involved, fewer direct integrations usually lead to better results. Keeping the CRM as the source of truth and limiting cross-platform dependencies helps avoid circular logic, data conflicts, and broken workflows.