--- title: "Construction two-way sync starts with customer, site and job" description: "Start construction two-way sync with customer, site, job and billing-status records that prevent repeated office handoffs." canonical: https://www.stacksync.com/blog/two-way-sync-for-construction-service-companies-which-records-to-connect-first last_modified: 2026-09-18 --- # Two-Way Sync for Construction Service Companies: Which Records to Connect First > 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 Start construction two-way sync with customer, site, job and billing-status records that prevent repeated office handoffs. Author Ruben Burdin · Founder & CEO Published September 18, 2026 Read time 5 min read DATA ENGINEERING ## The operating decision Construction service companies should start two-way sync with the records that identify who ordered the work, where it happens, which job owns it, and whether finance can bill it. Connect customer and site identities before automating financial transactions. Give each field an owner: sales maintains relationship information, operations maintains work status, and finance controls accounting status. Stacksync provides the data foundation; your mapping determines which changes may travel in each direction. 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: Construction two-way sync starts with customer, site and job](https://www.stacksync.com/images/blog-highlights/icp-two-way-sync-for-construction-service-companies-which-records-to-connect-first.webp) ## What this looks like in construction services and installation Consider a US contractor with several branches and separate service and installation teams. A facility manager requests electrical repairs through sales, dispatch schedules the visit, and the billing office sees a different customer name. Staff spend the afternoon matching addresses and forwarding completion notes. The first useful sync does not need every historical attachment. It needs a stable customer identifier, a site identifier, the originating request, and a shared job reference so each team can recognize the same work. ## Records, ownership, and update rules | Record | Owner | Operating rule | | --- | --- | --- | | Customer identity | Finance and CRM owner | Keep legal billing identity distinct from the trading name used by the account team. | | Service site | Operations | Assign an immutable site key even when several sites share a billing customer. | | Job reference | Job administration | Carry the originating branch and source identifier through every mapped record. | | Billing status | Finance | Expose approved invoice status to customer-facing teams without making CRM edits accounting approval. | ![Record ownership diagram: Customer identity, Service site, Job reference](https://www.stacksync.com/images/blog-diagrams/icp-two-way-sync-for-construction-service-companies-which-records-to-connect-first.webp) *Define the record owner and the rule before enabling updates.* ## Work through the process 1. 01 Rank handoffs by repeated lookup Ask dispatch, project coordination, and accounts receivable to show three recent jobs that required copying data. Record the exact missing field and the downstream decision it blocked. Prefer a bounded flow such as customer-to-site matching over a vague request to connect the entire ERP. This produces a first release that business users can actually inspect. 2. 02 Agree the identity hierarchy Document the relationship between parent organization, bill-to customer, property manager, physical site, and job. These are often different parties. Retain the native identifier from each system in a cross-reference rather than matching every update by company name. Have finance resolve ambiguous bill-to relationships before automatic creation begins. 3. 03 Choose field ownership For every mapped field, name the team that may originate changes and the system where that change is approved. A two-way connection can contain ERP-owned fields and CRM-owned fields. Do not use a last-update timestamp to settle a disagreement about payment terms, credit holds, or whether additional work was authorized. 4. 04 Validate a representative slice Use jobs covering a repeat customer, a new site, an inactive account, and a branch transfer. Confirm the selected objects and writes against the connector documentation and account permissions. NetSuite object access varies; Salesforce eligibility also depends on the selected change-detection approach. Test the intended record operations, not only a successful login. 5. 05 Measure reconciliation effort At the end of the pilot, compare source and destination counts and inspect unmatched identifiers. Track the number of jobs needing manual customer lookup, the age of unresolved mapping errors, and whether a correction travels to the intended system. Expand to work-order and invoice evidence only after the identity layer holds up. ![5-step operating sequence: Construction two-way sync starts with customer, site and job](https://www.stacksync.com/images/blog-diagrams-mermaid/icp-two-way-sync-for-construction-service-companies-which-records-to-connect-first.webp) *Follow the operating sequence; unresolved exceptions return to a responsible reviewer.* ## Handle the exceptions explicitly ### One customer has multiple billing entities Retain separate legal customers and link them to the relationship account; do not merge them because their brand is shared. ### A branch reuses a job number Qualify the key with its source and branch so another office cannot attach costs to the wrong job. ### An invoice status arrives before its job Hold the relationship for reconciliation and avoid creating a second placeholder job. ## What to verify before expanding - A repeat customer maps to one approved billing identity. - Two sites at the same street address remain distinguishable. - Finance changes appear in the correct customer-facing record. - A retried update does not create another customer or job. ## 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 customer identity example and the exception your team handles most often, for example one customer has multiple billing entities. - [HubSpot–Acumatica for Construction Services: Customers, Projects, and Invoice Status](https://www.stacksync.com/blog/hubspot-acumatica-for-construction-services-customers-projects-and-invoice-status) - [Salesforce–NetSuite for Construction Service Groups: Accounts, Jobs, and Approved Commercial Data](https://www.stacksync.com/blog/salesforce-netsuite-for-construction-service-groups-accounts-jobs-and-approved-commercial-data) - [HubSpot–Supabase for Construction Service Portals: Customers, Sites, and Request Status](https://www.stacksync.com/blog/hubspot-supabase-for-construction-service-portals-customers-sites-and-request-status) - [Acumatica to Salesforce & HubSpot Integration](https://www.stacksync.com/blog/acumatica-salesforce-hubspot-integration) - [How to Sync HubSpot and Supabase in minutes with Stacksync](https://www.stacksync.com/blog/how-to-sync-hubspot-and-supabase-in-minutes-with-stacksync) 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 Should construction companies sync every object at once? Start with the smallest connected set that removes a measurable handoff. Broad replication makes identity mistakes harder to isolate and can introduce records that nobody owns operationally. Does two-way sync mean everyone can edit financial fields? No. Direction should be decided at field and object level. The connection can support changes from both systems while finance retains control over payment terms and accounting state. What should we bring to a construction integration demo? Bring anonymized customer, site, and job examples, your branch structure, and one real handoff that fails today. Include the people who decide billing identity and completion status. 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) - [platform CRM synchronization](https://www.stacksync.com/crm) - [platform CRM and ERP integration](https://www.stacksync.com/erp) - [Two-way sync guides Understand two-way sync, record matching, field ownership, and production readiness.](https://www.stacksync.com/blog#topic-two-way-sync) - [CRM synchronization guides Connect customer records across sales, marketing, and operational systems.](https://www.stacksync.com/blog#topic-crm-sync) Keep reading ## Related articles [All articles](https://www.stacksync.com/blog) [Data engineering Salesforce–NetSuite Integration: Mapping and Setup 8 min read read](https://www.stacksync.com/blog/the-complete-guide-to-salesforce-netsuite-integration-achieving-true-bi-directional-sync) [Data engineering Construction Company Acquisitions: Unify Customer and Job IDs Across Branch Systems 5 min read read](https://www.stacksync.com/blog/construction-company-acquisitions-unify-customer-and-job-ids-across-branch-systems) [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) ## 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/)