Migrate from Concord CRM to monday CRM

Concord CRM Companies export with all standard and custom fields (name, domain, address, phone, industry, source, created_at, updated_at) via API or CSV. Companies must be exported and imported first because Concord Contacts reference company_id as a foreign key. We map each Concord Company to a Monday.com Company entity or a Company Board Item, using the company name as the dedupe key. Custom field types (text, select, date, number, boolean) map to their corresponding Monday column types (Text, Status/Label, Date, Numbers, Checkbox). If Concord stores multiple address components (street, city, state, postal, country) separately, we concatenate them into a single Address column in Monday.

Concord CRM Contacts export with first name, last name, email, phone, job title, source, owner, and company_id. We map company_id to the Monday.com People entity's Company association, resolving the Company Item ID from the preceding import phase. The Concord contact's email becomes the People email field and serves as the dedupe key. Custom fields on Contact migrate as additional columns on the People Item. The Concord contact's assigned user (owner_id) maps to a Monday People column or assignee field.

Concord CRM Deals export with deal name, value, stage, expected close date, assigned user, and associated company and contacts. We map Deals to Monday.com Deal Board Items, using the Concord dealstage name mapped to a Monday Status column representing pipeline stages. The Concord deal value maps to a Numbers column; expected_close_date maps to a Date column. The associated company and contacts from Concord become linked Deal Items or People Items in Monday CRM using the People and Company entity types. We configure the Monday Deal Board before migration to match the Concord pipeline stage names and order.

Concord CRM Deal pipeline stages are stored as deal properties and export as stage names or IDs. Each Concord pipeline maps to a Monday.com Deal Board with a Status column whose label values match the Concord stage names. Stage probability percentages from Concord do not map directly to Monday CRM (Monday Deal Boards do not have native stage probability fields at this tier) and are instead documented for the customer to add to a separate Numbers column or tracking dashboard post-migration.

Concord CRM Products export with name, price, SKU, and description. We map Products to a Monday.com Board configured as a Product or Inventory board with columns for product name, price (Numbers column), SKU (Text column), and description (Text column). Products are not tied to other Concord objects via foreign key constraints, so import order is flexible relative to Contacts and Deals. API-standard CRUD operations on the Concord Product endpoint are mirrored to Monday Board Items via the Monday.com API.

Concord CRM Activities (calls, meetings, tasks) export with type, date, notes, and linked resource type and ID. We split Activities by type: tasks map to a Monday.com Task Board with status, due date, and notes columns; meetings and calls are logged in the Monday CRM Emails & Activities board linked to the corresponding People or Deal Item. The linked resource type (Contact, Company, Deal) and its ID are stored as Text columns or relation columns so the association is visible in the board view. If the linked resource has not yet been migrated (a deal still pending import), we hold those Activity records in a staging queue and resolve the association after the parent record imports.

Concord CRM custom fields on Contacts, Companies, and Deals are accessible via the REST API using the field UUID as the key. Boolean fields map to Monday Checkbox columns, date fields to Monday Date columns, select fields to Status or Label columns, text fields to Text columns, and number fields to Numbers columns. We enumerate every Concord custom field during scoping, assign the corresponding Monday column type, and configure the board columns before data import begins. Custom field visibility settings from Concord (detail, create, update views) do not have a direct Monday equivalent and are noted for the customer to configure manually post-migration.

Concord CRM Users export via API with email, name, and role assignment. Monday.com CRM uses the workspace member list for assignees on Items. We match Concord owner_id to Monday workspace members by email during the user reconciliation phase. Any Concord owner without a matching Monday user goes to a reconciliation queue for the customer to provision before record import resumes. Concord role permissions (admin, user, restricted) do not map to Monday CRM roles directly; workspace-level permission management is separate from CRM board access and requires manual configuration post-migration.