Migrate from Link app to HighLevel

Conversation threads do not map to native HighLevel conversation objects

Link App's threaded conversation view is a core data structure — messages, timestamps, and participants are stored as a linear thread per client matter. HighLevel does not have a native threaded conversation object; communications are stored as individual Tasks, Emails, Calls, or Notes attached to a contact. We reconstruct thread context by attaching each message as a separate Note with a custom thread-ID field and chronological ordering. This preserves the content and timing but not the interactive threaded UI that Link App provides. Your team should review the Note stack to verify thread integrity before going live.

Case and matter records require a custom object setup before migration

HighLevel does not ship a native case or matter object. Firms migrating from Link App must have a Case_Matter__c custom object pre-created in HighLevel before data lands — this includes defining all custom fields (case type, billing rate, court jurisdiction, etc.), creating the lookup relationship to Contact, and configuring any workflow triggers that should fire on case status changes. We deliver a schema setup specification document as part of the migration plan so your HighLevel admin can pre-build the object before the data migration run. Without this pre-work, case records cannot be imported correctly.

Document-to-thread associations are reconstructed, not native

Link App links document attachments directly to specific conversation threads and case records with version history. In HighLevel, files attach to records (Contact, Company, or Custom Object) but there is no native thread-link association. We store the original thread ID as a custom field on the attachment record and add a note comment linking the document to the thread. This is a reference reconstruction — it requires admin acceptance of the mapping before the migration commits. Review the document linking plan in the sample migration output to confirm the association logic meets your operational needs.

Billing and invoice data cannot migrate to native HighLevel objects

Link App invoice records and billing logs have no native equivalent in HighLevel's data model — HighLevel does not include a billing, time-tracking, or invoicing module at the CRM level. We preserve invoice reference numbers and amounts as custom fields on the Case_Matter__c record and store billing history as Notes attached to the case. For ongoing billing workflows, your team will need to rebuild the logic in HighLevel's Workflow Builder or integrate with a third-party accounting tool such as QuickBooks or LawPay. This is disclosed upfront so you can plan the rebuild alongside the migration rather than discovering it post-cutover.

User and owner resolution by email match is required before migration

Link App staff records are resolved to HighLevel Users by email address. Any Link App user whose email does not match an existing HighLevel user account will be flagged as an unmatched owner. Unmatched owners require either creating the user in HighLevel first or reassigning their records to a designated fallback user before the migration run executes. This step is mandatory — HighLevel requires a valid OwnerId on all opportunity and custom object records. We provide an unmatched-owner report after the initial scan so your team can resolve each account before data moves.