> For the complete documentation index, see [llms.txt](https://docs.mercuri.cx/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mercuri.cx/integrations-guide/hubspot/using-mercuri-in-hubspot/hubspot-contact-sync.md).

# HubSpot Contact Sync

<figure><img src="/files/ZWpGyEomBX0klX3YCsDV" alt=""><figcaption></figcaption></figure>

### Contact Sync Overview

The **Sync Contacts** button in Mercuri makes it easy to keep your contact database in sync with HubSpot. When clicked, Mercuri automatically fetches all contacts from your connected HubSpot account and updates the Mercuri contact list.

***

### How it works

1. **Initiate sync**\
   In the Mercuri **Contacts** view, click the **Sync Contacts** button at the top right.
2. **HubSpot fetch**\
   Mercuri will use your connected HubSpot OAuth token to call the HubSpot Contacts API.
3. **Data imported**
   * All contacts from HubSpot are fetched.
   * Standard fields such as First Name, Last Name, Phone, and Email are mapped into Mercuri.
   * If two-way sync is enabled, existing Mercuri contacts are updated with the latest data from HubSpot.
4. **Duplicate handling**\
   If Mercuri detects contacts with the same phone number or email, they will be flagged as duplicates. You can review these by clicking **Manage** on the Duplicate Contacts banner.
5. **Subscription status**\
   Mercuri can mark contacts as **Subscribed** or **Not Subscribed** based on HubSpot opt-in properties (if mapped in settings).

***

### Best practices

* **Normalize phone numbers** in HubSpot to E.164 format for best matching.
* Set up a regular sync schedule if your HubSpot contact list changes frequently.
* Review and merge duplicates periodically to maintain clean data.
* Ensure HubSpot properties used for mapping (like opt-in status) are kept up to date.

***

###


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.mercuri.cx/integrations-guide/hubspot/using-mercuri-in-hubspot/hubspot-contact-sync.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.