--- title: "HubSpot–Acumatica Two-Way Sync for Solar Installers" description: "Connect solar sales opportunities to approved customer and project context." canonical: https://www.stacksync.com/use-case/hubspot-acumatica-solar-installers last_modified: 2026-09-21 --- Solar installation and O&M services # HubSpot–Acumatica Two-Way Sync for Solar Installers > 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) Align HubSpot opportunities with Acumatica customer and project records for commercial solar installation. Preserve the site, legal customer, accepted scope and originating opportunity so sales and project teams can discuss the same work. Financial and project actions remain subject to their approved ownership and supported operations. Sales contact, site owner and payer can be different parties, while accepted scope changes during project delivery. [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. ### Make the project handoff identifiable Carry approved customer and opportunity references into the project relationship and return the confirmed destination ID. ### Keep revisions visible Distinguish accepted scope from later proposal edits so a forecast change cannot silently alter committed work. ### Scope your actual environment Review HubSpot representation, Acumatica endpoint fields and permissions before enabling project writes. The process, end to end ## Follow the work across systems a commercial installer sells through a property manager while a separate entity signs the agreement. The integration connects both relationships to the correct site and project without turning the sales contact into the automatic billing customer. [HubSpot connector](https://www.stacksync.com/connectors/hubspot) [Acumatica connector](https://www.stacksync.com/connectors/acumatica) [Review the integration details ↗](https://www.stacksync.com/integrations/acumatica-and-hubspot) Scope your implementation ## Bring these details to the demo - Customer, payer and site relationships - Project-setup prerequisites - Approved scope revision fields - Acumatica entities and permitted 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 - [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 closed-won automatically create a project? Only if the agreed prerequisites and verified action support that design. A reviewed setup task can be the initial scope. ### Can one opportunity relate to several installations? Yes. Preserve explicit project relationships rather than assuming one deal always equals one site. ### What happens when the property manager's contact changes after the project is set up? The contact update stays with the site relationship in HubSpot. It does not touch the legal customer or billing terms that finance approved in Acumatica, because those fields belong to finance. Your team sees the new coordinator on the project, and the payer record keeps its identity. If the change suggests a different party now signs or pays, route that question to finance for approval instead of rewriting the customer. ### Which Stacksync product should a solar installer start with for HubSpot and Acumatica? Start with two-way sync between HubSpot opportunities and Acumatica customers and projects. Once the site, payer and accepted scope references hold up across a real handoff, add workflows to route equipment changes and revised billing through technical and commercial approval. Genies come next to assemble closeout evidence against the final approved scope for a project owner to validate. EDI belongs later, when your equipment distributors exchange purchase orders and shipment notices as documents rather than synced records.