Skip to content
Get a quote

monday CRM to Salesforce migration

We migrate People, Deals, Pipeline definitions, and Custom Columns from monday CRM into Salesforce Sales Cloud, resolving the flat board-and-item model into a relational Account-Contact-Opportunity schema with stage associations preserved and subitem hierarchies enumerated before any data moves to Salesforce.

Short answer

FlitStack AI migrates contacts, opportunities, record type + sales process, account or custom objects and task or custom object records from monday CRM to Salesforce, with their history and the associations between records. Every field is mapped and validated, a sample run is checked with you before the full migration, and the whole move can be rolled back in one click. Typical timeline: 4-8 weeks.

By

Source monday CRM
DestinationSalesforce
ContactOpportunityRecord Type + Sales ProcessAccount or Custom ObjectTask or Custom Object record
Mapped field by field · sample run · one-click rollback

What moves from monday CRM to Salesforce?

Moving from monday CRM to Salesforce Sales Cloud requires translating a flat, board-centric data model into a relational object hierarchy that Salesforce expects. monday CRM stores contacts as People entities, deals as CRM-typed Items inside Pipelines, and custom fields as flexible Columns without a fixed schema.

Read the full summary

Salesforce uses Account-Contact as the organizational unit with Opportunity as the deal record and explicit lookup relationships between objects. We enumerate subitems individually via API (they are absent from bulk exports), map pipeline stage values to Salesforce Opportunity stages, and resolve the People-to-Contact relationship with optional Account linkage. Automations built on monday's Recipe infrastructure are deprecated and not portable; we deliver a written inventory of every automation for the customer's admin to rebuild in Salesforce Flow. File attachments, updates, and historical timestamps migrate via API calls with throttling to respect monday's daily limits.

1:1

People (Contacts) → Contact

monday CRM's People entity stores name, email, phone, and CRM-specific properties as a distinct object from board Items.

How it maps

We map People 1:1 to Salesforce Contact. The email address becomes the dedupe key. If the monday account has any People records that represent organizations rather than individuals, we flag those for Account creation with a Contact of type Organization during scoping. Phone number formatting is normalized to E.164 where possible before insert.

1:1

Deal (CRM Item) → Opportunity

monday CRM Deals are CRM-typed Items attached to a Pipeline.

How it maps

Each Deal carries standard CRM columns (deal value, close date, stage) plus optional custom columns. We map the deal's Name to Opportunity.Name, Amount to Amount, CloseDate to CloseDate, and the pipeline Stage to Opportunity.StageName. The Salesforce Opportunity RecordType is set per Pipeline. Any monday custom columns map to existing or new Salesforce Opportunity fields with type matching.

configuration

Pipeline → Record Type + Sales Process

Each monday CRM Pipeline becomes a Salesforce Record Type on Opportunity with a corresponding Sales Process that whitelists the relevant Stage values.

How it maps

Pipeline stage names map to Salesforce StageName; stage probability percentages migrate to StageProbability. Stage ordering is preserved. If a monday account has multiple Pipelines, each gets its own Record Type so stage values stay scoped per business line.

configuration

Board (CRM Board) → Account or Custom Object

monday CRM Boards are the fundamental container for Items.

How it maps

CRM Boards expose special CRM column types (People, Deal info, Pipeline). We map board-level CRM data to Account if the board represents organizations, or to a Custom Object if it represents a non-standard entity (Projects, Subscriptions, Properties). The board's column definitions are captured as field definitions for the customer's admin to configure in Salesforce before data import.

1:1

Item → Task or Custom Object record

Non-CRM Items in monday (work management items, project tasks) map to Salesforce Task records if they represent action items, or to a Custom Object if they represent persistent entities that do not fit the standard CRM object model.

How it maps

We preserve Item status, assignee (via Owner lookup resolution), due dates, and the parent Board reference as a custom field for audit.

1:N

Subitem → Task or Custom Object record

Subitems are nested rows inside a monday Item and are NOT included in bulk account exports or Excel exports.

How it maps

We enumerate Subitems individually via API using each parent Item's ID, which multiplies API call volume. Subitems map to Salesforce Task records linked to the parent Opportunity or Contact via WhatId or WhoId. The subitem enumeration count is flagged during scoping so the customer understands the additional API load and timeline impact on lower-tier accounts (1,000 calls/day on Basic/Standard).

What moves12 objects
monday CRMSalesforce
  • PeopleContact1:1
  • DealOpportunity1:1
  • PipelineRecord Typetransformed
  • BoardAccount or Custom Objecttransformed
  • ItemTask or Custom Object record1:1
  • SubitemTask or Custom Object recordtransformed

+ 6 more in the mapping below

How monday CRM and Salesforce differ

The differences that decide how each record is mapped. These are what a CSV export and a native importer don't resolve for you.

Dimensionmonday CRMSalesforce
Data modelFlat board-and-item model with no native relational hierarchyAccount-Contact-Opportunity relational model with explicit lookup relationships
ContactsPeople as a distinct CRM entity, separate from board ItemsContacts always linked to Accounts; standalone Contacts require a no-Account flag decision at migration time
DealsCRM-typed Items inside ordered Pipeline StagesOpportunity with StageName mapped from pipeline stage and optional Record Type per pipeline
Custom fieldsFlexible Columns across 20+ types without a fixed schema; no field-level API name enforcementExplicit custom fields with typed schemas, API names enforced, governed by field-level security
Automation modelRecipe (Sentence Builder) automations being deprecated; new monday workflows with monthly action limitsSalesforce Flow with record-triggered, scheduled, and screen variants; no monthly action cap, governed by flow interview limits
API rate limits1,000 calls/day on Basic/Standard, 10,000 on Pro, 25,000 on Enterprise (all soft limits)Bulk API 2.0 with concurrent batch limits; REST API 24-hour rolling limit varies by org license count
Export formatExcel and account exports include only table views; Subitems absent from bulk exportsSalesforce Data Import Wizard, Data Loader, and Bulk API accept CSV with parent-lookup resolution required

What to watch for in a monday CRM to Salesforce migration

The issues we plan around on this pair: limits and data-model gaps that the official import tools leave to you.

high

Subitems are absent from bulk exports and require individual API enumeration

The monday.com account data export and the per-board Excel export do not include Subitems — they only export parent Item rows.

How we handle it

Subitems must be enumerated individually via the API using each parent Item's ID, which multiplies API call volume significantly. On Basic and Standard plans (1,000 calls/day), large subitem hierarchies can extend extraction over multiple days. We include a subitem enumeration step in every monday.com migration plan and flag the total subitem count during scoping so the customer understands the additional API load and timeline impact before extraction begins.

high

Daily API call limits vary sharply by plan and constrain extraction speed

Basic and Standard plans are capped at 1,000 API calls per day.

How we handle it

Pro allows 10,000 and Enterprise 25,000 (both soft limits). For larger accounts with tens of thousands of Items, these limits can make direct API migration take multiple days even before accounting for subitem enumeration. We throttle migration jobs to stay within limits, use exponential backoff on 429 responses, and schedule bulk jobs overnight to maximize the available daily window. Migrations from Standard-plan accounts with more than 5,000 Items routinely require 5-10 extraction days.

high

monday's flat item model has no native Account-Contact hierarchy in Salesforce

monday CRM does not have a relational object model.

How we handle it

People (Contacts) exist as a distinct entity but are not linked to organizational records the way Salesforce Accounts and Contacts are. We must decide during scoping whether each monday Person maps to a Salesforce Contact with a parent Account or to a Contact with a blank AccountId (standalone). If the monday People records include organization names, we create Accounts first and link Contacts. If the monday board mixes person-level and organization-level records without a clear distinction, we flag ambiguity for the customer's admin to resolve before migration begins.

medium

Legacy automations are not portable and the Recipe system is being deprecated

monday.com is deprecating the Sentence Builder custom fields and automation infrastructure in favour of the new monday workflows system.

How we handle it

Customers migrating out of monday with automations built on the old system find those automation definitions are not portable regardless of destination platform. We capture automation rule definitions during pre-migration review so customers have a written inventory of their workflow logic for rebuild in Salesforce Flow. The deprecation timeline from monday adds urgency to migration timing for accounts still on Recipe automations.

medium

Excel and account exports only capture table views; non-table views are lost

The bulk account export and per-board Excel export only capture the table view of a board.

How we handle it

Kanban, Calendar, Chart, Map, and other non-table views are not included in exports. Saved filters with group-by or conditional colouring and dashboard widgets are also absent. We advise customers to document any non-table view configurations before migration. Board views must be rebuilt in Salesforce using the imported tabular data as the foundation.

How the migration runs

  1. Discovery and plan tier audit

    We audit the source monday CRM account across plan tier (Basic/Standard/Pro/Enterprise), total People count, Deal count across all Pipelines, subitem count per board, custom column definitions, active automation count, file attachment volume, and API call history.

    What this step covers

    We pair this with a Salesforce edition assessment: Essentials ($25/user) covers basic Account-Contact-Opportunity migrations; Professional ($80/user) adds custom objects and advanced automation; Enterprise ($165/user) is required for complex territory management, multi-currency, or Advanced CSV Import. The discovery output is a written migration scope document with record counts, API call budget, and estimated timeline per extraction phase.

  2. Schema design and object relationship mapping

    We design the destination Salesforce schema.

    What this step covers

    This includes provisioning custom fields on Account, Contact, and Opportunity with API names matched to monday column names; creating Record Types per monday Pipeline; designing the Sales Process with stage values and probabilities mapped from monday; deciding the Account-Contact linkage strategy based on whether monday People records contain organization data; and mapping monday Custom Columns to Salesforce field types. Schema is deployed into a Salesforce Sandbox via metadata API or change set for validation before production migration.

  3. Sandbox migration and reconciliation

    We run a full migration into a Salesforce Sandbox (Partial Copy or Full Copy depending on data volume) using production-like record counts.

    What this step covers

    The customer's sales ops lead reconciles record counts across all objects, spot-checks 25-50 random records against the monday source, and validates pipeline stage mapping. Any mapping corrections (field type mismatches, missing picklist values, Account-Contact linkage decisions) happen in Sandbox before production. This step also surfaces any Salesforce validation rules or required field constraints that will block production import.

  4. API extraction with rate-limit management

    We extract data from monday CRM via API using the monday API v2 endpoint.

    What this step covers

    Extraction follows dependency order: People first, then Pipelines and Stage definitions, then Deals (with subitem enumeration per parent Item), then Files (attachment URLs retrieved per Item), then Updates. Each phase applies throttling to stay within the plan's daily call limit, uses exponential backoff on 429 responses, and logs API consumption so the customer can see the remaining budget. Large subitem-heavy accounts may require extraction spread over multiple days on Standard-plan accounts.

  5. Transformation and staging

    We transform extracted monday data into Salesforce-compatible CSV format.

    What this step covers

    This includes splitting People into Contact records with optional Account creation; mapping Deals to Opportunity with RecordTypeId and StageName resolved; applying field type transformations (date normalization, phone formatting, currency rounding); enumerating Subitems as Task records linked to parent Opportunities or Contacts; and preparing ContentVersion records for file attachments. The staging area emits a field-mapping manifest showing every monday column mapped to every Salesforce field.

  6. Production migration in dependency order

    We run production migration into Salesforce in record-dependency order: Accounts (if created from People), Contacts (with AccountId resolved), Opportunities (with AccountId, OwnerId, RecordTypeId, and Stage resolved), Tasks and Events (from Subitems and Updates via Bulk API 2.0), ContentDocument records (file attachments), and any Custom Object records last.

    What this step covers

    Each phase emits a row-count reconciliation report. We coordinate with the customer's Salesforce admin to temporarily disable active validation rules during load to prevent record rejection.

  7. Cutover, validation, and automation rebuild handoff

    We freeze monday writes during cutover, run a final delta migration of any records modified during the migration window, then enable Salesforce as the system of record.

    What this step covers

    We deliver the automation inventory document (documenting every monday Recipe and workflow with trigger, conditions, and actions) to the customer's admin for rebuild in Salesforce Flow. We support a one-week hypercare window for reconciliation issues. We do not rebuild monday automations as Salesforce Flow inside the migration scope; that is a separate engagement or an internal admin task.

monday CRM Salesforce
  1. Connect
  2. Map
  3. Sample
  4. Migrate
  5. Verify
  • Contacts48,210 / 48,210 Done
  • Companies9,134 / 9,134 Done
  • Deals6,377 / 11,920 In progress
Example run
Restore points · SalesforceRollback ready
  1. Before sample runRestore point 01Restore
  2. Before full migrationRestore point 02Restore
  3. After verificationRestore point 03Current
Example

How long it takes, and what drives the quote

4-8 weeksTypical, smaller accounts
10-16 weeksLarge or heavily customised accounts

A quote scales with record volume, subitem enumeration count, and custom column complexity. Every quote is scoped with you; there is no self-serve pricing.

Get a quote for monday CRM to Salesforce →

Why teams move from monday CRM to Salesforce

  • Teams requiring enterprise CRM depth outgrow monday's flat item model. monday CRM's board-and-item mental model does not natively represent standard CRM relationships like Account-to-Contact or many-to-many Deal associations, leading to data duplication and confusion as deal volume grows. Salesforce's relational object model (Account, Contact, Opportunity, Custom Objects with lookup fields) handles complex sales motions with proper data integrity enforced at the schema level rather than through naming conventions or column discipline.
  • Automation action limits on lower tiers force teams to purchase additional packs or upgrade unexpectedly. Basic and Standard plans are capped at 250-1,000 automations per month, which mid-market sales teams exhaust quickly when automating lead routing, stage updates, and email triggers. Salesforce Flow has no monthly action cap; flow interview limits are governance-based rather than billing-based, removing the ceiling that forces monday upgrades.
  • monday's flexible column system lacks the schema governance that Salesforce enforces with field-level security, validation rules, and required field constraints. While monday's no-schema approach accelerates initial setup, it leads to inconsistent data (unformatted phone numbers, mixed date formats, duplicate columns with slightly different names) that becomes technical debt during migration. Salesforce's explicit field typing forces data cleaning at the schema level, which is a feature for teams migrating from monday's flexible environment.
  • Legacy Recipe automations are being deprecated, forcing teams to rebuild workflows or risk breakage during migration. Teams that built automations on monday's Sentence Builder system face a forced migration event regardless of whether they are switching platforms, which makes timing the switch to Salesforce strategic rather than reactive. We capture automation definitions during pre-migration review so customers have a written inventory before rebuilding in Salesforce Flow.
  • Per-seat pricing scales linearly and annual billing is non-refundable, creating cost lock-in risk as teams grow. Teams that overbought on annual contracts feel trapped during migration. Salesforce's per-user model, while higher per-seat, offers more predictable pricing at scale for teams with complex sales motions, and the Developer, Partial, and Full Copy Sandboxes allow safe migration testing without consuming production licenses.

Questions, answered

monday CRM to Salesforce migration questions

How long does a monday CRM to Salesforce migration take?

Most monday CRM migrations land between four and eight weeks for accounts under 10,000 People, 3,000 Deals, and no complex subitem hierarchies. Migrations with large subitem counts (requiring individual API enumeration), multiple Pipeline definitions, extensive custom column mapping, or Standard-plan accounts with tight API rate limits move to ten to sixteen weeks because of extended extraction windows and sandbox reconciliation cycles. The monday plan tier is a direct scoping variable for any account with more than a few thousand records.

Do monday automations and workflows migrate to Salesforce Flow?

No. monday automations are built using the Recipe (Sentence Builder) language or the new monday workflows system, both of which are structurally different from Salesforce Flow. They are workflow logic, not data, and are not migrated as code. We deliver a written inventory of every active monday automation with its trigger, conditions, and actions, plus a recommended Salesforce Flow equivalent for each. The customer's admin or a Salesforce partner rebuilds them post-migration. Note that monday is actively deprecating the Recipe system regardless of whether customers are switching platforms.

Do we lose Subitem data when migrating from monday CRM?

No, but Subitems require individual API enumeration because they are absent from monday's bulk account export and Excel export. We enumerate each Subitem via API using the parent Item's ID, which multiplies API call volume. On Basic and Standard plans (1,000 calls/day), large Subitem hierarchies extend the extraction timeline significantly. We flag the Subitem count during scoping so the customer understands the API load and timeline impact before extraction begins. Subitems migrate as Task records linked to the parent Opportunity or Contact.

Can we migrate monday CRM boards that are not CRM-related (project management boards)?

Yes. Non-CRM monday boards migrate as Salesforce Task records (for action items) or as Custom Object records (for persistent entities that do not fit the standard CRM object model). We preserve Item status, assignee, due dates, and the parent board reference as a custom field for audit. Board views (Kanban, Calendar, Chart) do not migrate — these must be rebuilt in Salesforce using the imported tabular data. We recommend documenting any board view configurations before migration begins.

What happens to files and attachments from monday CRM Items?

Files uploaded to monday Items are stored in monday's file storage and accessible via API. We retrieve attachment URLs and re-attach them to the corresponding Salesforce record as ContentDocument linked via ContentDocumentLink. File names and mime types are preserved. Files that exceed the destination org's storage limit are flagged for the customer's admin to address before import. If the destination Salesforce org has limited storage capacity, we recommend purchasing additional storage or migrating only active-record attachments during the initial migration.

How do we handle monday CRM's API rate limits during migration?

monday Basic and Standard plans are capped at 1,000 API calls per day; Pro at 10,000; Enterprise at 25,000. We throttle migration jobs to stay within limits, use exponential backoff on 429 responses, and schedule bulk extraction jobs overnight to maximize the available daily window. Large accounts on Standard plans with tens of thousands of Items may require 5-10 extraction days before transformation begins. We surface the total API call budget during scoping so the customer understands the extraction timeline before migration starts.

Do monday CRM Dashboards and saved views migrate to Salesforce?

No. monday Dashboards aggregate data across boards into chart widgets that reference live board data. Dashboard definitions do not export. Saved views (Kanban, Calendar, Chart, Map) are view configurations that are not included in Excel or account exports. We migrate the underlying tabular data so that Salesforce Reports and Dashboards can be rebuilt using the imported data. The customer's admin or a Salesforce partner rebuilds report and dashboard layouts based on the migrated data.

Get a quote

Moving from monday CRM to Salesforce?

Tell us roughly how many records and objects you have. We scope the mapping and the Salesforce setup with you, then send a quote.

Get a quote