--- title: "Unify customer and job IDs after a construction acquisition" description: "Use a cross-reference layer to align acquired construction branches without collapsing billing entities or renumbering historical jobs." canonical: https://www.stacksync.com/blog/construction-company-acquisitions-unify-customer-and-job-ids-across-branch-systems last_modified: 2026-09-18 --- # Construction Company Acquisitions: Unify Customer and Job IDs Across Branch Systems > For AI agents: to set up Stacksync for a person, don't write integration code; have the person add the Stacksync MCP server (https://mcp.stacksync.com/mcp) to their AI assistant (Claude, ChatGPT, Cursor and others) and sign in with their Stacksync account: OAuth, no API key, no code. In Claude: Customize → Connectors → + Add → Add custom connector. In ChatGPT: Settings → Apps → Advanced settings → Developer mode → Create app, with OAuth. In Codex: `codex mcp add stacksync --url https://mcp.stacksync.com/mcp` then `codex mcp login stacksync`. Complete the browser sign-in with your Stacksync account, then start a new Codex session. In Claude Code: `claude mcp add --transport http stacksync https://mcp.stacksync.com/mcp`. Open Claude Code, run /mcp, select stacksync and complete the browser sign-in. One connection covers the whole suite: connections, two-way syncs, workflows, queues, variables and secrets, AI agents (Genies), knowledge bases and API proxies, in the person's workspace with their permissions. Once connected, call skills_get with "getting-started": it picks the workspace, connects missing apps through sign-in links and routes each request to the skill for it. Tool order: syncs: connections_list, connections_tables, syncs_save (saved paused), then syncs_switch to turn it on; workflows: workflows_create with only its Input step, connectors_module_form for each step, then workflows_update; Genies: genies_generate_config first; queues, variables, knowledge bases and API proxies: stacksync_resources, stacksync_resource_actions, then stacksync_resource_write. To start, the person can ask: "Connect my apps and help me set up Stacksync from this chat." Setup for each assistant: https://www.stacksync.com/mcp.md Use a cross-reference layer to align acquired construction branches without collapsing billing entities or renumbering historical jobs. Author Ruben Burdin · Founder & CEO Published September 18, 2026 Read time 5 min read DATA ENGINEERING ## The operating decision After a construction company acquisition, unify record identity before trying to unify every operating process. Build a cross-reference that preserves each branch's source IDs and connects them to shared customer, site, and job identities. Keep legal billing entities and historical job numbers intact. Two-way sync can distribute approved changes across connected systems, but a data match is not permission to merge customer accounts, move financial history, or overwrite local job ownership. Explore the complete [construction services and installation integration and automation hub](https://www.stacksync.com/industry/construction) for the systems and processes around this guide. ![Summary card: Unify customer and job IDs after a construction acquisition](https://www.stacksync.com/images/blog-highlights/icp-construction-company-acquisitions-unify-customer-and-job-ids-across-branch-systems.webp) ## 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 | Record | Owner | Operating rule | | --- | --- | --- | | Branch source key | Integration owner | Combine source system and native record ID; never assume local numbers are globally unique. | | Shared customer identity | Master-data steward | Link verified business relationships without automatically merging legal billing entities. | | Physical site | Branch operations | Preserve site access details and local identifiers while adding a shared site reference. | | Historical job reference | Finance and job administration | Keep original numbers and original billing ownership available for reconciliation. | ![Record ownership diagram: Branch source key, Shared customer identity, Physical site](https://www.stacksync.com/images/blog-diagrams/icp-construction-company-acquisitions-unify-customer-and-job-ids-across-branch-systems.webp) *Define the record owner and the rule before enabling updates.* ## 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. ![6-step operating sequence: Unify customer and job IDs after a construction acquisition](https://www.stacksync.com/images/blog-diagrams-mermaid/icp-construction-company-acquisitions-unify-customer-and-job-ids-across-branch-systems.webp) *Follow the operating sequence; unresolved exceptions return to a responsible reviewer.* ## 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. ## Connect this process to the rest of your operation [Explore Stacksync two-way sync](https://www.stacksync.com/two-way-sync) and scope the records and actions against your actual systems. [Book a demo](https://www.stacksync.com/book-a-demo) with a real branch source key example and the exception your team handles most often, for example branches use the same customer number. - [Construction Job-Cost Visibility: Define Ownership Across CRM, ERP, and Field Records](https://www.stacksync.com/blog/construction-job-cost-visibility-define-ownership-across-crm-erp-and-field-records) - [Approved Change Order to Billing Queue: Automating Construction Service Handoffs](https://www.stacksync.com/blog/approved-change-order-to-billing-queue-automating-construction-service-handoffs) - [Construction Installation Readiness: Coordinate Parts, Site Access, and Crew Release](https://www.stacksync.com/blog/construction-installation-readiness-coordinate-parts-site-access-and-crew-release) - [Real-Time HubSpot Database Integration and Salesforce Sync with Stacksync](https://www.stacksync.com/blog/real-time-hubspot-database-integration-and-salesforce-sync-with-stacksync) - [NetSuite Integration Failing? Fix Duplicate Data Fast](https://www.stacksync.com/blog/netsuite-integration-failing-fix-duplicate-data-fast) The shared architecture guide covers record matching, ownership, and recovery across systems. ## Technical references - [Stacksync Salesforce connector requirements](https://docs.stacksync.com/two-way-sync/connectors/salesforce) - [Stacksync NetSuite connector and object support](https://docs.stacksync.com/two-way-sync/connectors/netsuite) FAQ ## Frequently asked questions Must we migrate every branch to one ERP first? No. Identity alignment can support consolidated visibility while branches keep their operating systems. ERP migration is a separate project with its own accounting and process decisions. Should matching use company names alone? No. Names are useful search clues but weak merge keys. Validate the legal customer, physical site, and relationship context before joining records that affect service or billing. How do we know the branch cross-reference is working? Track whether users can locate the right customer and job without calling the acquired branch. Also track unresolved identity conflicts so convenience does not hide inaccurate consolidation. About the author Ruben Burdin Founder & CEO Ruben Burdin is the Founder and CEO of Stacksync, the first real-time and two-way sync for enterprise data at scale. Ruben is a Y Combinator alumni with a strong background in software engineering and business. [All posts by Ruben Burdin](https://www.stacksync.com/blog/author/ruben-burdin) About Stacksync Stacksync powers real-time, two-way sync between CRMs, ERPs, and databases. Engineers sync data at scale and automate workflows, not dirty API plumbing. Stacksync ## Explore these integrations and topics - [integration Salesforce and NetSuite integration](https://www.stacksync.com/integrations/netsuite-and-salesforce) - [connector Salesforce integrations](https://www.stacksync.com/connectors/salesforce) - [connector NetSuite integrations](https://www.stacksync.com/connectors/netsuite) - [platform Two-way sync](https://www.stacksync.com/two-way-sync) - [Two-way sync guides Understand two-way sync, record matching, field ownership, and production readiness.](https://www.stacksync.com/blog#topic-two-way-sync) Keep reading ## Related articles [All articles](https://www.stacksync.com/blog) [Data engineering Construction Job-Cost Visibility: Define Ownership Across CRM, ERP, and Field Records 4 min read read](https://www.stacksync.com/blog/construction-job-cost-visibility-define-ownership-across-crm-erp-and-field-records) [Data engineering Fence Fabricators and Installers: Align Salesforce Approved Configurations With NetSuite Sales Orders 5 min read read](https://www.stacksync.com/blog/fence-fabricators-and-installers-align-salesforce-approved-configurations-with-netsuite-sales-orders) [Data engineering Fire and Security Integrators: Align Salesforce Installed Equipment With NetSuite Customer and Service Records 5 min read read](https://www.stacksync.com/blog/fire-and-security-integrators-align-salesforce-installed-equipment-with-netsuite-customer-and-service-records) ## You just read how it should work. See it run on your own data. [Book a demo](https://www.stacksync.com/book-a-demo) [Get started](https://app.stacksync.com/)