CRM migration

Migrate from MyCase to Freshsales

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

MyCase logo

MyCase

Source

Freshsales

Destination

Freshsales logo

Compatibility

92%

11 of 12

objects map 1:1 between MyCase and Freshsales.

Complexity

BStandard

Timeline

48–72 hours

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

MyCase organizes legal practice data around clients and matters with a built-in billing engine, time tracking, IOLTA accounting, and a client portal. Freshsales is a sales-focused CRM with Leads, Contacts, Accounts, Deals, and activity tracking but no native legal billing or matter management. FlitStack AI migrates all standard objects — clients, matters, tasks, calendar events, documents, and time entries — converting MyCase's flat client model into Freshsales's separate Leads and Contacts based on whether a client has open matters or recent activity. Matters become Deals, with case type stored as a custom field and stage derived from MyCase status values. Tasks and calendar events map to Freshsales Tasks and Events with original timestamps and owners. Time entries migrate as Notes with billable hours and rates preserved in custom fields. MyCase custom fields and custom objects carry over as Freshsales custom fields and custom objects. User assignments resolve by email match to Freshsales users. Documents re-upload to Freshsales Files with original names and association to the linked contact or deal. After migration, firms need to rebuild MyCase billing workflows, client portal configurations, document templates, and e-signature setup in Freshsales or a companion tool. FlitStack sequences the migration using MyCase's API export and Freshsales's bulk import API, respecting MyCase's 25 requests-per-second limit and Freshsales's plan-tier rate ceiling.

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

MyCase logo

MyCase

What's pushing teams away

  • QuickBooks integration syncs one direction only—deleting a transaction in MyCase does not remove it in QuickBooks, and the sync can get stuck, forcing manual reconciliation that solo practitioners find disruptive.
  • Users report missing billing features that mid-size firms require: inability to bulk-update rates on past time entries, limited flat-fee case management, and manual invoice adjustments across multiple sections.
  • UI changes between releases (especially around notifications and client message navigation) create friction for staff trained on earlier layouts, per Capterra and G2 reviews.
  • Advanced features including the open API are gated behind the $109/user/month Advanced tier, so growing firms hit feature ceilings on lower plans and face a pricing cliff.
  • Firms outgrowing the platform report that Clio's integration marketplace and enterprise features better support scaling case volume, which drives switchers toward larger legal CRMs.

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 MyCase objects map to Freshsales

Each row shows how a MyCase 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.

MyCase

Client

maps to

Freshsales

Contact / Lead

1:many
Fully supported

MyCase Clients have no separate lead/contact distinction — they are all people with an optional role. FlitStack routes MyCase Clients with open or recently closed matters to Freshsales Contacts; inactive clients with no matters in the past 12 months route to Freshsales Leads. Role data (Attorney, Billing Contact, etc.) stored as a custom pick-list field on both Contact and Lead.

MyCase

Client Address

maps to

Freshsales

Contact Address Fields

1:1
Fully supported

MyCase stores primary and billing addresses per client. All address fields including street address, city, state, zip code, and country map directly to Freshsales Contact address fields. When clients have multiple addresses, they are associated using Freshsales Contact's address type indicator to distinguish between billing and shipping locations.

MyCase

Company

maps to

Freshsales

Account

1:1
Fully supported

MyCase Companies map 1:1 to Freshsales Accounts. Company name maps to Account Name; domain maps to Website; industry maps to Industry pick-list. Multi-contact relationships in MyCase collapse to the primary AccountId on each Contact in Freshsales, with additional contacts added via the Account Contact Relationships model.

MyCase

Matter (Case)

maps to

Freshsales

Deal

1:1
Fully supported

MyCase Matters map to Freshsales Deals. Matter name becomes Deal Name; amount maps to Deal Amount if billable; status maps to Freshsales stage via value mapping. Case type (Family Law, Criminal Defense, Personal Injury, etc.) migrates as a custom field since Freshsales has no native matter-type concept. Responsible attorney and paralegal assignments map to Freshsales Deal Owner.

MyCase

Matter Custom Fields

maps to

Freshsales

Deal Custom Fields

1:1
Fully supported

Any custom fields on MyCase Matters — such as Court Name, Case Number, Judge Assigned, or Insurance Carrier — create matching custom fields on Freshsales Deals. Data types are preserved: text to text, date to date, pick-list to pick-list. FlitStack audits the full MyCase field list before migration to identify every custom field that needs a destination counterpart.

MyCase

Task

maps to

Freshsales

Task

1:1
Fully supported

MyCase Tasks map to Freshsales Tasks. Subject maps to Task Subject; description maps to Task Description; due date maps to Due Date; status (Open, Completed) maps to Freshsales Task Status. Parent record links (task belongs to a client and matter) are preserved as Freshsales ContactId and DealId lookups on the Task record.

MyCase

Calendar Event

maps to

Freshsales

Event

1:1
Fully supported

MyCase calendar events map to Freshsales Events. Event title, start time, end time, event type, and visibility (firm-wide or matter-specific) all transfer. Events linked to a matter in MyCase link to the corresponding Freshsales Deal via DealId. Events without a matter association link to the primary Contact.

MyCase

Time Entry

maps to

Freshsales

Note (with custom fields)

1:1
Fully supported

MyCase time entries (hours worked, billable rate, date, description, and associated attorney) cannot map to a native Freshsales object. FlitStack creates a Note on the corresponding Deal with hours, rate, and billable flag stored as custom fields on the Note. This preserves all time-tracking data for billing reconstruction in Freshsales or a linked accounting tool.

MyCase

Document / File

maps to

Freshsales

Freshsales Files

1:1
Fully supported

MyCase Drive files re-upload to Freshsales Files and are linked to the corresponding Contact or Deal record. Original file names and upload dates are preserved. MyCase's Drive folder hierarchy does not map to Freshsales native folders — the migration engineer produces a folder mapping plan and optionally stores the original Drive path as a custom field on each file.

MyCase

Billing / Invoice

maps to

Freshsales

Note + Custom Fields (on Account)

1:1
Fully supported

MyCase invoices, trust account balances, IOLTA tracking, and flat-fee billing rules have no native Freshsales equivalent. FlitStack preserves invoice totals, payment status, and outstanding balance as custom fields on the linked Account record. Firms must rebuild billing workflows and payment collection in Freshsales or a connected legal accounting tool.

MyCase

Client Portal Access

maps to

Freshsales

Custom Field

1:1
Fully supported

MyCase's client portal gives clients access to case updates, documents, and invoices. Freshsales has no built-in client portal — portal access status is stored as a custom field on the Contact record as a reference flag. Firms needing a client portal in Freshsales should evaluate Freshworks Freshdesk or a third-party integration.

MyCase

User / Staff

maps to

Freshsales

User

1:1
Fully supported

MyCase users and staff map to Freshsales Users by email address match. Unmatched users are flagged before migration — firms either invite them to Freshsales first or assign their records to a designated fallback owner. MyCase role-based permissions (Attorney, Paralegal, Admin) are stored as a custom field on the Freshsales User record.

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.

MyCase logo

MyCase gotchas

High

QuickBooks sync is strictly one-directional

High

Advanced API access is tier-gated

Medium

Document migration requires offline file transfer

Medium

Bulk rate updates on historical time entries are not supported

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

  • Client-to-contact routing requires a lifecycle split that MyCase does not enforce

    MyCase has one Client object for every person — whether they are a prospective client who inquired once or a long-standing client with ten open matters. Freshsales separates Leads and Contacts into distinct objects with different views, workflows, and conversion paths. There is no automatic MyCase equivalent to the Freshsales lifecycle stage concept. FlitStack applies a routing rule at migration time: clients with open or recently active matters (status = 'Open' or 'Pending' in the past 12 months) land as Freshsales Contacts; all others land as Freshsales Leads. Firms should review the split before the full run because changing a Lead to a Contact in Freshsales requires manual conversion, not a data update.

  • MyCase billing data has no native Freshsales equivalent and must be reconstructed

    MyCase's time tracking, IOLTA trust accounting, flat-fee invoicing, and LawPay payment integration are deeply integrated into the matter lifecycle. Freshsales has no IOLTA model, no trust-account field, and no native flat-fee billing construct — its billing layer is limited to Products, Quotes, and standard invoices. FlitStack preserves every time entry, invoice total, outstanding balance, and payment status as custom fields on the Account and Deal records, but the firm's billing workflows, payment collection, and IOLTA reconciliation logic must be rebuilt in Freshsales or a connected accounting tool. Firms using MyCase's integrated LawPay payments should plan for a separate payment processing migration.

  • MyCase Drive folder hierarchy does not map to Freshsales native file storage

    MyCase Drive stores files in a folder structure organized by matter and sub-folder type (Pleadings, Correspondence, Discovery, etc.) with file versioning. Freshsales Files are attached directly to Contact or Deal records with no native folder hierarchy and no version history — each file upload is a standalone attachment. When FlitStack migrates documents, files re-upload to Freshsales Files and are linked to the correct Contact or Deal record, but the folder tree is flattened. The migration engineer produces a document mapping plan before the full run, and the original MyCase Drive path is stored as a custom field on each file attachment so firms can reference the original structure.

  • MyCase API 25 req/s and Freshsales plan-tier rate limits require coordinated throttling

    MyCase API allows 25 requests per second per client — fast enough to extract large record sets in a short window. Freshsales API rate limits are set per plan tier: 1,000 requests per hour on Growth, 2,000 on Pro, and 5,000 on Enterprise, with a 429 Too Many Requests response when exceeded. If FlitStack extracts from MyCase faster than Freshsales can accept the data, the migration will stall and retry, extending the timeline. The migration engineer implements request throttling on the Freshsales write side and exponential backoff on 429 responses. Firms on the Growth plan with large record sets should consider upgrading to Pro for the migration duration to avoid extended cutover windows.

  • MyCase document files must be downloaded and re-uploaded individually

    MyCase does not expose a bulk file download endpoint — each file must be downloaded individually via the MyCase Drive API. This means that a firm with 500 files across 200 matters will generate 500 individual API calls to MyCase and 500 individual upload calls to Freshsales Files. Combined with Freshsales plan-tier rate limits, document migration can become the longest single phase of a MyCase-to-Freshsales cutover. FlitStack parallelizes file transfers where possible and sequences them after record data to ensure the CRM schema is in place before files land.

Migration approach

Six steps for a successful MyCase to Freshsales data migration

  1. Audit MyCase data and prepare Freshsales schema

    FlitStack reviews the MyCase account structure — listing all client fields, matter fields, custom fields, matter types, billing types, and document counts. The migration engineer identifies every MyCase custom field that requires a Freshsales custom field counterpart and creates a mapping specification. On the Freshsales side, custom fields are created in advance so the migration validation runs against the complete target schema. Firms receive a schema preparation checklist so Freshsales administrators can pre-create fields before the first data load.

  2. Resolve user and attorney assignments by email

    MyCase user accounts and attorney assignments are matched against Freshsales users by email address. Unmatched users — staff members who have not yet been invited to Freshsales — are flagged in a pre-migration report. Firms either invite those users to Freshsales before the migration run or designate a fallback owner (a senior attorney or admin) for records belonging to unmatched staff. No record lands in Freshsales without an owner; unresolved assignments do not silently drop records.

  3. Migrate Accounts, Contacts, and Leads before Deals

    Freshsales requires Accounts to exist before Contacts can link to them (via the AccountId lookup), and Contacts or Leads to exist before Deals can reference them via Contact Roles or Deal Contact relationships. FlitStack sequences the migration in the correct dependency order: MyCase Companies first → Freshsales Accounts; then MyCase Clients (split into Contacts and Leads) with AccountId resolution; then MyCase Matters → Freshsales Deals with stage mapping and case-type custom field population. This sequence ensures foreign key integrity and prevents orphaned deal records.

  4. Run a sample migration with field-level diff

    A representative sample — typically 100 to 300 records spanning clients, matters, tasks, events, and a subset of documents — migrates first. FlitStack generates a field-level diff showing every source field value and its destination counterpart. The firm reviews the diff to verify client-to-contact routing, case-type custom field population, attorney owner resolution, and time entry placement. Sample approval is required before the full run commits. Any mapping adjustments are made to the migration specification before the next phase.

  5. Execute full migration with delta-pickup window

    The full record set migrates after sample approval. A delta-pickup window — typically 24 to 48 hours — captures any MyCase records created or modified during the migration run. Audit logs record every operation (create, update, link) with timestamps and operator. One-click rollback is available if the reconciliation check reveals missing records, incorrect field values, or duplicate contacts. After rollback validation, the firm transitions to Freshsales as the production CRM and the MyCase account is decommissioned per the firm's retention policy.

  6. Post-migration: rebuild billing, document workflows, and client portal

    After data lands in Freshsales, FlitStack delivers a rebuild reference package covering MyCase billing workflows, client portal configurations, document templates, and e-signature setup. Firms use this package to reconstruct billing rules in Freshsales (or a connected accounting tool), restore document folder logic via a custom object, and configure Freshsales workflows for task automation. FlitStack does not migrate workflow definitions but provides the structured reference needed for an accurate rebuild.

Platform deep dives

Context on both ends of the pair

MyCase logo

MyCase

Source

Strengths

  • All-in-one practice management combines case files, client comms, billing, and docs in a single platform.
  • Client portal with secure document sharing reduces reliance on third-party file-sharing tools.
  • Built-in texting and e-signature are included at all tiers, avoiding per-transaction fees.
  • Workflow automation auto-generates tasks and calendared deadlines on new case creation.
  • AffiniPay parentage ties payments tightly to practice management through LawPay integration.

Weaknesses

  • Open API and advanced document management require the Advanced tier at $109/user/month.
  • One-way QuickBooks sync means billing deletions in MyCase must be manually voided in QuickBooks.
  • Cannot bulk-update rates on past time entries—each record requires individual editing.
  • UI changes between releases have caused navigation friction, especially around notifications.
  • Document automation templates are tied to the original creator's machine and cannot be exported.
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 MyCase 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

    MyCase: 25 requests per second per client.

  • Data volume sensitivity

    B

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

Estimator

Estimate your MyCase 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 MyCase to Freshsales data migrations

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

Can't find your answer?

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

Book a free 30 minute consultation

No. FlitStack AI migrates data and schema only — MyCase workflow definitions, task templates, automated deadline rules, and document generation setups do not transfer to Freshsales. These must be rebuilt in Freshsales Workflows or Freshdesk. FlitStack exports your MyCase workflow definitions as a structured rebuild reference that your Freshsales admin can use to reconstruct automated task creation and deadline calendaring.

Adjacent paths

Related migrations to explore

Ready when you are

Move from MyCase.
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