Solar Installer Customer Handoffs: Align HubSpot Opportunities With Acumatica Project Accounts

What this looks like in solar installation and O&M services

A commercial solar installer wins a project through a property manager, but the project customer is a separate ownership entity. Sales has the site and main contact in HubSpot; finance needs the approved payer and project information in Acumatica. The customer later changes the installation scope. If the deal is copied as an undifferentiated customer record, the project team loses the distinction between sales contact, site owner and the entity responsible for the agreement.

Records, ownership, and update rules

Work through the process

1. 01
   Identify the approved handoff event

   Define what makes the opportunity eligible for project setup. A salesperson's stage change may be one signal, but the handoff can also require accepted scope, verified customer identity and internal review. Make these prerequisites visible before the workflow acts on the synchronized record.
2. 02
   Map parties and location separately

   Record who owns the site, who coordinates the installation and who signs or pays under the agreement. Preserve those roles in the mapping. An updated property-manager contact should not replace the approved legal customer or change the project billing relationship.
3. 03
   Carry the accepted scope version

   Send the reference and agreed commercial fields for the approved revision. Keep later proposal edits separate so project administration can review changes deliberately. Returning project status to sales is useful, but it should not allow a forecast adjustment to alter an already accepted project amount.
4. 04
   Verify system representation

   Confirm the HubSpot objects and associations used for site and opportunity context, including any plan-specific custom objects. Review Acumatica endpoint fields, permissions and the intended project actions. Use supported reads and writes only, with a review task for any action not yet verified.
5. 05
   Reconcile changes after setup

   Test a corrected customer, a second project at the same site and a scope change after the project exists. Keep the original opportunity-to-project link and route changes as revisions. Record destination identifiers so a retried setup event cannot create another project.
6. 06
   Return the handoff status sales can act on

   Use separate states for awaiting customer setup, project created and commercial revision pending. A single synced flag tells the salesperson little about why the project team has not started. Include the destination reference and the next decision owner so account management can answer the customer accurately. Keep technical project detail in its owning workspace while exposing the specific administrative blocker that sales can help resolve.

Handle the exceptions explicitly

Property manager is not the legal customer

Preserve the relationship contact and request finance approval for the actual project customer.

One opportunity covers several installations

Create explicit project relationships rather than forcing all sites into one record.

Deal amount changes after acceptance

Keep the accepted amount and route the new value for commercial revision review.

What to verify before expanding

• Each project resolves to an approved customer and physical site.
• Retries reuse the established project cross-reference.
• Sales forecast edits cannot overwrite accepted project scope.
• A repeat installation at the same site remains a distinct project.

Technical references

• Stacksync HubSpot connector and object support
• Acumatica construction management