How long does a The Case File to HighLevel migration take?

For a standard migration with under 10,000 records (contacts, companies, cases, and tasks), FlitStack completes the full run within 24 to 72 hours. Larger setups with 50,000+ records or multiple case-type pipelines extend to 5 to 10 days, primarily because HighLevel's API rate limits (200,000 requests per day per sub-account) require staged batch processing. The pre-migration schema setup and sample diff phase typically adds 2 to 3 days of planning time before the first record moves.

Will my The Case File automation rules migrate to HighLevel Workflows?

No. The Case File automation rules — case-status-change triggers, deadline alerts, staff assignment notifications — run on The Case File's own rule engine and have no export mechanism. They cannot be transferred directly to HighLevel's Workflow Builder because the trigger events are entirely different platforms. FlitStack delivers a Workflow Rebuild Reference export listing every rule as a description your team can use to re-implement logic in HighLevel's visual Workflow Builder. This is always a manual rebuild step.

What happens to The Case File case status values in HighLevel?

The Case File matter status (Active, Pending, Closed, etc.) maps to HighLevel Pipeline stages on the Opportunity record. Each status value maps to a corresponding stage name in your target Pipeline. If your source uses more than one case taxonomy — for example, different statuses for litigation vs. transactional matters — those map to separate HighLevel Pipelines. We create the Pipeline and stage structure in HighLevel before importing so the stage mapping has valid targets. Stage probabilities and forecast category are applied from the HighLevel side after import.

Can I migrate custom fields from The Case File to HighLevel?

Yes. Any custom fields on The Case File Contact or Case objects — such as court jurisdiction, opposing counsel, practice area, or billing arrangement — are migrated as Custom Fields on the HighLevel Contact or Opportunity object. FlitStack creates the fields in HighLevel (with matching field types: text, number, date, or pick-list) before importing the data. Pick-list values are recreated as field options so they remain usable for HighLevel Workflow triggers and reporting filters.

What happens to court dates and scheduled hearings during the migration?

Court dates, filing deadlines, and scheduled hearings stored in The Case File are exported as dated Notes on each relevant Opportunity record in HighLevel, with the event type noted in the note body. HighLevel's Calendar feature is separate from the CRM object model, so calendar events do not automatically link to Opportunities. Your team recreates the most time-sensitive calendar events as HighLevel Calendar events, which can then trigger workflow reminders. FlitStack provides a sorted list of all dated events to prioritize this step.

Does the migration affect my The Case File account during cutover?

No. FlitStack uses scoped read access on The Case File — your team continues working in The Case File throughout the migration window. A delta-pickup window of 24 to 48 hours runs after the main batch completes, capturing any records created or modified during the cutover period. Records modified after the delta window closes are not captured and would need a separate small migration if needed. No writes are made to The Case File during the entire process.

What happens to contacts with multiple open cases in The Case File?

The Case File allows a single contact to be associated with multiple open matters. In HighLevel, each Opportunity (case) links to a primary Contact via the built-in contactId field. For contacts with multiple open cases, we create one Opportunity per matter — each linked to the same Contact record. Tags are applied to the Contact for reporting visibility (e.g., 'Multi-Matter Client'). This preserves the full relationship history without data duplication.

The Case File to HighLevel Migration — Field-Level Mapping & Rollback

Overview

What this migration involves

The Case File is a legal-case-management platform centered on Contacts, Cases (matters), Documents, and Notes — with role-based assignments and court-date scheduling. HighLevel is an all-in-one CRM with Contacts, Companies, Opportunities (pipelines), Tasks, and a Workflows automation engine. The two platforms share the Contact and Company object but differ fundamentally in how they model matters and automation: The Case File treats case status as a standalone entity; HighLevel models deal progression inside Opportunities with stage-keyed pipelines. FlitStack AI migrates every Contact, Company, Task, Note, and tagged custom field through HighLevel's Contacts API and bulk-import endpoints. We surface case-record linkages that require a custom field or tag reconstruction in HighLevel's workflow model. Automations, document templates, and court-calendar integrations do not migrate — those require manual rebuild inside HighLevel's Workflow Builder and Calendar tools. FlitStack sequences the migration so foreign-key relationships resolve before Opportunity records land.

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

The Case File

What's pushing teams away

Document management limitations make handling extremely large or complex litigation document sets difficult.
The platform lacks depth for multi-party or high-volume matters that require advanced workflow automation.
Reporting and analytics are basic compared to purpose-built litigation analytics platforms.
Limited API documentation and third-party integration ecosystem makes automation difficult.
Some firms outgrow the platform as they scale and need more robust matter-level permissions controls.

Choosing

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 The Case File objects map to HighLevel

Each row shows how a The Case File 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.

The Case File

Contact

maps to

HighLevel

Contact

1:1

Fully supported

Every The Case File contact maps directly to a HighLevel Contact. We preserve full name, email, phone, address, and all custom contact fields. Source owner resolved by email match against HighLevel users.

The Case File

Company

maps to

HighLevel

Company

1:1

Fully supported

The Case File firm or client organization maps to a HighLevel Company record. Company name, address, and industry fields map directly. Multi-contact firms collapse to one primary Company with secondary contact links.

The Case File

Case / Matter

maps to

HighLevel

Opportunity (Pipeline)

1:1

Fully supported

Each The Case File matter becomes a HighLevel Opportunity inside a designated Pipeline. The matter's case number and description map to Opportunity name and notes fields. Case status (Open / Closed / Pending) maps to a pipeline stage via value mapping against your target Pipeline's stage list.

The Case File

Case Status

maps to

HighLevel

Pipeline Stage

1:1

Fully supported

The Case File status pick-list values (Active, Pending, Closed Won, etc.) map one-to-one against the corresponding HighLevel Pipeline stage names. If your source has more statuses than the target Pipeline has stages, we create additional stages or collapse values per your instruction.

The Case File

Document / Attachment

maps to

HighLevel

Contact File / Opportunity File

1:1

Fully supported

File attachments linked to The Case File contacts or matters are downloaded and re-uploaded to the corresponding HighLevel Contact or Opportunity as Files. File size and format compatibility checked against HighLevel's 25 MB per-file limit.

The Case File

Note / Case Note

maps to

HighLevel

Note

1:1

Fully supported

Case notes, internal memos, and time-stamped entries migrate as HighLevel Notes attached to the relevant Contact or Opportunity record. Original author preserved as note owner.

The Case File

Task / To-Do

maps to

HighLevel

Task

1:1

Fully supported

The Case File task list entries and deadline assignments map to HighLevel Tasks. Due dates, task body, and assigned user (matched by email) all transfer. Open/closed status reflected in HighLevel task completion flag.

The Case File

Custom Field (Contact)

maps to

HighLevel

Custom Contact Field

1:1

Fully supported

Any custom properties on The Case File Contact object that have no direct HighLevel equivalent are created as Custom Fields on the HighLevel Contact object before import. Field data type (text, number, pick-list, date) is preserved.

The Case File

Custom Field (Case)

maps to

HighLevel

Custom Opportunity Field

1:1

Fully supported

Custom case-level fields (court jurisdiction, opposing counsel, filing deadline, etc.) are created as Custom Fields on the HighLevel Opportunity object and populated per record. Pick-list values are recreated as field options.

The Case File

Role / User Assignment

maps to

HighLevel

Contact / Opportunity Owner

1:1

Fully supported

The Case File staff assignments on a matter map to the Opportunity Owner field in HighLevel, resolved by email match. If the assignee has no HighLevel user account, they are flagged for team invitation before migration.

The Case File

Calendar / Court Date

maps to

HighLevel

HighLevel Calendar Event

1:1

Fully supported

Court dates and scheduled hearings in The Case File have no direct HighLevel equivalent outside of the Calendar feature. We export them as Notes on the relevant Opportunity and flag them for manual calendar event creation in HighLevel.

The Case File

Tag / Category

maps to

HighLevel

Tag

1:1

Fully supported

Contact and case category tags in The Case File map directly to HighLevel Tags on the Contact record. Tags are preserved for segmentation and workflow triggers.

The Case File	HighLevel	Compatibility
Contact	Contact1:1	Fully supported
Company	Company1:1	Fully supported
Case / Matter	Opportunity (Pipeline)1:1	Fully supported
Case Status	Pipeline Stage1:1	Fully supported
Document / Attachment	Contact File / Opportunity File1:1	Fully supported
Note / Case Note	Note1:1	Fully supported
Task / To-Do	Task1:1	Fully supported
Custom Field (Contact)	Custom Contact Field1:1	Fully supported
Custom Field (Case)	Custom Opportunity Field1:1	Fully supported
Role / User Assignment	Contact / Opportunity Owner1:1	Fully supported
Calendar / Court Date	HighLevel Calendar Event1:1	Fully supported
Tag / Category	Tag1:1	Fully supported

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.

The Case File gotchas

High

No publicly documented API for programmatic data extraction

High

Trust account ledger balances require manual verification

Medium

Custom fields lack a documented export schema

Medium

Document folder structure does not export flatly

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

The Case File gotchas		HighLevel gotchas
Severity	Issue	Severity	Issue
High	No publicly documented API for programmatic data extraction	High	Sub-account architecture creates isolated data silos per client
High	Trust account ledger balances require manual verification	High	Usage-based telecom and AI costs are not in the subscription price
Medium	Custom fields lack a documented export schema	Medium	Workflows have no native equivalent in most destination CRMs
Medium	Document folder structure does not export flatly	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

Case status maps to a single HighLevel Pipeline stage — not a multi-pipeline structure

The Case File stores a flat status value (Open, Pending, Closed) per matter. HighLevel Pipelines are multi-stage by design, and each Pipeline can have its own stage sequence. If your source setup uses more than one case-status taxonomy — for example, separate status for litigation vs. transactional matters — those need to map to separate HighLevel Pipelines. We create the Pipeline and stage structure in HighLevel before the import so the stage mapping has a valid target. This is a schema-first step that your team approves before data lands.
Court dates and calendar events have no direct HighLevel equivalent — manual recreation required

The Case File includes scheduled hearings and court-date fields. HighLevel's Calendar feature stores events but does not automatically attach them to an Opportunity as a first-class relationship. FlitStack exports court dates as dated Notes on each Opportunity and flags them for manual calendar event creation. If your team relies on deadline reminders linked to case records, those reminders need to be rebuilt as HighLevel Workflow triggers after migration. This is disclosed during the pre-migration planning call so your team can prioritize the highest-impact calendar events for manual recreation.
HighLevel API rate limits require batched migration — large case volumes need scheduling

HighLevel enforces per-sub-account API rate limits of 200,000 requests per day and 100 requests per 10 seconds on API 2.0. The Case File exports with more than 50,000 contact records require staged batch processing across multiple days. FlitStack manages back-off and retry logic, distributes load across off-peak hours, and reports throughput progress in the migration dashboard. We surface the estimated run window before committing so your team can plan the cutover date accordingly.
Automations and workflow triggers do not migrate — The Case File logic cannot transfer to HighLevel Workflows

The Case File automation rules (case-status-change triggers, assignment notifications, deadline alerts) run on The Case File's own rule engine and cannot be exported as a configuration file. They have no direct equivalent in HighLevel's Workflow Builder because the trigger events differ entirely — HighLevel triggers on contact actions, form submissions, pipeline stage changes, and calendar events. FlitStack delivers a Workflow Rebuild Reference export listing every The Case File automation rule as a description your team can use to re-implement logic in HighLevel's visual Workflow Builder.

Migration approach

Six steps for a successful The Case File to HighLevel data migration

Audit The Case File data and design the HighLevel target schema

FlitStack connects to The Case File via scoped API read access (or your exported CSV/backup) and catalogs every object: contact count, company count, case record count, custom field names and types, and any existing document or note attachments. We then map out the HighLevel target: which Pipeline each case type goes into, what stages exist per Pipeline, and which custom fields need to be created on the Contact and Opportunity objects before data lands. Your team approves the schema plan before we touch any data.
Create HighLevel custom fields and pipeline structure

Before importing records, FlitStack creates the custom fields on Contact and Opportunity objects via the HighLevel API. We create one Pipeline per source case type and configure the stage sequence to match the source status taxonomy. If your The Case File setup uses multiple staff roles or case-type-specific fields, we set up those configurations in the HighLevel sub-account so field-level mapping has valid targets.
Run a sample migration with field-level diff on 50–200 records

A representative slice of contacts, companies, case records, and tasks migrates into the HighLevel sub-account first. We generate a field-level diff showing every source field and its mapped destination value. You verify that case numbers, status-to-stage mapping, custom fields, and owner resolution all look correct. We adjust the mapping until the diff passes your sign-off before the full migration runs.
Execute full migration with delta-pickup window and audit log

All records move in a sequenced run: Companies first (HighLevel requires companies before contacts), then Contacts, then Opportunities with stage mapping and owner resolution. A delta-pickup window of 24–48 hours runs after the main batch, capturing any records modified in The Case File during cutover. Every record operation is written to an audit log. If reconciliation fails, one-click rollback reverts the sub-account to its pre-migration state.
Deliver Workflow Rebuild Reference and post-migration reconciliation

FlitStack delivers a Workflow Rebuild Reference document listing every The Case File automation rule, trigger condition, and action, formatted as a rebuild guide for HighLevel's Workflow Builder. We run a final record-count reconciliation and spot-check 20 records against the source to confirm field-level accuracy. Your team then has the runway to rebuild automations, create calendar events from the exported court-date notes, and validate pipeline reporting in HighLevel.

Platform deep dives

Context on both ends of the pair

The Case File

Source

Strengths

Cloud-native platform with no on-premises infrastructure requirements for the standard edition.
Native Full Data Backup tool and export spreadsheets provide a structured data extraction path.
Integrated client intake, case management, billing, and time tracking in one platform.
Good mobile app availability for attorneys working outside the office.
Dedicated Data Migration help center collection suggests some investment in migration tooling.

Weaknesses

Limited public API documentation makes programmatic migration and integration work harder to plan.
Document management is basic; large-scale litigation document sets are difficult to organize within the platform.
Reporting and analytics capabilities are shallow compared to specialized litigation software.
Third-party integrations ecosystem is smaller than enterprise-class legal CRMs.
Custom field definitions must be reviewed manually during migration scoping as no exportable schema is documented.

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.

	The Case File Source	HighLevel Destination
Strengths	Cloud-native platform with no on-premises infrastructure requirements for the standard edition. Native Full Data Backup tool and export spreadsheets provide a structured data extraction path. Integrated client intake, case management, billing, and time tracking in one platform. Good mobile app availability for attorneys working outside the office. Dedicated Data Migration help center collection suggests some investment in migration tooling.	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	Limited public API documentation makes programmatic migration and integration work harder to plan. Document management is basic; large-scale litigation document sets are difficult to organize within the platform. Reporting and analytics capabilities are shallow compared to specialized litigation software. Third-party integrations ecosystem is smaller than enterprise-class legal CRMs. Custom field definitions must be reviewed manually during migration scoping as no exportable schema is documented.	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.

POPULAR PLATFORMS

POPULAR MIGRATIONS

POPULAR PLATFORMS

POPULAR MIGRATIONS

POPULAR PLATFORMS

POPULAR MIGRATIONS

POPULAR PLATFORMS

POPULAR MIGRATIONS

POPULAR PLATFORMS

POPULAR MIGRATIONS

Migrate from The Case File to HighLevel

What this migration involves

Field-level fidelity

Schema-aware mapping

Relationships preserved

Full activity history

Attachments & notes

Two sides of the same decision

The Case File

HighLevel

How The Case File objects map to HighLevel

What specifically takes care here

Six steps for a successful The Case File to HighLevel data migration

Context on both ends of the pair

How hard is this migration?

Estimate your The Case File to HighLevel migration cost

What are you migrating?

Frequently asked questions about The Case File to HighLevel data migrations

Can't find your answer?

Related migrations to explore

Move from The Case File.
Land in HighLevel, intact.

Migrate from The Case File to HighLevel

What this migration involves

Field-level fidelity

Schema-aware mapping

Relationships preserved

Full activity history

Attachments & notes

Two sides of the same decision

The Case File

HighLevel

How The Case File objects map to HighLevel

What specifically takes care here

Six steps for a successful The Case File to HighLevel data migration

Context on both ends of the pair

How hard is this migration?

Estimate your The Case File to HighLevel migration cost

Frequently asked questions about The Case File to HighLevel data migrations

Can't find your answer?

How long does a The Case File to HighLevel migration take?

Will my The Case File automation rules migrate to HighLevel Workflows?

What happens to The Case File case status values in HighLevel?

Can I migrate custom fields from The Case File to HighLevel?

What happens to court dates and scheduled hearings during the migration?

Does the migration affect my The Case File account during cutover?

What happens to contacts with multiple open cases in The Case File?

Related migrations to explore

Move from The Case File. Land in HighLevel, intact.

Move from The Case File.
Land in HighLevel, intact.