How Google Sheets and CompanyCam 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 HighLevel 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 who both records are: 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.

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, and 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, or 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, near real time, on Agency, or as a faster sync add-on on any plan: every hour for $5, every 30 minutes for $10 or every 15 minutes for $20 a month. A few systems set their own limit: HighLevel, 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.

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 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, and a record a rule made never comes back as new work in the system it came from, so a sale is never billed twice.

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 HighLevel tags one way and Pipedrive labels the other. A filter only one of the two systems has works one way only.

Not today. The standard fields of each record type sync; custom fields do not. One exception: an open HighLevel opportunity that becomes a Jobber request can carry the contact's custom fields you pick, in one note on the request.

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