CRM migration

Migrate from Insight Legal Case Management to HighLevel

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 logo

Insight Legal Case Management

Source

HighLevel

Destination

HighLevel logo

Compatibility

80%

12 of 15

objects map 1:1 between Insight Legal Case Management and HighLevel.

Complexity

BStandard

Timeline

2–5 days

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

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.

Field-level fidelity

Every standard and custom field arrives verified.

Schema-aware mapping

AI proposes the map; you confirm before any record moves.

Relationships preserved

Parent–child, lookups, and ownership stay linked.

Full activity history

Calls, emails, meetings — with original timestamps.

Attachments & notes

Documents, uploads, and inline notes move with the record.

Why teams make this switch

Two sides of the same decision

Leaving

Insight Legal Case Management logo

Insight Legal Case Management

What's pushing teams away

  • Pricing lacks transparency on the vendor site — firms report needing to request a quote rather than self-serve pricing information
  • No publicly documented API means all data exports must go through Insight Legal's own migration service, limiting flexibility
  • Smaller firm users report that the feature depth designed for mid-to-enterprise practices can introduce unnecessary complexity
  • Switching to alternatives like Clio or Smokeball often cited for better mobile experience and lower entry cost for small practices
  • Some users find the UK-specific compliance features add administrative overhead that smaller practices do not require

Choosing

HighLevel logo

HighLevel

What's pulling them in

  • Agencies choose HighLevel to consolidate CRM, email, SMS, scheduling, and funnels into one subscription, eliminating monthly bills for five to ten separate SaaS tools they previously stitched together.
  • The flat-rate pricing model bills per sub-account rather than per contact, so growing a contact database from 1,000 to 100,000 records does not trigger a billing surprise—a common pain point avoided by migrating customers.
  • White-label and sub-account capabilities let agencies resell HighLevel access to their own clients, turning a software cost center into a recurring revenue stream that justifies the subscription.
  • The platform ships a 14-day free trial with no credit card required, giving teams a low-friction entry point to validate fit before committing to the $97/month Starter tier.
  • Marketing agencies managing multiple client accounts use sub-accounts to maintain data isolation per client while operating under a single agency billing relationship with HighLevel.

Object mapping

How Insight Legal Case Management objects map to HighLevel

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

maps to

HighLevel

Contact

1:1
Fully supported

Insight 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

maps to

HighLevel

Contact.Address

1:1
Fully supported

Client 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

maps to

HighLevel

Opportunity

1:1
Fully supported

Insight 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

maps to

HighLevel

Opportunity.ContactId

1:1
Fully supported

The 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

maps to

HighLevel

Company + Custom Junction Object

many:1
Fully supported

Insight 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

maps to

HighLevel

Custom Field on Opportunity

1:1
Fully supported

Insight 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

maps to

HighLevel

Custom Field on Opportunity

1:1
Fully supported

Hourly 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

maps to

HighLevel

Task + Custom Fields

many:1
Fully supported

Insight 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

maps to

HighLevel

Custom Object Record

1:1
Fully supported

Insight 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

maps to

HighLevel

Custom Object Record

1:1
Fully supported

HighLevel 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

maps to

HighLevel

Custom Object Record (child of Trust Account)

many:1
Fully supported

Individual 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

maps to

HighLevel

Opportunity Custom Fields

1:1
Fully supported

Insight 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

maps to

HighLevel

Not Migrated

1:1
Fully supported

Insight 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

maps to

HighLevel

User

1:1
Fully supported

Insight 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

maps to

HighLevel

Tag

1:1
Fully supported

Insight 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.

Gotchas + challenges

What specifically takes care here

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 logo

Insight Legal Case Management gotchas

High

No public API forces all migrations through vendor services

High

Hybrid hosting creates two distinct extraction paths

Medium

Thousands of fields per matter require explicit scoping

Medium

Trust account compliance data has regulatory retention requirements

Low

Out-of-the-box workflows may not transfer to non-Insight systems

HighLevel logo

HighLevel gotchas

High

Sub-account architecture creates isolated data silos per client

High

Usage-based telecom and AI costs are not in the subscription price

Medium

Workflows have no native equivalent in most destination CRMs

Medium

API rate limits cap bulk migration throughput at 100 requests per 10 seconds per sub-account

Low

White-label configuration and branding assets do not export via API

Pair-specific challenges

  • Insight Legal SQL Server extraction requires direct database credentials

    Insight Legal stores its data in Microsoft SQL Server, not a cloud API. FlitStack AI extracts data via a direct database connection using credentials provided by the firm's IT administrator. If Insight Legal runs on a local desktop PC rather than a hosted server, the firm must either provide RDP access to the machine or export a SQL Server backup file (.bak) for us to restore and extract from. This is a specific technical requirement of Insight Legal that does not apply to cloud-native CRMs — it must be resolved before migration planning begins, and it extends the discovery phase by 3–5 business days in most cases.

  • HighLevel has no native legal accounting — IOLTA references and trust transactions require custom objects

    Insight Legal's practice management includes full billing ledgers, time recording, disbursement tracking, and IOLTA client-account management. HighLevel has no equivalent. We map trust-account references and transaction history to a Trust_Account__c custom object with child Trust_Transaction__c records, preserving the audit trail for bar compliance purposes. However, the firm must handle ongoing IOLTA bookkeeping in a separate accounting tool (such as LawPay, CosmoLex, or QuickBooks) after migration. Any Insight Legal billing invoices, client statements, or ledger reconciliation reports are not transferable to HighLevel — the firm should export and archive these as PDFs before the migration date.

  • HighLevel API v2.0 rate limits constrain bulk import speed on large matter sets

    HighLevel's API v2.0 enforces a daily limit of 200,000 requests per sub-account and a burst limit of 100 requests per 10-second window. For migrations exceeding 5,000 records, we batch writes to stay within these constraints and pace inserts to avoid 429 Too Many Requests responses. The practical throughput for a matter migration with 30+ custom fields per record is approximately 1,500–2,500 record writes per hour. Firms with 50,000+ matters, time entries, and trust transactions may see migration clock time extend to 3–5 days of API throughput, not counting the test run. We disclose this in the scoping call and plan batch windows accordingly.

  • Document binary files must be re-hosted after migration — only metadata transfers automatically

    Insight Legal stores documents with full version history inside its own file repository. HighLevel stores files in its own file system with a 25MB per-file limit. FlitStack AI migrates document metadata (file name, type, reference number, upload date, matter link) to a Case_Document__c custom object so the document index survives in HighLevel. The actual binary files must be re-uploaded manually to HighLevel's file storage after migration, or re-hosted to a linked storage service (Google Drive, Dropbox, SharePoint) with the URLs recorded in the Case_Document__c record. Firms with large document repositories should allocate 2–5 days of staff time for post-migration file re-uploads.

  • HighLevel Workflows cannot import Insight Legal automation logic

    Insight Legal ships with pre-built process workflows for conveyancing, employment, family law, and private client work. These are Insight-Legal-specific automation rules that have no structural equivalent in HighLevel's Workflow engine. HighLevel Workflows are built around CRM events (contact created, Opportunity stage changed, tag added) and are configured from scratch in the HighLevel interface. FlitStack AI does not migrate workflow logic. We export a written reference document listing each Insight Legal workflow step, its trigger condition, and its actions so the firm's HighLevel admin can rebuild them post-migration. This is a firm-facing effort — most legal workflow rebuilds take 1–3 days per process.

Migration approach

Six steps for a successful Insight Legal Case Management to HighLevel data migration

  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. 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

Context on both ends of the pair

Insight Legal Case Management logo

Insight Legal Case Management

Source

Strengths

  • Combines case management, legal accounting, practice management, and compliance in a single integrated platform
  • Offers both cloud-hosted and on-premise deployment options for UK law firms
  • Built-in workflows for common practice areas reduce initial configuration overhead
  • SRA-compliant trust accounting with dedicated client money handling
  • Mobile apps for iOS and Android support fee-earners working outside the office

Weaknesses

  • No publicly documented API — all data extraction requires vendor-provided migration tooling or manual export
  • Pricing is opaque; firms cannot self-serve tier information and must request a quote
  • Feature depth optimized for mid-to-enterprise practices can create complexity for smaller firms
  • Alternatives like Clio and Smokeball are rated higher on G2 for ease of use in small practice contexts
  • Limited published documentation on custom field limits and schema details
HighLevel logo

HighLevel

Destination

Strengths

  • Consolidates CRM, marketing automation, email, SMS, scheduling, and funnels into one platform at a predictable flat monthly rate.
  • Supports unlimited contacts and unlimited users on all paid tiers, removing per-record billing anxiety as databases grow.
  • Offers white-label and sub-account capabilities that let agencies resell access and manage multiple client environments under one billing relationship.
  • Includes built-in review management, reputation monitoring, and AI agents as native features rather than third-party add-ons.
  • Exports Contacts and Companies via a scalable async bulk CSV system that handles multi-million-row datasets without blocking the UI.

Weaknesses

  • The breadth of features creates a steep learning curve; advanced automations and Workflow configuration require significant time investment that smaller teams may not recover.
  • The platform charges usage-based fees for telecommunications and AI features that are not included in the base subscription, leading to bill surprises.
  • Recurring user reports on Reddit and G2 describe bugs, errors, and slow support response times that disrupt live marketing and sales operations.
  • Sub-account architecture, while powerful for agencies, adds migration complexity when identifying which client data lives in which isolated environment.
  • The platform is designed for agencies and SMBs; larger enterprises requiring deep reporting, custom objects at scale, or complex role-based access may outgrow its capabilities.

Complexity grading

How hard is this migration?

Standard CRM migration. 2 of 8 objects need a mapping; the rest are 1:1.

B

Overall complexity

Standard migration

Derived from compatibility, mapping clarity, API constraints, and data volume across Insight Legal Case Management and HighLevel.

  • Object compatibility

    B

    2 of 8 objects need a mapping; the rest are 1:1.

  • Field mapping clarity

    C

    Field mapping is derived from defaults — final spec confirmed during the sample migration.

  • Timeline complexity

    B

    8-object category — typical timelines run 2–7 days end-to-end.

  • API constraints

    B

    Insight Legal Case Management: Not publicly documented.

  • Data volume sensitivity

    B

    Insight Legal Case Management doesn't expose a bulk API — REST + parallelization used for high-volume runs.

Estimator

Estimate your Insight Legal Case Management to HighLevel migration cost

Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.

Step 1

What are you migrating?

Pick a category, then your source and destination platforms.

Category

FAQ

Frequently asked questions about Insight Legal Case Management to HighLevel data migrations

Answers to the questions buyers ask most during Insight Legal Case Management to HighLevel migration scoping. Not seeing yours? Book a call.

Can't find your answer?

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 consultation

Most Insight Legal to HighLevel migrations complete in 2–5 days of clock time for under 5,000 records. Large firms with 50,000+ matters, time entries, and trust transactions typically need 2–4 weeks when accounting for SQL Server access provisioning, custom field setup in HighLevel, the test migration, and the delta-pickup window. The SQL Server credential and schema extraction phase adds 3–5 business days to the timeline compared to cloud-to-cloud migrations.

Adjacent paths

Related migrations to explore

Ready when you are

Move from Insight Legal Case Management.
Land in HighLevel, intact.

Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.

Accuracy guarantee Rollback included Quote in 1 business day