---
title: "Salesforce–NetSuite for Solar Installation and O&M"
description: "Keep solar asset, service and billing relationships aligned across ownership changes."
canonical: https://www.stacksync.com/use-case/salesforce-netsuite-solar-om
last_modified: 2026-09-21
---

Solar installation and O&M services

# Salesforce–NetSuite for Solar Installation and O&M

> 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

![Solar installation and O&M services systems connected through Stacksync two-way sync: HubSpot, Acumatica, Salesforce, NetSuite, Supabase](https://www.stacksync.com/images/industry-heroes/icp-solar-installation-service-800.webp)

Connect Salesforce customer and asset context with approved NetSuite billing and project records. Solar installation and O&M teams can preserve equipment history while tracking current ownership, contacts and agreement relationships. Effective-dated changes keep future service context distinct from historical invoices and authorizations.

An ownership or property-management change updates one system while service and billing still use the old relationship.

[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 commercial solar installers and O&M providers with 100–1,000 employees that combine equipment supply, installation and service.

### Preserve the installed asset

Keep the equipment and site identity stable while approved ownership relationships change.

### Separate future and historical billing

Finance controls the new customer relationship and the treatment of existing financial records.

### Show the current service obligation

Return verified agreement and customer context to account teams without assuming a transfer automatically assigns coverage.

The process, end to end

## Follow the work across systems

a commercial solar property changes owners. Dispatch needs a new site contact, account management needs the new relationship, and finance must retain invoices issued to the previous customer. The connection preserves all three meanings.

[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

- Asset and site identifiers
- Ownership effective dates
- Agreement-transfer review process
- Customer and financial field ownership

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

- [Solar Installer Customer Handoffs: Align HubSpot Opportunities With Acumatica Project Accounts](https://www.stacksync.com/blog/solar-installer-customer-handoffs-align-hubspot-opportunities-with-acumatica-project-accounts)

  Connect solar sales opportunities to approved Acumatica project customers without losing site, payer or scope identity.
- [Solar Fleet Ownership Changes: Align Salesforce Asset Owners With NetSuite Billing Customers](https://www.stacksync.com/blog/solar-fleet-ownership-changes-align-salesforce-asset-owners-with-netsuite-billing-customers)

  Handle solar asset ownership changes without moving historical service obligations or invoices to the wrong customer.
- [Solar Customer Portals: Connect HubSpot Milestones With Supabase Customer Access](https://www.stacksync.com/blog/solar-customer-portals-connect-hubspot-milestones-with-supabase-customer-access)

  Share verified solar project milestones through a customer portal with explicit site access and status ownership.

[Explore all solar installation and O&M services integration and automation guides ↗](https://www.stacksync.com/industry/construction/solar-installation-service)

## Common evaluation questions

### Does an owner change create a new asset?

The physical asset generally keeps its identity; ownership is a separately reviewed relationship.

### Can past invoices move automatically?

No blanket transfer is implied. Financial corrections require the authorized finance process.

### Can this support ongoing O&M after installation?

Yes, when the mapped customer, asset and agreement records support the service handoffs you want to improve.

### Where does a solar O&M provider begin with Stacksync when Salesforce and NetSuite hold the customer and asset records?

Begin with two-way sync so the Salesforce asset, site and ownership relationship match the NetSuite billing customer under a reviewed effective date. When that holds across a real ownership change, add workflows to carry confirmed repair completion, coverage and customer authorization into a finance review queue. Genies follow for closeout, gathering serial and completion evidence against the approved scope for your project owners to check. EDI comes last, for supplier purchase lines and partial equipment deliveries that arrive as documents, not synced records.
