Migrate from monday CRM to Salesforce Sales Cloud

monday CRM's People entity stores name, email, phone, and CRM-specific properties as a distinct object from board Items. 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.

monday CRM Deals are CRM-typed Items attached to a Pipeline. 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.

Each monday CRM Pipeline becomes a Salesforce Record Type on Opportunity with a corresponding Sales Process that whitelists the relevant Stage values. 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.

monday CRM Boards are the fundamental container for Items. 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.

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. We preserve Item status, assignee (via Owner lookup resolution), due dates, and the parent Board reference as a custom field for audit.

Subitems are nested rows inside a monday Item and are NOT included in bulk account exports or Excel exports. 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).

monday boards support over 20 column types (text, numbers, dates, formulas, dependencies, status, etc.). Each Custom Column maps to a Salesforce custom field on the appropriate object with matching field type. Date columns map to Date; formula columns are flagged for Salesforce formula field recreation post-migration; multi-select columns map to multi-select picklist. Column types relying on monday's proprietary runtime (Formula, Dependency) cannot be evaluated during migration and are noted for manual rebuild.

Files uploaded to monday Items are stored in monday's file storage and accessible via API as attachment URLs. 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.

monday Updates are per-item comment threads. We preserve update text and timestamps. If the destination org uses Chatter, updates migrate as FeedItem records on the parent record's feed. If Chatter is not enabled, updates migrate as Salesforce Note records linked via ContentDocumentLink. Activity timeline ordering is preserved by timestamp.

monday Users are account members assigned as owners or collaborators. We map users 1:1 by email and name. monday User IDs are preserved in a custom field monday_user_id__c for audit. Enterprise permission structures (multi-level permissions, SAML SSO) are not part of the standard API export and require manual configuration in Salesforce after migration. Users without a matching Salesforce User are held in a reconciliation queue for the customer's admin to provision before record import resumes.

monday automations are defined using the Recipe (Sentence Builder) language or the new monday workflows system. They are workflow logic, not data, and are not migrated. We capture automation rule definitions during pre-migration review so customers have a written inventory with trigger, conditions, and actions documented for rebuild in Salesforce Flow. Legacy Recipe automations are being deprecated by monday regardless of migration status.

monday Dashboards aggregate data across multiple boards into charts and summary widgets, referencing board Items and column data live. Dashboard definitions do not export. We migrate the underlying tabular data so that dashboards can be rebuilt in Salesforce Reports and Dashboards post-migration. The customer's admin or a Salesforce partner rebuilds dashboard layouts based on the imported data.