---
title: "CRM System Integrations"
slug: "crm-system-integration"
updated: 2023-11-02T13:27:43Z
published: 2023-10-12T14:05:38Z
canonical: "wiki.cobblestonesoftware.com/crm-system-integration"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://wiki.cobblestonesoftware.com/llms.txt
> Use this file to discover all available pages before exploring further.

# CRM System Integration with CobbleStone Software

## CRM Integrations

CRM systems are systems that can perform many important functions. Some examples of popular CRM systems are Oracle NetSuite, [**Salesforce**](/v1/docs/salesforce), HubSpot, and Monday.com.

#### Common Use Case Scenarios

Typically, these CRM systems are integrated with the CobbleStone® platform to provide a myriad of functions. Some of the typical use case scenarios are: **(****diagrams below****)**

- Syncing Customer/Vendor Metadata between systems
- Syncing Contract/Contract Requests between systems
- Syncing Purchase Order/Invoicing between systems
- Automating workflow between systems
  1. Ex: Signed Contract in CobbleStone® triggers a Purchase Order in NetSuite
  2. Ex: New Opportunity in Salesforce triggers a Contract Request in CobbleStone®

#### Setup

Once connections are established linking the CobbleStone® platform with the client’s CRM system, the integration setup can commence.

Each system has its records identified by an Internal key. CobbleStone® will automatically auto-increment new records and assign them their own unique identifier (i.e. : 1st new vendor “123 Company” will have VendorID 1 when created. No new vendor records will have that VendorID). The same process applies to the records created within CRM systems (i.e. : Salesforce creates a Salesforce Account ID for new records within the system).

For the integration to properly function, a record sync must be performed. The unique identifier for a record must be appended to the correct record between systems. If a system cannot correctly identify existing records, the results are normally erroneous (i.e. : duplicate records, incorrect amendments, etc.).

To ensure that these keys match up, there are actions that can be taken:

- New fields must be created to store external record identifiers (Ex: Salesforce Account ID created in CobbleStone® system/CobbleStone® Vendor ID created in Salesforce)
- CSV Files containing the unique identifiers for records from one system matched to records in the integrated system and imported to be stored on those records

#### Integration Maintenance

To ensure ongoing automation and accuracy with these integrations, record syncing must remain constant. Depending on the frequency of record changes in a system, the frequency of the sync of the records between the systems must match.

Ex: New Opportunities in Salesforce need to be mapped into CobbleStone® as quickly as possible so proper steps can be taken. These triggers should be set to trigger in real-time when the Opportunity is created or updated or in intervals checking for new or updated Opportunities every 5-10 minutes.

Ex: Vendor records in a client’s Salesforce system rarely change. The sync of record metadata between that system and CobbleStone® system doesn’t need to happen as frequently. A daily or weekly sync may be all that is necessary.

#### CRM Systems Common Functionality Diagrams

![](https://cdn.document360.io/e3626857-1fb5-4e27-b278-2d3fc5508be4/Images/Documentation/image-1663175643300.png)

![](https://cdn.document360.io/e3626857-1fb5-4e27-b278-2d3fc5508be4/Images/Documentation/image-1663175653698.png)

![](https://cdn.document360.io/e3626857-1fb5-4e27-b278-2d3fc5508be4/Images/Documentation/image-1663175673568.png)

![](https://cdn.document360.io/e3626857-1fb5-4e27-b278-2d3fc5508be4/Images/Documentation/image-1663175687661.png)

![](https://cdn.document360.io/e3626857-1fb5-4e27-b278-2d3fc5508be4/Images/Documentation/image-1663175696153.png)

![](https://cdn.document360.io/e3626857-1fb5-4e27-b278-2d3fc5508be4/Images/Documentation/image-1663175703588.png)