Migrate from Merlin to Odoo CRM

Merlin stores chat threads but has no CRM schema. We parse conversation text to identify person names, email addresses, and company references. Each distinct person identified in conversations becomes either an Odoo Contact (if company affiliation is established) or a Lead (if no company link is found). We preserve the original conversation text as an Odoo Note linked to the created Contact or Lead. Email addresses found in conversations are validated and mapped to the email field on Contact/Lead. Name parsing splits first and last name where possible; ambiguous extractions go to a manual validation queue for the customer's team to confirm before final creation.

Merlin's Document Chat uploads are stored as files in user-scoped storage. Free tier limits uploads to 10 pages; Pro allows unlimited length. We preserve the original file binary, filename, and upload date as an Odoo ir.attachment record. The attachment is linked to the most relevant Contact or Account based on entity extraction from the document text. Documents that reference multiple companies are attached to the primary Contact or Account identified in the document and noted in the attachment description for admin review.

Each Document Chat session in Merlin includes the uploaded file and the Q&A pairs generated during the session. We preserve these as Odoo Note records with the original question as the Note title and the AI-generated answer as the body. The Note is linked to the Contact or Account associated with the document. This captures the business context that was surfaced during the Merlin session even though the Q&A content does not map to a standard CRM field.

Merlin account metadata (email address and plan tier) is retrieved from account settings during the manual export. This information is used to map the Merlin user to a corresponding Odoo User record by email match. If the customer plans to continue using Merlin alongside Odoo for document analysis, the Odoo User record enables the admin to assign migrated entity ownership correctly. Note that Merlin does not support team workspaces, so any multi-user migration requires the customer to define role and territory assignments for Odoo User records that did not exist as structured concepts in Merlin.

Merlin image generation outputs are stored as image files in user-scoped storage. We preserve the file binary, original generation timestamp, and file type as an Odoo ir.attachment record. These are attached to the relevant Contact, Account, or Opportunity based on the conversation context or document context in which the image was generated. Image metadata (prompts used, model attribution) is not available in Merlin export and is flagged as permanently unavailable.

Merlin does not maintain a contacts database. Any Contact records created in Odoo are the result of entity extraction from conversation history and uploaded documents, not a direct object migration. We perform document-level entity extraction as a supplementary migration step to identify and structure any person names, email addresses, and phone numbers found in uploaded files. The customer reviews and approves all extracted contacts before creation in Odoo.

Merlin does not store company records. Any Account records created in Odoo are extracted from conversation text and document content where company names, domains, or business context is referenced. We use domain-name parsing from email addresses and document metadata to supplement company name extraction. Accounts are created in Odoo before Contacts so that Contact-Account lookups are satisfied at insert time.

Merlin has no deal or opportunity objects. Any Opportunity records in Odoo CRM must be manually defined by the customer based on business context recovered from conversation history and documents. We provide a structured template for the customer to document which conversations or documents reference deal values, pipeline stages, or sales milestones, and we create the corresponding Odoo Opportunity records from that documentation. This step requires significant customer involvement because deal data is not structurally stored in Merlin.

Merlin has no workflow, automation, or sequence objects. Odoo CRM's Automated Actions cannot be populated from source data because there is no source equivalent. We deliver a written inventory of Odoo CRM's available automation capabilities and map each to the customer's documented business process requirements, but the customer rebuilds automations in Odoo Studio as a post-migration configuration step.

Merlin does not expose a tagging or labeling system that is accessible via export. We cannot migrate tags as structured metadata because no tags exist in the source platform. If the customer used informal tagging conventions within conversation titles or document filenames, we document those patterns and propose a Tags strategy in Odoo CRM during scoping.

Merlin does not support user-defined properties or custom fields. Any structured data beyond conversation text and file blobs is not accessible for export. We cannot migrate custom properties because none exist. If the customer needs custom fields in Odoo for data that was conceptually tracked in Merlin conversations, we define those fields in Odoo Studio during the migration scope and document the mapping for the customer's admin to populate.

Merlin stores no call, email, meeting, or task records as structured objects. Any business activities must be documented by the customer and manually created in Odoo CRM. We provide a CSV template that maps date, type, subject, and related Contact or Account for the customer to populate from their documented activity history. Odoo Tasks and Events are created from this template as a post-migration data entry step.