--- title: "Salesforce NetSuite sync for fire and security equipment" description: "Connect installed fire and security asset context to customer and service records without losing device identity." canonical: https://www.stacksync.com/blog/fire-and-security-integrators-align-salesforce-installed-equipment-with-netsuite-customer-and-service-records last_modified: 2026-09-18 --- # Fire and Security Integrators: Align Salesforce Installed Equipment With NetSuite Customer and Service Records > 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 Connect installed fire and security asset context to customer and service records without losing device identity. Author Ruben Burdin · Founder & CEO Published September 18, 2026 Read time 5 min read DATA ENGINEERING ## The operating decision Fire, life-safety and security integrators need persistent installed-equipment identities across sales, service and billing. Salesforce–NetSuite two-way sync can connect accessible asset or approved custom records to the correct customer, site and service context. Preserve device identifiers and installation relationships separately from the payer. The sync provides administrative continuity; it does not certify inspection results or prove that a device is suitable for a particular application. Validate the selected objects and writes before enabling changes. Explore the complete [fire, life-safety and security integrators integration and automation hub](https://www.stacksync.com/industry/construction/fire-life-safety-security-integrators) for the systems and processes around this guide. ![Summary card: Salesforce NetSuite sync for fire and security equipment](https://www.stacksync.com/images/blog-highlights/icp-fire-and-security-integrators-align-salesforce-installed-equipment-with-netsuite-customer-and-service-records.webp) ## What this looks like in fire, life-safety and security integrators An integrator installs access-control equipment for a multisite customer and later adds recurring service. Salesforce holds the relationship and installed-equipment context; NetSuite holds the customer and service-related commercial records. A panel is replaced and its serial number changes, but the serviced location remains the same. If the old asset is simply overwritten, the team loses the link between prior work and the equipment actually present at the time. ## Records, ownership, and update rules | Record | Owner | Operating rule | | --- | --- | --- | | Installed asset | Service asset administrator | Retain the device identity, site and installation relationship. | | Replacement relationship | Service supervisor | Link predecessor and replacement equipment rather than erasing history. | | Billing customer | Finance | Keep the payer and service agreement reference distinct from the asset owner. | | Service coverage | Contract administration | Identify the covered equipment and effective service term. | ![Record ownership diagram: Installed asset, Replacement relationship, Billing customer](https://www.stacksync.com/images/blog-diagrams/icp-fire-and-security-integrators-align-salesforce-installed-equipment-with-netsuite-customer-and-service-records.webp) *Define the record owner and the rule before enabling updates.* ## Work through the process 1. 01 Choose persistent asset keys Use a stable internal asset reference plus the available manufacturer or serial identifiers. A serial number can be missing, corrected or replaced, so it should not be the only way to locate history. Document how the site and functional position relate to the installed device. 2. 02 Map business records by meaning Connect Salesforce relationship and asset context to the relevant NetSuite customer and supported service records. Do not map a CRM account to the NetSuite accounting Account object. Check the actual object model in both environments, especially when installed equipment uses custom records. 3. 03 Preserve installation and replacement history Represent replacement as an event or relationship with effective dates. Keep previous service and inspection documents attached to the device and location they described. The current customer view can highlight active equipment while historical records remain available for authorized service review. 4. 04 Control equipment-data edits Give service asset administration ownership of identifiers and installation relationships. Sales may update relationship contacts, but it should not silently change the device assigned to a completed visit. Route conflicting identifiers or unverified serial corrections to the owner rather than resolving them by the latest timestamp. 5. 05 Validate the service lookup Test a technician's ability to find the active asset, its prior replacement and the correct customer agreement. Verify Salesforce eligibility and NetSuite custom-record access for the proposed operations. Keep unsupported writes outside the automatic scope and provide an owned correction path. 6. 06 Separate asset correction from asset replacement A mistyped serial number is a correction to identity evidence; a newly installed device is a replacement relationship. Use different review paths so the team does not lose history by treating every changed serial as a new device, or overwrite history by treating every replacement as a typo. The reviewer should see the original entry, supporting field evidence and the intended relationship before accepting either kind of update. ![6-step operating sequence: Salesforce NetSuite sync for fire and security equipment](https://www.stacksync.com/images/blog-diagrams-mermaid/icp-fire-and-security-integrators-align-salesforce-installed-equipment-with-netsuite-customer-and-service-records.webp) *Follow the operating sequence; unresolved exceptions return to a responsible reviewer.* ## Handle the exceptions explicitly ### Replacement reuses a location label Keep a new device identity and link it to the same functional location. ### Serial number appears on two assets Hold the identity change for investigation instead of merging the devices automatically. ### Customer sells the building Review asset ownership, billing and coverage separately with effective dates. ## What to verify before expanding - Replacing a device preserves the prior service history. - The active asset resolves to the correct site and customer. - Sales contact edits cannot alter equipment identity. - A disputed serial number reaches an owned review queue. ## 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 installed asset example and the exception your team handles most often, for example replacement reuses a location label. - [Salesforce–NetSuite for Fire and Security Integrators](https://www.stacksync.com/use-case/salesforce-netsuite-fire-security-integrators) - [HubSpot–Acumatica for Inspection and Monitoring Contracts](https://www.stacksync.com/use-case/hubspot-acumatica-fire-security-contracts) - [Inspection and Monitoring Contracts: Align HubSpot Renewal Status With Acumatica Billing Accounts](https://www.stacksync.com/blog/inspection-and-monitoring-contracts-align-hubspot-renewal-status-with-acumatica-billing-accounts) - [Multi-Site Alarm and Access-Control Service: Connect a Supabase Asset Register With Salesforce](https://www.stacksync.com/blog/multi-site-alarm-and-access-control-service-connect-a-supabase-asset-register-with-salesforce) - [New Security Installations: Route Customer Acceptance Before Activating Recurring Billing](https://www.stacksync.com/blog/new-security-installations-route-customer-acceptance-before-activating-recurring-billing) - [Salesforce–NetSuite Integration: Mapping and Setup](https://www.stacksync.com/blog/the-complete-guide-to-salesforce-netsuite-integration-achieving-true-bi-directional-sync) - [Building Triggers and Workflows on Top of Your Bidirectional CRM Sync](https://www.stacksync.com/blog/building-triggers-and-workflows-on-top-of-your-bidirectional-crm-sync) 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 Can this certify that a fire system passed inspection? No. It maintains administrative records and evidence relationships. Inspection, technical acceptance and any required certification remain with qualified people and the applicable process. Are custom equipment objects automatically writable? No. Confirm the specific Salesforce object eligibility, NetSuite custom-record support and permissions. Connector availability alone does not establish every action on your asset model. Why separate location from device identity? The physical position may remain while the installed equipment changes. Keeping both lets service teams understand current equipment without attaching old inspection evidence to a replacement that was never inspected in that record. 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 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/)