In Brief: monday.com and HubSpot connect through two native options. monday.com's own app pushes HubSpot contacts, companies and deals into a board, then keeps only a short list of default fields updated. HubSpot Data Sync runs one-way or two-way between monday.com items and HubSpot records, with custom field mappings on Data Hub Starter or above. Whichever you choose, three setup decisions determine whether the sync holds: which HubSpot object an item becomes, how records are matched, and which system wins a conflict.
Sales closes the deal in HubSpot. Delivery picks it up in monday.com. Somewhere between the two, customer details get retyped, statuses drift out of date, and nobody is quite sure whether the board or the CRM record is the one to trust.
Connecting the two tools is the easy part. Either native app installs in minutes. What decides whether a monday.com and HubSpot integration actually holds is the set of choices on the setup screen, most of which come pre-filled and are easy to click past.
The same lesson runs through our Mailchimp to HubSpot migration guide: what a connector moves is narrower than teams assume. This post walks through the decisions in the order you meet them, with every setting checked against monday.com's and HubSpot's documentation in October 2026.
HubSpot
monday.com app
one-way, default fields
one-way, default fields
HubSpot Data Sync
one- or two-way, per field
one- or two-way, per field
monday
.com
.com
Two Native monday.com and HubSpot Integrations, and Why the Choice Matters
There are two separate apps, built by two different companies, and they work in very different ways. The HubSpot Jira integration has a similar split: two apps with similar names, very different behaviour.
The monday.com app is set up from inside a board: you pick a template and map HubSpot contact, company or deal fields to board columns. Any field, custom or not, can be mapped when the item is created.
After that, according to monday.com's HubSpot integration documentation, only a short list of default fields keeps syncing:
- Companies: name and domain
- Contacts: email, first and last name, owner and job title
- Deals: name, pipeline, stage, amount, close date and owner
One detail catches teams out: deal owner arrives as a HubSpot owner ID, not a name.
HubSpot Data Sync for monday.com is set up from HubSpot's connected apps. It syncs monday.com items with almost any HubSpot record, one-way or two-way, brings historical data across on the first run and comes with default field mappings.
| monday.com appBuilt by monday.com | HubSpot Data SyncBuilt by HubSpot | |
|---|---|---|
| 🔄Sync direction |
monday.com appOne-way HubSpot → monday.com |
HubSpot Data SyncOne- or two-way HubSpot ⇄ monday.com, set per field |
| 🗂️HubSpot records | monday.com appContacts, companies, deals | HubSpot Data SyncContacts, companies, deals, tickets, orders, tasks, invoices, products, custom objects and more |
| 📥Existing records |
monday.com appNot synced At setup, as reported in user reviews |
HubSpot Data SyncSynced Historical records on the first run |
| 🧩Custom fields |
monday.com appLimited Mapped on item creation; only a short list of default fields keeps updating |
HubSpot Data SyncSupported Custom mappings on Data Hub Starter or above |
| 🎯Best for | monday.com appHanding new contacts or deals to a delivery board | HubSpot Data SyncKeeping commercial and delivery data aligned in both systems |
A simple rule of thumb: if delivery only needs to receive work from sales, the monday.com app can be enough. If HubSpot needs to know what happens after the sale, such as delivery status, completion dates or fulfilment, you need Data Sync, and the rest of this post applies.
Want delivery progress visible next to your pipeline?
Explore HubSpot CRM DashboardsChoose the HubSpot Object Before You Map a Single Field
In HubSpot Data Sync, a monday.com item can become almost any HubSpot record. The setup screen asks for this first, and it is the hardest choice to undo, because every mapping, filter and report built afterwards depends on it. The question to answer is what one row on your board actually represents:
- A project with commercial value belongs on Deals, so it stays inside pipeline and revenue reporting.
- Something being fulfilled or shipped belongs on Orders, so fulfilment data sits with the customer record.
- A request or case being worked belongs on Tickets, so it follows your service process.
- Something with its own lifecycle, such as an implementation or an installation, may need a custom object rather than being forced into one of the above.
In one recent setup, board items mapped to HubSpot Orders: the item's created date to the order's created date, its name to the order name, its status to the order status, and its completion date to the order's closed date. Note that Name is a required field on the HubSpot side, so an item without one has nothing to create a record from.
Every migration starts with this question too, as we explained in our Attio to HubSpot migration guide: decide what a record means on the other side before you move it.
Record Matching: The Setting That Decides Pairs or Duplicates
Get this setting wrong and your first sync either duplicates records or fails on them. Most guides skip it, yet it is the screen that decides what your first sync creates.
HubSpot supports three matching methods: default settings (email for contacts, company name or domain for companies), your own chosen fields, or no matching at all, though not every app and object offers all three. For monday.com items synced to Orders, the screen offers two: choose your own fields to match on, or do no matching.
Here is how it works, based on HubSpot's record matching documentation. When the matching property finds a record on the other side, the sync does not create anything new. It pairs the two record IDs and keeps them in sync from then on. When no match is found, the sync creates a new record on the other side and pairs that instead. In other words, the first sync makes a permanent decision about every record it touches.
Do no matching is the option HubSpot suggests when you are bringing all your records over for the first time. If records already exist in both systems, it can create one-time duplicates during the initial sync or cause record syncs to fail.
To see what is at stake, picture 400 deals already in HubSpot and the same 400 projects on a monday.com board. With no matching, the first sync has nothing to pair them on, so you could end up with 800 records, or with a long list of failed syncs to work through.
Choose my own fields to match on is the safer option whenever both systems already hold data. Pick one property that is unique and filled in on both sides, such as an order number or a project reference. Only text fields qualify. HubSpot matches on that property alone, so inconsistent formatting, like a prefix in one system and not the other, means no match and a new record.
Two more rules matter. Only use a record ID as the matching key if those IDs have already been synced across. And because this choice applies only to records that have not been matched yet, changing it later will not undo pairs that already exist.
"The record matching screen looks like a setup detail, but it decides whether your first sync pairs your records or quietly duplicates them. We treat it as an architecture decision, not a checkbox," says Antonio Karneluti, CTO of Loncom Consulting.
If duplicates have already landed, resist the urge to disconnect and run the first sync again. A second run on unmatched data usually doubles the problem. We took this approach when finishing an Insightly to HubSpot migration without re-importing: fix the matching key first, then clean up what already exists.
Data Conflict Resolution: Decide Which System Owns Which Data
If both systems can edit the same field, one of them has to lose. Data conflict resolution decides which: it sets the app that overwrites the other when it is unclear which one has the most up-to-date information. HubSpot notes that these conflicts mostly happen during the first sync. When there is no conflict, your field mapping rules decide what data moves.
That makes field ownership, not the dropdown, the real decision in any HubSpot monday.com two-way sync. A model that works for most sales-to-delivery handoffs looks like this:
- HubSpot owns commercial data: amount, close date and deal owner. These map one-way into monday.com.
- monday.com owns delivery data: delivery status, completion date and the assigned team. These map one-way into HubSpot.
- Two-way only where both teams genuinely edit the same field, and those fields should be few.
Ownership in the sync should also match ownership inside HubSpot. If delivery data is supposed to come only from monday.com, HubSpot users should not be able to overwrite it by hand, which is where HubSpot permissions and user roles come in.
How to Sync HubSpot Deals to monday.com Without Breaking Your Data
With those decisions made, the setup itself follows a predictable sequence:
- Audit both systems. Count the records on each side, look for duplicates, and confirm a shared unique reference exists.
- Align your values. monday.com status labels and HubSpot dropdown options or deal stages need to match, or values will not land where you expect.
- Write down the object, the matching key and field ownership before opening the setup screen.
- Start with a test board and a filter. Data Sync lets you filter by field or by HubSpot list, so sync a small, known set of records first.
- Run one-way first, check the results record by record, then switch the agreed fields to two-way.
- Check sync errors weekly for the first month, while edge cases surface.
That last step matters more than it looks. An integration that shows as connected is not proof that records are moving, as we found when auditing a HubSpot-Shopify integration that looked healthy on paper.
monday.com HubSpot Integration Limitations, and Why Updates Stop Syncing
The monday.com app has firm limits. Setup needs a HubSpot Super Admin and a monday.com Standard, Pro or Enterprise plan. Only the short list of default fields updates after an item is created.
There are structural limits too. monday.com recommends no more than one HubSpot template per board. The same HubSpot portal cannot be connected to several monday.com users or accounts; to create a new connection, all existing HubSpot integrations on that portal have to be deleted first. The integration column it adds to your board cannot be edited, and the app is not available on monday.com's AU server.
Data Sync is more flexible, but not immune to the same symptom. The one review on HubSpot's monday.com Data Sync listing reports that the initial sync worked while later HubSpot updates never reached monday.com, and HubSpot replied that its support team could investigate. When updates stop, check these in order:
- Which app is installed. With the monday.com app, fields outside the short default list never update after creation. That is by design, not a fault.
- The direction of that specific mapping. A field set to sync from monday.com to HubSpot will ignore changes made in HubSpot.
- Whether the mapping is switched on. Individual mappings can be turned off without anything else looking different.
- Whether the record is still inside the sync filter. A record that drops out of a filter or list may stop syncing.
- Whether the value fits. A status label with no matching dropdown option on the other side may fail to write.
- The sync errors HubSpot reports for the integration in your connected apps.
When Native Sync Is Not Enough
For most sales-to-delivery handoffs, Data Sync with the right object, matching key and ownership model is enough. It stops being enough when the logic outgrows field mappings: creating a full project from a board template with predefined subitems, syncing subitems at all (HubSpot's listing names items as the monday.com data source, not subitems), transforming values on the way, or guaranteeing delivery at high volume with retries and alerting.
That is where a custom integration built on the monday.com and HubSpot APIs earns its cost. The decisions in this post do not go away; they just get written into code instead of a setup screen. If you are weighing that step, our integration services cover both native setups and custom builds.
Planning a monday.com and HubSpot integration?
Book a Free ConsultationFAQ
Does monday.com integrate with HubSpot?
Yes, through two native options. monday.com's own app sends HubSpot contacts, companies and deals into a board, and HubSpot Data Sync connects monday.com items with HubSpot records in one or both directions. Third-party platforms and custom API integrations cover more complex logic.
How do I connect monday.com to HubSpot?
For the monday.com app, open a board, click Integrate, choose HubSpot and a template, then connect a HubSpot account with Super Admin access and map the fields. For HubSpot Data Sync, install the monday.com app from the HubSpot Marketplace, connect your monday.com account, then choose the HubSpot object, sync direction, record matching, conflict resolution and field mappings.
Is the monday.com HubSpot integration two-way?
It depends on which app you use. The monday.com app only syncs from HubSpot to monday.com. HubSpot Data Sync supports two-way sync, and each field mapping can be set to one-way or two-way separately.
Which HubSpot plan do I need for monday.com Data Sync?
HubSpot's listing ties custom field mappings, and activating the sync, to Data Hub Starter or above. You can install the app first to check whether the default mappings fit your use case. A monday.com subscription is also required.
Why aren't HubSpot updates syncing to monday.com?
Common causes are the monday.com app's short list of syncing fields, a field mapped one-way in the other direction, a mapping that is switched off, a record that has dropped out of the sync filter, or a value with no matching option on the other side. The sync errors HubSpot reports for the integration are the place to start.
Can I sync HubSpot custom properties to monday.com?
With the monday.com app, custom properties can be mapped when an item is created but do not update afterwards. With HubSpot Data Sync, custom properties sync continuously through custom field mappings, which need Data Hub Starter or above.
How does Loncom set up a monday.com and HubSpot integration?
We start with the decisions, not the connector: which HubSpot object a monday.com item becomes, which property matches records, and which system owns each field. We then audit and align data in both systems, test on a filtered board, and roll out one-way before enabling two-way sync. When the logic goes beyond what native mappings support, we build a custom integration. As a HubSpot Diamond Solutions Partner with 150+ CRM implementations, we treat every sync as part of the wider CRM architecture.
Share:
Leave a comment