Jobber duplicate clients: a pre-merge and reconciliation checklist

The short answer

Jobber now documents a native client merge, but confirm the two records represent the same person or business before using it. Choose which client survives, inspect payment authorization and external accounting IDs, and assign someone to reconcile the result. The merge cannot be undone. If the identity or authority is uncertain, keep the records separate while you investigate. Jobber's current merge guide, updated 14 August 2026, is the source for product behavior; the worksheet below is our proposed decision record.

What the product does, and what remains yours

The official guide says the option is available on all plans in Jobber Online, not the mobile app. It requires permission to view, edit and delete full client and property information, and both records must belong to the same account. The primary record remains; the secondary is removed. Jobs, visits, quotes, invoices and properties transfer, with each job retaining its attached property. In ordinary field conflicts, primary values win, while emails, phone numbers, tags and list-type custom fields are combined under their specific rules. Review the exact confirmation screen rather than guessing which detail wins.

Payment boundaries matter more than a tidy client list. A secondary record's stored card, other payment method and ACH consent do not transfer to the primary. Never copy credentials or treat one person's authorization as another's, or assume automatic payment will continue after a merge. The same Jobber documentation says a merge does not automatically merge external QuickBooks, Xero or other app records. Its secondary link drops in Jobber, while external records remain and a later sync may recreate a duplicate. Record mapping is not an external merge. Give a named owner the accounting and integration follow-up for the actual connected system; no automatic or blind external merge follows from this article.

A client may have several properties, including separate contacts at each site, according to Jobber's client basics. A shared phone number, address or surname is a clue to investigate, not proof that two accounts belong to the same party. A property manager, payer, tenant and access contact may each have a different role. Preserve those distinctions in the authorized system.

Copy the A/B reconciliation sheet

Use these field names in a private, access-controlled note or spreadsheet. The values are fictional and do not contain real account, card, bank or client details. A blank result means no check was run here.

Record the person who can confirm identity, the person responsible for invoices and balances, and the integration owner separately. For each open job, note its original property and current responsible team. For financial records, store only a review status here. Payment-method presence can be a yes or no flag; keep card, bank and consent details in the approved payment system.

Stop before the confirmation screen if a basic gate fails

1. Identity. Two parties with similar names, a shared site, or one office phone are not automatically duplicates. Obtain reliable confirmation from the authorized record owner. If there is doubt, stop.
2. Survivor. Choose the primary for the correct identity, contact and authorized payment context, not for its job count. DEMO-B-42 has more jobs than DEMO-A-17, yet that does not make B the right survivor. Review the differences that the primary will win.
3. Work and money. Map properties and live work, then have the responsible person reconcile invoices, balances, credits and unsettled authorizations. Jobber documents a temporary block when an unsettled payment authorization or external sync is in progress. Wait and investigate; do not force a workaround.
4. External links and access. Record both external IDs and the integration owner's plan before proceeding. Check which Client Hub path survives and which customer communications need careful follow-up.
5. Confirmation. Read Jobber's preview of what transfers and what does not. If it disagrees with the worksheet, stop and resolve the mismatch. A CSV export may help compare fields, but it is not a complete, restorable backup of the account or an undo button.

The fictional pair is deliberately unresolved. A has a payment-method flag and B has more jobs, while property authority and invoice review remain open. No merge should happen in that state. We did not connect an account, run a merge or inspect real records to produce this example.

If an authorized operator merges, reconcile afterward

Compare the surviving ID against the pre-action sheet. Check the number and ownership of properties, open jobs, invoices and contact routes, then have finance reconcile balances in the actual accounting system. Confirm payment authority separately rather than assuming a transferred method. Verify external IDs, the next intended sync and Client Hub access with their owners. Record each actual finding, including anything still unresolved. Conflicting secondary values may be lost when primary values win, and support is not a guaranteed undo path. No checklist guarantees recovery after a permanent action. Jobber explicitly describes the merge as irreversible.

For wider product decisions, see our Jobber review. The accounting sync guide covers record ownership across systems; the migration checklist addresses a full system change. Neither substitutes for identifying the two client records correctly before this merge.