How ServiceM8 and Square sync

No. Records synced before stay linked. Before anything new is created, the platform looks for the same record in the other system and updates that one instead:

• A contact on its email, phone or name
• An invoice or quote on its number and total, or on its customer, day and total where no number is kept
• A deal on its name and contact

When several records were matched to one record in the other system, that record's changes are not copied back to them.

On a two way sync two records can both match one record on the other side, for example two HubSpot contacts with the email of one GoHighLevel contact.

The record that already syncs keeps syncing and the second one waits. Nothing is merged and the sync carries on.

You get a notification, and the integration's Conflicts tab shows both records. Use the other one instead or keep the current one, one at a time or many at once. A history keeps every resolved conflict with who resolved it and when, and a choice can be switched back or reopened.

No. A deal or opportunity already lost, a job already cancelled, or an invoice already voided before its first sync is not created. A deal that was still open when it first travelled moves to won or lost on a later sync, and a closed deal is never reopened.

Yes. Test with sample records on the last setup step shows per record type how many records would sync, how many are left out and why, with a few examples field by field. It reads up to 100 records per record type and writes nothing to either system.

A record whose contact was deleted or archived in the other system, an invoice for a customer deleted in QuickBooks for example, is skipped with that reason instead of failing on every sync. The contact is never created again behind your back. Restore it in that system and the record syncs with its next change, or with a Full sync.

The other system gets a payment for exactly the amount newly paid. A 40 instalment on a 100 invoice arrives as 40, and a later instalment bringing it to 70 arrives as one more 30, so nothing is counted twice. FreeAgent records no payment from outside and leaves it to its bank feed.

Only in two cases. No customer is ever deleted, and an update only sends the fields it carries, so a field the other system does not know is never wiped.

The two exceptions:

• A draft invoice voided in the other system is deleted in Xero, which cannot void a draft
• Closing a finished job in Jobber removes its visits still to come

The platform notices, switches that connection off, pauses the integrations that use it and sends you one message with a button to fix it:

• Reconnect, for a system you sign in to
• Replace the key on the integration, for a system that uses a typed key

Once it works again, the paused integrations start again by themselves within a few minutes, without creating anything twice.

The one where your team makes most changes. It only decides the rare case where the same record changed in both systems between two syncs.

You choose per integration, from every 15 minutes up to every 3 days. Every 4 hours and slower is included on every plan.

Faster syncing comes with the higher plans, down to every 15 minutes on Agency. On any plan you can add faster sync:

• Every hour: $5 a month
• Every 30 minutes: $10 a month
• Every 15 minutes: $20 a month

A few systems set their own limit: GoHighLevel, Keap and Simpro are synced at most every 30 minutes, WooCommerce at most every hour.

No. On a one way sync the receiving system is where the work lives, so what your team does there stays there.

Yes. Pick one way and the setup shows what travels in that direction. Pick both ways and it shows everything the two systems can do, also what only travels the other way round, such as GoHighLevel invoices into Xero next to contacts from Xero.

Those run one way, and the contacts then sync both ways, so every record finds its contact in both systems.

A stage rule turns a moment in one system, such as a deal won or a quote accepted, into new work or a draft invoice in another.

Each rule needs a start date, 60 days back by default, so nothing won or accepted long ago becomes a new record on the first run.

A sale is never billed twice:

• A rule cannot run next to a sync of the same record type between the same two app connections, in the same integration or another one
• A record a rule made never comes back as new work in the system it came from

Yes. The start date, the moment a record may travel and the minimum amount apply in both directions.

Tags and pipeline stages belong to one system, so each side gets its own pick, like GoHighLevel tags one way and HubSpot lifecycle stages the other. A side without such a filter sends all of its records the other way.

The standard fields of each record type sync. Custom fields sync in two places today:

• GoHighLevel and HubSpot contacts: map your own custom fields by hand, both ways
• An open GoHighLevel opportunity that becomes a Jobber request can carry the contact's custom fields you pick, in one note on the request

Need custom fields for another pair? Request it.

Yes. Tell us through the request form what should travel and when. We answer every request within one working day.