Manaz Afzal Book a consultation

Work snippet

Duplicate contact merge across ServiceM8, HubSpot and Xero

Concept DesignIllustrative integration walkthrough. Business details, figures and records are worked examples.

A service group with 35 technicians whose customers appear up to three times across ServiceM8, HubSpot and Xero. One registry keeps the master record, likely duplicates are scored in pairs, and a person approves each merge so jobs and invoices stay with the right customer.

The problemThe same customer exists three times across three systems.

What changesOne master record, and every merge approved so jobs and invoices stay attached.

Area
Data quality across three systems
Tools
ServiceM8 · HubSpot · Xero · Airtable
Typical scope
US$1,800-3,200
Timeline
About 5 weeks · fixed milestones

The problem

A customer is created in the job system, again by a web form in the CRM, and again when the first invoice goes out. Each system then holds part of the history, and a search for the customer returns three answers.

  • Job history sits on one record and invoices on another
  • Sales talks to a contact that the field team cannot find
  • A merge done in one system leaves orphans in the other two
  • New duplicates appear the week after a clean-up

What discovery would examine

A count of contacts, clients and customers across ServiceM8, HubSpot and Xero for a 35-tech service group, plus a review of 80 apparent pairs.

Findings from the review
IDFindingEvidenceRisk if left
F1The same email exists in all three systems under two or three display namesOf 80 pairs reviewed: 31 exact email matches with different namesJob history and invoices sit on different records
F2A prior merge in HubSpot was not repeated in ServiceM8 or XeroHubSpot merge log vs still-open ServiceM8 clientsSales and the field team do not share a record
F3Shared site phones and group reception numbers create false matchesSeveral pairs shared a switchboard number onlyA merge would attach the wrong jobs
F4New duplicates appear in the week after a manual clean-upIntake zaps create contacts without a lookupThe clean-up does not hold
F5Xero invoices were left behind on the discarded customer in an earlier attemptOpen invoice on a merged-away contactAged receivables cannot be collected cleanly

Approach

  1. Build a cross-system registry

    Every source id is kept, even after a merge.

  2. Score, then ask a person

    High-confidence pairs still go through approval, in batches.

  3. Merge in a fixed order

    ServiceM8, then HubSpot, then Xero, so jobs and invoices stay attached.

  4. Stop new duplicates at the door

    Entry rules check the registry before a new record is created.

Current state and future state

How duplicates are found and merged

Current state

Three systemsEach creates contacts
Manual searchWhen someone notices
Merge in one placeThe other two are left
Next weekThe duplicate returns

Future state

RegistryAll source ids
Score pairsEmail, phone, name, address
Person approvesNo silent merge
Merge in orderJobs, then CRM, then invoices

Future-state modules

ServiceM8ClientsHubSpotContactsXeroCustomersAirtable registryMaster + scoresApproval queuePerson decidesMerge + entry rulesOrder, then block new

How it is built

Module-level build
  1. Module ARegistry load

    Every contact, client and customer is loaded with its source id, and those ids are never discarded.

  2. Module BScoring

    Name, phone, email and address each add to a score. Above a threshold is a likely match; the band below it is for review.

  3. Module CApproval

    A person sees the two records side by side and approves, rejects or parks the pair.

  4. Module DMerge order

    ServiceM8 first, so job history stays on the kept client, then HubSpot, then Xero, so invoices stay attached.

  5. Module EEntry rules

    A lookup against the registry runs before a new contact is created in any of the three systems.

Field mapping

How a pair is scored and what is kept
SignalWeightKept on the surviving recordNote
Email exactHighThe verified emailA shared group inbox is parked, not auto-approved
Mobile exactHighThe mobile used in the fieldA switchboard number is a weak signal on its own
Legal or trading name closeMediumThe longer official name, with the other stored as an aliasA person confirms a trading-name change
Street address + unitMediumAll sites combinedSame street, different unit, is not a merge on its own
Source idsAlways keptAll three source ids on the master recordNeeded for rollback and for entry rules

Worked exhibits

A 35-tech group, walkthrough counts
Records across three systems6,142before
Master records after merge4,018approved pairs only
Pairs approved1,126by a person
Pairs parked87shared phone or group address
Job links broken0history kept on the surviving record
Match reasonPairs scoredApprovedRejectedParked
Email exact, name close61260174
Mobile exact, name close4283901424
Trading name change, same email968835
Same street, different name154475354
Total in these bands1,2901,1267787
A pair on the review desk
Record A · kept
ServiceM8Client 10428, 11 jobs
HubSpotContact 8831, 3 deals
XeroCustomer, 8 invoices, $0 due
NameTrading name, official form
Record B · merge in
ServiceM8Client 11902, 2 jobs
HubSpotContact 9104, 1 deal
XeroCustomer, 1 invoice, $420 due
NameSame firm, shortened trading name

After approval, both job histories sit on client 10428, both HubSpot deals on contact 8831, and the $420 invoice stays open on the surviving Xero customer. Both records share the same accounts mailbox.

Exceptions and runbook

Exception runbook
CaseRuleWho actsRollback
Shared switchboard number onlyPark, do not approve on that signal aloneData ownerN/A, no merge yet
Property group, many sites, one billing contactKeep one master, attach all sites; do not merge two legal entitiesData owner with financeSites can be moved back; legal entities stay separate
Open invoice on the record that will be discardedMove invoices with the Xero merge, then check the open balanceFinanceNamed backup of the invoice list taken first
Wrong approval noticed after the batchUse the snapshot and the source ids to split the recordsData owner and me, inside the 14-day fix windowJobs and invoices still carry their source tags

How to read the exhibits

  1. The totals are counts of records and approved pairs, not a claim about revenue.
  2. The review desk shows why a trading-name difference still needs a person.
  3. The order is the safety rule: jobs first, invoices last, with a rollback snapshot at each step.

Test plan

PASS / FAIL checks
IDCheckMethodPASS whenFAIL when
T1Exact email pairApprove a scripted pairOne master, all source ids kept, jobs and invoices attachedA source id is lost, or an invoice is left behind
T2Switchboard-only pairSubmit a pair that shares only a reception numberThe pair is parked, not auto-approvedA merge runs unattended
T3Entry ruleCreate a contact with an email already in the registryThe existing master is reusedA new duplicate is created
T4Merge orderRun a three-system pair in a copyServiceM8 first, then HubSpot, then XeroXero is merged before jobs are combined
T5Rollback exportTake the snapshot, merge, then restore a test pairThe two records can be separatedA job has no client

Scope

AreaIncluded
DiscoveryCounts and a review of pairs in ServiceM8, HubSpot and Xero, with written findings
RegistryAirtable master record with all source ids
Scoring and approvalWritten weights, and a side-by-side queue
MergesCarried out in the agreed order, with job and invoice links kept
Entry rulesChecks that stop a new duplicate being created
Rollback exportA snapshot before each batch
Handover and supportSOPs, a recorded walkthrough, 14 days of fixes, and an optional monthly hour block
Not includedMerging records the owner has rejected, or cleaning data in other products

Rollout, handover and monthly support

MilestoneDeliverableTimingShare of fee
M1 Discovery, registry and scoringFindings, loaded records and the scoring rulesWeek 125%
M2 First approval batchQueue live, first batch merged in a copy then liveWeeks 2 to 335%
M3 Remaining batches and entry rulesApproved pairs done, new-duplicate checks onWeek 425%
M4 HandoverSOPs, export, 14 days of fixesWeek 515%
Handover and monthly support

Handover

  • Written operating procedures for the happy path and each exception in the runbook
  • A recorded walkthrough of the architecture, the queue and how to replay an item
  • A credentials and ownership list, with every connection in your name
  • Fourteen days of fixes after go-live, for defects in the agreed scope

Monthly support

A set block of hours each month, at US$35 per hour, agreed in writing before it starts. Typical use of the block: new pairs in the review queue, entry-rule exceptions, and any change to scoring weights

  • Review of the exception queue and the weekly digest
  • Small mapping or rule changes, agreed before they are made
  • A short written note on what was done and what is still open

Typical scope for this kind of project: US$1,800-3,200

About 5 weeks · fixed milestones. The systems health check (US$150, fixed) comes first and confirms the scope. Extra hourly work is US$35 per hour, agreed before it starts. After handover, a set block of hours each month is available at the same rate, agreed in writing, to watch the flows, handle changes and work the exception queue.

Discuss an engagement.

Outline the operational problem through the contact form. I respond with a recommended starting point, including whether the US$150 systems health check is the appropriate first step.

Related work snippets

Next step

Bring me the work that repeats.

I scope it in writing, test it against your current process on your own data and hand over everything I build.

Book a consultation