Migrate from CRM and Deals for Zendesk to monday CRM

Zendesk Contact records map directly to Monday.com CRM Contacts with standard field transforms for email format and phone number formatting. The contact's primary Organization link migrates as a lookup to the mapped Monday.com Account. Any custom contact properties migrate as Monday.com Contact custom fields. We preserve the Zendesk contact ID in a legacy_id__c field for reconciliation during the warranty window.

Zendesk Organizations map to Monday.com CRM Accounts. Organization-level custom fields migrate as Account custom fields. The flat Zendesk org structure maps directly to Monday.com's account model. We resolve the Organization-to-Account mapping before Contact import so that the relationship is satisfied at insert time. Address, domain, and industry fields map to their Monday.com equivalents.

Zendesk Deals map to Monday.com CRM Items on a Board. The Deal's monetary value, name, and owner migrate as Item columns. We preserve the Zendesk Deal ID in a legacy_id__c column for post-migration reconciliation. Pipeline and stage metadata from Zendesk's separate Pipeline and Stage objects map to the destination Board's Groups representing pipeline stages.

Zendesk Pipelines and their associated Stages map to Monday.com CRM Boards with each Stage becoming a Group. We extract stage ordering, stage names, and stage probabilities from Zendesk and configure Groups in the corresponding order on the Monday.com Board. Probability percentages migrate as a Number column. If the source has multiple Zendesk Pipelines, we create a Monday.com Board per Pipeline, and a status column indicates which pipeline each Item belongs to.

Zendesk does not store stage-change history on the Deal record; stage transitions are logged as Activity records. We run a de-normalization query joining Activities to Deals to reconstruct the stage transition timeline, then write the sequence as an Update Log column or a linked sub-board. This is not a native Monday.com feature but we reconstruct it using the Update Log or a linked Items board representing the deal history sequence.

Zendesk Activities (calls, emails, meetings, tasks) linked to Contacts or Deals migrate as Monday.com CRM Activity timeline entries. Call disposition, duration, and recording URL move to custom columns. Meeting details including attendees and location migrate. The original timestamp is preserved. We write Activities after Contacts and Deals are inserted so the parent-item relationship resolves at insert time.

Zendesk Tickets do not have a native Monday.com CRM equivalent because Monday.com is a sales CRM, not a help desk. We create a separate Work Item Board in Monday.com and map Tickets as Items with status mapped from Zendesk ticket status to a Status column. Requester maps to a Contact or email column, assignee maps to an Owner column, and tags migrate as Labels. Ticket conversations do not migrate as threaded views; they are written as Activity entries on the item.

Zendesk v2 Custom Object types map to Monday.com Boards created as custom entities. Each Custom Object type becomes its own Board with columns corresponding to the custom object's fields. Lookup relationships between Custom Objects and standard objects (Contact, Organization, Deal) map to Monday.com Connect Boards or relation columns. We pre-create all board schemas in Monday.com before any records import. Plan-tier limits (3 on Team, 5 on Growth, 30 on Professional, 50 on Enterprise Plus) must be validated against the customer's source plan during scoping.

Zendesk's Legacy Custom Objects API is deprecated and incompatible with the current v2 API. We run the mandatory five-step Legacy-to-v2 migration (object type definition, schema creation, relationship type creation, record import, then relationship linkage) before any records can be written to Monday.com. This step alone can add three to five days to the timeline and may reveal Custom Objects that exceed Monday.com's board-structure-based capacity for the customer's planned use case. We flag any legacy objects that cannot be represented cleanly in Monday.com's board model.

Zendesk User and Agent records map to Monday.com Users by email match. We extract role and group assignment metadata from Zendesk but do not replicate internal Zendesk group memberships that have no Monday.com equivalent. The customer's admin provisions Monday.com User seats before production migration. Any Zendesk User without a matching Monday.com User goes to a reconciliation queue.