CRM migration

Migrate from The Case File to Freshsales

Field-level mapping, validation, and rollback between The Case File and Freshsales. We move data and schema; workflows are rebuilt natively in Freshsales.

The Case File logo

The Case File

Source

Freshsales

Destination

Freshsales logo

Compatibility

93%

14 of 15

objects map 1:1 between The Case File and Freshsales.

Complexity

BStandard

Timeline

24–48 hours

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

Teams move from The Case File to Freshsales when legal case data needs to live alongside a sales pipeline, or when case-management-only workflows need the automation breadth of a full CRM. The migration carries cases (as deals), clients (as contacts), case participants (as account-contact relationships), notes, tasks, and all custom fields into Freshsales. Workflows, document templates, and billing-rate configurations do not migrate — those are case-management-specific logic that has to be rebuilt in Freshsales's workflow builder. FlitStack extracts The Case File data via CSV export, maps every object and field, runs a test migration with field-level diff, then executes the full load with a 24–48 hour delta-pickup window for in-flight records. The destination schema — including Freshsales's custom modules, lifecycle stages, and Freddy AI scoring — is set up before data lands so the migration lands on a clean, validated structure. Additionally, FlitStack performs a pre-migration data quality check, flagging duplicate contacts, missing required fields, and inconsistent case statuses before the migration load begins. This step reduces the risk of data integrity issues after go-live and ensures your Freshsales instance starts with clean, reliable case records.

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 logo

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

Freshsales logo

Freshsales

What's pulling them in

  • Lowest barrier to entry among major CRMs — the free tier supports up to 3 users and includes core CRM functionality before committing to per-seat pricing.
  • Built-in chat, email, and phone reduce reliance on third-party integrations for basic sales communication and contact management.
  • Freddy AI contact scoring and deal insights are included on Pro plans at a lower price than comparable HubSpot tiers.
  • Kanban pipeline views across Contacts, Accounts, and Deals provide visual deal management without requiring custom configuration.
  • Integration with the broader Freshworks ecosystem (Freshdesk, Freshchat, Freshservice) reduces tool sprawl for teams already using Freshworks.

Object mapping

How The Case File objects map to Freshsales

Each row shows how a The Case File object lands in Freshsales, 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

Case

maps to

Freshsales

Deal

1:1
Fully supported

Each The Case File case becomes one Freshsales deal. Case title maps to deal name; case status values (Active, Pending, Closed, On Hold) map to Freshsales deal stage values via value-by-value mapping. Filing date and case number are preserved as custom fields on the deal record.

The Case File

Client

maps to

Freshsales

Contact

1:1
Fully supported

Client records in The Case File map to Freshsales contacts. Client name splits into first_name and last_name; email, phone, address, and company fields map directly. Clients without a firm association create standalone Freshsales contacts without an account link. If a client already exists in Freshsales, we match by email to avoid duplicate contact creation.

The Case File

Case Participant

maps to

Freshsales

Account Contact Relationship / Contact Role

many:1
Fully supported

The Case File stores attorneys, opposing counsel, experts, and witnesses as labeled participants per case. These merge into Freshsales contacts with a role label stored on the account-contact relationship. The participant type (Attorney, Expert, Witness) maps to a custom pick-list field on the relationship record.

The Case File

Client Firm

maps to

Freshsales

Account

1:1
Fully supported

When The Case File stores a client firm or company associated with a client, that firm maps to a Freshsales account. Firm name becomes account name; industry and website map directly. Unassigned clients get linked to a default 'Individual' account record.

The Case File

Time Entry

maps to

Freshsales

Task

1:1
Fully supported

Billable hours logged in The Case File become Freshsales tasks with type='Time Entry'. The task subject carries the case name and date; the time duration maps to the task's numeric duration field. Billing amount is preserved as a custom currency field on the task for invoicing continuity.

The Case File

Note

maps to

Freshsales

Note

1:1
Fully supported

Case notes in The Case File map to Freshsales notes. Original author, creation date, and parent-case reference are preserved. Notes are linked to the corresponding deal record in Freshsales so the full case narrative stays attached to the migrated deal.

The Case File

Document / Attachment

maps to

Freshsales

Files

1:1
Fully supported

Documents attached to cases (filings, correspondence, contracts) are downloaded and re-uploaded to Freshsales Files, then linked to the corresponding deal record. File size limits of 25MB per file in Freshsales apply; larger files are flagged for manual review. We also preserve the original file timestamps and metadata during re-upload to maintain audit trails.

The Case File

Custom Field (Case-level)

maps to

Freshsales

Custom Field (Deal-level)

1:1
Fully supported

The Case File custom fields per case (e.g., jurisdiction, case type, judge, court location, insurance carrier) require Freshsales custom fields on the deal object. We create each custom field in Freshsales before migration, matching the field type (text, pick-list, date, currency) from The Case File's field definition.

The Case File

Attorney / User

maps to

Freshsales

User

1:1
Fully supported

The Case File attorney and staff records map to Freshsales users resolved by email match. Unmatched attorneys are flagged before migration — your team either creates their Freshsales user account first or assigns their case records to a fallback owner during migration.

The Case File

Billing Record

maps to

Freshsales

Custom Field / Note on Deal

1:1
Fully supported

Billing totals, invoice numbers, and payment status stored in The Case File preserve as custom fields and notes on the corresponding Freshsales deal. Freshsales does not have native legal billing; invoice tracking is handled via custom fields or the Freshsales product catalog for fee-item tracking.

The Case File

Case Type / Category

maps to

Freshsales

Deal Stage / Custom Pick-list

1:1
Fully supported

Case types in The Case File (e.g., Contract Dispute, Personal Injury, Family Law, Criminal Defense) map to a custom pick-list field on the Freshsales deal. Each case type can also route to a separate Freshsales pipeline if your team uses different stage sequences per practice area.

The Case File

Workflow / Automation

maps to

Freshsales

Freshsales Workflow

1:1
Fully supported

Case management workflows (e.g., 'notify attorney when case status changes to Pending') do not have a Freshsales equivalent. We export the workflow definitions as a reference document for your Freshsales admin to rebuild using Freshsales's workflow builder. The export includes trigger conditions, action steps, and any conditional logic to assist in accurate recreation.

The Case File

Calendar Event

maps to

Freshsales

Event

1:1
Fully supported

Court dates, filing deadlines, and client meetings from The Case File calendar map to Freshsales events with original start/end times and attendees preserved. Events are linked to the corresponding deal and contact records. We also retain the event description and any recurrence patterns to ensure continuity.

The Case File

Lead

maps to

Freshsales

Lead

1:1
Fully supported

Prospective client leads stored in The Case File migrate directly to Freshsales leads. Lead status, source, and assigned attorney map to Freshsales lead status, lead source, and owner respectively. If a lead already exists in Freshsales, we match by email address to prevent duplication and preserve historical activity.

The Case File

Custom Object

maps to

Freshsales

Custom Module (Enterprise) / Custom Field

1:1
Fully supported

If The Case File stores custom entities (e.g., Insurance Policy, Witness Record, Evidence Item), those map to Freshsales custom modules on Enterprise plans or custom fields on the deal or contact object on lower plans. The mapping approach is determined during the schema audit phase.

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 logo

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

Freshsales logo

Freshsales gotchas

Medium

Freddy AI is Pro-tier only despite heavy marketing

High

Post-migration emails and sequences are disabled

Medium

Bot session credits are a one-time 500-session allocation

Medium

Phone credits charged per minute with no cap

Low

File storage limits scale with plan tier

Pair-specific challenges

  • Case status value mapping requires explicit value-by-value setup

    The Case File stores case statuses like Active, Pending, Closed, On Hold, and Dismissed as free-form or semi-structured fields. Freshsales deal stages are pick-list values scoped per pipeline. Migrating case statuses without explicit value mapping results in all cases landing in the same stage regardless of their original status. FlitStack builds a value-map table before migration, mapping each The Case File status to the correct Freshsales stage name per pipeline. Any unmapped values are flagged for your admin to decide before the migration commits.

  • Case numbers require Freshsales custom fields — they are not native identifiers

    Freshsales deals do not have a native case number field. The Case File's case_number field does not map to any built-in Freshsales field and would be silently dropped during a generic import. We create a case_number custom text field on every deal record during schema setup, preserving the original case identifier for reference, reporting, and cross-referencing with The Case File exports. This field must exist in Freshsales before the migration load runs.

  • Documents cannot be imported directly — they require re-upload to Freshsales Files

    Freshsales does not accept binary file imports via its standard import wizard. Case documents (filings, correspondence, contracts, evidence) attached to The Case File records must be downloaded, re-uploaded to Freshsales Files, and manually linked to the corresponding deal record. We automate the download-and-re-upload pipeline for files under 25MB; files exceeding Freshsales's 25MB per-file limit are flagged for your team to handle separately. This is a known Freshsales platform constraint for all inbound document migrations.

  • Workflows and automations in The Case File do not transfer

    The Case File case-management workflows (e.g., 'notify attorney when case status changes to Pending') are case-event-triggered automations with no equivalent construct in Freshsales. Freshsales workflows are triggered by lead, contact, or deal events — there is no case-event trigger type. FlitStack exports your The Case File workflow definitions as a written reference document so your Freshsales admin can rebuild them using Freshsales's workflow builder. Billing rate configurations and time-tracking rules similarly require manual setup in Freshsales.

  • No official API export in The Case File — CSV export requires pre-migration preparation

    Unlike Freshsales, which has a well-documented REST API and native export tools, The Case File does not expose a public API for automated data extraction. Data is exported as CSV via The Case File's built-in export function. Multi-table exports (cases, clients, participants, notes, documents) must be requested separately and may require field alignment before FlitStack can map them. We provide a pre-migration checklist specifying which exports to run, which fields to include, and how to format the CSV headers for our import connector.

Migration approach

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

  1. Audit The Case File export and set up Freshsales schema

    We audit your The Case File CSV exports — cases, clients, participants, notes, tasks, and custom fields. We count records, identify multi-value fields and case-participant roles, and produce a Freshsales schema setup plan: custom fields to create on deals and contacts, deal stage names per pipeline, and custom pick-list values for case types and jurisdictions. Your Freshsales admin (or our team) creates the schema before the migration load runs so all custom fields are ready for inbound data.

  2. Resolve user and attorney records by email

    The Case File attorney and staff records are matched to Freshsales users by email address. Any attorney with no matching Freshworks account is flagged before migration — your team either creates their Freshsales user account first or assigns their records to a designated fallback owner during the migration. No case or client record lands in Freshsales without a resolved owner.

  3. Migrate accounts, contacts, and leads before deals

    Freshsales requires account records to exist before contact and lead records can link via the account_id lookup field. We sequence the migration so firm accounts load first, then contacts and leads, then cases as deals with stage mapping and case-number custom fields populated. Participant roles on cases merge into account-contact relationship records during the deal migration step. This ordering also guarantees that firm details such as industry or office location propagate to contacts, minimizing later corrections, and lets us validate referential integrity before any deal record is created.

  4. Run a sample migration with field-level diff

    A representative slice — typically 100–200 records spanning cases, clients, participants, and time entries — migrates first. We generate a field-level diff report comparing source values against destination values so you can verify case status mapping, custom field population, attorney owner resolution, and billing amount preservation before the full run commits. Your sign-off on the sample report gates the full migration.

  5. Full migration with delta-pickup window and audit log

    The full migration runs against Freshsales. A delta-pickup window (24–48 hours) captures any records modified in The Case File during the cutover period so your Freshsales instance reflects the final state at go-live. We generate an audit log mapping every The Case File record ID to its Freshsales ID for traceability. One-click rollback is available if record counts or field integrity checks fail post-migration.

Platform deep dives

Context on both ends of the pair

The Case File logo

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.
Freshsales logo

Freshsales

Destination

Strengths

  • Generous free tier for small teams with core CRM functionality without per-seat costs.
  • All-in-one sales CRM with built-in telephony, chat, and email reducing third-party tool dependency.
  • Freddy AI contact scoring and deal predictions available on Pro tier.
  • Multiple pipeline views with Kanban and list options across all plans.

Weaknesses

  • Reports lack depth compared to competitors like HubSpot, with limited customization options.
  • Integration setup is poorly documented with no clear guides for connecting third-party tools.
  • AI features gated behind $39/user/month Pro tier despite marketing emphasis on Freddy AI.
  • Bot sessions limited to 500 one-time allocation with no monthly refresh.

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 The Case File and Freshsales.

  • 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

    The Case File: Not publicly documented.

  • Data volume sensitivity

    B

    The Case File doesn't expose a bulk API — REST + parallelization used for high-volume runs.

Estimator

Estimate your The Case File to Freshsales 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 The Case File to Freshsales data migrations

Answers to the questions buyers ask most during The Case File to Freshsales migration scoping. Not seeing yours? Book a call.

Can't find your answer?

Walk through your The Case File to Freshsales migration with a real engineer — 30 minutes, free, written quote within 24 hours.

Book a free 30 minute consultation

Most The Case File to Freshsales migrations complete in 24–48 hours of clock time for under 5,000 records. Larger setups with 50,000+ records or complex multi-pipeline setups extend to 5–7 days. The longest planning step is building the case-status-to-deal-stage value map and creating Freshsales custom fields for case-type, jurisdiction, and billing metadata before the migration load runs. During the planning phase we also verify data completeness and coordinate with your team to ensure all necessary permissions and API access are in place.

Adjacent paths

Related migrations to explore

Ready when you are

Move from The Case File.
Land in Freshsales, 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