Two way
HighLevel starts the integration and changes made in ServiceM8 flow back into HighLevel as well.
- You pick whether HighLevel or ServiceM8 leads in a conflict
- Changes on either side travel
- Nothing bounces back and forth
CRM Connector Platform
ServiceM8 and HighLevel, kept in step both ways
HighLevel captures leads and books appointments, ServiceM8 runs jobs and the schedule in the field. CRM Connector keeps the contacts and appointments the same in both, so nobody retypes a record.
- Private Integration Token for HighLevel
- Either system can lead
- 7 day free trial
Two way, or one way if you prefer
- Contacts
- Appointments
At a glance. Contacts and appointments stay the same on both sides. Below: which field matches which, and what every change does.
Your choice
Two way or one way
Keep both systems identical, or let one feed the other. You decide per record type.
One way
HighLevel feeds ServiceM8 and ServiceM8 changes stay in ServiceM8.
- HighLevel stays the source of truth
- ServiceM8 always has the latest customers
- Switch to two way later
Fine tune it:A different choice per record typeOnly invoices from a date you pickOnly sent or paid invoicesEveryone, customers only or leads onlyEvery 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- Client nameWhen createdBusiness name
- Contact first nameBoth waysFirst name
- Contact last nameBoth waysLast name
- Contact emailBoth waysEmail
- Contact mobileBoth waysPhone
- Address line 1Both waysAddress
- Address line 2Only in ServiceM8Not in HighLevel
- City, state, postcodeBoth waysCity, state, postal code
- CountryWhen createdCountry
- Has completed jobsEach works it outContact type
- Not in ServiceM8Only in HighLevelSource
It happens in ServiceM8, then in HighLevel
A new contact
Looked for in HighLevel with its own duplicate check, email first, then phone, and updated when found. A phone number that belongs to somebody with another email is left off the new contact, so two people are never merged.
Name, email, phone and address change
The same change is made to the HighLevel contact on the next sync.
Company and country change later
Not carried: HighLevel takes these only when the contact is created.
A contact without email or phone
Not written into HighLevel: it needs an email address or a phone number on every contact.
- Some fields travel once, when the record is created: HighLevel takes these only when the contact is created.
- Before anything is created the other system is searched first, so nothing is created twice.
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 ServiceM8 and HighLevel 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 ServiceM8 or HighLevel 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 phone number of the same client is changed in both systems
Leading system
+1 415 555 0101+1 415 555 0199Two 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 ServiceM8 or HighLevel on its own is on its own page.
- HighLevel starts the integration
- It can only be the source; ServiceM8 changes still flow back on two way.
- Company and country on create
- Later changes stay in the system where they were made.
- Address line 2 stays in ServiceM8
- HighLevel has no such field.
- Not run live yet
- Built on the same proven engine as the other pairs.
FAQ
Questions about ServiceM8 and HighLevel?
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.
- Can I sync ServiceM8 and HighLevel both ways?
- Yes. HighLevel starts the integration, and on a two way route changes made in ServiceM8 flow back into HighLevel.
- What syncs between ServiceM8 and HighLevel?
- Contacts and appointments. Each record type can run two way or one way.
- How does HighLevel connect?
- With a Private Integration Token you create in HighLevel under Settings, Private Integrations, plus your Location ID. No password is stored.
- Does a changed company reach the other system?
- Company travels when the record is created, because highLevel takes these only when the contact is created. A later change is made in both systems.
- What happens when an appointment is cancelled?
- A cancellation in HighLevel stays in HighLevel. Whether the work happened is decided in ServiceM8.
- Will it create duplicates?
- No. Before anything is created in ServiceM8 or HighLevel, the platform looks for the same record first and updates that one instead. Records synced before stay linked.
- What if the connection to ServiceM8 or HighLevel drops?
- 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.
- How often does it sync?
- From every 30 minutes up to every 3 days, depending on your plan. Every plan includes a 7 day free trial.
Ready to connect ServiceM8 and HighLevel?Start your 7 day free trial
Sign in to ServiceM8 and HighLevel, pick which one leads or sync one way, confirm what syncs, and watch the first sync run.