CRM migration

Migrate from Case UI to Freshsales

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

Case UI logo

Case UI

Source

Freshsales

Destination

Freshsales logo

Compatibility

83%

10 of 12

objects map 1:1 between Case UI and Freshsales.

Complexity

BStandard

Timeline

48–72 hours

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

Case UI organizes law-firm data around matters, clients, and billing records with a practice-management schema optimized for legal workflows. Freshsales uses a standard CRM object model — Leads, Contacts, Accounts, Deals, Tasks, and Events — with pipeline stages, contact lifecycle stages, and custom modules for extensibility. The migration maps Case UI clients to Freshsales Contacts and Accounts, matters to Deals with a custom matter-type field, and billing records to custom fields or Deal line items depending on your preferred structure. Case UI's custom fields, user assignments, and timestamps transfer directly. What does not transfer: matter-status automation rules, client intake workflows, document-generation templates, billing-rule automations, and any third-party integrations Case UI has connected. Those must be rebuilt as Freshsales workflows or custom modules post-migration. We use Case UI's export API and Freshsales REST API to move records, running a sample migration first with field-level diff so you verify every mapping before the full run commits.

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

Case UI logo

Case UI

What's pushing teams away

  • Small law firms report outgrowing the platform when they need advanced integrations, custom workflows, or multi-office support that Case UI does not provide.
  • Lack of public API documentation makes Case UI difficult to connect with third-party tools, forcing firms to manually export and re-enter data when workflow needs change.
  • Users with complex practice areas report that the platform lacks depth in features like advanced reporting, conflict checking, or specialized litigation tools.
  • On-Premise customers who lack dedicated IT staff struggle with self-managed security updates and backups, leading some to move to fully managed alternatives.

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

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

Case UI

Client

maps to

Freshsales

Contact + Account

many:1
Fully supported

Case UI clients with billing and contact details merge into Freshsales Contacts with Account linkage. Client-level address and company data become Account records; individual attorney and paralegal contacts become Contact records with role assignments. We also map the primary contact flag to the appropriate Contact record to ensure the main client is identified correctly in Freshsales.

Case UI

Matter

maps to

Freshsales

Deal

1:1
Fully supported

Case UI matters map 1:1 to Freshsales Deals. The matter name becomes Deal Name, matter status maps to Deal stage values, and matter-type (e.g., litigation, corporate, family law) becomes a custom Deal field for pipeline segmentation. All existing timestamps, such as opened_date and closed_date, transfer to the Deal's created_at and closed_date fields to preserve historical timing.

Case UI

Matter Status

maps to

Freshsales

Deal Stage

1:1
Fully supported

Case UI status values (Active, Pending Review, Closed, Archived) map to Freshsales Deal stage pick-list values. Each stage maps value-by-value, and stage-transition timestamps are preserved as custom datetime fields on the Deal record. This mapping ensures that any historical status changes are visible in Freshsales reports, allowing your team to audit the evolution of each matter.

Case UI

Matter Type / Practice Area

maps to

Freshsales

Custom Deal Field (Matter_Type__c)

1:1
Fully supported

Case UI practice-area classifications (Family Law, Employment, Real Estate, etc.) have no direct Freshsales equivalent. We create a custom pick-list field on Deal to preserve this categorization for reporting by matter type across pipelines. The pick-list values are populated with the same labels used in Case UI, ensuring consistency for users who reference matter types in both systems.

Case UI

Billable Hours / Billing Record

maps to

Freshsales

Custom Fields on Deal + Product Line Items

1:1
Fully supported

Case UI time entries and billing records transfer as custom numeric fields (Total_Hours__c, Billing_Rate__c) on the Deal, with detailed line items as Deal Product records when the Freshsales Product Catalog is in use. Hourly rates map to Product price book entries, including any applicable tax adjustments.

Case UI

Document / Attachment

maps to

Freshsales

Salesforce Files / Freshsales Document

1:1
Fully supported

Case UI documents attached to matters re-upload to Freshsales Files linked to the corresponding Deal record. File size limits apply (Freshsales default 25MB per file). Inline images in matter notes are extracted and rehosted as separate file attachments.

Case UI

Task / Reminder

maps to

Freshsales

Task

1:1
Fully supported

Case UI task records map to Freshsales Tasks. Original due dates, owners (resolved by email match), and task descriptions transfer. Completed status maps to Freshsales task completion field; open tasks land as pending Tasks on the mapped Deal. If the location contains a conference room or virtual link, we preserve those details so your team can recreate the event without additional research.

Case UI

Calendar Event / Court Date

maps to

Freshsales

Event

1:1
Fully supported

Case UI court dates and scheduled events map to Freshsales Events with original start/end times and location preserved. Assigned attorney resolves to Freshsales user by email match; unmatched events flag for manual assignment before migration commits. This ensures continuity of client service and accurate ownership tracking.

Case UI

Custom Fields (Matter)

maps to

Freshsales

Custom Fields on Deal

1:1
Fully supported

Case UI custom fields on matters create corresponding custom fields on Freshsales Deals. Field types are preserved: text fields to text, pick-lists to pick-lists, date fields to date. Any field requiring a new custom property is pre-created in Freshsales before data loads.

Case UI

User / Attorney

maps to

Freshsales

User

1:1
Fully supported

Case UI attorneys and staff resolve to Freshsales Users by email address. Unmatched users are flagged before migration runs — your team either provisions Freshsales licenses for them or assigns their matters to a designated fallback attorney before data lands. This ensures continuity of client service and accurate ownership tracking.

Case UI

Workflow / Automation

maps to

Freshsales

No Equivalent

1:1
Fully supported

Case UI matter-status triggers, intake routing rules, and document-generation workflows have no Freshsales equivalent and cannot be exported. We provide an exported JSON summary of your workflow definitions for your Freshsales admin to reference during manual rebuild in Freshsales Workflow Builder.

Case UI

Client-Matter Association (N:N)

maps to

Freshsales

Contact + Account + Deal + Contact Role

many:1
Fully supported

Case UI allows multiple clients per matter and multiple matters per client. In Freshsales, each matter becomes a Deal linked to one primary Account (the most relevant client). Secondary client contacts attach via Contact Roles on the Deal, preserving the full association graph as contact-role entries.

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.

Case UI logo

Case UI gotchas

High

No public API documentation found

Medium

On-Premise perpetual license has upgrade isolation risk

Low

No verified public reviews or G2/Capterra feedback

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

  • Matter-status workflows and intake automations do not export

    Case UI uses internal rule-engine triggers for matter-status transitions, client-intake routing, and document-generation automation. Freshsales Workflow Builder cannot import these definitions. We export your Case UI workflow rules as a JSON reference document and deliver it to your Freshsales admin for manual recreation. The business logic encoded in those workflows — routing rules, status-change notifications, SLA timers — must be rebuilt from scratch in Freshsales Workflow Builder on your Growth or Pro plan.

  • N:N client-matter associations require junction resolution

    Case UI allows multiple clients per matter and multiple matters per client. Freshsales Deals link to one primary Account and optionally to secondary contacts via Contact Roles. We resolve the most-recently-modified client as primary (configurable by your rule) and surface all secondary associations as Contact Role entries on the Deal. Circular references — a client that is also an opposing party on the same matter — are flagged for your admin to resolve before the full migration runs.

  • Custom fields must pre-exist in Freshsales before data loads

    Freshsales requires custom fields to be created in the UI or via API before records are inserted into those fields. Our migration plan delivers a custom field manifest for every Case UI custom property — with field name, type, and pick-list values — so your Freshsales admin can pre-create them. Fields created during migration rather than before cause batch failures that require re-running the affected record set. This manual rebuild ensures that each rule aligns with Freshsales's workflow syntax and trigger conditions, preserving the operational intent of your original automations.

  • Billing data shape requires schema decision before migration

    Case UI stores billable hours, billing rates, and invoice totals as separate matter properties. Freshsales Deals have an amount field and a Product Catalog for line items. Your team must decide before migration: should billing data land as Deal-level custom fields (total hours, total amount), or should individual time entries become Deal Product records? We support both patterns but cannot guess which your practice prefers, so this decision gates the field mapping phase.

  • Unmatched attorneys require Freshsales user provisioning

    Case UI attorney and staff records resolve to Freshsales Users by email match. If a Case UI user has no corresponding Freshsales license, their assigned matters land under a fallback owner (designated by you) and the unmapped user is flagged in the pre-flight report. We cannot complete the migration until all matter owners have a Freshsales User ID — either by provisioning a license or by assigning to a fallback.

Migration approach

Six steps for a successful Case UI to Freshsales data migration

  1. Audit Case UI data model and Freshsales target schema

    We read your Case UI export and Freshsales instance to document every object, field, and relationship. We identify custom fields, matter types, billing properties, and user accounts. The output is a migration blueprint with object-level and field-level mapping that your Freshsales admin reviews before any data moves. This step takes 3–5 business days and includes a pre-flight report flagging any unmapped fields or missing Freshsales custom field creations.

  2. Create Freshsales custom fields and custom modules

    Your Freshsales admin creates the custom fields identified in the blueprint — matter_type pick-list, billing fields, court/judge fields, source IDs — using the field manifest we deliver. If your plan includes Custom Modules (Pro or Enterprise), we scope custom object creation for any Case UI domain objects that don't map to standard Freshsales entities. Custom fields must exist before the migration batch runs.

  3. Resolve owners and provision Freshsales users

    Case UI attorneys and staff match to Freshsales users by email address. We generate an owner-resolution report showing matched users, unmatched users, and the fallback assignments for each. Your team provisions Freshsales licenses for any attorney without an account, or confirms the fallback owner assignment. No matter record migrates without a resolved owner. This verification step prevents orphaned records and ensures that every Deal inherits the correct owner in Freshsales, maintaining accountability and accurate reporting.

  4. Run sample migration with field-level diff

    A representative slice — typically 100–300 records across clients, matters, tasks, and events — migrates first. We produce a field-level diff comparing every source field to its destination value so you can verify billing field mapping, matter-type categorization, and contact role resolution. You approve the sample before the full run commits. This step surfaces mapping errors at low volume before they affect your full dataset.

  5. Execute full migration with delta-pickup window

    All remaining records migrate in dependency order: Accounts first, then Contacts, then Deals with associated Tasks and Events. A 24–48 hour delta-pickup window captures any Case UI records created or modified during cutover. Audit log records every operation, and one-click rollback is available if reconciliation reveals data integrity issues. Freshsales workflows and automations are rebuilt separately using the exported workflow reference document.

Platform deep dives

Context on both ends of the pair

Case UI logo

Case UI

Source

Strengths

  • Clear per-user pricing with no surprise fees or mandatory add-ons on the Cloud plan.
  • On-Premise perpetual option eliminates per-user billing for firms with many attorneys and staff.
  • Free trial lets firms validate fit before committing to a paid subscription.
  • Daily backups and segregated databases reduce data loss risk for solo practitioners.
  • Straightforward interface purpose-built for small law firm workflows.

Weaknesses

  • No publicly documented API limits third-party integrations and automated migration tooling.
  • Limited public documentation and no verified reviews make independent evaluation difficult.
  • Smaller feature set compared to enterprise legal platforms may not support complex or multi-practice operations.
  • On-Premise version requires firm IT staff to manage upgrades, security, and backups independently.
  • No transparent rate limits or SLA terms published on the website for Cloud customers.
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. 3 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 Case UI and Freshsales.

  • Object compatibility

    B

    3 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

    Case UI: Not publicly documented.

  • Data volume sensitivity

    B

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

Estimator

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

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

Can't find your answer?

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

Book a free 30 minute consultation

Most Case UI to Freshsales migrations complete in 48–72 hours of clock time for under 25,000 matter and client records. Larger setups with 100,000+ records, multiple matter types requiring custom field proliferation, or complex client-matter N:N resolution extend to 5–10 days. Pre-flight user provisioning and custom field creation are the longest planning steps before data moves. The actual duration also depends on the responsiveness of your team in provisioning Freshsales user accounts and confirming custom field definitions prior to the migration run.

Adjacent paths

Related migrations to explore

Ready when you are

Move from Case UI.
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