CRM migration
Field-level mapping, validation, and rollback between My Legal Software and Freshsales. We move data and schema; workflows are rebuilt natively in Freshsales.
My Legal Software
Source
Freshsales
Destination
Compatibility
12 of 12
objects map 1:1 between My Legal Software and Freshsales.
Complexity
BStandard
Timeline
48–72 hours
Overview
My Legal Software is a law-firm management platform built around matters, clients, documents, and billing timers — it has no native concept of leads, sales pipelines, or opportunity stages. Freshsales is a sales CRM organized around Leads, Contacts, Accounts, and Deals with pipeline stages, contact lifecycle stages, and built-in telephony. The fundamental migration challenge is translating My Legal Software's matter records into Freshsales Deal records while mapping client contacts to Freshsales Contact and Account objects, preserving case number and practice-area metadata in custom fields, and handling the fact that My Legal Software's billing timers, invoice history, and document repositories have no direct Freshsales equivalent. FlitStack AI maps every client record by email into a Freshsales Contact, creates a corresponding Account for the law firm or client organization, converts open and closed matters into Deals with stage and amount data, and surfaces billing history, time-tracking totals, and document links as custom fields. Legal-specific automations like conflict-check workflows, matter-opening sequences, and billing rule triggers must be rebuilt in Freshsales Workflows after migration — we provide an export of your My Legal Software workflow definitions as a rebuild reference. The migration runs via Freshsales's CSV import API with FlitStack handling the intermediate ETL layer, custom field creation, and pre- and post-migration validation.
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 My Legal Software 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.
My Legal Software
Client
Freshsales
Contact + Account
1:1My Legal Software clients map to Freshsales Contacts for individual persons and Accounts for firm or organization entities. We create the Account first, then link the Contact to it via the AccountId lookup. Clients without an organization name land as individual Contacts with no AccountId.
My Legal Software
Matter / Case
Freshsales
Deal
1:1Every open or closed matter in My Legal Software becomes a Freshsales Deal. The matter name maps to Deal Name, the case number migrates as a custom text field (Matter_Number__c), and the current status (open/closed/pending) maps to a Freshsales Deal stage via value mapping. Closed matters get a closed Deal stage; open matters use the pipeline stage closest to the matter status.
My Legal Software
Practice Area
Freshsales
Custom Field on Deal
1:1My Legal Software practice areas (Immigration, Family Law, Personal Injury, etc.) have no native Freshsales equivalent. We create a custom pick-list field called Practice_Area__c on the Deal object and map each value by name. If your Freshsales plan supports only the default stage values, we store practice area as a text custom field instead.
My Legal Software
Billing Timer / Time Entry
Freshsales
Custom Field on Deal + Custom Field on Contact
1:1Total billed hours and billable amount per matter migrate as Number fields (Total_Billed_Hours__c and Total_Billed_Amount__c) on the Deal record. Cumulative firm billing totals per client migrate as fields on the Contact record. Freshsales has no native billing engine — these fields preserve reference data for financial reconciliation inside Freshsales after go-live.
My Legal Software
Invoice / Billing Record
Freshsales
Custom Object or Custom Fields on Deal
1:1My Legal Software invoice records (invoice number, amount, date, status) have no Freshsales native equivalent. We migrate the last 24 months of invoice metadata as custom fields on the associated Deal. Older invoices are exported as a CSV and stored as a reference attachment on the Account. Firms requiring full invoice history should use Freshsales's Notes or a custom Invoice object.
My Legal Software
Calendar Event / Deadline
Freshsales
Event + Task
1:1My Legal Software court dates, filing deadlines, and appointments map to Freshsales Events with the original date, time, and description preserved. All-day events without a time map as all-day Events. Tasks (reminders, follow-ups) migrate as Freshsales Tasks with the due date and priority set from the source reminder fields.
My Legal Software
Document Link / File Attachment
Freshsales
Sales Activities / Notes
1:1My Legal Software stores documents linked to matters — PDFs, correspondence, court filings. Freshsales does not have a native document management system matching this depth. We migrate document filenames and URLs as a text list on the Deal Notes field or as Sales Activities with the filename as the subject. Actual file re-hosting must be done post-migration using Freshsales's file storage or a connected DMS.
My Legal Software
Custom Form / Intake Field
Freshsales
Custom Field on Contact or Deal
1:1My Legal Software custom intake forms generate firm-specific fields (referral source, visa type, case priority) with no standard equivalent. We create matching Freshsales custom fields on the Contact object for intake fields and on the Deal object for case-specific form data. Field type matching (text, pick-list, date, number) is enforced during schema creation.
My Legal Software
User / Attorney / Staff
Freshsales
User
1:1My Legal Software users (attorneys, paralegals, admins) map to Freshsales Users resolved by email match. Unmatched users are flagged before migration — your team either creates Freshsales accounts for them first or assigns their records to a fallback user. Owner fields on Deals resolve via the same email-to-user lookup.
My Legal Software
Client Communication / Note
Freshsales
Sales Activity + Note
1:1Notes attached to matters in My Legal Software migrate as Freshsales Notes with the original create date preserved. Phone call logs and email references migrate as Sales Activities with Type='Call' or Type='Email'. Full email body content is migrated where the My Legal Software export includes it; otherwise, a summary note is created linking back to the matter.
My Legal Software
Trust Account / Ledger Entry
Freshsales
Custom Field on Account
1:1My Legal Software trust account balances and ledger entries are legal-specific accounting records with no Freshsales equivalent. We migrate trust account balance as a Number field on the Account for reference purposes. Actual accounting must remain in a dedicated legal accounting system — Freshsales is not designed to replace trust accounting.
My Legal Software
Workflow / Conflict Check / Automation
Freshsales
Not Migrated
1:1My Legal Software conflict-check workflows, matter-opening rules, and automated billing triggers have no Freshsales equivalent. They must be rebuilt in Freshsales Workflows after migration. We export your My Legal Software workflow definitions as a structured JSON reference document for your Freshsales admin to use during the rebuild phase.
| My Legal Software | Freshsales | Compatibility | |
|---|---|---|---|
| Client | Contact + Account1:1 | Fully supported | |
| Matter / Case | Deal1:1 | Fully supported | |
| Practice Area | Custom Field on Deal1:1 | Fully supported | |
| Billing Timer / Time Entry | Custom Field on Deal + Custom Field on Contact1:1 | Fully supported | |
| Invoice / Billing Record | Custom Object or Custom Fields on Deal1:1 | Fully supported | |
| Calendar Event / Deadline | Event + Task1:1 | Fully supported | |
| Document Link / File Attachment | Sales Activities / Notes1:1 | Fully supported | |
| Custom Form / Intake Field | Custom Field on Contact or Deal1:1 | Fully supported | |
| User / Attorney / Staff | User1:1 | Fully supported | |
| Client Communication / Note | Sales Activity + Note1:1 | Fully supported | |
| Trust Account / Ledger Entry | Custom Field on Account1:1 | Fully supported | |
| Workflow / Conflict Check / Automation | Not Migrated1: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.
My Legal Software gotchas
Unexpected session timeouts cause lost unsaved work
Pricing requires sales contact and is not published
Multi-year billing and trust records may reference inactive Case IDs
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 My Legal Software data export and prepare Freshsales schema
We extract a full data export from My Legal Software — clients, matters, calendar events, notes, and custom form fields. We analyze the schema for field types, pick-list values, and relationship structures. Then we create the Freshsales custom fields, pipeline, and deal stages to match the export structure before any data is loaded. This includes naming custom fields exactly as they will appear in the CSV headers to prevent the silent-skip issue.
Match attorneys and staff to Freshsales users by email
We resolve My Legal Software users (attorneys, paralegals, admins) against Freshsales users using email as the matching key. Before matching, we normalize email addresses to lowercase and strip whitespace to prevent case‑sensitive mismatches. Any attorney without a Freshsales user account is flagged in a pre‑migration report, and any duplicate email entries are identified to avoid ambiguous resolution. Your team creates the missing Freshsales accounts or assigns those attorneys' matters to a designated fallback user before the migration run. No Deal lands without a valid OwnerId, and we verify that each assigned OwnerId corresponds to an active Freshsales user.
Run a sample migration with field-level diff on 100–500 records
We run a representative slice of your data — spanning contacts, matters, calendar events, and notes — through the full ETL pipeline and load it into a Freshsales test environment. We generate a field-level diff comparing source values against destination values, surfacing any custom field label mismatches, value-mapping gaps, or owner-resolution failures before the full run commits. You review the diff and approve or request corrections.
Execute full migration with delta-pickup window
The full migration runs in sequence: Accounts first (for organization-level records), then Contacts linked to Accounts, then Deals with owner assignment, then Events and Tasks, then Notes and Sales Activities. During the cutover window (typically 24–48 hours), we capture any records modified in My Legal Software after the initial export and apply them as a delta load. An audit log records every record created or updated. One-click rollback is available if the post-migration reconciliation identifies record count or field-value discrepancies exceeding the agreed tolerance threshold.
Post-migration reconciliation and workflow rebuild handoff
We run a record-count reconciliation across all object types and sample a field-value spot-check against the original My Legal Software export. The reconciliation generates a discrepancy report listing any missing, duplicate, or mismatched records, and we resolve these before final sign‑off. We deliver the workflow export JSON, the document-link migration manifest, and the billing-history CSV as reference artifacts stored in a secure shared folder. Your Freshsales admin uses these to rebuild conflict-check workflows, matter-opening automations, and billing sequences in Freshsales Workflows and the Quotes module.
Platform deep dives
My Legal Software
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 My Legal Software 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
My Legal Software: Not publicly documented.
Data volume sensitivity
My Legal Software 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 My Legal Software to Freshsales migration scoping. Not seeing yours? Book a call.
Walk through your My Legal Software 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 My Legal Software
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.