Fox & SantiagoTechnology, applied.Call (877) 244-9687

Problem guide

The same customer exists three times in your systems

Duplicate customer records come from matching rules nobody in the office can see. Each system decides on its own whether a person is new, using a different key. ServiceTitan's online scheduler recognizes a returning customer by phone number only, so a spouse booking from another phone becomes a new customer, and QuickBooks Desktop gets a second customer when the first exported name differs by a comma or a space. Pick one system that creates customers, search by phone and address before adding anyone, and merge in a fixed order, because most merges cannot be undone.

A technician and a customer shaking hands on a loading dock

How it actually happens

Duplicates are rarely typos. They are what happens when several systems each decide on their own whether a person is someone they already know, using different evidence. A booking tool matches on phone, a storefront on email, an accounting file on exact name, a patient system on name and date of birth. Any customer who shows up with a different phone, email or spelling becomes a new record.

Take a household that has been a customer of a service company for six years. The account is in the wife's name with her cell number. Her husband books a tune-up on the company website from his own phone. ServiceTitan's online scheduler looks up returning customers by the phone number entered, finds nothing, and creates a new customer. The tech arrives at the same address and sees no equipment history, no membership and no prior repairs, because all of that lives on the first record. The person who notices later has a choice between merging the records and leaving them, and on a busy Monday the answer is leaving them.

The phone line does the same thing in a different system. One office user on Reddit described FieldEdge's phone integration creating a new account whenever the caller ID differed slightly, unless someone clicked the similar account shown on the side, and having to merge twice, once in QuickBooks and once in FieldEdge. FieldEdge's own merge procedure confirms the double work: rename in QuickBooks, merge there, then merge in FieldEdge.

The accounting file adds its own rule. With QuickBooks Desktop, ServiceTitan matches a customer by exact name on the first export, commas and spaces included, and creates a new QuickBooks customer if the name is off by one character. QuickBooks Online insists on unique names across customers, vendors and employees, so a customer who shares a name with a supplier will not sync until someone renames one of them. The rename is usually a period or a number, which is a duplicate made on purpose.

Business accounts multiply the paths. A property manager calls about one building and gets set up as the customer; a second building gets set up under its street name; the owner's accounts payable office is a third record in QuickBooks. A wholesale buyer orders online under one account and through a sales rep under another. On construction projects, Procore creates a company-level record every time a project manager adds a company to a project, so Star Framing and Star Framing, LLC become two companies with split insurance and bidder history.

Migrations are the largest single source. When a company moves from QuickBooks Desktop to Online with ServiceTitan connected, every Desktop name that carries ServiceTitan's appended ID meets a clean name from the field system, and the customer list doubles unless the IDs were stripped first. Any move between systems carries the same risk when the two lists are loaded side by side instead of matched.

Then the cleanup meets permanence. Most of these systems say a merge cannot be undone, and a merge in one system does not reach the copy in the other.

Why it costs more than it looks

A duplicate is not a cosmetic problem. A payment lands on one copy while collections chases the other. Someone walks into a visit, a call or an appointment with no history in front of them. A renewal or a statement goes to an address nobody uses. The cost shows up in collections, in the service record and in every report that counts customers.

Signs you have this problem

  • A customer search returns the same person or company under two spellings, two emails or two phone numbers
  • History for one customer or one address is split across two records
  • A payment is applied to one copy of the customer while the other copy shows overdue
  • QuickBooks rejects an invoice because the name is already used by a customer, vendor or employee
  • The office renames customers with a period or a number to get the sync to go through

What usually causes it

  • The same customer is typed into the booking tool, the operating system, the accounting file and the project directory, and each one matches on a different keyThe re-entry trap
  • Whoever takes the first call or order creates a record instead of searching, because the customer is on a new phone or email, or the search is slowThe handoff gap
  • Landlords, tenants, property managers, parent companies, family accounts and multiple sites are handled case by case with no written ruleThe exception swamp
  • Possible-duplicate reports and sync error alerts exist, but nobody owns reading themThe invisible queue

Find your cause

Ask these in order. The first yes is usually where yours starts.

  1. Does your system's duplicate report or merge tool show more than a few dozen possible duplicates?If yes: the matching is failing at intake. Start with search-before-create and the account rule.
  2. Do customers get created in more than one system, including directly in QuickBooks?If yes: there is no single creating system. Name one and remove create rights elsewhere.
  3. Has the office ever added a period or a number to a customer's name to make a sync work?If yes: the accounting file has name collisions with vendors, employees or old customers. Reconcile the lists before merging anything.
  4. Did you switch accounting systems or operating systems in the last three years?If yes: the migration probably created a second set of customers. Compare the two lists name by name.
  5. Are property managers, families, parent companies and their sites set up differently by different people?If yes: write the account rule before merging, or the cleanup will be undone by the next booking.

How it breaks in each industry

Residential HVAC, plumbing and electrical service
Households call from more than one phone, and homes change hands. A spouse booking online from a different number becomes a new customer, and a new owner at an old address either inherits the last owner's history or gets a second location. Equipment and warranty history live on the location, so a duplicate location splits the service record of the unit itself.
Commercial service for property managers and multi-site owners
One management company pays for many buildings, each with its own site contact. If the buildings are set up as customers instead of locations, or the management company exists under its legal name and an abbreviation, payments land on one record and collections calls go to the other.
Healthcare practices and clinics
A patient registers once under a maiden name and again under a married name, or the front desk misses a match on a mistyped date of birth. The chart splits: allergies and history on one record, the new insurance and the latest visit on the other, and statements go to whichever copy billing finds first.
E-commerce and consumer brands
A buyer checks out as a guest with a work email, later makes an account with a personal one, and calls support from a third. Each becomes its own customer, so order history, returns and loyalty credit split three ways, and a wholesale buyer can sit in the storefront and the sales rep's list as two different accounts.

Where it breaks between systems

ServiceTitan Scheduling Pro
The online scheduler identifies returning customers by the phone number entered, so a husband booking from his own phone on his wife's account gets a new customer record by default. The Takeover setting books the job on the existing location's customer instead, but booking notifications then go to that existing customer.[1]
ServiceTitan and QuickBooks Desktop
On the first invoice export, the customer name must match QuickBooks exactly, including commas and spaces, or QuickBooks gets a duplicate. After that, ServiceTitan appends its own ID to the QuickBooks name and matches on it. The list reconciliation sorts every customer into Exact, Strong, Weak, No Match or Exception, where an Exception is one ServiceTitan customer matching more than one QuickBooks customer.[3]
ServiceTitan moving from QuickBooks Desktop to QuickBooks Online
QuickBooks Online does not support the customer sync ID, so a customer stored in Desktop as Alex Rodriguez 123 meets a new Alex Rodriguez exported to Online, and the two become separate customers. ServiceTitan's documented fix is to strip the ID numbers from the Desktop names before the move.[4]
Housecall Pro and QuickBooks
QuickBooks Online requires every customer, vendor and employee to have a unique name, so an invoice for a customer who shares a name with a vendor raises a Name Already Taken alert. With QuickBooks Desktop, if the Desktop customer name does not match the Housecall Pro display name before the job is completed, completing the job creates a duplicate.[7]
Jobber and QuickBooks Online or Xero
Jobber names request forms, phone mismatches and records coming in from QuickBooks Online, Zapier or other apps as sources of duplicates. Merging in Jobber drops the second client's link to those apps, but the record still exists on the other side, and a later sync can recreate it. A card on file never transfers, and a merge cannot be undone.[10]
FieldEdge and QuickBooks Desktop
FieldEdge's merge procedure starts in QuickBooks: rename one display name to match the other, then merge in FieldEdge, with the Connector paused and QuickBooks in single-user mode. The FieldEdge merge deletes one customer, cannot be undone, and only joins parents to parents or sub-customers to sub-customers.[12]
ServiceM8 and Xero
A client created in ServiceM8 reaches Xero only with its first approved invoice. Until then, if someone types the same client into Xero by hand, the ServiceM8 client is overwritten rather than duplicated.[13]
Procore Company Directory and ERP integrations
Every company added to a project directory also creates a company-level record. With an ERP connected, each ERP vendor links to exactly one Procore company, so duplicates must be merged first; the merge cannot be reversed, prompts for which Sage ID to keep, and archives the other linked vendors.[16]
BuildOps and QuickBooks Online
BuildOps lists duplicate customer records between the two systems, and a Company Name that does not match the Customer Display Name, among the causes of QuickBooks Online sync errors.[17]

By the numbers

FigureWhat it measures
14,500 and 10,500[19]QuickBooks Desktop Pro and Premier name limits: 14,500 names across employees, customers, vendors and other names combined, and 10,500 on any one list. Enterprise 17.0 and later allows up to one million. Every duplicate uses a slot (Intuit).
39%[22]Share of annual revenue that came from repeat customers, self-reported by more than 1,000 U.S. residential service contractors (ServiceTitan survey run by Thrive Analytics, released December 2023, vendor survey). It shows how much rides on a customer's history staying in one record; no published study measures how often customer records are duplicated or what a duplicate costs.

Rules that apply

Texas Property Code 53.056(a), (a-1) and (a-2), notice of claim[23]
On Texas private projects, a sub or supplier must send the notice of claim to the owner or reputed owner and the original contractor by the 15th day of the third month after the month the work was done, or the second month on residential projects. The statute sets the deadline and the addressees; the link to customer records is our reading, not the statute's: a job filed under the wrong customer or company record is how a notice gets addressed to the wrong party.

Measure it in your own shop

From: Your operating system's customer and location lists, its possible-duplicates report or merge tool, and the customer list in your accounting file.

  1. Run the duplicate report (ServiceTitan's Duplicate Customers and Duplicate Locations templates, Housecall Pro's Manage Duplicates groups, or an export sorted by phone, email and address).
  2. Count possible duplicates by key: same phone, same email, same address and unit, same name only.
  3. For QuickBooks Desktop with ServiceTitan, run the list reconciliation and count Exceptions and No Match customers.
  4. Pick the 20 customers you billed most last year and check each for a second record in any system.

Reading it: The count of possible duplicates, how many of your top 20 customers have more than one record, and how many accounting customers have no clean match. The top-20 check is the one that shows up in collections and reporting.

What does not fix it

A one-time cleanup weekend
The cleanup fixes the past. Without one creating system and a search habit, the booking tool, the phones and the next migration rebuild the duplicates within months.
Merging in one system only
Jobber says plainly that merging does not remove the copy in the connected app and a later sync can recreate it. FieldEdge has you merge in QuickBooks first for the same reason.
Renaming customers to get past sync errors
Adding a period or a number lets the invoice through, but it creates two customers on purpose, and the history splits from that day forward.

What to try this week

  1. Count the duplicates before touching anythingRun your system's duplicate report or merge tool to list possible duplicates, and run the accounting reconciliation if your system has one. Write down the count of each kind: same phone, same email, same address, same name.
  2. Name the system that creates customersOne system creates customers; every other system receives them. Write it down, remove create permission from everyone who does not need it, and stop typing customers straight into QuickBooks.
  3. Write the account ruleDecide how a property manager, a landlord with tenants, a household, and a company with many sites or buyers are set up: who is the customer, what is a location or contact, who is the bill-to. One page, with three examples.
  4. Search by phone, email and address before creatingMake that search the first step of every booking, order or intake. A customer on a new number or a new email is the most common way a second record starts.
  5. Merge in the right order, biggest accounts firstCheck which systems hold each copy before merging. Merge where your vendor's documentation says to merge first, keep the record with the card on file and the history, and start with the customers you bill most.

Where do-it-yourself stops

These steps slow new duplicates and clean up the ones costing you the most, but every system still keeps its own copy of the customer and its own matching rule, so the copies start drifting the day after the cleanup. The lasting fix is a tool built around your operating, accounting and project systems, so a customer is created once, matched the same way everywhere, and a possible duplicate is caught before it is saved. That is what a Workflow Spec designs.

How a Workflow Spec fixes it for good

Questions people ask

Why does the same customer show up more than once?

Because each system matches on something different: ServiceTitan's online scheduler on phone number, QuickBooks Desktop on the exact name at first export, Jobber's older sync on first and last name. When a customer uses another phone or a name is typed slightly differently, nothing recognizes them and a new record is saved.

Can two different customers have the same name in QuickBooks Online?

Not as written. QuickBooks Online requires names to be unique across customers, vendors and employees. An Intuit community moderator's suggestion in 2022 was to add a character to make the display name unique, which is exactly how deliberate duplicates begin, so decide the convention once and write it down.

Can a merge be undone?

In ServiceTitan, yes; its help center documents Undo Merge. In Jobber, Housecall Pro, FieldEdge, simPRO, Procore and QuickBooks Online, the vendors say the merge is permanent. Check the card on file, any recurring plan and the history before you merge.

Which record should we keep when we merge?

The one with the card on file, the history and the accounting link. Jobber, for example, does not move a card on file during a merge, and a ServiceTitan merge adds whatever is missing from the kept record from the removed one.

We are switching from QuickBooks Desktop to QuickBooks Online. What do we do first?

If you use ServiceTitan, remove the sync ID numbers from the end of your Desktop customer names before the move. ServiceTitan documents that skipping this step creates a second copy of every customer in QuickBooks Online.

Next step

How we fix this

This guide is how to find it and work around it. If it keeps coming back, it is rarely the only thing costing you. We come on site, find the issues costing you the most, and fix them, starting with the most pressing.

Fox & Santiago, Genesee, Idaho. We work nationwide, for clients across the United States, from our headquarters in Genesee, Idaho.