Migrate from monday CRM to Pipedrive

monday CRM's People feature is a distinct entity storing name, email, phone, and CRM-specific properties accessible via the API as a separate object from regular board Items. We migrate People directly to Pipedrive Person records, mapping name to the Person object's name fields, email to email0, and phone to phone. The CRM module's contact properties (company association, lead status) map to Pipedrive Person custom fields. Duplicate detection uses email as the dedupe key. People without an email address are imported with a placeholder and flagged in the reconciliation report for manual review.

monday CRM Deals are CRM-typed Items attached to a Pipeline. Each Deal carries standard column values (deal value, close date, stage name) plus optional custom column values. We map deal value to Pipedrive's weighted_value and formatted_value, close date to close_date, and the Pipeline stage column to Pipedrive stage_id. The deal title maps from the Item's name field. Custom column values from monday map to Pipedrive custom Deal fields, with type coercion applied (monday number columns to numeric, date columns to datetime, status columns to picklist). Deals without a linked Person or Organization in monday are imported as standalone Deals and flagged for linking during reconciliation.

monday CRM Pipelines group Deals into ordered Stages. Each Pipeline has stage names and optional probability percentages. We map each monday Pipeline to a Pipedrive Pipeline, preserving stage names and probabilities. The stage order is preserved. Probability percentages from monday map to Pipedrive's stage probability values. If monday has multiple Pipelines, we create corresponding Pipedrive Pipelines so the deal distribution maps correctly.

Each monday Pipeline stage becomes a Pipedrive stage within the mapped Pipeline. Probability percentages migrate from monday to Pipedrive stage_probability values. We configure the stage as open, won, or lost in Pipedrive based on the monday stage's type. Stage order is preserved as the Pipedrive stage order. If monday's pipeline stages use custom status labels (not default Open/Won/Lost), we create custom stage names to match.

monday CRM has no native Organization or Account object — organizations must be inferred from Deals or from People entries. We compute Organization candidates by: (1) extracting the company name from monday People records where available, (2) extracting organization context from Deal Items where a company column is populated, and (3) using domain-based grouping from email addresses. Each inferred Organization becomes a Pipedrive Organization record, and we link the corresponding Person and Deal records to it via the OrganizationId lookup. Organizations without a name are created with a placeholder and flagged.

monday CRM Boards contain the column definitions that represent deal fields. The board structure (column types, names, settings) is preserved as a reference document for rebuilding custom fields in Pipedrive. Pipedrive does not have a board concept; the board's column layout maps to Pipedrive's custom field definitions on Deal, Person, and Organization objects. We deliver a column-to-field mapping table as part of the migration documentation.

Non-Deal CRM Items in monday (items in a CRM board that are not typed as Deals) are evaluated during scoping. If they represent activities or tasks linked to a Deal, they migrate as Pipedrive Activities (calls, meetings, tasks) or Notes attached to the parent Deal. Items without a Deal association are imported as standalone Notes on the related Person or Organization, or excluded if no link exists.

Subitems are excluded from monday's bulk account export and standard Excel export. We enumerate Subitems individually via the monday API using each parent Item ID, which multiplies API call volume. Each Subitem maps to a Pipedrive Deal Product entry (if it represents a line item with quantity and price) or a Note attached to the parent Deal (if it represents an activity or annotation). Subitem enumeration is the primary API-volume driver in monday CRM migrations.

monday board columns (text, numbers, dates, formulas, dependencies, status, country, phone, etc.) are preserved as field definitions in the migration documentation. Custom columns on Deals map to Pipedrive custom Deal fields. Custom columns on People map to Pipedrive custom Person fields. We pre-create the custom field definitions in Pipedrive (with matching API names) before the data import phase so that the import job can write to typed fields without post-import field creation.

monday CRM Users map to Pipedrive Users by email match. Active users on monday become active Pipedrive Users. We extract all owners referenced on Deals and People records and match them against the Pipedrive User table by email. Any monday Owner without a matching Pipedrive User is placed in a reconciliation queue for the customer to provision before the record import phase continues.

monday Updates are per-item comment threads. The Excel export can include Updates as a separate tab; via API they are enumerable per Item. We migrate Update text and timestamps to Pipedrive Notes attached to the relevant Deal, Person, or Organization, preserving the author name and timestamp. If the Update includes a mention or attachment, we note this in the reconciliation report for manual recreation in Pipedrive.

Files uploaded to monday board Items are stored in monday's file storage and accessible via the API. We retrieve attachment URLs via the monday API and re-upload them to Pipedrive as Deal attachments (linked to the migrated Deal). Large files are included at customer request; we can exclude files to reduce download time and focus on contact and deal data.