The Definitive Guide to Migrating to monday.com CRM

monday.com Ltd. (styled in lowercase as monday.com) was founded by Roy Mann, Eran Zinman and Eran Kampf in 2012, launched its platform in 2014, and is headquartered in Tel Aviv, Israel ¹. The company went public on Nasdaq in June 2021. monday CRM is the sales-side product inside a broader Work OS that also includes monday work management, monday dev, monday service and monday campaigns, all built on the same underlying mondayDB engine and board model.

The typical monday CRM customer is a sales team — 10 to 300 reps — that already runs cross-functional work on monday boards and wants pipeline, contact management and email logging in the same workspace. Compared with Salesforce Sales Cloud, monday CRM positions on a flatter learning curve and a visual Kanban-first pipeline; compared with HubSpot or Pipedrive, it positions on the elasticity of a board model where every CRM object is a customisable board rather than a fixed schema.

The shapes of migration that actually land on monday CRM tend to fall into four patterns. First, Pipedrive and Zoho exits, driven by teams that grew out of a single-pipeline tool and want multi-board structure ⁹¹⁰. Second, HubSpot moves, usually a cost-driven downgrade or a desire for blended sales + ops workflows on one platform.

Third, spreadsheet and legacy replacements — teams running sales on Excel, Google Sheets, Bitrix24 or a homegrown database where the schema is loose. Fourth, work-management-to-CRM conversions, where the team has monday Work Management boards and now wants to overlay the CRM template with Emails & Activities ²². Each shape has a different profile: a Pipedrive move has clean object parity but messy column defaults; a HubSpot exit has rich automation that does not move across.

What makes migrating *to* monday CRM easier than the category average is the board model itself — every CRM object is a board you can shape exactly to your process, and the native CSV/Excel importer ships under the Add → Import items button on any board ²⁹.

What makes it harder than the average is column-type discipline: monday boards do not enforce a schema at the platform level, so the same field on two boards can drift into different types and break Connect Boards and Mirror columns silently ⁵⁰⁵¹. Pricing is also per-seat across the entire CRM tier, so teams that bring in stale users to preserve ownership inflate the seat count and cost ¹²⁴.

Automations (recipes), Emails & Activities templates, lead scoring, and dashboard widgets do not import — they are rebuilt from documentation. Teams that scope for that work up front finish on time; teams that assume parity do not.

Teams that scope for the rebuild work up front finish on time; teams that assume parity do not.

monday CRM is built around a simple primitive — the board — and everything else composes from it. The CRM template ships a workspace pre-populated with linked boards for Contacts, Accounts, Deals, Leads and Activities, and the same primitive serves every record type ¹⁵⁰. The model is: a workspace contains boards, a board contains groups, a group contains items, an item contains column values, and items can have subitems and Connect Boards links to items on other boards.

Before you can map a field on the source side, you need to know exactly which destination board the row belongs on, which column type each value will store into, and what will serve as the upsert key. The table below summarises the boards you will touch in a monday CRM migration.

There is no platform-enforced unique identifier on a monday board — item names are not unique, and the system always assigns an internal numeric Item ID on create. To upsert deterministically you create a Text or Email column on the destination board, fill it from the source export with a stable external ID (UUID or source platform PK), and use that column as your match key in the ingest job ³¹.

Connect Boards columns link items across boards — a Deal item links to one or more Account items, and a Mirror column then pulls through specific Account fields onto the Deal view without duplicating storage. Mirror columns read-only by default and recompute when the source column changes.

Column types are where the schema actually lives. The catalogue below covers the column types that carry the load on a CRM migration and the limits you need to plan around.

Relationships in monday CRM are modelled exclusively through Connect Boards — there is no master-detail or cascade-delete construct. Deleting an Account does not delete its Contacts or Deals; the Connect Boards reference simply goes orphan and the Mirror columns return empty. If your source platform relied on cascade behaviour, you replicate it through automations (recipes) that fire on delete.

The single best predictor of a clean monday CRM migration is how much work you do on the source side before the first import button is pressed. monday CRM does not deduplicate on import — it will create two separate Contact items for the same email address if you let it — so cleansing has to happen in the export file, not in the destination.

monday CRM does not deduplicate on import. Two rows with the same email become two separate items — clean the file, not the board.

Treat the source export as raw material that needs to be shaped to monday's expected formats — email lowercased, phone normalised to E.164 with the country code split out, dates rewritten to ISO-8601 with timezone, picklist values matched character-for-character to Status and Dropdown column labels, and owners resolved to monday user IDs or emails of users that already exist on the account.

Source-side prep

• Audit and dedup the source database before export. Excel's *Data → Remove Duplicates*, Google Sheets' *Data → Data cleanup → Remove duplicates*, or a third-party dedup tool keyed on email and phone — monday will not catch email-case duplicates.
• Normalise emails to lowercase, trim whitespace, and strip role-based addresses (info@, sales@) that do not belong on the Contacts board.
• Match picklist values exactly to monday Status and Dropdown labels — including casing and punctuation. The importer creates a new Status label on the fly for any unmatched value, which silently bloats the column past its 40-label ceiling on Status.
• Stamp a stable external ID on every record in the source export — a UUID or the source platform's primary key — so re-runs and Connect Boards linking are deterministic ³¹.
• Decide what is in scope for historical activities. The Emails & Activities feature does not have a documented bulk-import path, so most historical email/call data is either logged manually, attached as a Long Text field on the parent item, or imported into a parallel Activity board you build ⁷⁰.

Destination-side prep

• Provision users first, ideally through Okta, Microsoft Entra ID or Google Workspace SSO, and assign seats and roles before importing — the Person column resolves by monday user ID, and rows whose owner cannot be matched are imported with no person set ⁹¹.
• Build the CRM workspace from the monday CRM template rather than rebuilding from Work Management. The template ships Contacts, Accounts, Deals, Leads and Activities boards with pre-wired Connect Boards columns and Emails & Activities ready to log — Option 2 in monday's official migrate-from-Work-Management guide ²².
• Pre-create every custom column on the right board with the right column type. Type-conversion in place is limited; once a Numbers column exists, you cannot retroactively change it to Status without recreating it and losing the data.
• Build pipelines as separate Deals boards (or as separate Groups on one Deals board) before importing deals. Each pipeline has its own Status column values for stages, and rows whose stage label does not match silently create a new label on import.
• Set Required columns (Pro+ tier) only *after* the initial import — required columns block item creation when the value is missing, which fails the import outright ⁴².

People prep

Cutover only works if humans cooperate. Lock down a source-system freeze window — typically 24 to 72 hours — and communicate it to every department. Train reps on the item card, Emails & Activities and the Kanban deal pipeline view before go-live. A clean Pipedrive-to-monday move under 25,000 records runs one to two business days; a complex multi-source migration with rebuilt automations runs two to twelve weeks. Build the human runway accordingly.

monday CRM exposes load paths whose right choice depends on dataset size, board count, and whether the load needs to be repeatable. The UI importer covers most one-shot migrations under 10,000 items per board. Bulk ingest jobs handle programmatic, repeatable, and very large loads. Third-party staging tools sit on top of both and add transformation and dedup layers.

UI importer (CSV / Excel)

The native importer lives on every board under Add → Import items → From Excel or From CSV ¹¹⁷¹⁵⁹. It accepts CSV, XLS and XLSX. The wizard auto-detects columns, lets you map each source column to an existing board column or create a new one of an inferred type, and runs the load synchronously for files under a few thousand rows. Items land in the group you select.

There are two known limits worth planning around. Status column labels are capped at 40 unique values; if the source has more, collapse them in the file before import. The importer does not deduplicate — rows with the same email or item name create new items every time. The UI importer is the right call for one-shot loads under 5,000 items per board, or any time you want a visual column-mapping review before commit.

Bulk ingest jobs

For larger volumes, monday exposes a bulk ingest job pattern. The standard ingest job handles up to 10,000 rows per job; a separate admin-only backfill path raises the ceiling to 20,000 rows and is intended for the one-time seed before users touch the board ³¹. Both jobs accept a CSV uploaded to a pre-signed URL, with the same column-mapping payload as the UI importer.

Use the standard ingest path for ongoing sync work and the admin backfill path exactly once — at the start, before users touch the board. Choose this path when the load is over 5,000 items per board, when you need to populate Connect Boards relationships at scale, or when the migration needs to be repeatable and audit-logged from your side.

Third-party staging tools

Tools like Fivetran, Airbyte, Stitch, Workato, Make and n8n sit between the source and monday CRM. They are used in two ways: (a) reverse-ETL, where the source loads into a warehouse, gets transformed in SQL, then syncs into monday; and (b) staging-and-validate, where the tool handles file generation, type coercion and dedup before feeding the ingest job. SyncMatters MigrateMyCRM and Trujay add a packaged HubSpot/Pipedrive/Salesforce-to-monday flow for DIY teams.

For one-time migrations, the value of an iPaaS layer is repeatability under failure; for ongoing syncs (the post-migration phase), they become the system of integration.

Mapping is where every migration earns its scars. The decisions you make in your mapping spreadsheet — which board, which column type, which Connect Boards link — determine whether reports work on day two, whether automations fire correctly on day five, and whether your sales team trusts the data on day thirty.

Work board by board, top to bottom of the import order: Accounts first (so contacts and deals can link to them via Connect Boards), then Contacts, then Deals, then Leads, then Activities, then any custom boards and subitems.

Contacts board

Accounts (Companies) board

Deals board and pipeline stages

Recreate every pipeline either as a separate Deals board or as separate Groups on a single Deals board before importing deals. Each deal stage maps to a Status column label; build the mapping table source-stage → monday-pipeline + monday-Status-label. The importer creates new Status labels on the fly for unmatched values, which both silently degrades reporting and can push the column past its 40-label ceiling. Match labels exactly.

If you are consolidating multiple source pipelines, the cleanest approach is to keep them as separate Deals boards for at least 90 days post-migration, then merge once reporting has stabilised. Connect Boards columns to Accounts and Contacts are wired *after* the Deals load — populate the Item ID lookup table during the source export so the link can be set in a second pass.

Custom-column mapping strategy

Resist the urge to map every source custom field one-to-one. Migrate only the columns used by an active process, report or dashboard in the last 12 months. Excess columns weaken governance, slow board loads, and make Connect Boards and Mirror columns harder to audit. monday boards have no documented hard cap on columns per board, but past ~50 columns the item card becomes unwieldy and reps stop trusting the view.

For picklist fields whose source values do not match the destination, either: (1) extend the destination Status/Dropdown column with the missing labels (mindful of the 40-label Status ceiling), (2) collapse adjacent values during transform, or (3) introduce a parallel Text column that holds the legacy value verbatim. Formula columns (Pro+ tier) do not import — monday recomputes them on-platform — so any source formula must be rebuilt as a monday Formula column expression ⁵².

Historical activities — emails, calls, meetings, notes

monday CRM's Emails & Activities app logs emails, calls, meetings and notes on the item card timeline. The integration is set up per user under the Updates section by connecting Gmail or Outlook, and ongoing email sync flows in from that connection forward ⁷³¹⁵². The catch: there is no documented bulk-import path for historical emails or activities into Emails & Activities — community threads from monday users trying to backfill years of call/email history are unresolved ⁷⁰.

The patterns most teams adopt: (a) build a parallel Activities board with columns for Type, Date, Body, Owner and a Connect Boards link to the parent item, and bulk-import there; (b) attach a Long Text *Legacy activity log* column with the most recent N activities inline; or (c) keep the source CRM in read-only archive for 12 to 24 months and link out via URL. Calendar sync is set up per user and back-syncs from the connection date forward ¹⁵².

Files and attachments

Files attach to items via the Files column or inline in Updates. The cap is 500 MB per item ¹⁰⁰; if files exceed that, the supported path is to zip them or upload from Google Drive, Dropbox, Box or OneDrive via the cloud-storage integration. Large attachment estates (hundreds of GB) typically use the cloud-storage link pattern, with a deep link stored in a URL column on the item.

Storage allowance is tier-dependent — Basic gets 5 GB, Standard gets 20 GB, Pro gets 100 GB, and Enterprise is effectively unlimited. Plan for storage tier consumption before you bulk-upload — the account-wide cap aggregates across every board, not just CRM.

Audit trail, ownership and original timestamps

monday's per-item Activity Log captures column-value changes for up to 1 week on Basic, 6 months on Standard, 1 year on Pro and 5 years on Enterprise. The system-managed Created timestamp is stamped to import day and cannot be overwritten through the standard create or ingest paths. To preserve the original audit trail, create *Legacy Created Date* and *Legacy Created By* columns on every board and populate them from the source export.

Owner assignment via the Person column works only if the monday user ID or email exists at the moment of import; rows whose owner cannot be resolved land with no person set, which silently breaks downstream owner-based automations.

Account-level activity audit logging is Enterprise-only ⁹⁶ — lower tiers can see per-item history in the Activity Log panel but not account-wide events.

CRM-specific: automations, lead scoring, dashboards, email/calendar sync

Automations (recipes) do not import — they are rebuilt from documentation. Each monday tier ships a different monthly action allowance: Basic includes no automations, Standard 250 actions/month, Pro 25,000, and Enterprise scales to 250,000+. Build the recipe inventory from the source platform first, prioritise the top 10 by run-frequency, and rebuild those before go-live. Lead-scoring models do not transfer; rebuild as a Numbers column populated by an automation recipe that increments on defined triggers.

Dashboards (widgets, charts, forecasting views) do not import either — rebuild from the source dashboard inventory. The Deals board ships a default Forecast Value formula column wired to {Deal Value} * {Close Probability} ¹⁵⁰; use it rather than rebuilding from scratch.

Email and calendar sync (Gmail/Outlook) is set up per user under Emails & Activities *after* users are provisioned ¹⁵²; do not enable it during the import window or you risk a flood of duplicate email logs as the connector backfills against the same contacts you are loading.

Validation is the bridge between the import finishing and users being allowed in. Field-engineering practice on monday CRM migrations follows a three-stage validation: a test load of 10 percent of records with stakeholder spot-checks, the full load with real-time monitoring of item counts and Connect Boards integrity, and a 30-day post-migration data-quality audit. The most reliable signal is having department reps verify their own boards — they know what right looks like better than any reconciliation script.

Build a reconciliation queries spreadsheet that compares source and destination on each of these counts. Anything outside a 0.5 percent variance gets investigated before users get login access.

• Total contacts imported vs source — minus deliberately excluded rows (role-based emails, opt-outs, bounced lists).
• Total accounts imported vs source — checking that the domain-based dedup transform did not over-merge or miss case duplicates.
• Total deals per board per Status label vs source, plus sum of Deal Value per pipeline — a non-trivial dollar variance usually signals a Status-mapping error or a currency-precision drop.
• Total activities imported vs source — and a date-bucketed comparison to confirm the Date column round-tripped during the bulk load.
• Connect Boards link counts — count Deal→Account, Contact→Account, and Deal→Contact links and compare against source-derived expected counts; missing links cause silent Mirror column blanks.
• Person column distribution — group items by owner and confirm no record landed unowned that should not have, and no row landed on a Legacy Owner placeholder when an active owner existed.
• Unique-identifier integrity — count distinct emails on the Contacts board and distinct domains on Accounts; any duplicates indicate the dedup transform missed cases (monday will not catch them).

On top of reconciliation, run a manual spot-check protocol: pick 30 random items across boards and verify each column value against the source UI. Pick five high-value deals and trace the full Connect Boards graph — primary contact, account, subitems (line items), Mirror columns. If a non-trivial discrepancy shows up in three or more of the 30, halt the load, fix the root cause, and re-import the affected items by external-ID column.

Rollback on monday is per-item, not per-import. The Activity Log on each item supports undo of recent column-value changes, but there is no native bulk-undo for an entire import batch. The community-built LogBack app provides per-board undo for bulk-edit accidents, and the Rewind backup product offers granular per-board restore for items and columns¹⁴⁷. Neither is a one-click rollback of a 50,000-row ingest job.

The real rollback strategy remains: export everything to S3 before the import starts, stamp every imported item with an *Import Batch ID* Text column, and if catastrophe strikes, bulk-delete by that batch ID in a loop, then re-import from the cleaned source.

Cutover sequencing: (1) source goes read-only and the team is notified; (2) final delta export captures everything that changed during the test-import window; (3) delta is imported via the bulk ingest job; (4) reconciliation runs; (5) Connect Boards relationships are populated in a second pass; (6) users get login access and a 48-hour hyper-care window with the migration lead on call; (7) source decommission is scheduled for 30 to 90 days out, never the same day.

The monday.com Partner Program tiers Diamond, Platinum, Gold, Silver and Bronze partners by certifications, customer count and revenue. For monday CRM migrations specifically, partners with explicit Pipedrive-to-monday, HubSpot-to-monday or Salesforce-to-monday practices tend to ship cleaner than generalist Work Management implementation shops ¹²⁰¹²⁹.

Fruition Services, OrangeDot, Deviniti, CloudCache Consulting, CarbonWeb, TaskRhino and Idalko all run monday-certified migration practices and each offers fixed-scope migration packages alongside ongoing managed services. OrangeDot publishes a $5,000 standard package (3–4 weeks) covering Deals, People, Organizations and Activities from Pipedrive; SyncMatters' MigrateMyCRM offers a self-serve tier from $299 and a guided tier from $1,174 for HubSpot-to-monday.

On the ETL and iPaaS side, Fivetran, Airbyte, Stitch, Workato, Make, n8n and Zapier all have monday connectors. Their role in a migration is rarely the migration itself — it is the staging layer that lands source data into a warehouse, the transformation layer that converts picklist values and resolves owner names to monday user IDs, and the ongoing-sync layer that takes over once the one-time migration is complete.

Airbyte and Fivetran are common picks for warehouse-first teams; Workato and Make are common where the migration is bundled with workflow automation rebuilds; n8n is used heavily by Fruition for monday-side automation post-migration.

Managed-migration cost ranges vary widely. A Pipedrive-to-monday move under 25,000 records with no historical activities and a single pipeline often lands in the $3,000–$10,000 range — Advaiya quotes $1,500–$2,250 for spreadsheet migrations and $9,000–$15,000 for a 50-user project taking 60 hours. A multi-source migration with deal history, custom boards, multiple pipelines and HubSpot or Salesforce decoupling typically runs $15,000–$80,000, with the upper end driven by record count, column complexity, historical-activity depth and integrations that need rebuilding.

For teams that want to outsource the migration end-to-end, FlitStack specialises in monday.com CRM migrations and handles the column-type design, Connect Boards wiring, external-ID upsert keying, historical-data preservation, and validation work described in Sections 5 and 7 of this guide. Pricing is fixed-fee, based on item count and source platform, with separate line items for Emails & Activities historical depth and Connect Boards complexity so the scope is transparent before signature. Explore FlitStack →

This is one of several legitimate paths — the right choice for any given team depends on whether they want a Diamond/Platinum monday Partner, a self-serve product like MigrateMyCRM, an iPaaS-first approach, or a specialist migration vendor.