Migrate from Merlin to HighLevel

Merlin user account metadata (email address, plan tier, usage quota from account settings) maps to a GoHighLevel User record. The email address becomes the GoHighLevel User login. Owner assignment for conversations is not a first-class concept in Merlin's model, so conversation and document ownership maps to whichever GoHighLevel User the customer designates as the migration target during scoping. We do not create multiple Users from a single Merlin account export.

Merlin conversation threads (chat text and timestamps) do not map to a native CRM object because GoHighLevel has no standalone conversation store. We map conversation text to a Custom Object called 'AI Conversation Log' with fields for thread_id, created_at, and conversation_text. Alternatively, for threads that reference identified contacts extracted from document content, we link the conversation text as a Note attached to the relevant Contact record via ContentDocumentLink. Thread-level metadata (per-turn model, token counts, latency) is permanently absent from Merlin's export and cannot be reconstructed.

Documents uploaded to Merlin's Document Chat feature migrate as binary blobs into a GoHighLevel Custom Object called 'Document Archive.' Each record holds document_name, file_type, upload_date, file_size, and the binary content as a linked attachment. Free-tier uploads were capped at 10 pages; Pro allowed unlimited length. We flag any documents that appear truncated (file size below expected threshold for page count) so the customer can re-upload the full version if needed. Document-chat Q&A pairs are extracted as separate Custom Object records linked to the parent document.

Each question-answer pair generated during Merlin's Document Chat feature migrates as a record in a Custom Object called 'Document Q&A Log.' Fields include source_document_id (lookup to Document Archive), question_text, answer_text, and timestamp. The customer can use these records for audit or reference but should note that the Q&A context is preserved as plain text only; the original document remains the source of truth.

Image outputs from Merlin's image generation feature migrate as Attachments linked to the User record or to a Custom Object called 'AI Asset Library.' We preserve file type, creation date, and binary content. Downstream mapping to a specific Contact or Opportunity is not possible from Merlin's source data because image outputs carry no business context in the platform.

Merlin has no Contact database. Any person names, email addresses, phone numbers, or job titles found inside uploaded documents are extracted via document parsing during migration. Extracted entities map to GoHighLevel Contact records with FirstName, LastName, Email, Phone, and JobTitle fields populated where data is present. Names without email are created as Contacts with a 'Source: Document Extract' tag for admin review. This is an enrichment step, not a guaranteed complete contact list; the customer should validate and complete ownership assignment post-import.

Company names, domains, addresses, and industries extracted from Merlin's uploaded documents map to GoHighLevel Company records. We link extracted Companies to extracted Contacts where a relationship is inferable from document context (e.g., a person listed under a company name in a contract or report). Company records without a clear domain are created with Company Name only and flagged for enrichment in GoHighLevel.

Merlin does not store deal or pipeline data. No migration action is possible. The customer creates Pipelines and Opportunity records in GoHighLevel after migration using the extracted Contact and Company records as a foundation. We provide a pipeline template skeleton based on common GoHighLevel stage configurations as a reference document.