CRM migration

Migrate from My Legal Software to Freshsales

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 logo

My Legal Software

Source

Freshsales

Destination

Freshsales logo

Compatibility

100%

12 of 12

objects map 1:1 between My Legal Software and Freshsales.

Complexity

BStandard

Timeline

48–72 hours

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

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.

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

My Legal Software logo

My Legal Software

What's pushing teams away

  • Session timeouts occur without warning during active use, causing attorneys to lose unsaved case notes and form entries mid-session, which reviewers flag as a recurring frustration.
  • Pricing is not published on the website and requires contacting sales for a custom quote, making it difficult to assess total cost of ownership during the migration planning phase.
  • Advanced users report that the platform lacks depth in complex practice areas and customization options compared to purpose-built tools for larger or specialized law firms.

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 My Legal Software objects map to Freshsales

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

maps to

Freshsales

Contact + Account

1:1
Fully supported

My 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

maps to

Freshsales

Deal

1:1
Fully supported

Every 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

maps to

Freshsales

Custom Field on Deal

1:1
Fully supported

My 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

maps to

Freshsales

Custom Field on Deal + Custom Field on Contact

1:1
Fully supported

Total 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

maps to

Freshsales

Custom Object or Custom Fields on Deal

1:1
Fully supported

My 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

maps to

Freshsales

Event + Task

1:1
Fully supported

My 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

maps to

Freshsales

Sales Activities / Notes

1:1
Fully supported

My 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

maps to

Freshsales

Custom Field on Contact or Deal

1:1
Fully supported

My 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

maps to

Freshsales

User

1:1
Fully supported

My 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

maps to

Freshsales

Sales Activity + Note

1:1
Fully supported

Notes 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

maps to

Freshsales

Custom Field on Account

1:1
Fully supported

My 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

maps to

Freshsales

Not Migrated

1:1
Fully supported

My 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.

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.

My Legal Software logo

My Legal Software gotchas

Medium

Unexpected session timeouts cause lost unsaved work

Medium

Pricing requires sales contact and is not published

Low

Multi-year billing and trust records may reference inactive Case IDs

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

  • CSV column header names must exactly match Freshsales custom field labels

    Freshsales's CSV import process uses a static mapping: custom field column headers in your CSV must exactly match the custom field label as created in Freshsales before import runs. A single character difference — 'Matter_Number' vs 'Matter Number' vs 'matter_number' — causes the column to be silently skipped. We handle this by generating the exact label string during schema preparation, creating the custom field with that label, and exporting the CSV with byte-for-byte matching headers. If your My Legal Software export generates headers with different casing or spacing, we normalize them before writing the import CSV.

  • Billing history and invoice records have no native Freshsales equivalent

    My Legal Software stores invoice records, trust account balances, and billing timers as first-class objects integral to the product. Freshsales has no invoice, trust-account, or billing engine object. We migrate the most recent 24 months of invoice metadata (invoice number, amount, date, status) as custom fields on the Deal record, and we export the full billing ledger as a reference CSV attached to the Account. But the Freshsales UI will not show billing timers, and any invoice generation workflow must be rebuilt using Freshsales's Quotes module or a third-party integration.

  • Document files must be re-hosted post-migration

    My Legal Software's document repository stores PDFs, court filings, and client correspondence linked to matters. Freshsales's file storage attaches documents to individual Contact, Account, or Deal records but does not replicate a hierarchical matter-based folder structure. We migrate document filenames and the source URLs or storage paths as a text list on each Deal. The actual files must be re-uploaded to Freshsales Files or moved to a connected document management system post-migration. We flag any document link that points to an inaccessible URL before the migration runs.

  • Freshsales 25,000-record instant import cap requires batch planning

    Freshsales caps instantaneous CSV imports at 25,000 records. Records above this threshold are queued as a support ticket and processed during off-peak hours, typically within 1–2 business days. For firms with 25,000+ contacts and matters combined, we split the migration into two or more batches — Contacts and Accounts first, then Deals, then Activities and Notes — and configure the Freshsales account to accept the additional batches without triggering duplicate-record creation. We use the Source_System_ID__c field to prevent re-importing records that already exist in Freshsales from an earlier batch.

  • Conflict-check and billing workflows cannot migrate and require rebuild

    My Legal Software conflict-check workflows, matter-opening approval chains, and automated billing rule triggers (e.g., 'generate invoice when status changes to closed') are platform-specific automation constructs that have no Freshsales equivalent in Workflows. Freshsales Workflows can trigger on record creation, field changes, and stage changes but does not natively replicate legal billing automation logic. We export your My Legal Software workflow definitions as a structured JSON document listing each rule's trigger, condition, and action. Your Freshsales admin uses this as a rebuild reference after go-live.

Migration approach

Six steps for a successful My Legal Software to Freshsales data migration

  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. 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

Context on both ends of the pair

My Legal Software logo

My Legal Software

Source

Strengths

  • Consolidates case management, billing, document storage, and marketing into a single integrated platform.
  • User-friendly interface consistently praised by small firm reviewers for ease of adoption and daily use.
  • Built-in client communication portal and case notes sharing reduce reliance on external collaboration tools.
  • Responsive customer service with high satisfaction scores on third-party review platforms.
  • Flexible storage allows uploading files without strict size limits per the G2 review data.

Weaknesses

  • Session timeouts occur without warning, risking loss of unsaved work during active sessions.
  • Pricing model is opaque and requires contacting sales, complicating budget forecasting.
  • Platform is best suited for smaller firms and lacks the depth required by complex or large-scale practices.
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 My Legal Software 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

    My Legal Software: Not publicly documented.

  • Data volume sensitivity

    B

    My Legal Software doesn't expose a bulk API — REST + parallelization used for high-volume runs.

Estimator

Estimate your My Legal Software 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 My Legal Software to Freshsales data migrations

Answers to the questions buyers ask most during My Legal Software to Freshsales migration scoping. Not seeing yours? Book a call.

Can't find your answer?

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 consultation

Most My Legal Software to Freshsales migrations complete in 48–72 hours for firms with under 25,000 combined records (contacts, matters, events). Firms with 25,000+ records hit Freshsales's import queue threshold and extend to 7–14 days. The longest single step is schema preparation — creating Freshsales custom fields that exactly match your CSV column headers — which takes 1–2 days. The actual data load runs overnight in most cases.

Adjacent paths

Related migrations to explore

Ready when you are

Move from My Legal Software.
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