--- title: "Salesforce NetSuite sync for solar asset ownership changes" description: "Handle solar asset ownership changes without moving historical service obligations or invoices to the wrong customer." canonical: https://www.stacksync.com/blog/solar-fleet-ownership-changes-align-salesforce-asset-owners-with-netsuite-billing-customers last_modified: 2026-09-18 --- # Solar Fleet Ownership Changes: Align Salesforce Asset Owners With NetSuite Billing Customers > 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 Handle solar asset ownership changes without moving historical service obligations or invoices to the wrong customer. Author Ruben Burdin · Founder & CEO Published September 18, 2026 Read time 5 min read DATA ENGINEERING ## The operating decision Solar service organizations should model asset ownership, site contacts, service agreements and billing customers as separate effective-dated relationships. Salesforce–NetSuite two-way sync can distribute approved updates, but a change in the current asset owner must not rewrite historical invoices or automatically transfer an agreement. Finance and contract administration should review the commercial transition, while asset administration preserves the equipment and service history at the site. Explore the complete [solar installation and O&M services integration and automation hub](https://www.stacksync.com/industry/construction/solar-installation-service) for the systems and processes around this guide. ![Summary card: Salesforce NetSuite sync for solar asset ownership changes](https://www.stacksync.com/images/blog-highlights/icp-solar-fleet-ownership-changes-align-salesforce-asset-owners-with-netsuite-billing-customers.webp) ## What this looks like in solar installation and O&M services A solar O&M provider services a commercial installation after the property changes ownership. Salesforce needs the new customer relationship, dispatch needs new site-access contacts, and NetSuite must retain outstanding invoices for the previous customer. The installed equipment remains in place. A single overwrite of customer ID would blur who requested earlier service and who is responsible for future work. The handoff needs an effective date and a decision about the service agreement. ## Records, ownership, and update rules | Record | Owner | Operating rule | | --- | --- | --- | | Installed asset and site | Asset administration | Keep equipment identity stable across ownership changes. | | Ownership relationship | Account administration | Record previous and new owner with the reviewed effective date. | | Service agreement | Contract owner | Determine whether future service transfers, renews or requires a new agreement. | | Billing customer and receivables | Finance | Retain historical payer identity and approve future billing instructions. | ![Record ownership diagram: Installed asset and site, Ownership relationship, Service agreement](https://www.stacksync.com/images/blog-diagrams/icp-solar-fleet-ownership-changes-align-salesforce-asset-owners-with-netsuite-billing-customers.webp) *Define the record owner and the rule before enabling updates.* ## Work through the process 1. 01 Gather the transition evidence Capture the verified ownership-change reference, effective date and affected sites or assets. Do not infer transfer from a new contact email or company name. Ask the account owner to identify whether the change applies to one installation, a property portfolio or only the management contact. 2. 02 Preserve the equipment history Keep the installed-asset and site identifiers unchanged unless the equipment itself changes. Link prior service events to the relationships that applied at the time. The current view can highlight the new owner while historical visits remain attributable to the customer that authorized them. 3. 03 Review agreement treatment Have contract administration decide the future service obligation. Ownership transfer does not by itself establish assignment of every agreement or warranty relationship. Record the approved agreement reference and effective dates, and leave unresolved coverage visible to dispatch and account management. 4. 04 Apply finance changes deliberately Create or approve the new billing relationship using the supported NetSuite customer operations. Preserve open receivables and previously issued invoices under their correct historical customer. A CRM update should not automatically reassign debt or change financial document ownership. 5. 05 Reconcile current and historical views Test a visit before the transfer, a visit after it and a correction to an older invoice. Confirm the correct customer context for each date. Validate the selected Salesforce asset model and NetSuite record operations so the mapping respects both object capability and business authority. 6. 06 Recheck service contacts independently of billing Ownership transitions often change site access and reporting contacts before finance completes the new customer relationship. Record those updates under their own verified roles and dates. Dispatch may need the new facilities contact immediately, while future billing still waits for contract review. Keeping these paths separate lets operations use current access information without implying that a new payer, agreement transfer or outstanding-balance decision has already been approved. ![6-step operating sequence: Salesforce NetSuite sync for solar asset ownership changes](https://www.stacksync.com/images/blog-diagrams-mermaid/icp-solar-fleet-ownership-changes-align-salesforce-asset-owners-with-netsuite-billing-customers.webp) *Follow the operating sequence; unresolved exceptions return to a responsible reviewer.* ## Handle the exceptions explicitly ### Only the property manager changes Update coordination contacts without assuming the owner or payer changed. ### Transfer date is disputed Keep the proposed relationship pending and route the decision to the account and contract owners. ### Old customer has an unpaid invoice Preserve the finance record and handle any reassignment only through the authorized financial process. ## What to verify before expanding - The installation keeps its equipment and service history. - Past visits retain the customer context applicable at the time. - Future billing begins only under the approved relationship. - A contact change alone cannot transfer a service agreement. ## 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 and site example and the exception your team handles most often, for example only the property manager changes. - [HubSpot–Acumatica Two-Way Sync for Solar Installers](https://www.stacksync.com/use-case/hubspot-acumatica-solar-installers) - [Salesforce–NetSuite for Solar Installation and O&M](https://www.stacksync.com/use-case/salesforce-netsuite-solar-om) - [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) - [Solar Project Change Orders: Route Equipment Swaps Through Approval and Revised Billing](https://www.stacksync.com/blog/solar-project-change-orders-route-equipment-swaps-through-approval-and-revised-billing) - [Solar Service Visits: Route Confirmed Repair Completion Into O&M Billing](https://www.stacksync.com/blog/solar-service-visits-route-confirmed-repair-completion-into-o-m-billing) - [Distinguish Solar End Customers from Installation Partners](https://www.stacksync.com/blog/distinguish-solar-end-customers-from-installation-partners) - [Check Solar Installation Readiness Across Salesforce and NetSuite](https://www.stacksync.com/blog/check-solar-installation-readiness-across-salesforce-and-netsuite) 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 we create a new asset when ownership changes? Usually the physical asset identity should remain stable. Represent ownership as a relationship so historical service evidence stays attached to the equipment it described. Can the sync transfer outstanding balances? That is a separate financial decision and action. This design preserves approved customer relationships; it does not authorize moving receivables between parties. What should operations see while the transfer is unresolved? Show the current verified contact and agreement state, the pending change and the owner responsible for resolving it. Avoid presenting proposed coverage as active. 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 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) [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) ## 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/)