Construction Company Acquisitions: Unify Customer and Job IDs Across Branch Systems

What this looks like in construction services and installation

Consider two commercial service companies joining one group. Both have a customer called Central Properties and a job numbered 1042, but they serve different sites and bill different entities. The group wants consolidated customer visibility before deciding whether to replace either branch's systems. A simple name match creates a false duplicate. A careful cross-reference lets national account management recognize the relationship while finance retains the correct local customers and job histories.

Records, ownership, and update rules

Work through the process

1. 01
   Inventory the records before merging

   Collect representative customer, contact, site and job exports from each branch. Compare what each record means, not just its column names. One system may call a property a customer, while another uses a separate site table. Write down these differences so later mappings do not erase them.
2. 02
   Introduce a source-qualified key

   Use a stable cross-reference that identifies the branch system and its native record. Assign shared identities only after the match is reviewed. Preserve the original key alongside the shared one so service coordinators can still find older work in the acquired company's operating system.
3. 03
   Classify match confidence operationally

   Exact legal identifiers, verified billing addresses and confirmed site relationships provide different evidence from similar names. Put uncertain matches in a steward queue with both source records. Do not auto-merge records because the same property manager or generic accounts-payable email appears on both.
4. 04
   Stage the ownership transition

   Start by sharing read context and approved relationship updates. Keep job-cost and billing fields with their existing finance owner until the group agrees a migration plan. If responsibility changes, set an effective date and test how late invoices or corrections to historical jobs will be handled.
5. 05
   Reconcile by branch and record type

   Compare linked, unmatched and conflicting counts for each source. Investigate changes that unexpectedly move work between billing entities. Before adding another acquisition, replay a duplicate job number and a customer with different legal names to prove that the cross-reference prevents accidental consolidation.
6. 06
   Keep a reversible identity decision

   For each reviewed match, record who approved it and why the records represent the same relationship. Preserve the original source records and allow a steward to separate a mistaken link without losing branch history. This matters when an acquired company uses informal customer names that initially look identical. A cross-reference is useful precisely because the group can improve identity decisions without immediately renumbering jobs or changing the financial records in either branch.

Handle the exceptions explicitly

Branches use the same customer number

Retain the branch-qualified source key and map each to the appropriate shared identity.

Customer relationship matches but payer differs

Link the commercial relationship while keeping separate finance customers.

Acquired system is retired later

Export the cross-reference and retain historical source identifiers in the replacement system.

What to verify before expanding

• Identical local job numbers remain separate jobs.
• Uncertain customer matches wait for a named steward.
• Historical invoices retain their original billing entity.
• A branch can locate its original record from the shared customer view.

Technical references

• Stacksync Salesforce connector requirements
• Stacksync NetSuite connector and object support