Most teams planning a monday.com to HubSpot migration export their boards and import them as deals. Six months later the stages mean three different things, half the deals have no contact, and the forecast is a guess.
The export is not the problem. A board lets you call anything an item and any column a status. A CRM does not. The migration is when someone has to decide what a deal, a contact and a stage mean in your company. Nothing in a board ever forced that decision.
What changed when you leave the board
On a board, an item can be a lead, a customer, a project or a task, depending on who set the board up. In HubSpot, records live in separate objects: contacts, companies, deals, tickets and others, linked by associations. HubSpot’s import file guide is strict about this. Each column header has to match a HubSpot property. New deals need a Deal name, a Pipeline and a Deal stage, and the pipeline and stage values must already exist in your account and fit each other. Dropdown values must match options that are already defined.
So the import will not invent your process for you. If your board has a status column with twelve values, someone has to decide which of them are real deal stages, which belong to onboarding, and which are just notes.
HubSpot’s App Marketplace does list a monday.com app built by monday.com, which maps monday.com items to HubSpot contacts, companies and deals. It is a sync between two tools that stay in use, not a migration plan. It still needs the same decisions about what each item becomes.
Who this matters for
- Founders and heads of sales who ran pipeline on a board and now want a forecast they can trust. The forecast depends on stage definitions made during the move.
- Heads of marketing who need contacts and companies as real records, so lists, emails and attribution work.
- Operations leads who kept delivery and sales on the same board. Those usually need to split.
If your team only tracks tasks and projects on monday.com and has no repeatable sales process yet, you may not need a CRM migration at all. That is an honest answer, and a cheaper one.
What to check in your portal before the monday.com to HubSpot migration
- Sort every board into objects. For each board, write down what one item really is: a person, a company, a sales opportunity, a support case or a project. Items that are tasks usually stay as tasks, not deals.
- Build the deal pipeline first. Go to Settings, then Data Management, then Objects, select Deals and open the Pipelines tab. Create the stages there before any import, because the import only accepts stages that already exist. HubSpot’s pipelines guide also notes that each stage in the default sales pipeline carries a probability, which feeds the weighted amount.
- Map status values to stages, one by one. Every old status gets one of three fates: a stage, a property value, or nothing. Write the mapping down and get the head of sales to sign it.
- Decide owners and identifiers. Owners can be imported by user email, which avoids clashes when two people share a name. Give every contact an email and every company a domain, so associated records do not import as duplicates.
- Run a small test import. Imports start in Data Management, then Data Integration, as the import guide describes. Map columns, mark unwanted ones as “Don’t import column”, and fix the errors shown before you load the full file.
For decisions every CRM move shares, like what to leave behind and how to clean data first, see our Salesforce to HubSpot migration post. This one is only about boards becoming objects.
Our take
The portal mirrors the process. A board export copies whatever process you had, including the parts nobody agreed on. That is why we treat a monday.com move as a process project with an import at the end, not an import with some cleanup after.
The real cost is not the file work. It is the two or three meetings where sales, marketing and delivery agree on what a deal is, where it starts, and when it is won. If nobody owns those decisions, the import will go fine and the CRM will still fail quietly.
Who should own it: the head of sales for stages, one admin for the mapping, and a named person who says no to new statuses after go-live. Put it inside a written HubSpot implementation plan, not a spreadsheet of columns.
Implementation
Planning a HubSpot rollout or a migration?
We set up pipelines, data and onboarding so the team actually uses it.
FAQ
Can I import monday.com boards directly into HubSpot?
You can export a board to a spreadsheet and import it, since HubSpot accepts .csv, .xlsx and .xls files with one sheet. Each column must map to a HubSpot property, and deal stages must exist before the import. The board itself does not carry over as a structure.
Should board items become deals or contacts in HubSpot?
It depends on what the item represents. A person becomes a contact, an organization a company, a sales opportunity a deal. Many boards mix these in one item, so split the columns into separate objects and link them through associations.
Is there a monday.com integration for HubSpot?
Yes, the HubSpot App Marketplace lists a monday.com app built by monday.com that connects items with contacts, companies and deals. It keeps two tools connected. It does not decide your stages or clean your data.
If you are moving this quarter, start with one hour and one sheet: list every board, write what an item on it really is, and list its status values. Bring that sheet to your head of sales before anyone touches the import button.
Related reading
Alignify
On this page
Get the audit checklist
All 25 checks as a spreadsheet with auto-scoring.
Talk to Alignify
45 minutes, your portal on screen, no slides. We show what we would fix first.