Migrate from Merlin to monday CRM

Merlin document uploads (up to 10 pages on Free tier, unlimited length on Pro) are parsed and their binary content preserved. We upload documents as file attachments to the nearest Monday.com CRM Item—either the relevant Person, Organization, or Deal record—using the Monday.com API file upload endpoint. File type, original filename, and upload date transfer. Documents that exceed the Free-tier page limit during Merlin upload may have been truncated; we flag these during scoping so the customer can re-upload from source if available.

Merlin Document Chat sessions generate question-and-answer pairs against uploaded files. These are not first-class CRM activities but are stored as conversational context. We extract Q&A pairs and convert them to Notes attached to the corresponding Monday.com Person, Organization, or Deal item, with the original question as the Note title and the answer as the body. This preserves the reference context from Merlin without creating duplicate records.

Merlin stores no contacts database. Any person names found within uploaded documents (contracts, proposals, reports) are extracted via document parsing as a supplementary migration step. Each extracted person becomes a Monday.com People item with name fields populated. Email addresses and phone numbers found alongside person names in documents are mapped to the corresponding email and phone column types in Monday.com. This is entity reconstruction, not a direct record migration.

Company and organization names appearing in Merlin-uploaded documents are extracted during document parsing. Each extracted organization becomes a Monday.com Organization item with the company name mapped to the organization name column. Any associated addresses, websites, or industry tags found in documents are mapped to the corresponding Monday.com column types. This is a best-effort extraction based on document content; organizations not mentioned in documents are not captured.

Merlin conversation threads (chat sessions with the AI assistant) have no equivalent structure in Monday.com CRM. The E&A timeline tracks emails, calls, meetings, and tasks associated with CRM records—not general AI chat logs. We do not migrate conversation threads as structured records. We extract any business-relevant entities mentioned in conversations during document parsing and flag thread export for the customer's offline archive if needed.

Merlin account metadata (email address, plan tier) can be retrieved from account settings. This maps to the Monday.com User record for team provisioning. Owner assignment for CRM Items in Monday.com is based on User records; the Merlin user's email becomes the Monday.com User email for team member setup. This is a prerequisite for item assignment during migration.

Merlin image generation outputs (stored as attachments in Merlin) are treated as file blobs. We upload generated images as attachments to the nearest Monday.com CRM Item using the file upload API. Image creation date transfers as the attachment upload timestamp. Image-generation outputs without associated CRM context are attached to a general workspace Items board at the customer's direction.

Merlin does not support custom fields, tags, or any automation engine. There are no structured metadata properties or workflow rules to migrate. Monday.com CRM custom columns, tags, and Automation Center rules must be configured fresh post-migration by the customer's admin. We deliver a written configuration guide covering recommended column setup for People and Organization items based on the extracted entity fields.