Teams that run sales on monday.com reach the same point sooner or later. The board that worked for forty deals does not work for four hundred, and the questions the founder asks (which channel produced this deal, what will close this quarter) are not ones a board can answer. The decision to move to HubSpot is the easy part. The mapping is where the work is.
Every monday.com and HubSpot limit below was read on the vendor's own documentation on 7 October 2026 and is linked. INSIDEA's timelines are the ones published on its monday.com to HubSpot migration page. Where something could not be verified, the text says so.
How do monday.com boards map to HubSpot objects?
A board is one table of items. HubSpot is several linked objects. So one board usually becomes two or three: items on a deals board become deals, the company name on each row becomes a company record, and the contact email becomes a contact. The links between them, which the board held implicitly on one row, become associations.
That is the first decision in the mapping document, and it is made per board, not per account:
- A leads or contacts board becomes contacts, with the company column split out into company records.
- A deals or pipeline board becomes deals, associated to the contact and company on the same row.
- An accounts board becomes companies.
- A project or onboarding board usually stays in monday.com. More on that below.
Groups on a board need a decision too. If the groups are stages ("New", "Proposal sent", "Won"), they become deal stages. If they are time periods or owners, they become a property or are dropped, because HubSpot already has a close date and an owner on every deal.
Which monday.com columns map to which HubSpot property types?
Most columns have a direct equivalent. Status and Dropdown become dropdown select or multiple checkboxes properties, People becomes the record owner, Date becomes a date picker, Numbers becomes a number property. The ones that need a design decision are Timeline, Formula, Files, Connect boards, Mirror and Subitems.
| monday.com column | HubSpot property type | What to decide |
|---|---|---|
| Item name | Deal name, Company name, or first and last name | Contact names are split into two properties |
| Status (the main one) | Deal stage in a pipeline | Each label becomes a stage with exit criteria |
| Status (others), Dropdown | Dropdown select, or multiple checkboxes when several values apply | Options are created in HubSpot before the import |
| People | Record owner | Each person needs a HubSpot user first |
| Date | Date picker | Use one date format across the file |
| Timeline | Two date picker properties, start and end | HubSpot has no single range field |
| Numbers | Number, formatted as currency where it is money | The deal value goes to Amount |
| Text, Long Text | Single-line text, multi-line text | Free text that drives reports becomes a dropdown |
| Email, Phone, Link | The default Email property, phone number, URL | Email is the contact's unique identifier |
| Formula | Calculation or rollup property | Rebuilt, not imported |
| Files | File property or record attachments | Files are moved separately |
| Connect boards, Mirror | Associations between records | Rebuilt as object relationships |
| Subitems | Line items, tasks or associated records | Depends on what the subitems hold |
The HubSpot side of this table follows HubSpot's property field types page and its import file requirements, both read on 7 October 2026. Three rules from the import page shape the file:
- Multiple checkbox values are separated by a semicolon with no spaces, and the options must exist before the import.
- New deals need a deal name, a pipeline and a deal stage, and the stage must be a valid stage in that pipeline. A status label that has no matching stage stops the row.
- To update records and avoid duplicates, each object needs a unique identifier: email for contacts, company domain name for companies, or the record ID.
One gap to name: the monday.com pages we read do not say how Formula, Mirror and Connect boards columns appear in an export file. Run a sample export of each board before the mapping is signed off and look at those columns first.
What does not transfer from monday.com to HubSpot?
Six things, and none of them is a surprise once you have seen the export. Board views, subitem updates, the Auto Number column, automations, dashboards and the files themselves do not arrive in the spreadsheet. Each one is rebuilt in HubSpot or moved by a separate step.
The first three come from monday.com's export documentation, last modified on 2 October 2026 and read on 7 October 2026:
- Board views. Only table views export. Kanban, chart and other views are rebuilt as HubSpot board views, saved views and reports.
- Subitem updates. Item updates export; updates written on subitems do not. If the sales notes live on subitems, they are copied out by hand or through the API.
- Auto Number. The column is not supported in the export. If the number is a reference customers quote, keep it by copying it into a text column before exporting.
- Automations. Recipes are logic, not data. Each one is read, mapped to a HubSpot workflow and tested.
- Dashboards. Rebuilt as HubSpot reports and dashboards, which is usually the reason for the move.
- Files. A spreadsheet carries data, not documents. An account admin can download the whole account as a zip file containing all boards and files, per the same monday.com page. HubSpot's import page says a file property takes the File ID of a file already uploaded to HubSpot, so files are uploaded first and referenced second.
How do updates and activity history get across?
Through the Updates tab of the export, loaded into HubSpot as notes. When a board is exported with updates, monday.com puts the table in one tab and every update and reply in a second tab. HubSpot's importer accepts files with only one sheet, so that second tab is saved as its own file and imported as notes.
Two details decide whether the history reads well afterwards:
- The date. HubSpot's import page lists Note body as the required property for notes and recommends an Activity date. Without it, every note is stamped with the date and time of the import, and three years of history appears to have happened on one afternoon.
- The record. Each note has to land on the right deal or contact, so the notes file carries the unique identifier of the record it belongs to.
A worked example on size, as an illustration and not a client figure. A sales board with 4,000 items is 4 percent of the 100,000 items monday.com exports from one board at a time. A paid HubSpot account imports up to 1,048,576 rows per file, so those 4,000 rows are under half a percent of one file. Volume is almost never the constraint in a monday.com migration. The mapping is.
How long does it take, and what does it cost?
INSIDEA's published plan is 4 weeks for a light migration and 6 to 8 weeks with a marketing rebuild. It is scoped as a fixed fee, from $2,000, with the number, the scope and the timeline written down before work begins.
The four phases on the migration page are audit and plan in week 1, build in a HubSpot sandbox in weeks 2 to 3, cutover in week 4 in three waves under a 24-hour freeze, and training and hand-off in weeks 5 to 6. Thirty days of post-cutover support follow. The migration timelines page compares this with other source systems, and the Salesforce timeline post shows how much longer a migration runs when there is custom code to translate.
The customer supplies three things: one person who can decide what a stage means, admin access to monday.com in week one, and a team that will accept the freeze.
When should you keep monday.com?
Often, for project work. Moving the CRM out of monday.com does not mean leaving monday.com. Most teams keep it for delivery and onboarding boards and use HubSpot for contacts, deals and reporting, with the two connected so project status shows on the HubSpot record.
And sometimes the answer is not to migrate at all. If the sales motion is simple and a board fits it, if the automations run across project, marketing and sales boards and would be costly to rebuild, or if the company is small enough that HubSpot's price is not yet justified, staying is the better call. The HubSpot vs monday.com comparison sets out where each one fits.
INSIDEA
Ready to get more out of HubSpot?
We are an Elite HubSpot Partner rated 4.99 across 500+ verified reviews. Let's make your portal work harder.
Where INSIDEA fits
INSIDEA is an Elite HubSpot Partner, rated 4.99 across 500+ verified reviews, and holds HubSpot's CRM Data Migration Accreditation. What that credential covers is on the CRM Data Migration Accreditation page.
On a monday.com migration that means a sample export of every board before a quote, a mapping document signed off before anything is built, a build in a sandbox, cutover in three waves with same-day rollback, and validation against the board's own counts. If you want to see how other partners approach it, the agencies for a monday.com to HubSpot migration page lists them on the same criteria.
How INSIDEA works
