Migrate from Legal Case Tracker to HighLevel

Case status to pipeline stage mapping requires a value-by-value table before migration runs

Legal Case Tracker defines case status values (e.g., Intake, Active, Pending, Closed) that are fixed and uniform across the platform. HighLevel's pipeline stages are customizable per pipeline, and the stage pick-list must be configured before any Opportunity record can be saved with a stage value. If your Legal Case Tracker statuses don't match HighLevel's default stage names, we need to create a status-to-stage mapping table during schema setup. Mismatched values that aren't pre-mapped will cause Opportunity import rows to fail validation. We deliver this mapping plan before the migration runs and your HighLevel admin pre-creates the pipeline stages so data lands cleanly.

Document re-upload is a manual step — attachments do not migrate as file pointers

Legal Case Tracker stores file attachments directly on case records in its own document hub. HighLevel does not read Legal Case Tracker's file storage — every attachment must be downloaded from Legal Case Tracker and re-uploaded to HighLevel Files, then programmatically linked to the corresponding Opportunity record. For cases with dozens of documents (pleadings, contracts, correspondence), this step adds measurable time to the migration. We handle the download, re-upload, and linking via the HighLevel API, but the per-file API call count means document-heavy cases push toward the upper end of the pricing range. We recommend reviewing case document counts during discovery to scope this accurately.

Legal-specific custom fields require HighLevel custom field creation before migration

HighLevel ships with a fixed set of standard fields on Contacts, Companies, and Opportunities. Fields like court jurisdiction, filing deadline, opposing counsel, case type classification, and billing rate have no native HighLevel equivalent. These must be created as custom fields in HighLevel (Settings → Custom Fields) before any data containing those values can be imported. We deliver a custom field creation plan listing each legal-specific field, its data type (text, pick-list, date, currency), and which HighLevel object it belongs to. If your firm has more than 20 custom fields, the additional schema setup time is factored into the upper pricing tier.

Workflows, automations, and email templates do not transfer and must be rebuilt

Legal Case Tracker supports rule-based email notifications and task reminders triggered by case status changes or deadline approaching events. HighLevel's Workflow Builder provides equivalent or more powerful automation capabilities (triggers, conditions, time delays, CRM actions, SMS/email sends), but the logic cannot be imported. Every automation, workflow, and email template in Legal Case Tracker must be manually recreated in HighLevel's Workflow Builder after migration. We export your Legal Case Tracker workflow definitions as a reference document so your HighLevel admin can rebuild them efficiently. This limitation is disclosed upfront so your team budgets the post-migration rebuild time.

HighLevel sub-account model affects data isolation — cases may need a dedicated sub-account

HighLevel's agency-tier plans support sub-accounts, which isolate data between clients or business units. If your law firm manages multiple practice areas or client portfolios that need strict data separation, the migration plan must decide whether all cases land in a single HighLevel account or are distributed across sub-accounts. Cases that cross sub-account boundaries (e.g., a client with matters in two practice areas) cannot share a single Opportunity record if the sub-accounts are fully isolated. We surface this decision point during discovery and help you configure sub-account boundaries before data is placed.