> ## Documentation Index
> Fetch the complete documentation index at: https://usepike.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# HubSpot

> Connect HubSpot CRM to Pike so companies, contacts, and deals stay aligned with customers and pipeline in your workspace.

Connecting **HubSpot** to Pike closes the gap between **revenue and CRM** (HubSpot) and **delivery and PSA** (Pike). Marketing and sales keep working in HubSpot; delivery, time, and projects stay in Pike—with **customers** and **deals** that reflect what your team already tracks in the CRM.

For how deals work inside Pike, see [Deals](/customers/deals). For customer records, see [Customers](/customers/overview).

## 1. Connecting HubSpot with Pike

1. Go to **Workspace settings** → **Integrations** → **HubSpot**
2. Click **Add integration**
3. Complete the OAuth flow to authorise Pike for your HubSpot account (choose the portal you want to sync)

Workspace admins can connect the integration; only members who should see synced data need access to **Customers** and **Deals** in Pike as usual.

## 2. What syncs from HubSpot to Pike

After a successful connection, use **Import data** or scheduled sync on the integration page to bring CRM entities into Pike. Typical mappings:

### Companies → customers

* **HubSpot company** records become or update **Pike customers** when a match is found (by linked HubSpot company id) or when you allow creation of new customers from HubSpot.
* **Company name** maps to Pike **customer name**.
* **Company domain** and **address** fields help populate primary contact and billing-style details where your workspace uses them.
* Each synced Pike customer carries an integration marker so you can see it came from HubSpot and when it was last updated.

### Contacts → customer contacts

* **HubSpot contacts** associated with a company are attached to the corresponding Pike customer as **contacts** (for example primary contact name, email, and phone), so proposals and delivery comms align with CRM.

### Deals → deals

* **HubSpot deals** sync into Pike **[Deals](/customers/deals)** so pipeline value and stage stay visible next to delivery work.
* **Deal name** and **amount** map to Pike deal title and **value**.
* **Pipeline stage** in HubSpot maps to Pike **deal stages** (for example Prospect, Qualified, Proposal, Negotiation, Won, Lost)—you configure how HubSpot stages align to Pike stages in the integration settings so both tools speak the same language.
* **Deal owner** in HubSpot maps to Pike **owner** when the HubSpot user’s email matches a **workspace member**; otherwise the deal still syncs with owner metadata from HubSpot for reference.

This keeps [pipeline value and forecasting](/customers/deals) in Pike aligned with HubSpot without re-keying opportunities.

## 3. Sync direction and edits

* **Default:** HubSpot is the **system of record** for company, contact, and deal **fields** that originate in CRM. Updates in HubSpot flow to Pike on sync.
* **Pike-specific fields** (for example linking a deal to a **project** after win, or internal notes) remain managed in Pike.
* When a deal is **closed won** in HubSpot, Pike can reflect **Won** and your team can attach the resulting **project** without losing the CRM history.

Use **Refresh** on a customer or deal in Pike to pull the latest from HubSpot when you need up-to-the-minute alignment before a meeting or handoff.

## 4. Synced entity management

For entities connected to HubSpot you will see:

* A **Refresh** action to update from HubSpot
* **Last synced** time
* A clear indicator that the record is tied to HubSpot

<Tip>
  If you also use accounting integrations (for example
  [QuickBooks](/integrations/quickbooks)), treat **HubSpot** as source for
  **pipeline and CRM identity**, and your accounting system as source for
  **posted invoices**—Pike is where those views meet for your team.
</Tip>