CRM migration
Field-level mapping, validation, and rollback between The Attorney Case File and Freshsales. We move data and schema; workflows are rebuilt natively in Freshsales.
The Attorney Case File
Source
Freshsales
Destination
Compatibility
9 of 10
objects map 1:1 between The Attorney Case File and Freshsales.
Complexity
BStandard
Timeline
48–72 hours
Overview
The Attorney Case File organizes law firm data around a client-matter model — clients, matters, contacts, documents, time entries, and legal-specific custom fields like practice area and case type. Freshsales uses a leads-contacts-accounts-deals model native to sales CRMs, with standard objects for leads, contacts, accounts, and deals plus custom fields on each. The migration maps every client contact to a Freshsales Contact (linked to an Account), every matter to a Freshsales Deal with legal-specific custom fields (Matter_Number__c, Practice_Area__c, Case_Type__c, Referral_Source__c), and time entries to custom numeric fields on the deal. Document handling requires a separate file-storage strategy since Freshsales stores attachments differently than a legal DMS. FlitStack AI runs the migration against Freshsales' REST API for records and uses bulk-mode where record volumes justify it. Client-matter hierarchy resolves through Freshsales' contact-account relationships. Any case-status automations or matter-alert workflows in The Attorney Case File do not migrate — they must be rebuilt in Freshsales Workflows after go-live. The delta-pickup window (24–48 hours) captures any new matters or client contacts created in The Attorney Case File during the cutover window so Freshsales reflects the final state at migration completion.
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 Attorney 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 Attorney Case File
Client
Freshsales
Account + Contact
many:1The Attorney Case File clients (individuals or organizations) split into Freshsales Account (for organizations) and Contact. Individual clients without a firm name map to a Contact with the individual as the account name. Each client record carries forward with original create date preserved in Source_System_Created_Date__c.
The Attorney Case File
Matter (Case)
Freshsales
Deal
1:1Matters migrate as Freshsales Deals. The matter name becomes the deal name. Matter number, case type, practice area, case status, and referral source map to Freshsales custom fields on the deal. Close date maps to Freshsales Close Date only for closed matters — open matters leave Close Date blank. Owner resolved by attorney email match against Freshsales users.
The Attorney Case File
Matter Contact (Party to Case)
Freshsales
Contact + Opportunity Contact Role
1:1Parties linked to a matter in The Attorney Case File become Freshsales Contacts associated with the matter-as-deal via Opportunity Contact Roles. Opposing counsel, co-counsel, and court contacts get role labels matching the association. Contacts without an email are flagged for manual review before migration commits.
The Attorney Case File
Time Entry / Billable Hours
Freshsales
Custom Fields on Deal
1:1The Attorney Case File time entries map to custom numeric fields on the corresponding Freshsales Deal (Total_Billable_Hours__c, Total_Billed_Amount__c, Billing_Rate__c). Time entry line items are rolled up to the matter-level deal record. Trust account balances are not native to Freshsales and require a separate financial tracking tool post-migration.
The Attorney Case File
Document / File Attachment
Freshsales
Freshsales Files
1:1Documents attached to matters download from The Attorney Case File and re-upload to Freshsales Files, linked to the corresponding deal record. File size limits from Freshsales apply (25MB per file). Inline documents in case notes are extracted and re-hosted. Document version history is preserved as separate file versions where the source supports it.
The Attorney Case File
Note / Case Note
Freshsales
Note
1:1Case notes migrate as Freshsales Notes linked to the corresponding deal. Original author and timestamp are preserved, and the note body is imported into the Freshsales Note record. Rich-text formatting in source notes is retained where the export format supports it; plain-text fallback applies otherwise. If a case note contains inline references to documents or contacts, those references are mapped to Freshsales file links or contact lookups as applicable.
The Attorney Case File
Task / Calendar Event
Freshsales
Task / Event
1:1Case-related tasks (filing deadlines, court dates, client meetings) migrate as Freshsales Tasks and Events. Court hearing dates map to Freshsales Events with start/end times and the case as the parent record. Deadline tasks map to Tasks with due dates and the matter as the related-to object. Owner resolved by attorney email match.
The Attorney Case File
Custom Case Field (Practice Area, Judge, Court, Filing Deadline)
Freshsales
Custom Field on Deal
1:1Every custom field in The Attorney Case File that has no direct Freshsales equivalent becomes a custom field on the Deal object. Practice_Area__c, Judge__c, Court__c, Filing_Deadline__c, Opposing_Counsel__c, and Referral_Source__c are created in Freshsales Admin before migration. Dropdown values from the source are mapped value-by-value to the destination pick-list.
The Attorney Case File
Lead / Prospective Client
Freshsales
Lead
1:1Prospective client records in The Attorney Case File that have not yet opened a matter migrate as Freshsales Leads. Lead status, source, and any scoring data from The Attorney Case File map to Freshsales Lead custom fields. Leads convert to Contacts and Accounts when a matter is formally opened.
The Attorney Case File
Client Intake Form Data
Freshsales
Contact Custom Fields
1:1Intake form fields from The Attorney Case File (referral source, initial matter type, client classification) migrate as custom fields on the Freshsales Contact record. These are preserved for reporting continuity even if the intake workflow is rebuilt in Freshsales Forms post-migration.
| The Attorney Case File | Freshsales | Compatibility | |
|---|---|---|---|
| Client | Account + Contactmany:1 | Fully supported | |
| Matter (Case) | Deal1:1 | Fully supported | |
| Matter Contact (Party to Case) | Contact + Opportunity Contact Role1:1 | Fully supported | |
| Time Entry / Billable Hours | Custom Fields on Deal1:1 | Fully supported | |
| Document / File Attachment | Freshsales Files1:1 | Fully supported | |
| Note / Case Note | Note1:1 | Fully supported | |
| Task / Calendar Event | Task / Event1:1 | Fully supported | |
| Custom Case Field (Practice Area, Judge, Court, Filing Deadline) | Custom Field on Deal1:1 | Fully supported | |
| Lead / Prospective Client | Lead1:1 | Fully supported | |
| Client Intake Form Data | Contact Custom Fields1: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 Attorney Case File gotchas
No public API — extraction requires vendor coordination
Export envelope is limited to workbook-level records
Trust accounting data is outside the export scope
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
Confirm The Attorney Case File export mechanism
FlitStack AI assesses the available data export method — API access, CSV export, or manual spreadsheet extraction — during the discovery call. If only manual exports are available, we provide a structured export template that maps every The Attorney Case File field to a CSV column so nothing is missed. We validate the export completeness before building the migration pipeline.
Design Freshsales custom field schema
We audit every custom field in The Attorney Case File that has no direct Freshsales equivalent and deliver a schema setup plan: field names, data types, pick-list values, and which object each field belongs to (Deal, Contact, or Account). The Freshsales admin creates these fields in Admin settings before we run any migration load. We validate that the schema is complete and matches the export field list before proceeding.
Run sample migration with field-level diff
A representative slice of records — typically 50–200 clients, matters, contacts, and a sample of documents — migrates first. We generate a field-level diff report that compares each source field value against the corresponding Freshsales destination field, highlighting any discrepancies in mapping such as matter-number, practice-area pick-list, client-to-contact resolution, and attorney-to-owner matching. This allows the firm to review and confirm the correctness of all custom field transformations before the full migration run commits.
Execute full migration with delta-pickup window
The full migration runs against Freshsales via the API (or bulk import where record volumes justify batch mode). A delta-pickup window of 24–48 hours captures any clients or matters added to The Attorney Case File during the cutover period. Audit logs record every operation (source ID, target ID, timestamp, user). One-click rollback is available if the reconciliation report shows unexpected discrepancies.
Post-migration reconciliation and document re-upload
FlitStack AI delivers a record-count reconciliation report comparing total clients, matters, contacts, time entries, and documents between source and destination. Discrepancies are investigated and corrected. We provide a document batch-upload script and linking guide so the firm can complete file re-upload to Freshsales Files with the correct deal associations. Any automations or matter-status-change triggers exported from The Attorney Case File are provided as rebuild reference documentation for the Freshsales admin.
Platform deep dives
The Attorney 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 Attorney 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 Attorney Case File: Not publicly documented.
Data volume sensitivity
The Attorney 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 Attorney Case File to Freshsales migration scoping. Not seeing yours? Book a call.
Walk through your The Attorney 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 Attorney 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.
