--- title: "Salesforce–NetSuite for Fire and Security Integrators" description: "Keep installed-equipment, site and billing-customer context connected through the service lifecycle." canonical: https://www.stacksync.com/use-case/salesforce-netsuite-fire-security-integrators last_modified: 2026-09-21 --- Fire, life-safety and security integrators # Salesforce–NetSuite for Fire and Security Integrators > 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 ![Fire, life-safety and security integrators systems connected through Stacksync two-way sync: Salesforce, NetSuite, HubSpot, Acumatica, Supabase](https://www.stacksync.com/images/industry-heroes/icp-fire-life-safety-security-integrators-800.webp) Connect Salesforce customer and asset context with the approved NetSuite commercial records for fire, life-safety and security service. Preserve device identity, site relationships and replacement history while finance controls billing customers. Scope the supported objects and actions against your actual asset model. Service teams find one device label in a report, another in the CRM and a different customer relationship in billing. [Book a demo](https://www.stacksync.com/book-a-demo) Explore your process in a demo, or get our shared two-way sync architecture guide. When this fits ## Built for this operating problem US fire, life-safety, alarm and access-control integrators with 100–1,000 employees that supply equipment and deliver installation or recurring service. ### Keep equipment history intact Separate the device from its functional location so replacements do not erase the evidence for prior work. ### Connect service and commercial context Let account and service teams find the correct customer and agreement references without changing finance-owned decisions. ### Review custom-record capability Validate object eligibility and permissions rather than assuming every installed-asset representation supports the same writes. The process, end to end ## Follow the work across systems an integrator replaces a panel at a long-served property. The current device changes, but historical service records and the property's customer relationship must remain traceable to the correct equipment and dates. [Salesforce connector](https://www.stacksync.com/connectors/salesforce) [NetSuite connector](https://www.stacksync.com/connectors/netsuite) [Review the integration details ↗](https://www.stacksync.com/integrations/netsuite-and-salesforce) Scope your implementation ## Bring these details to the demo - Installed-asset and site model - Replacement-history requirements - NetSuite customer and service records - Field ownership and supported operations Review [current platform pricing](https://www.stacksync.com/pricing) alongside the records, volume, and actions in your process. Use your own operating baseline to evaluate the economics. [Book a demo](https://www.stacksync.com/book-a-demo) Explore your process in a demo, or get our shared two-way sync architecture guide. From foundation to action ## One connected operating process 01 ### [Two-way sync](https://www.stacksync.com/two-way-sync) Keep shared customer, order, and operational records aligned, with clear field ownership. Explore two-way sync 02 ### [Workflows](https://www.stacksync.com/workflow-automation) Move approved work between systems, assign exceptions, and confirm the result. Explore workflows 03 ### [AI agents (Genies)](https://www.stacksync.com/ai-agents) Investigate cross-system questions, assemble the evidence, and prepare the next action. Explore ai agents (genies) 04 ### [EDI](https://www.stacksync.com/edi) Connect trading-partner documents to operational records and exception handling. Explore edi Go deeper ## Implementation guides for your team - [Fire and Security Integrators: Align Salesforce Installed Equipment With NetSuite Customer and Service Records](https://www.stacksync.com/blog/fire-and-security-integrators-align-salesforce-installed-equipment-with-netsuite-customer-and-service-records) Connect installed fire and security asset context to customer and service records without losing device identity. - [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) Separate inspection and monitoring agreement terms from sales renewal stages and finance-owned 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) Build a multisite alarm and access-control asset register with clear identity, service history and authorized access. [Explore all fire, life-safety and security integrators integration and automation guides ↗](https://www.stacksync.com/industry/construction/fire-life-safety-security-integrators) ## Common evaluation questions ### Does this certify inspection results? No. It maintains administrative context; qualified personnel retain inspection and technical decisions. ### Can a property change owners without losing asset history? Yes. Preserve asset identity and review ownership, service and billing relationships separately. ### What will we validate first? Validate a replacement device, a multisite account and the customer lookup used by service and finance. ### Which Stacksync product should a fire and security integrator start with? Start with two-way sync between Salesforce and NetSuite so installed-asset, site and billing-customer records share one identity before anything acts on them. Add workflows once that context holds, for example routing a disputed serial number or a property ownership change to the person who owns it. Bring in Genies when coordinators want replacement history and agreement references assembled into a review packet that a person still approves. EDI comes last, as a separate transport for supplier shipment documents on project equipment headed into NetSuite.