Two-way record sync
HubSpot contacts map to OpenSolar contacts. HubSpot deals map to OpenSolar projects. Supported field changes can flow in either direction.
HubSpot contact⇄OpenSolar contact
HubSpot deal⇄OpenSolar project
HubSpot ↔ OpenSolar
Contacts, deals and solar projects update both ways automatically — with live OpenSolar data right on the HubSpot record.
Contactskept aligned
Deals + projectslinked together
Relationshipspreserved across tools
CRM cardssolar context in HubSpot
One customer journey, not two data silos
Sales lives in HubSpot. Design and proposals live in OpenSolar. SolarSync handles the hand-off so your team can work where they are strongest without re-keying the same customer.
HubSpot contacts map to OpenSolar contacts. HubSpot deals map to OpenSolar projects. Supported field changes can flow in either direction.
HubSpot contact⇄OpenSolar contact
HubSpot deal⇄OpenSolar project
When contacts belong to a deal or project, SolarSync mirrors the supported associations instead of leaving disconnected records behind.
CRM cards show project stage, annual usage, dates, notes and linked contacts, with a direct route back to the OpenSolar record.
Choose canonical and custom field mappings, direction, empty-value behaviour, and optional deal-stage creation guards per connection.
From install to useful
There is no browser extension and no desktop agent. SolarSync runs as a hosted integration between your accounts.
Approve the requested contact, deal and file scopes through HubSpot OAuth.
Authenticate to OpenSolar and select the organisation that should pair with the HubSpot portal.
Confirm mappings and creation guards. New events then keep connected records aligned.
Less tab switching
OpenSolar project context appears alongside the HubSpot record: the information needed for the next customer conversation, plus a direct link when deeper design detail is required.
Designed for customer data
The app requests the contact, deal and file permissions used by the integration—not broad company or list scopes.
HubSpot callbacks and UI data requests are signature-checked. OpenSolar webhooks use a configured shared secret.
OpenSolar credentials are exchanged for an API token during setup; the password itself is not stored by SolarSync.
Review what is processed, why it is needed and how to request deletion in the privacy policy.
Simple launch pricing
Start with the complete HubSpot + OpenSolar integration. Need onboarding help or a tailored rollout? Talk to us.
SolarSync Standard
$30 USD / month
15 days free
Questions before installing? Email support.
Good questions
For setup help or a workflow question that is not covered here, email support@solarsync.app.
The commercial launch path connects one HubSpot portal with an OpenSolar organisation. Contacts map to contacts; HubSpot deals map to OpenSolar projects; supported associations and configured fields are kept aligned.
Sync is webhook-driven, so updates normally begin shortly after HubSpot or OpenSolar sends an event. Provider delivery, rate limits and temporary outages can add delay, so SolarSync does not promise an exact number of seconds.
The standard flow acts on new records and subsequent supported updates. Historical bulk backfill is not automatic today; contact support before launch if you need an existing database migrated.
No. SolarSync does not automatically delete the counterpart record when a source record is deleted. This is deliberate for launch safety and prevents an accidental deletion in one system from erasing work in the other.
They are not part of the public commercial plan yet. Those connectors remain pre-release while their onboarding, support and security paths are completed.
Email support@solarsync.app from the address associated with your account. We will confirm the account, help with billing cancellation and handle deletion under the published privacy policy.
The hand-off can happen by itself