CRM migration
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
Source
Freshsales
Destination
Compatibility
14 of 15
objects map 1:1 between The Case File and Freshsales.
Complexity
BStandard
Timeline
24–48 hours
Overview
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.
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 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
Freshsales
Deal
1:1Each 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
Freshsales
Contact
1:1Client 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
Freshsales
Account Contact Relationship / Contact Role
many:1The 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
Freshsales
Account
1:1When 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
Freshsales
Task
1:1Billable 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
Freshsales
Note
1:1Case 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
Freshsales
Files
1:1Documents 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)
Freshsales
Custom Field (Deal-level)
1:1The 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
Freshsales
User
1:1The 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
Freshsales
Custom Field / Note on Deal
1:1Billing 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
Freshsales
Deal Stage / Custom Pick-list
1:1Case 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
Freshsales
Freshsales Workflow
1:1Case 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
Freshsales
Event
1:1Court 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
Freshsales
Lead
1:1Prospective 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
Freshsales
Custom Module (Enterprise) / Custom Field
1:1If 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.
| The Case File | Freshsales | Compatibility | |
|---|---|---|---|
| Case | Deal1:1 | Fully supported | |
| Client | Contact1:1 | Fully supported | |
| Case Participant | Account Contact Relationship / Contact Rolemany:1 | Fully supported | |
| Client Firm | Account1:1 | Fully supported | |
| Time Entry | Task1:1 | Fully supported | |
| Note | Note1:1 | Fully supported | |
| Document / Attachment | Files1:1 | Fully supported | |
| Custom Field (Case-level) | Custom Field (Deal-level)1:1 | Fully supported | |
| Attorney / User | User1:1 | Fully supported | |
| Billing Record | Custom Field / Note on Deal1:1 | Fully supported | |
| Case Type / Category | Deal Stage / Custom Pick-list1:1 | Fully supported | |
| Workflow / Automation | Freshsales Workflow1:1 | Fully supported | |
| Calendar Event | Event1:1 | Fully supported | |
| Lead | Lead1:1 | Fully supported | |
| Custom Object | Custom Module (Enterprise) / Custom Field1: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.
The Case File gotchas
No publicly documented API for programmatic data extraction
Trust account ledger balances require manual verification
Custom fields lack a documented export schema
Document folder structure does not export flatly
Freshsales gotchas
Freddy AI is Pro-tier only despite heavy marketing
Post-migration emails and sequences are disabled
Bot session credits are a one-time 500-session allocation
Phone credits charged per minute with no cap
File storage limits scale with plan tier
Pair-specific challenges
Migration approach
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.
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.
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.
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.
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
The Case File
Source
Strengths
Weaknesses
Freshsales
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 The Case File and Freshsales.
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
The Case File: Not publicly documented.
Data volume sensitivity
The Case File 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 The Case File to Freshsales migration scoping. Not seeing yours? Book a call.
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 consultationAdjacent paths
Other ways to leave The Case File
Other ways to arrive at Freshsales
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.