Migrate from HubSpot to monday CRM

HubSpot Contacts map to Monday.com Person entities and optionally as Board Items on a Contacts board. The HubSpot contact's email, phone, lifecycle stage, and custom properties map to Monday.com Column types (Email, Phone, Status, Text, Number, Date). The original HubSpot contact ID is preserved as a Legacy ID column for traceability. Note that Monday.com has no native Contact object with a lifetime timeline; contact records live as Items on a board rather than a normalized relational table.

HubSpot Company records map to Monday.com Groups on a Companies board, or optionally as Items with the company name in a Name column. The HubSpot company domain maps to a Website Column type. HubSpot's contact-to-company association is preserved by linking the related Contact Items to the same Group or by storing the HubSpot company ID in a Legacy Company ID column on each Contact Item.

HubSpot Deals map to Monday.com Items on a pipeline board. The HubSpot dealstage maps to a Status column on the board, with each HubSpot pipeline stage becoming a Status value. Deal amount, close date, owner, and hubspot_object_id map to Number, Date, Person, and Text columns respectively. The HubSpot pipeline name becomes the board name or a Board Label. Multi-pipeline setups in HubSpot (up to 100 at Enterprise) map to multiple Monday.com boards, each with its own Group/Status structure.

Each HubSpot deal pipeline stage maps to a Monday.com Status column value. We configure the Status options to match the HubSpot stage names (e.g., Appointment Scheduled, Qualified to Buy, Presentation Scheduled, Decision Maker Bought-In, Contract Sent). Stage probabilities from HubSpot do not migrate natively; we document them as a reference for the Monday.com team to configure Forecast columns if needed.

HubSpot pipelines (up to 15 on Professional, 100 on Enterprise) map to separate Monday.com Boards. On Starter (1 pipeline), this is a single board; on Professional and Enterprise, we create one board per HubSpot pipeline and use Board Labels to distinguish pipeline context. Pipeline-level settings like associated Deal stages and deal-stage probability are documented as Monday.com board configuration notes for the customer's admin.

HubSpot email engagements (email body, timestamp, sender, recipient) migrate as Items on a dedicated Activity board. Each Item is tagged with the related Contact and Deal via Connect board columns or a text reference column storing the HubSpot contact and deal IDs. The email subject becomes the Item name; the body becomes a Text column. Monday.com does not have a native email timeline; this tagging approach gives reps a way to retrieve the activity record without a native association model.

HubSpot call engagements (duration, disposition, recording URL, outcome) migrate as Items on the Activity board with a Call Type column. Call duration maps to a Number column; disposition maps to a Status or Tags column. Each Item is linked to the originating Contact via a Connect board column or Legacy Contact ID text reference.

HubSpot meeting engagements (title, start/end time, attendees, location) migrate as Items on the Activity board with Date and Person columns. Attendee information from HubSpot maps to a Text column listing attendee emails, since Monday.com does not have an EventRelation equivalent. The meeting title becomes the Item name and the legacy deal reference is stored in a text column.

HubSpot Task engagements (task subject, status, due date, owner, completion status) migrate as Items on the Activity board. HubSpot hs_task_id is stored in a Legacy Task ID column. Task completion status maps to a Status column with Open/Complete values matching HubSpot's model.

HubSpot Tickets migrate to Monday.com Board Items on a dedicated board mapped from the HubSpot ticket pipeline. HubSpot ticket status maps to a Status column, priority to a Priority or Labels column, and the conversation threads migrate as a long-text Column on the Item. Klamp.io documents this same pattern: HubSpot tickets become Monday.com Items tagged with Legacy Ticket ID for searchability.

HubSpot Products migrate as Items on a Products board in Monday.com. The product name becomes the Item name; SKU, price, and description map to Text and Number columns. Products are referenced from Deals via a Connect board column on the Deal Items, preserving the deal-product association.

HubSpot Line Items migrate as Subitems attached to the corresponding Deal Item on the pipeline board. Subitem columns carry quantity, unit price, and product reference (linked to the Products board Item). Total price is computed or stored as a Number column. This preserves the deal-product line structure within the Monday.com board hierarchy.

HubSpot Owners (sales reps) map to Monday.com workspace members. We match by email. Any HubSpot Owner without a matching Monday.com user account is held in a reconciliation queue for the customer's admin to provision before record import. Owner is then assigned via the Monday.com Person column on Deal Items and Contact Items.

HubSpot Tags migrate to Monday.com Tags applied to the corresponding Items. Tags are preserved as flat string labels and applied to Contact, Company, and Deal Items for segmentation consistency.

HubSpot custom objects (Enterprise-only on source) have no native equivalent in Monday.com CRM because Monday.com does not have a custom object type. We create a dedicated Board for each HubSpot custom object, with Columns matching the custom object's properties. Custom object records migrate as Items. The board name reflects the HubSpot custom object label. Lookup relationships between custom objects are represented via Connect board columns pointing to related Items.