Integration
Salesforce
Sales and marketing work on the same contact instead of two versions of it. Contacts, accounts and activity sync in both directions.
- Area
- CRM system
- Direction
- Two-way between Salesforce and Caymland M4
- Cadence
- Scheduled sync, changes additionally in real time
- Vendor
- salesforce.com
One contact, two systems, one truth.
Both directions.
Contacts go to Salesforce, leads and accounts come back.
Sales sees the response.
Opens, clicks and form submissions appear on the Salesforce record.
No duplicates.
Every contact keeps its Salesforce id and is updated rather than created twice.
Sales knows something your marketing does not. And the other way round
In most businesses running Salesforce, two versions of the truth sit side by side. The CRM holds what sales recorded: call notes, stage, ownership, likelihood to close. Marketing holds what the person actually did: which email they opened, which link they clicked, which form they filled in.
Both describe the same person. They are rarely brought together, and when they are, someone does it by hand.
The Salesforce integration for Caymland M4 syncs both sides automatically — in both directions, with nobody exporting, importing or retyping.
What the integration gives you
- One contact instead of two index cards. Whoever is maintained in Salesforce is the same person in Caymland M4, and the other way round.
- Sales sees the response. Opens, clicks and form submissions appear on the Salesforce record without anyone having to ask.
- Marketing sees reality. Stage, ownership and account membership are available as filters and triggers.
- Keep your campaigns. Existing Salesforce campaigns and their members can be used as an audience.
- No duplicates. Matching runs on the Salesforce id, not on similar-looking names.
What gets synced
Objects:
| Object | Content |
|---|---|
| Lead | Prospects not yet qualified |
| Contact | People belonging to existing accounts |
| Account | Companies, linked to their people |
| Campaign | Campaigns and their members, read only |
Per person:
| Field | Content |
|---|---|
| Id | The Salesforce record id, as the lasting link |
| Name | First and last name, salutation, job title |
| Also used for matching | |
| Phone | Landline and mobile |
| Company | A text field on leads, a link to the account on contacts |
| Address | Street, town, postcode, country |
| Ownership | Who owns the record in Salesforce |
Which Salesforce field maps to which field in Caymland M4 is yours to set, per object. Custom fields on either side can be included without anyone writing code.
How the sync works
Direction: two-way. Contacts from Caymland M4 are written to Salesforce; leads, contacts and accounts from Salesforce are picked up. Which side wins on conflicting values is your decision.
Timing: the sync collects what changed in Salesforce on a schedule, in the background. Changes to a contact in Caymland M4 additionally go out straight away, so sales does not wait for the next run.
Matching: every record carries its Salesforce id. On the next run the same record is recognised and updated. No duplicates are created, not even for people who have been worked on in both systems for years.
Activity flows back. What a person did in marketing is written to the Salesforce record as activity. Sales sees what they responded to before picking up the phone.
Origin stays visible. Every contact created this way is marked as having come from Salesforce.
What this means for your data
The connection uses OAuth 2.0. No user passwords are stored. Access is granted in Salesforce and can be withdrawn there at any time, without anyone changing a password.
You set the scope. Which objects are synced and which fields travel is your decision. What you do not map is not transferred.
The rest holds as everywhere in Caymland M4: all data on a person sits in one profile, can be viewed, exported and deleted, every change is logged, and operation in Switzerland or the EU is possible.
Requirements
On the Salesforce side:
- A Salesforce edition with API access
- A connected app with a key and secret for OAuth 2.0
- A user with read access to the objects being synced, and write access wherever data is written back
On the Caymland M4 side:
- Enable the Salesforce integration and store the credentials. They are kept encrypted
- Decide which objects are synced
- Set the field mapping per object once
- Set the schedule for the sync
Setting this up is an appointment, not a project.
What this looks like day to day
Sales calls prepared. A lead opens the same pricing page three times. The activity sits on the Salesforce record, the owner sees it in their list and calls the same day instead of next week.
Marketing addresses the right people. A campaign goes only to contacts sitting at the evaluation stage in Salesforce and owned by a particular rep. The audience keeps itself current because it follows the stage in the CRM.
Existing customers stay out of it. Anyone recorded as a customer in Salesforce no longer receives the new-business sequence. The boundary is drawn by the CRM, with nobody maintaining lists.
Questions & answers
Frequently asked questions about this integration
Which system wins when the data disagrees?
You decide. By default Salesforce wins, because in most businesses that is where the maintained master record lives. The direction can be set differently per field.
Are accounts synced as well?
Yes. Alongside leads and contacts, accounts are picked up and linked to the people who belong to them.
What happens to contacts that already exist in both systems?
They are recognised through the stored Salesforce id and merged. No second record is created.
Can we see in Salesforce what marketing did?
Yes. Activity such as email opens, clicks and form submissions is written back to Salesforce and sits on the record.
Can we keep using our Salesforce campaigns?
Yes. Campaigns and their members are read and can be used as an audience in Caymland M4.
How is the connection secured?
Through OAuth 2.0. No user passwords are stored, and access can be withdrawn in Salesforce at any time.
