Does it work with our existing HubSpot licenses?
Yes — the adapter rides on top of your existing HubSpot subscription. We use service-principal or OAuth M2M credentials so the integration never burns a named-user seat and never pushes you into a higher tier.
How is data security handled?
Tokens and credentials live inside a hardware-backed secret store with audit logging on every read. The HubSpot adapter runs on isolated workers with deny-by-default egress, and every message is replayable from a tamper-evident journal for downstream forensics.
What happens if HubSpot changes their API after we go live?
Our SRE team monitors HubSpot change announcements and rolls compatibility updates inside our maintenance retainer. If a breaking change ships, we own the migration; you don't pay extra to stay current and you don't field calls from the vendor.
How long does the HubSpot integration take to ship?
Our standard window is thirty days from signed scope to live HubSpot adapter in production, plus a one-week monitored stabilization phase. For Champaign, Illinois, that includes a sandbox loop with your team, parallel-run reconciliation, and a documented runbook handed to your operations lead.
Do we own the integration code at the end?
Yes. The Connectify HubSpot adapter ships with full source escrow rights — at any point you can request a snapshot of the code, configuration, and runbooks. We prefer you stay on our managed runtime, but you are never locked in.
Can the HubSpot adapter handle our custom fields?
On first connection the adapter discovers every custom field, custom object and custom workflow inside your HubSpot tenant and presents them as first-class mappings — you decide which to mirror, which to ignore, and which to enrich.