CRM migration
Field-level mapping, validation, and rollback between Insight Legal Case Management and HighLevel. We move data and schema; workflows are rebuilt natively in HighLevel.
Insight Legal Case Management
Source
HighLevel
Destination
Compatibility
12 of 15
objects map 1:1 between Insight Legal Case Management and HighLevel.
Complexity
BStandard
Timeline
2–5 days
Overview
Insight Legal Case Management is a UK-based practice management system that stores its data in Microsoft SQL Server, organising information around clients, matters, parties, time entries, documents, and ledgers. It runs as desktop software with optional cloud hosting and does not expose a REST API for third-party migrations. HighLevel is an all-in-one CRM and marketing platform that uses a REST API with bulk endpoints for data ingestion. Its data model centres on Contacts, Companies, Opportunities, Tasks, and Custom Objects. There is no native legal accounting module in HighLevel. FlitStack AI extracts your Insight Legal data directly from SQL Server, maps each table into HighLevel's object graph — clients become Contacts, parties become Companies, matters become Opportunities — and uses HighLevel custom fields to carry legal-specific metadata (practice area, fee earner, billing rate, IOLTA reference) that has no HighLevel native equivalent. Trust-account transaction history migrates as a related custom-object record. Workflows, automations, document files, and accounting ledgers do not transfer; we document them for manual rebuild. All migration runs use HighLevel's API v2.0 with its 200,000-request daily limit and 100-request per-10-second burst, and we run in batches to stay within those constraints.
Every standard and custom field arrives verified.
AI proposes the map; you confirm before any record moves.
Parent–child, lookups, and ownership stay linked.
Calls, emails, meetings — with original timestamps.
Documents, uploads, and inline notes move with the record.
Why teams make this switch
Leaving
What's pushing teams away
Choosing
What's pulling them in
Object mapping
Each row shows how a Insight Legal Case Management object lands in HighLevel, including any object-level transformations, lookup resolution, or schema-design dependencies.
Typical mapping — final map is confirmed during the sample migration step.
Insight Legal Case Management
Client
HighLevel
Contact
1:1Insight Legal Client records map to HighLevel Contacts. The client's name splits into firstname/lastname or stays as a single FullName field if no individual contact name exists. Email, phone, address, and client-number fields map to custom fields on the HighLevel Contact record.
Insight Legal Case Management
Client.Address
HighLevel
Contact.Address
1:1Client postal and billing addresses from Insight Legal map directly to the standard HighLevel Contact address fields. Multi-line address strings are parsed algorithmically and distributed across Address1, Address2, City, State, and PostalCode components. Country codes are validated and preserved exactly as they appear in the source database to maintain data integrity and jurisdiction flags for compliance purposes.
Insight Legal Case Management
Matter
HighLevel
Opportunity
1:1Insight Legal Matters become HighLevel Opportunities. The matter reference number maps to Case_Reference__c, the description maps to Opportunity Name, case status maps to StageName via value mapping, and all legal-specific metadata (practice area, fee earner, billing rate) goes into custom fields on the Opportunity.
Insight Legal Case Management
Matter.Client
HighLevel
Opportunity.ContactId
1:1The parent-client lookup on a Matter resolves to the HighLevel Contact ID created in step 1. This is the primary link that connects the Opportunity to its client record. If a Matter spans multiple clients, the primary client maps first and additional clients are surfaced as junction-object records.
Insight Legal Case Management
Matter.Party
HighLevel
Company + Custom Junction Object
many:1Insight Legal parties (Claimant, Defendant, Opposing Counsel, Witness, etc.) have two roles: they are both a Company and a Contact. We map the party name to a Company record and the individual contact name to a Contact record, then link both to the Matter-Opportunity via a custom-party-role junction object.
Insight Legal Case Management
Matter.FeeEarner
HighLevel
Custom Field on Opportunity
1:1Insight Legal fee earner codes (solicitor names or department codes) have no native HighLevel equivalent. We create a Fee_Earner__c pick-list custom field on Opportunity and map each code by name. HighLevel users must create matching values in their Opportunity settings before migration.
Insight Legal Case Management
Matter.BillingRate
HighLevel
Custom Field on Opportunity
1:1Hourly billing rates stored on the Matter are preserved in Billing_Rate__c on the Opportunity record. This is informational only and does not generate invoices or trigger billing actions — HighLevel does not produce legal invoices or process client trust accounting. The firm must select and configure an appropriate third-party accounting integration or establish a manual invoicing workflow after migration completes.
Insight Legal Case Management
Time Entry
HighLevel
Task + Custom Fields
many:1Insight Legal time entries merge into a HighLevel Task record. The description maps to Task Subject, the hours to Hours__c, the date to Task Date, and the billing rate to Billing_Rate__c. Time entries linked to a specific Matter connect to the corresponding Opportunity via the task's related-to lookup.
Insight Legal Case Management
Document
HighLevel
Custom Object Record
1:1Insight Legal document metadata (file name, document type, reference number, matter link, upload date) migrates as a Case_Document__c custom object. The binary file itself must be re-uploaded separately; we provide a document-repository checklist so nothing is missed. HighLevel's 25MB per-file limit applies.
Insight Legal Case Management
Trust Account
HighLevel
Custom Object Record
1:1HighLevel has no native IOLTA or client-trust accounting. We create a Trust_Account__c custom object with fields for account reference, client link, matter link, transaction type, description, amount, and date. Trust-account opening balances and reconciliation must be completed in a separate accounting tool post-migration.
Insight Legal Case Management
Trust Transaction
HighLevel
Custom Object Record (child of Trust Account)
many:1Individual trust-account debit and credit transactions map to Trust_Transaction__c records as children of the Trust_Account__c record. Each record carries the transaction date, description, amount, reference number, and matter link. This preserves audit history for bar compliance even though HighLevel does not process IOLTA bookkeeping.
Insight Legal Case Management
Matter Custom Properties
HighLevel
Opportunity Custom Fields
1:1Insight Legal allows user-defined matter properties for practice-area-specific data. Each custom property becomes an Opportunity custom field with the appropriate data type (text, number, pick-list, date). The firm reviews and names each field during the schema-setup phase before migration runs.
Insight Legal Case Management
Workflow / Automation
HighLevel
Not Migrated
1:1Insight Legal's pre-built legal workflows (conveyancing checklists, employment law step sequences, family law processes) have no HighLevel equivalent and cannot be migrated. We export the workflow definitions as a written reference document so the firm's HighLevel admin can rebuild them using HighLevel Workflows after migration.
Insight Legal Case Management
User / Staff
HighLevel
User
1:1Insight Legal staff records (solicitors, fee earners, admin) are resolved by email match against HighLevel Users. Unmatched staff are flagged before migration — the firm must create HighLevel accounts for them or reassign their matters to a fallback user before the full run.
Insight Legal Case Management
Tag / Category
HighLevel
Tag
1:1Insight Legal matter categories and tags — including practice area designations, matter-type classifications, and billing labels — map directly to HighLevel Tags using a one-to-one name correspondence. Tags applied to a Matter connect to the corresponding Opportunity record automatically during migration. The complete tag vocabulary is preserved unchanged so existing reporting filters, dashboards, and segmentation rules function without any rebuilding or reconfiguration required.
| Insight Legal Case Management | HighLevel | Compatibility | |
|---|---|---|---|
| Client | Contact1:1 | Fully supported | |
| Client.Address | Contact.Address1:1 | Fully supported | |
| Matter | Opportunity1:1 | Fully supported | |
| Matter.Client | Opportunity.ContactId1:1 | Fully supported | |
| Matter.Party | Company + Custom Junction Objectmany:1 | Fully supported | |
| Matter.FeeEarner | Custom Field on Opportunity1:1 | Fully supported | |
| Matter.BillingRate | Custom Field on Opportunity1:1 | Fully supported | |
| Time Entry | Task + Custom Fieldsmany:1 | Fully supported | |
| Document | Custom Object Record1:1 | Fully supported | |
| Trust Account | Custom Object Record1:1 | Fully supported | |
| Trust Transaction | Custom Object Record (child of Trust Account)many:1 | Fully supported | |
| Matter Custom Properties | Opportunity Custom Fields1:1 | Fully supported | |
| Workflow / Automation | Not Migrated1:1 | Fully supported | |
| User / Staff | User1:1 | Fully supported | |
| Tag / Category | Tag1:1 | Fully supported |
Gotchas + challenges
Platform-specific issues from each side, plus the pair-specific challenges that don't show up on either platform's page on its own.
Insight Legal Case Management gotchas
No public API forces all migrations through vendor services
Hybrid hosting creates two distinct extraction paths
Thousands of fields per matter require explicit scoping
Trust account compliance data has regulatory retention requirements
Out-of-the-box workflows may not transfer to non-Insight systems
HighLevel gotchas
Sub-account architecture creates isolated data silos per client
Usage-based telecom and AI costs are not in the subscription price
Workflows have no native equivalent in most destination CRMs
API rate limits cap bulk migration throughput at 100 requests per 10 seconds per sub-account
White-label configuration and branding assets do not export via API
Pair-specific challenges
Migration approach
Establish SQL Server access and extract Insight Legal schema
FlitStack AI requests read-only SQL Server credentials from the firm's IT administrator. We connect to the Insight Legal database, document the schema for clients, matters, parties, time entries, documents, trust accounts, and trust transactions, and produce a data dictionary. If Insight Legal runs on a local desktop installation, we guide the IT administrator through producing a backup file (.bak) for off-site extraction. This step completes the discovery phase and establishes the complete source-data inventory before any field mapping begins.
Create HighLevel custom fields and custom objects
Before any data is written to HighLevel, we create all required custom fields and custom objects identified during discovery: Practice_Area__c, Fee_Earner__c, Billing_Rate__c, Case_Reference__c, and Case_Type__c on the Opportunity object; Case_Document__c and Trust_Account__c custom objects; and Trust_Transaction__c as a child custom object under Trust_Account__c. The firm's HighLevel admin reviews and approves the field names and pick-list values before we proceed. This step prevents import errors and ensures all custom fields are present when the migration API calls are made.
Map and validate all object and field mappings
FlitStack AI produces a detailed mapping specification covering every object and field in the migration scope. Client records are mapped to Contacts, parties to Companies with a junction object for party-role relationships, matters to Opportunities with stage-name value mapping, time entries to Tasks, and trust data to the Trust custom objects. We cross-reference the mapping spec against the source schema and the destination custom field IDs to confirm every field resolves correctly. Any ambiguous mappings — particularly multi-party matters and non-standard case statuses — are flagged for the firm to decide before the test migration runs.
Run a sample migration with field-level diff
A representative sample — typically 100–300 records across clients, matters, parties, time entries, and trust accounts — migrates first. We generate a field-level diff comparing source values against destination field values so the firm's administrator can verify that matter statuses, fee earner assignments, billing rates, and IOLTA references all landed correctly in HighLevel. Any mapping errors are corrected before the full run. The sample also validates that HighLevel API rate limits are respected at the target sub-account's throughput rate.
Execute full migration with delta-pickup window
The full data set migrates in API batches, respecting HighLevel's 200,000-request daily limit and 100-request per-10-second burst. A delta-pickup window of 24–48 hours runs after the initial bulk load, capturing any matters, contacts, or time entries modified or created in Insight Legal during the cutover period. FlitStack AI's audit log records every record written, every field set, and every error encountered. One-click rollback is available if the post-migration reconciliation check fails. The firm's team continues working in Insight Legal throughout — no downtime is required on the source system.
Platform deep dives
Insight Legal Case Management
Source
Strengths
Weaknesses
HighLevel
Destination
Strengths
Weaknesses
Complexity grading
Standard CRM migration. 2 of 8 objects need a mapping; the rest are 1:1.
Overall complexity
Standard migration
Derived from compatibility, mapping clarity, API constraints, and data volume across Insight Legal Case Management and HighLevel.
Object compatibility
2 of 8 objects need a mapping; the rest are 1:1.
Field mapping clarity
Field mapping is derived from defaults — final spec confirmed during the sample migration.
Timeline complexity
8-object category — typical timelines run 2–7 days end-to-end.
API constraints
Insight Legal Case Management: Not publicly documented.
Data volume sensitivity
Insight Legal Case Management doesn't expose a bulk API — REST + parallelization used for high-volume runs.
Estimator
Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.
Step 1
Pick a category, then your source and destination platforms.
Category
FAQ
Answers to the questions buyers ask most during Insight Legal Case Management to HighLevel migration scoping. Not seeing yours? Book a call.
Walk through your Insight Legal Case Management to HighLevel migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationAdjacent paths
Other ways to leave Insight Legal Case Management
Other ways to arrive at HighLevel
Ready when you are
Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.