Migrate from monday CRM to Nutshell

monday CRM's People feature is the primary contact object, storing name, email, phone, and CRM-specific properties accessible via the API as a distinct entity from regular board Items. We migrate People 1:1 into Nutshell People, using the email address as the dedupe key. Any monday People records that lack an email address are flagged in the reconciliation report for the customer's admin to resolve before final import because Nutshell requires a contact method for CRM records.

monday CRM Deals are CRM-typed Items attached to a Pipeline. Each Deal Item has standard column values for deal value, close date, and pipeline stage, plus any custom columns. We map these to Nutshell Leads by default, using the Deal name as the Lead name, the deal value column as the estimated_value field, and the close date column as the close_date field. For teams that use monday People linked to Deals, we resolve the Person link and create the Lead with a primary People association. The customer chooses during scoping whether unqualified Deals import as Leads or Contacts attached to existing Nutshell People records.

monday CRM Pipelines define the ordered Stage structure for Deals, with each Stage having a name and an optional probability percentage. We map Pipeline definitions 1:1 to Nutshell Pipelines, preserving the stage order and probability values. Probability percentages are stored on each Nutshell Stage and used for weighted pipeline reporting. Multi-pipeline accounts (Pro and Enterprise) generate one Nutshell Pipeline per monday Pipeline, which Nutshell supports on all paid tiers.

monday CRM board custom columns (text, number, date, status, formula, dependency, etc.) are field definitions that live on the board, not the record. We extract every custom column definition during pre-migration scoping and create matching Nutshell custom fields on the relevant entity (People, Account, or Lead). Column type mapping follows the most appropriate Nutshell field type: monday Number columns map to Nutshell number fields, Date columns to date fields, Status columns to Nutshell drop-down fields. Formula and Dependency columns that rely on monday's calculation engine are flagged as not migratable data and documented for rebuild.

monday board Items that are not CRM-typed but contain sales-relevant data (e.g., a board used to track prospect research or account notes) migrate as Nutshell Leads with the Item name as the lead name and the Item description or Updates as lead notes. We evaluate each board during scoping to determine whether its Items represent Deals to migrate or contextual notes to attach to the related Deal.

Subitems nested inside monday CRM Deal Items are enumerated individually via the monday API because they are excluded from bulk exports. We pull each Subitem by parent Item ID, then map the Subitem name and content to a Nutshell Note attached to the related Lead or Contact record. If the Subitem contains structured data (numeric values, dates, or people assignments), we parse those into separate Note fields rather than a single text blob. This step carries the highest API call volume on the source side because every parent Item requires a follow-up enumeration request.

monday Item Updates are per-record comment threads enumerable via the monday API. We map each Update text and timestamp to a Nutshell Activity record linked to the related Lead or Contact. The activity_type is set to NOTE and the created date preserves the original monday timestamp. Attachments referenced in Updates are retrieved as file URLs and attached to the corresponding Activity record.

monday files uploaded to CRM board Items are stored in monday's file storage and retrievable via the API. We enumerate file URLs per Item during the Subitem and Updates enumeration pass, then create file attachments on the corresponding Nutshell Lead or People record. Large files that exceed Nutshell's attachment limits are flagged in the reconciliation report with a recommendation to migrate them to a linked cloud storage location.

monday account Users are mapped 1:1 to Nutshell Users by email address during the migration. Enterprise permission structures such as multi-level permissions and SAML SSO do not migrate from monday and are noted for the customer's admin to configure in Nutshell post-migration. Any monday Owner without a matching Nutshell User is held in the reconciliation queue for admin provisioning before the record import phase.

monday automations built using the Sentence Builder language are not migratable because they are workflow logic, not data, and because the Sentence Builder system is being deprecated by monday.com in favour of the new monday workflows infrastructure. We capture every active automation definition during pre-migration review (trigger, conditions, actions) and deliver a written inventory document with a recommended equivalent in Nutshell's automation builder. The customer's admin rebuilds these in Nutshell post-migration.