Two way
Both systems stay the same. Every sync runs from the leading system into the other, then back.
- You pick whether Keap or ServiceM8 leads
- Changes on either side travel
- Nothing bounces back and forth
CRM Connector Platform
Won in Keap, on the board in ServiceM8
Contacts stay the same both ways. A won Keap opportunity becomes a ServiceM8 work order for the same client, and a Keap tag can show who has had work completed.
- Official sign in for both
- Either system can lead
- 7 day free trial
Contacts both ways, won opportunities into work orders
- Contacts
- Won opportunities into work orders
At a glance. Contacts stay the same. A won opportunity becomes a work order.
Your choice
Two way or one way
Keep both systems identical, or let one feed the other. You decide per record type.
One way
One system feeds the other. Pick Keap or ServiceM8 as the source; the other receives.
- Good for a migration, in either direction
- A read copy for a colleague or partner
- Switch a record type to two way later
Fine tune it:Only opportunities won from a date you pickOnly opportunities above an amount you pickOnly Keap contacts with a tag you pick, on a one way syncEveryone, customers only or leads only, when ServiceM8 sendsA Job completed tag in Keap, a switch you turn onEvery 30 minutes up to every 3 days
Record by record
What travels, and what each change does
Pick a record type and the system where a change starts. On the left, which field matches which and when it travels; on the right, what that change does on the other side.
Starts in
Fields- First nameBoth waysFirst name
- Last nameBoth waysLast name
- CompanyWhen createdClient name
- Email, first slotBoth waysEmail
- Phone, first slotBoth waysPhone
- Billing street, city and postal codeBoth waysStreet, city and postal code
- State and countryWhen createdState and country
- TagsOnly in KeapNot in ServiceM8
It happens in Keap, then in ServiceM8
A new contact
Looked for in ServiceM8 on the contact email before a client is created.
Name, email, phone or street changes
The same change is made to the ServiceM8 client on the next sync.
A phone is emptied
Not carried: ServiceM8 keeps the phone it has.
The company changes later
Not carried: the company reaches ServiceM8 when the client is created.
The state or country changes later
Not carried: Keap sets state and country when the contact is created.
- Before anything is created the other system is searched first, so nobody is created twice.
- ServiceM8 client names are unique, so a taken name gets the email, else the phone, else the Keap record id added in brackets.
- Tags that follow the money, only when you switch them on: the Keap contact gets the tag "Job completed" once a ServiceM8 job of theirs is completed, and it stays. Missing tags are created, every other tag stays, and none is renamed or deleted. With Keap as the source contacts must sync both ways. Tags start campaigns and automations in Keap, so check which ones listen first.
How a sync runs
One sync, step by step
What happens every time the integration runs, in the order it really happens. Pick which system leads and watch the records move.
Which system leads?
Connections
CRM
Step 1 of 8
Both connections are checked
Credentials for Keap and ServiceM8 are checked and sign in tokens refreshed automatically. If a connection was removed on either side, the integration pauses and you get one message with a reconnect button.
Conflicts
When both sides changed the same record
- For each two way record type you choose whether Keap or ServiceM8 leads. The leading side always runs first in a sync.
- It only matters when the same record changed in both systems between two syncs. Every other change simply travels.
- A record is never moved backwards by a sync: a paid invoice is not reopened, a decided quote is not undecided.
Between two syncs
The first name of the same client is changed in both systems
Leading system
KateKatherineTwo different values. Run the sync to see which one both systems end up with.
Good to know
What is particular to this pair
What holds for Keap or ServiceM8 on its own is on its own page.
- Only won opportunities become work
ServiceM8 jobs do not travel into Keap; completion and invoicing stay in ServiceM8.
FAQ
Questions about Keap and ServiceM8?
Every answer below is true for the app as it runs today. If something is not covered, ask us and we will answer in plain words.
Contacts, yes: they sync in both directions and you choose which system leads when the same person changed on both sides.
No. Only one that reaches your won stage does, and only when it was won on or after your start date. Open and lost opportunities stay in Keap.
Yes, with a switch that is off until you turn it on. The contact gets the tag "Job completed" once a ServiceM8 job of theirs is completed, and it stays. Tags start Keap campaigns, so check which ones listen first.
Contacts and tags do. Everything about opportunities needs Keap Max Classic, because Keap opens opportunities to other apps only on that edition. On Keap Pro and Max the opportunity rows stay empty and contacts keep syncing.
No. Before anything is created in Keap or ServiceM8, the platform looks for the same record first and updates that one instead. Records synced before stay linked.
The platform notices on the next sync, pauses the integration and sends you one message with a reconnect button. Reconnecting takes one step, and syncing picks up where it left off without creating anything twice.
From every 30 minutes up to every 3 days, depending on your plan. Every plan includes a 7 day free trial.
Ask your AI assistant
Ask ChatGPT or Claude what this pair can do
Add CRM Connector to the assistant you use and ask in your own words. It answers from the same rules the platform runs, and needs no CRM Connector account. For example: “With CRM Connector Platform, what can I sync between Keap and ServiceM8?”
ChatGPT
Claude
Get started
Ready to connect Keap and ServiceM8?Start your 7 day free trial
Sign in to Keap and ServiceM8, pick which one leads or sync one way, confirm what syncs, and watch the first sync run.