Migrate your monday CRM data

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

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

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

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

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

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

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