Skip to content
Get a quote

Migrate to monday CRM

monday.com CRM is a board-based sales platform whose import model rewards teams that pre-build the Contacts, Accounts and Deals boards and choose the right column types up front.

Short answer

FlitStack AI migrates pipelines, contacts, and deals into monday CRM from 850+ CRMs, including Close, Dynamics 365, Marketing Star, Pipedrive. Every field is mapped to monday CRM's objects, history and associations come across, the monday CRM setup is configured alongside, and the whole migration stays reversible in one click.

By

From Any source
Destinationmonday CRM
CloseDynamics 365Marketing StarPipedrive
850+ sources mapped into monday CRM

Systems we move into monday CRM

The CRMs teams most often move from. Each page shows what moves, the field mapping and what to watch for.

What monday CRM supports, and where its import tools stop

  • Users praise the board-based visual interface for making pipeline stages immediately legible to non-technical team members without CRM training.
  • The no-code automation builder lets sales ops teams create lead routing, stage updates, and email triggers without developer involvement.
  • Integration ecosystem connects to Slack, Gmail, Outlook, and Zapier with minimal configuration, reducing friction for teams already using these tools.
  • The flexible column system lets teams build custom CRM views — deal value, close date, lead source — without needing a developer or pre-defined schema.
REST onlyAPI token (Bearer token)
Rate limitsVaries by plan — 200/day (Free/Trial), 1,000/day (Basic/Standard), 10,000/day soft limit (Pro), 25,000/day soft limit (Enterprise). Per-minute limits also apply.
ObjectSupportNote
People (Contacts)fullPeople is monday CRM's native contact object, storing name, email, phone, and CRM-specific properties. It is accessible via the API as a distinct entity from regular board Items. We migrate People records 1:1 and preserve all CRM-native properties during import.
Deals (CRM Items)mappedDeals in monday CRM are CRM-typed Items attached to a Pipeline. Each Deal has standard columns (value, close date, stage) plus optional custom columns. We map pipeline stage values to the destination CRM's stage labels and preserve deal value, expected close date, and owner assignment. Custom deal columns require field-level mapping at scoping.
PipelinesfullPipelines are the CRM module's grouping structure for Deals. Each Pipeline has ordered Stages with stage names and optional probability percentages. We preserve pipeline definitions and stage order; probabilities are stored as column metadata and transferred as custom fields.
Boards (CRM Boards)mappedBoards are the fundamental container in monday.com, used for both work management and CRM. CRM boards expose special CRM column types (People, Deal info, Pipeline). We preserve board structure, column types, and group headers, but board-level settings like permissions require manual reconfiguration in the destination.
ItemsmappedItems are the rows inside Boards — equivalent to CRM records or tasks depending on context. We map standard item properties (name, status, assignees, dates) 1:1. Custom columns and subitems require additional mapping logic at scoping. Subitems do not export via the standard API export endpoint and must be enumerated separately.
SubitemsmappedSubitems are nested rows inside an Item, often used to track line items, activities, or related records. They do not appear in the bulk account export or standard Excel export — we must enumerate them via the API using the parent item ID, which adds API calls and complexity. We flag subitem volume during scoping.
Custom ColumnsmappedBoards support over 20 column types including text, numbers, dates, formulas, dependencies, and status. Custom columns are preserved as field definitions in exports. Column types that rely on monday's internal enum IDs (status, dropdown) must be mapped to the destination CRM's picklist values. We flag any formula or dependency columns that produce calculated values rather than raw data.
AutomationsnoneAutomations in monday.com are defined using the Recipe (Sentence Builder) language. They fire on item changes, not on import. We do not migrate automations because they are workflow logic, not data, and they frequently break when Items are renumbered during import. We advise customers to document automation intent separately for manual rebuild in the destination.
Files / AttachmentsmappedFiles uploaded to board Items are stored in monday's file storage. They can be excluded from the account export to reduce download time. We retrieve attachment URLs via the API and re-attach them to the corresponding records in the destination, preserving file names and associations by Item ID.
Updates and Activity LogmappedUpdates are per-item comment threads. The Excel export can include Updates as a separate tab. Via API, updates are enumerable per item. We preserve update text and timestamps, mapping them to the destination's activity or note structure. High-volume update threads increase API call counts significantly.
Users / Team MembersfullUsers are account members assigned as owners or collaborators. We map users 1:1 by email and name. Enterprise permission structures (multi-level permissions, SAML SSO) are not part of the standard export and must be manually reconfigured in the destination.
DashboardsmappedDashboards aggregate data across multiple boards into charts and summary widgets. They reference board Items and column data live. We cannot migrate dashboard definitions directly — we migrate the underlying data and recommend rebuilding dashboards in the destination using imported data as the source.

The monday CRM migration guide

Why teams migrate to monday.com CRM

The four shapes a monday CRM migration takes, and what makes the platform easier — or harder — than the category average.

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, Israel1. 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 structure910. 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 & Activities22. 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 board29.

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 silently5051. 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 cost124.

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.

The monday.com CRM data model you need to map into

Boards, items, subitems, columns and Connect Boards — the destination schema decoded, and the upsert keys you'll wire on every field.

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 type150. 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.

ObjectWhat it storesRequiredTier
Contacts boardIndividual people — leads, prospects, customersItem name (used as person name); Email column recommended as upsert keyAll monday CRM tiers
Accounts (Companies) boardOrganisations associated with contacts and dealsItem name (account name); Domain or Website column for upsertAll monday CRM tiers
Deals boardRevenue opportunities in a pipeline (one board per pipeline)Item name (deal name), Status column (stage), Person column (owner)All monday CRM tiers
Leads boardUnqualified prospects before conversion to ContactsItem name, Status (lead status)All monday CRM tiers
Activities (Emails & Activities)Engagement timeline — emails, calls, meetings, notes, tasksActivity type, date, assigned-to person; logged on the parent item cardAll monday CRM tiers; UI-only logging, no documented bulk import70
SubitemsChild rows attached to a parent item (e.g. line items on a deal)Parent item ID, subitem nameAll tiers; subitem boards inherit a separate column schema
Custom boardsAny record type you need — Quotes, Products, Tickets, ProjectsItem name; column schema defined per boardAll tiers — there is no separate Custom Object concept; every board is custom
Workdocs and Files columnDocuments and attachments associated with itemsFile column on the destination boardAll tiers; storage cap scales per tier102

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 job31.

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.

Field typeLimitNotes
Text / Long TextNo documented hard char cap; UI handles up to ~64kLong Text supports line breaks; Text does not50
StatusUp to 40 labels per columnDeal stage / lead status; each label has internal index value
DropdownUp to 500 labels per columnMulti-select; semicolon-delimited on import50
NumbersStandard 64-bit floatDeal value, probability; strip currency symbols before import
Date / Date & TimeISO-8601 with timezoneImporter expects explicit date formatting on Date column112
Email / PhoneOne value per cellPhone column stores country code separately; normalise to E.164 first
PersonOne or more users per cellOwner column; resolves by user ID, not email — pre-provision first13
Connect BoardsUp to ~10,000 linked items per column on a single itemDeal → Account, Contact → Account; required for Mirror columns
MirrorDepends on source column typeRead-only pull-through from a Connect Boards target; can't be written via import
FormulaSpreadsheet-style expressionPro+ tier; recomputed on platform, does not import — rebuild on destination52
Files500 MB per item, no per-cell file count capInline upload or link from Drive/Dropbox/Box/OneDrive100
Required columnsUp to 100 per boardPro+ tier only; not supported on monday service Tickets boards42

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.

Pre-migration prep — the work before you touch monday.com CRM

What must be true on the source, the destination, and across the team before the first row hits the importer.

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 deterministic31.
  • 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 build70.

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 set91.
  • 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 guide22.
  • 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 outright42.

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.

Import mechanisms: UI wizard and bulk ingest

Multiple paths in, each with different limits and shapes. Picking the wrong one is how mid-migrations stall at scale.

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 CSV117159. 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 board31. 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 your data into monday.com CRM

The longest section — because column mapping and Connect Boards wiring are where almost every monday migration that fails actually breaks.

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

Common source → monday Contacts board mapping
SourceDestinationNote
full_name / first + lastItem nameConcatenate first and last on export; item name is the visible label
emailEmail columnLowercase before import; use as external-ID upsert key
phonePhone columnNormalise to E.164; the column stores country code separately
owner / account_ownerPerson column (Contact owner)Map by monday user ID or email; pre-provision users first91
title / job_titleText columnPlain text; create the column before mapping
company / accountConnect Boards column → AccountsWire after Accounts board is loaded; uses Account item ID as the link
lead_sourceStatus or Dropdown columnStatus caps at 40 labels; use Dropdown if source has more
created_atCapture in a custom Date columnmonday stamps its own create timestamp; the system field cannot be overwritten

Accounts (Companies) board

Common source → monday Accounts board mapping
SourceDestinationNote
company_nameItem nameRequired
website / domainLink column or Text column (Domain)Use a Text Domain column as the dedup match key; strip http(s):// and www. on export
industryStatus or Dropdown columnMatch labels exactly to avoid bloating Status past 40 labels
annual_revenueNumbers columnStrip currency symbols and thousands separators
parent accountConnect Boards column (self-referential)Wire after the full account list is loaded so parent IDs exist

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.

Common source → monday Deal mapping
SourceDestinationNote
deal_name / opportunity_nameItem nameRequired
stage / pipeline_stageStatus column (Stage)Match labels exactly; up to 40 labels per column
amount / valueNumbers column (Deal Value)Strip currency symbols; pair with a Currency Text column if multi-currency
close_probabilityNumbers columnDrives the Forecast Value formula in the default template150
expected_close_dateDate columnISO-8601 with timezone for bulk loads; UI accepts looser formats112
ownerPerson column (Deal owner)Map by monday user ID or email; pre-provision users91
primary_contactConnect Boards → ContactsSet in a second pass using Contact Item IDs from the Contacts load
account / organisationConnect Boards → AccountsSet in a second pass; Mirror columns then pull through Account fields

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 expression52.

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 forward73152. 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 unresolved70.

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 forward152.

Files and attachments

Files attach to items via the Files column or inline in Updates. The cap is 500 MB per item100; 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-only96 — 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}150; use it rather than rebuilding from scratch.

Email and calendar sync (Gmail/Outlook) is set up per user under Emails & Activities after users are provisioned152; 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.

The pitfalls that derail monday.com CRM migrations

Nine specific failure modes — ranked by impact, each tied to the exact monday mechanism that breaks.

Validation and cutover

What to verify after the import job, in what order — and how to fail safely when something is wrong.

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 columns147. 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.

Migration partners and tools

Certified monday Partners, iPaaS vendors, specialist migration shops — what each is good for and how to choose.

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 shops120129.

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 →](/contact)

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.

monday CRM migration checklist

An atomic, phased task list for migrating sales data into monday.com CRM — covering scope, prep, export, transform, sandbox test, cutover, validation, and post-cutover cleanup. Typical timeline: 3–12 weeks.

0. Decide & Plan10 tasks
  • Document the full list of monday CRM entities in scope. The monday CRM template ships linked boards for Contacts, Accounts, Deals, Activities, and Leads. Decide which boards you will populate and which are deliberately out of scope.If skipped: Discovering at cutover that Leads or Accounts were assumed but never planned forces re-scoping mid-migration.
  • Define historical-data scope per board. Decide how many years of closed deals, logged activities, and archived contacts you will move. Decide whether historical Email & Activities entries and call logs are in scope.If skipped: Pulling all history by default can multiply the dataset and force you into a higher plan tier than you budgeted.
  • Confirm the target monday CRM plan and its feature ceilings. monday CRM is sold as Basic, Standard, Pro, and Enterprise (separate from Work Management). Mass-update permissions, custom dashboards, automation actions per month, file-storage caps, and HIPAA support are all tier-gated.If skipped: Buying Basic then discovering you need formula columns, private boards, or HIPAA coverage blocks the migration until billing is escalated.
  • Decide whether monday CRM or Work Management is the correct destination. Work Management boards can be promoted into the CRM product, but Email & Activities, the item-card layout, and the mobile CRM view only exist on monday CRM. Document the rationale.
  • Identify GDPR data-residency requirements and select the data region. monday.com defaults new accounts to the US AWS region. Enterprise customers can elect the EU (Frankfurt) region, but the choice is made at account creation and cannot be flipped on an existing tenant without a full re-migration.If skipped: Provisioning on the US region for an EU-resident customer forces a second migration to the Frankfurt region to satisfy GDPR.
  • Confirm HIPAA, SOC 2, and ISO 27001 evidence needs against the target plan. HIPAA coverage and a signed BAA are Enterprise-only. Confirm with procurement and legal before you provision the tenant.
  • Assign a single accountable migration owner (DRI). One named person owns scope decisions, cutover go/no-go, and post-migration signoff. Document their backup.
  • Document explicit out-of-scope items. List source-system features that will NOT be rebuilt — chat transcripts, marketing automation flows, custom reporting macros, etc. Get sponsor sign-off in writing.If skipped: Unwritten out-of-scope items resurface as urgent during cutover and derail the schedule.
  • Set the target cutover date and source-system freeze window. Pick a low-activity window. Communicate the freeze date and time to all source-system users at least two weeks in advance.
  • Define written success criteria for the migration. Examples: 100% of open deals migrated with correct Status column value; aggregate pipeline value within 0.5% of source; all owners assigned via the Person column; activities linked to the correct contact and deal items.If skipped: Without falsifiable criteria, the migration is never formally complete and tail issues drag on for months.
1. Pre-Migration Prep24 tasks
  • Run dedup analysis on source Contacts using email as the primary match key. Resolve duplicate contacts at the source before export. monday CRM does not deduplicate on import — two CSV rows with the same email produce two separate items.If skipped: Importing duplicates means rebuilding deal-to-contact linkages against the wrong item after a manual merge pass.
  • Run dedup analysis on source Accounts using website domain as the match key. Same constraint applies to company-level records. The monday CRM Account merge UI does not cascade to the linked Contacts, so cleaning at the source is cheaper.If skipped: Merging Accounts inside monday CRM leaves duplicate Contacts orphaned to one side of the merge.
  • Standardize email casing and phone-number formats at the source. Lowercase every email. Force phone values into E.164 (+15551234567) so the Phone column displays consistently and dialer integrations match.
  • Standardize country names against an ISO 3166 reference list. Mixed 'US' / 'USA' / 'United States' values turn into three distinct Status column labels in monday and break reporting.
  • Identify and resolve source records with missing mandatory fields. monday CRM lets a board owner mark up to 100 columns as required. Pre-validate that every source row will satisfy whichever columns you intend to make required.If skipped: Required-column violations block item creation through forms, automations, and integrations after cutover.
  • Export current record counts per object as a reconciliation baseline. Counts of Contacts, Accounts, Deals, Activities, Leads — and a sum of open pipeline value. This is the source-of-truth comparison set for Phase 6.
  • Archive or delete obviously stale source records before export. Records last touched more than five years ago, contacts who unsubscribed years ago, deals stuck in dead stages. Cheaper to drop now than to migrate and clean later.
  • Provision the production monday CRM tenant on the correct data region. EU customers must pick the Frankfurt region at sign-up. Confirm the region before any users are invited or boards are created.If skipped: Switching regions after data is loaded requires a full re-migration via the board-template path with manual rebuild of automations and Connect Boards links.
  • Provision a separate workspace as a sandbox for test loads. monday CRM has no native sandbox tenant. Create a dedicated workspace named 'Migration Sandbox' inside the same account, populate it with the boards under test, and restrict access to the migration team.
  • Install the monday CRM template to seed the Contacts, Accounts, Deals, Activities, and Leads boards. The template ships pre-built linked boards with the standard Status, Person, Phone, Email, Date, Numbers, Connect Boards, and Mirror columns in place. Start here rather than building from scratch.If skipped: Hand-rolling boards without the template means rebuilding the Email & Activities item-card layout and the mobile CRM view manually.
  • Configure org-level settings: default currency, fiscal year start, timezone, date format. These settings influence how the Numbers (currency display), Date, and Timeline columns render. Set them before any data lands.
  • Provision every destination user and assign role (admin, member, viewer, guest). Source owner emails must exist as monday users before owner mapping can succeed. Pre-create them via Admin > Users.If skipped: Importing items with Person column values that reference non-existent users assigns them to nobody and forces a re-link pass.
  • Create all required custom columns on every board before importing. Add every Status, Numbers, Date, Phone, Email, Long Text, Dropdown, Country, Link, and File column that the mapping spreadsheet calls out. Importing into a column that does not exist drops the value.If skipped: monday's importer silently ignores CSV columns that have no matching board column, with no skip-file or error.
  • Configure all Status column labels and colors to match source pipeline stage values. Deal stages in monday CRM are Status column labels. Add every stage label up front and lock the color mapping; importing a row with an unknown Status value creates a new label automatically.
  • Create Connect Boards columns linking Deals to Accounts and Activities to Contacts. The Connect Boards column is how monday CRM models parent-child relationships. Configure each one with the correct target board before importing dependent items.If skipped: Loading Deals before the Deal-to-Account Connect Boards column exists strands every deal without its account link.
  • Configure Mirror columns to surface Account fields onto the Deal board. Mirror columns pull Account-level values (industry, billing country) through to the Deal item. Configure them after Connect Boards are wired and before validation.
  • Mark mandatory columns as required only AFTER the bulk load completes. Required columns block item creation when missing values are present. Keep them off during the load; turn them on for end users in Phase 7.If skipped: Required columns active during the load reject every row that has the slightest gap and produce no skip file.
  • Disable every Automations recipe on the destination boards until cutover completes. Automations fire on item creation. Notification spam, status-change emails, and assignee notifications all trigger during bulk loads if left active.If skipped: Default Automations active during import send hundreds of nudge emails to customers within minutes of cutover.
  • Pause every third-party integration on the destination boards until cutover completes. Salesforce sync, HubSpot sync, Gmail/Outlook two-way sync, Slack notifiers — pause every one before any bulk load.
  • Reserve complexity-points budget for the cutover window. monday meters every read and write against a per-minute complexity budget. Pre-compute the expected complexity for the full load and confirm the tier you are on permits it.If skipped: Hitting the complexity ceiling mid-load stalls the import and forces a wait-and-retry loop that extends the cutover window.
  • Communicate the freeze window to every source-system user at least two weeks in advance. Specify the exact freeze date and time, what 'frozen' means for their daily workflow, and where to log changes during the freeze.
  • Schedule monday CRM training sessions segmented by role. Sales reps, sales managers, ops, marketing. Each group needs a different walkthrough — pipeline view for reps, dashboards for managers, board configuration for ops.
  • Designate first-responders for the first 48 hours post-cutover. Two to four named people available to triage end-user issues, with a shared inbox or channel for routing.If skipped: Without first-responders, day-one issues escalate to the migration owner and starve actual validation work.
  • Draft the go-live announcement email and store-of-help link. Login instructions, what changed, where to ask questions, who is the on-call first-responder. Queue it for Phase 7.
2. Source Export12 tasks
  • Export Contacts as CSV with every standard and custom field. Include the source-system unique ID column so re-linking to deals and activities later works deterministically.If skipped: Omitting the source ID column means relationship reconstruction has to fall back to fragile email or name matching.
  • Export Accounts (companies) as CSV with every standard and custom field. Include website domain and source ID — both are useful as match keys later.
  • Export Deals as CSV with every standard and custom field including stage, value, currency, expected close date, owner, account link, and contact link. Capture the source pipeline name on each deal row so multi-pipeline maps to multi-board or multi-group correctly.If skipped: Losing the source pipeline name forces a manual stage-by-stage reclassification.
  • Export Activities (calls, meetings, tasks) as a separate CSV with type, due date, completion status, owner, and linked contact/deal IDs. Activities in monday CRM live on a separate Activities board and link via Connect Boards columns.
  • Export Notes and Email threads as a separate CSV with timestamp, author, body, and linked record ID. These become Updates or Email & Activities entries on the destination item.
  • Export Leads as CSV with stage, source, owner, and qualifying notes. Leads are a separate monday CRM entity from Contacts and convert into Contact + Deal items at qualification.
  • Export the source user list with email, full name, role, and reporting manager. Drives the user-provisioning step in Phase 1b and the owner-mapping rule in Phase 3.
  • Export pipeline and stage definitions as a reference file. Stage names, sort order, probability percentages, and any closed-won/closed-lost flags. This becomes the Status column label map.
  • Export file attachments and their metadata. Two pieces: the binary files themselves, and a manifest CSV linking each file to its parent record ID. The Files column in monday accepts inline uploads up to 500 MB per item.If skipped: Without the manifest, files re-upload to the wrong item or end up unlinked.
  • Screenshot or document every source automation rule, workflow, and sequence. These will be rebuilt as monday Automations recipes in Phase 7 — they do not migrate. Capture trigger, conditions, and actions for each.
  • Screenshot every source report and dashboard. Dashboards rebuild manually in monday using widgets. The screenshots become the rebuild spec.
  • Document the exact UTC timestamp of every export file. Defines the delta window between the export and cutover. Drives the final delta-export step in Phase 5.If skipped: Without timestamps, the delta-load step risks duplicating rows that crossed the boundary or losing rows that came in just after.
3. Transform & Map31 tasks
  • Build a master mapping spreadsheet covering every source field for every board. Columns: source object, source field, source type, destination board, destination column, destination Column type, transformation rule, nullability, required-on-import flag.If skipped: Without a single source-of-truth mapping document, column decisions get made twice and the second decision overwrites the first silently.
  • Map every source field type to a monday Column type explicitly. Text → Text; numeric → Numbers; date → Date; email → Email; phone → Phone; picklist → Status or Dropdown; user reference → Person; relation → Connect Boards. Long Text, Country, Link, and Tags are also available.
  • Resolve every picklist value mismatch between source and destination Status labels. Source 'Won-Closed' must become the exact destination Status label (e.g. 'Won'). Build the mapping table inline so transforms reference one location.If skipped: Importing an unknown Status value creates a new label automatically and pollutes the column with near-duplicates.
  • Designate the source-system unique ID as the upsert key for every object. Store the source ID in a Text column named 'Source ID' on every board. Use it as the upsert key for re-runs via the ingest_items job.If skipped: Re-running an import without a stable upsert key creates duplicate items on every retry.
  • Decide handling for source fields with no monday equivalent. Options per field: drop, concatenate into Updates, or create a new column of the closest Column type. Document the choice for every orphan field.
  • Decide handling for source records whose owner email does not exist in monday. Either provision the missing user before import, reassign to a 'Migration' service user, or leave Person column blank. Document the rule.
  • Convert all date and datetime values to ISO-8601. Use YYYY-MM-DD for Date columns. The Date column accepts an optional time component; specify timezone explicitly when included.If skipped: Ambiguous DD/MM vs MM/DD strings get parsed by the importer's locale and silently shift dates by months.
  • Normalize numeric values: strip thousand separators and force a decimal point. The Numbers column stores raw numerics; symbols like $ or € are rejected. Use the column's display format setting for currency rendering.
  • Re-encode every text field as UTF-8. monday rejects non-UTF-8 payloads. Re-encode every CSV file before upload.If skipped: Non-UTF-8 encoding causes entire ingest_items batches to fail rather than single rows.
  • Escape commas, quotes, and newlines inside CSV cells per RFC 4180. Wrap any cell containing a comma, quote, or newline in double quotes and double-up internal quotes.If skipped: Unescaped commas split rows into wrong column counts and the row lands in the skip file.
  • Cap individual Text column values within the column's character limit. Use Long Text for anything that may exceed the Text limit. Truncate at the source where the cap is real; do not let the importer truncate silently.
  • Format Phone column values in E.164 with the country code. The Phone column has a country dropdown; consistent E.164 formatting makes dialer integrations and search work.
  • Format Email column values as lowercase with the address only (no display name). Display-name formatting like 'Jane Doe <[email protected]>' breaks the Email column's parser.
  • Map Status column values exactly to the labels created in Phase 1b. Case and whitespace must match. Trailing spaces produce silent new-label creation on import.If skipped: A trailing space on a Status value creates a duplicate label ('Won' and 'Won ') that pollutes reporting.
  • Decide strategy for preserving the original record creation timestamp. monday stamps item CreatedAt to the import moment. To preserve the source created date, store it in a 'Source Created Date' Date column on every board.If skipped: Reporting that filters on item CreatedAt will treat every migrated item as created at cutover, distorting historical trend analysis.
  • Decide strategy for record ownership. Best-match by source owner email into the Person column, or assign every imported item to a single 'Data Migration' service user. Document the rule.
  • Decide strategy for file attachments: re-upload binaries to the Files column or preserve as external links in a Link column. Re-upload consumes complexity points and counts against your plan's file storage. External links preserve quota but make files dependent on the source storage layer.
  • Pre-sort the load order: Users, Accounts, Contacts, Leads, Deals, Activities, Notes, Files. Children cannot reference parents that do not exist yet. Connect Boards links require the target item to already exist; load parents first.If skipped: Loading Deals before Accounts strands every deal without its Account link and forces a re-link pass after.
  • Configure the monday CRM template Contacts, Accounts, and Deals boards with the exact Column types you need. The template seeds the linked board structure. Add Status, Phone, Email, Person, Date, Numbers, Connect Boards, and Mirror columns to match the source schema.If skipped: Importing into a board that lacks the right Column types silently drops the value with no skip-file warning.
  • Configure the Deals board Status column with every source deal-stage label. Deal stages in monday CRM are Status column labels. Add every label up front, set the color, and decide which labels count as 'closed-won' for reporting.
  • Wire the Deal → Account Connect Boards column to the Accounts board. Each Connect Boards column targets one board. The Deal-to-Account link drives the rollup math on the Accounts board.If skipped: Loading Deals before this Connect Boards column exists leaves the link unset and the Mirror columns empty.
  • Wire the Activity → Contact and Activity → Deal Connect Boards columns. Activities need two Connect Boards columns — one to Contact and one to Deal — so the activity timeline renders on both items.
  • Configure Mirror columns to pull through Account-level fields onto the Deal board. Common picks: Account industry, billing country, account tier. Mirror columns are read-only on the child item.
  • Rebuild every source pipeline as Status labels or as separate Deal board groups. Decide per pipeline: separate groups inside one Deals board, or separate Deals boards. The Kanban view groups by Status, so a multi-pipeline view typically uses Groups.
  • Map every source deal close-date to the destination Date column on the Deals board. monday does not auto-stamp close-time on stage change. Write the source close date into a 'Closed Date' Date column during import.
  • Build the Email & Activities templates needed to log historical interactions. Email & Activities is the monday CRM equivalent of an activity timeline. Configure email log, call log, meeting log, and note templates before importing historical activity rows.If skipped: Importing activity rows before the templates exist drops the typed metadata and leaves a generic log entry.
  • Plan the Automations recipes rebuild — do not attempt to migrate them. Source automations never translate cleanly. Capture trigger, conditions, and actions from Phase 2 and rebuild in Automate > Automations Center after cutover. Leave them inactive until validation completes.If skipped: Activating automations before validation triggers notification cascades to customers on incorrect data.
  • Plan the Sales Pipeline board configuration: Kanban view, group-by-Status, and Forecast Value formula. The classic forecast formula is {Deal Value} * {Close Probability}. Build it as a Formula column on the Deals board before importing deals.
  • Plan the Gmail or Outlook two-way sync setup as a per-user post-cutover task. Email sync is a personal-account integration, not an admin-level one. Each rep must connect their mailbox individually after their owner email is mapped.
  • Decide lead-scoring rebuild strategy. monday CRM does not ship a native lead-scoring model. Plan to recompute scores via Formula columns on the Leads board or via an Apps Framework app from the Marketplace.
  • Plan the contact-merge logic. monday CRM does not auto-deduplicate on import. Document the manual merge process and which Connect Boards links the merge must preserve.If skipped: Merging Accounts in the UI does not automatically reassociate the linked Contacts and Deals — those stay attached to the deleted record.
4. Sandbox Test Migration13 tasks
  • Load a 1–5% representative sample of each board into the sandbox workspace. Use the Boards > Import items from Excel/CSV wizard for small samples, or the ingest_items job for anything over a few hundred rows.If skipped: Skipping a sample run means production becomes the first place errors surface.
  • Trigger every Status column label at least once in the sample. If the Status column has 12 labels, the sample should exercise all 12 so unknown-label creation surfaces here, not in production.
  • Verify 5–10 random sandbox items field-by-field against the source. Walk every column, every Status value, every Connect Boards link, every Person assignment, and every Date/Numbers value. Document and triage every mismatch.
  • Test edge cases: long strings, emoji, RTL languages, leading/trailing whitespace, NULL values. Each of these has historically broken at least one CRM importer; verify monday's behavior on yours.
  • Test the ingest_items job end-to-end on the sandbox. Start the import job with ingest_items, upload the CSV to the presigned upload location, then poll for completion. Capture job_id and row counts.If skipped: Skipping the async-job pattern in test means cutover is the first time you see timeout, retry, or partial-completion behavior.
  • Test the backfill_items job for the initial one-time admin-only seeding. backfill_items permits up to 20,000 rows per job and is account-admin-only. Use it for the bulk initial load; reserve ingest_items for ongoing/recurring imports.
  • Test parent-child relationship import: Deal → Account, Contact → Account, Activity → Contact + Deal. Confirm Connect Boards links resolve correctly and Mirror columns populate as expected on the child item.If skipped: Connect Boards links written before the target item exists silently fail to associate.
  • Test Email & Activities import for historical activity rows. Confirm timestamp, author, body, and the dual link (Contact and Deal) all land correctly on the timeline.
  • Test File column upload for a sample of attachments. Confirm files attach to the correct item, the file preview renders, and the 500 MB per-item ceiling is not exceeded.
  • Run a full-volume test if the sandbox plan permits. Surfaces complexity-points throttling, ingest_items job ceilings, and timeout behavior under realistic load.If skipped: If only small samples are tested, production hits ceilings the sample never approached.
  • Time the sandbox runs and extrapolate to production volume. Confirms whether the planned cutover window is realistic. Re-plan if extrapolated wall-clock exceeds the freeze window.
  • Have a sales-team domain expert spot-check the sandbox data. A rep or sales manager who knows the records walks the sandbox and flags anything that looks wrong. They catch business-logic mistakes engineers miss.
  • Sign off the sandbox test results in writing before proceeding to Phase 5. Migration owner, sales sponsor, ops sponsor. Recorded in the project tracker before the cutover window opens.If skipped: No formal sign-off means a cutover failure has no clear escalation owner.
5. Production Cutover15 tasks
  • Confirm the source-system freeze is in effect and verify no writes in the last hour. Check the source audit log, last-modified timestamps on the most recent records, and any active integration write paths.If skipped: Late writes after the delta cut produce silent data loss at cutover.
  • Take a final full export of source data as the cutover snapshot. Compute the delta against the Phase 2 baseline. Concatenate the delta into the existing exports or load it as a separate pass.
  • Confirm every monday Automations recipe is disabled on every destination board. Re-check from Admin > Automations Center. A re-enable that slipped during testing fires notification cascades during the bulk load.If skipped: Default 'Notify owner when item created' active during import sends hundreds of notification emails within minutes.
  • Confirm every third-party integration is paused. Gmail/Outlook sync, Salesforce sync, HubSpot sync, calendar sync, Slack notifiers, outbound notifications.
  • Load Users first if any new users are still missing. Confirm every Person column reference in the load files maps to an existing user email.If skipped: Person column values that reference non-existent users assign to nobody and require a re-link pass.
  • Load Accounts via backfill_items keyed off the Source ID Text column for idempotent upsert. Account items must exist before Deals reference them via Connect Boards.
  • Load Contacts via backfill_items keyed off Source ID; populate the Account Connect Boards column on each contact. Contacts depend on Accounts existing for the Connect Boards link to resolve.
  • Load Leads via backfill_items keyed off Source ID. Leads are independent of Accounts and Contacts; load in parallel with Contacts where useful.
  • Load Deals via backfill_items keyed off Source ID; populate the Account and Contact Connect Boards columns on each deal. Deals depend on both Accounts and Contacts existing.If skipped: Loading Deals before Contacts and Accounts strands their Connect Boards values empty.
  • Load Activities via ingest_items keyed off Source ID; populate the Contact and Deal Connect Boards columns. Use ingest_items rather than backfill_items so the job behaves the same as ongoing post-cutover loads.
  • Load Notes and Email & Activities entries via ingest_items. Apply the historical timestamp into the 'Source Created Date' Date column per Phase 3 decisions.
  • Re-upload file attachments to the Files column. Track failures in a skip log and retry idempotently.If skipped: File uploads consume complexity points fast; budget headroom or files mid-batch start failing.
  • Capture job_id, row counts, and error logs for every ingest_items and backfill_items job. Poll fetch_job_status until done. Persist the output for the Phase 6 reconciliation.
  • Cross-check destination row counts against source row counts at each step. If any board's count is off, stop and diagnose before loading dependent objects.If skipped: Pushing dependent loads on top of an incomplete parent load doubles the cleanup cost.
  • Re-enable Automations recipes and paused integrations only AFTER all loads complete and reconciliation passes. Bring them up one category at a time and watch for notification storms.
6. Validate20 tasks
  • Compare total item count per board between source and destination. Contacts, Accounts, Deals, Activities, Leads. Investigate any delta greater than zero.If skipped: A missing object surfaces as 'where did our deals go' from end users two weeks later.
  • Compare total open pipeline value: source vs. destination. Sum of Deal Value across open-stage deals. Investigate any delta beyond rounding.If skipped: Pipeline value drift breaks executive forecasts on day one of cutover.
  • Compare won-deal count and won-deal value for the trailing 12 months. Catches close-date and stage-mapping errors that the open-pipeline check misses.
  • Cross-check 25–50 randomly selected items field-by-field between source and destination. Walk every column, every Status value, every Connect Boards link, every Person assignment. Document and triage every mismatch.
  • Verify all custom column values arrived intact on a stratified sample. Sample by record age (new and old), by owner, and by pipeline stage. Coverage matters more than count.
  • Verify the 'Source Created Date' Date column is populated on every migrated item. Spot-check rather than full audit. If gaps exist, surface the Phase 3 transform bug before users notice.
  • Verify Deal → Account Connect Boards links on a sample of 25–50 deals. Pick deals from multiple Account sizes (large, mid, single-contact) so the sample catches edge cases.If skipped: An unlinked deal looks healthy in isolation but breaks the Mirror columns and the Account rollup math.
  • Verify Contact → Account Connect Boards links on a sample of 25–50 contacts. Multi-contact accounts and orphan contacts (no Account) are the common failure modes.
  • Verify Activity → Contact and Activity → Deal Connect Boards links on a sample. An activity must appear on both the Contact timeline and the Deal timeline if it carries both links.
  • Verify Mirror columns populate the expected Account fields on linked Deals. If the Mirror is blank, the underlying Connect Boards link is missing.
  • Verify file attachments open from the Files column and link to the correct items. Open at least one file per attachment type (PDF, image, doc). Confirm the preview renders.
  • Verify Email & Activities entries timeline-render correctly per Contact and per Deal. Order by timestamp; confirm the author shows correctly and the body renders without HTML escape artifacts.
  • Confirm the data region (Frankfurt EU vs. US) matches the contractual residency requirement. Verify in Admin > Privacy or in the support article confirming your tenant's region.If skipped: A region mismatch discovered post-cutover triggers a contractual breach notification.
  • Confirm the audit log is capturing item creation, column-value edits, and login events. Enterprise plan only. Pull the audit logs via Admin > Audit Log and confirm coverage.
  • Confirm HIPAA tier and BAA execution if PHI is in scope. HIPAA features are Enterprise-only and require an executed BAA before any PHI lands on the platform.
  • Snapshot the migrated dataset for forensic retention. Export every board as CSV and archive to long-term storage with a retention tag matching your compliance policy.
  • Run a UAT session with three to five sales reps from the using-team. Each rep walks their own pipeline, opens a few deals, checks the contact records, and confirms the data matches their memory.If skipped: Without rep UAT, business-logic errors only surface after go-live when trust is already shaken.
  • Run a UAT session with a sales manager focused on forecast and dashboard accuracy. Manager-level UAT catches rollup, Mirror column, and Formula column issues that rep-level UAT misses.
  • Document every UAT-surfaced issue with reproducibility steps. Triage into 'must-fix before go-live' and 'fix in first week post-go-live' buckets.
  • Obtain written sign-off from the migration sponsor before Phase 7. Sponsor, sales lead, ops lead. Stored in the project tracker. Without this, you do not have authority to flip the source-system to read-only.If skipped: No sign-off means an issue discovered in Phase 7 has no clear escalation owner and the rollback path becomes ambiguous.
7. Post-Migration Cleanup13 tasks
  • Send the go-live announcement to every end user. Login URL, what changed, who to contact for help, first-responder schedule for the next 48 hours.
  • Run training sessions on monday CRM basics segmented by role. Sales reps focus on pipeline view and Email & Activities. Managers focus on dashboards and reporting. Ops focuses on board configuration and Automations.If skipped: Skipping role-segmented training means adoption stalls and 'where do I do X' tickets dominate the first month.
  • Set the source system to read-only and announce the read-only date to all users. Confirms the freeze is permanent and ends the temptation to keep writing to the old system.
  • Rebuild every report and dashboard as monday CRM Dashboards with the appropriate widgets. Dashboards do not migrate. Use the Phase 2 screenshots as the rebuild spec. Chart widget, Numbers widget, Battery widget, Table widget.
  • Rebuild every Automations recipe in the Automations Center. Use the Phase 2 captures. Test each recipe on a single non-production item before activating on the full board.If skipped: Activating an untested recipe on a full board triggers a notification cascade and may corrupt Status values.
  • Rebuild every email template referencing monday merge fields. Source merge-field syntax does not translate. Test each template against a real contact before going live.
  • Help each rep connect Gmail or Outlook two-way sync to their monday CRM account. Email sync is per-user. Distribute the setup steps and confirm completion via Admin > Connected accounts.
  • Re-establish calendar sync, Slack notifiers, and any Apps Framework apps from the Marketplace. Bring them up one at a time and confirm each is firing as expected.
  • Turn on required columns now that the bulk load is complete. Up to 100 columns per board can be marked required. Turn on the ones documented in Phase 1b.
  • Schedule a 30-day post-migration retrospective. What went well, what went wrong, what to capture for the next migration. Migration owner, sponsors, first-responders attend.
  • Document the source-system decommission date. Typically 90 days after cutover, after the final retention window. Capture in the project tracker with the responsible owner.
  • Archive the source-system exports and the cutover snapshot to long-term storage. Per the retention policy defined in Phase 0. Tag the archive with a forensic-retention label.If skipped: Without an archive, a later dispute over what the source held cannot be resolved.
  • Close out the migration project formally. Final status report, lessons-learned doc, project closure note. Hand off ongoing administration to the steady-state owner.

Questions, answered

Migrating to monday CRM: questions

How long does migration to monday.com CRM take?

A small-business migration with under 5,000 contacts and a single pipeline runs one to two business days end-to-end. A mid-market project with multi-board structure, Connect Boards relationships, custom columns and historical activities runs two to twelve weeks of elapsed time including preparation, validation, training and a 48-hour hyper-care window.

Can I migrate from Pipedrive to monday.com CRM?

Yes, and Pipedrive-to-monday is usually the cleanest shape because the object models align reasonably well — People, Organizations, Deals and Activities correspond to Contacts, Accounts, Deals and the Activities board. Watch Status label casing against monday's 40-label cap, and rebuild Pipedrive workflows as monday automation recipes from scratch.

Can I migrate from HubSpot to monday.com CRM?

Yes — HubSpot-to-monday is a common move for teams consolidating sales and ops onto one platform. Standard objects map cleanly to Contacts, Accounts and Deals boards, but HubSpot workflows, sequences, lead-scoring models and Marketing Hub assets do not transfer and need to be rebuilt as monday automation recipes.

Does monday.com CRM preserve original timestamps on import?

Partially. The Date column on activities, deals and any custom Date column can be backdated and shows correctly. But system-managed item Created timestamps cannot be overridden — they stamp to import day. Use Legacy Created Date and Legacy Created By Date and Text columns on every board to preserve audit history.

What's the difference between using the UI importer and bulk ingest jobs for monday.com CRM?

The UI importer accepts CSV and Excel files, runs synchronously, and is best for one-shot loads under 5,000 items per board with a visual column-mapping step. Bulk ingest jobs handle 10,000 rows per job (or 20,000 in the admin-only backfill path) for larger volumes, repeatable loads, and Connect Boards population.

Can I migrate custom objects to monday.com CRM?

Yes — monday CRM has no separate Custom Object concept because every board is custom. Create a new board for the record type (Quotes, Products, Tickets), define column types, wire Connect Boards columns to the standard Contacts/Accounts/Deals boards, and import via UI or the bulk ingest job.

What happens to deal history and pipeline stages during migration?

Recreate every pipeline as a separate Deals board or as separate Groups before importing deals — unmatched Status labels are silently created on the fly and push the column past its 40-label cap. Deal stage transition history is not auto-preserved; capture stage-entered timestamps in custom Date columns such as Stage Entered Date.

Is there an undo or rollback for monday.com CRM imports?

Not for a full import batch. The per-item Activity Log supports undo of recent column changes, and the LogBack app and Rewind backup product add per-board restore. There is no one-click rollback of a 50,000-row ingest job — stamp every imported item with an Import Batch ID column instead.

Get a quote

Moving to monday CRM?

Tell us where your data lives today and roughly how much there is. We scope the migration and the monday CRM setup with you, then send a quote.

Get a quote