How long does a Case UI to Salesforce Sales Cloud migration take?

Most Case UI to Salesforce migrations complete in 48–72 hours of clock time for under 50,000 records (clients, matters, time entries, documents). Larger setups with 200k+ records or complex custom schema extend to 5–10 days. The longest step is Salesforce custom field creation in Setup — we deliver the manifest in advance so your admin can pre-create fields while we audit the data export.

Will my Case UI workflows, conflict checks, and document templates migrate to Salesforce Flow?

No. FlitStack AI migrates data and schema only. Workflows, conflict-of-interest checks, document auto-generation, and email templates do not transfer — they require manual rebuild in Salesforce Flow or Apex. We export every active Case UI workflow as a reference document listing trigger conditions, filters, and actions so your Salesforce admin can reconstruct them post-migration. Additionally, the export includes step-by-step configuration notes and suggested Flow type mapping (Record-Triggered, Schedule, Platform Event) to accelerate the rebuild process.

What does a Case UI matter become in Salesforce?

Each Case UI matter maps to a Salesforce Case record. Matter title becomes Case.Subject. Practice area, responsible attorney, and matter type migrate as custom fields on Case (Practice_Area__c, Responsible_Attorney__c, Matter_Type__c) because Salesforce has no native legal taxonomy. Billing arrangements, court venue, and statute of limitations also become custom fields on the Case record. Additionally, the matter status and priority map to Salesforce Case Status and Priority pick‑lists, and any matter‑specific custom fields (e.g., Court_Venue__c, Statute_of_Limitations__c) are preserved as text or date fields on the Case. The original matter open date is stored in Original_Create_Date__c, ensuring historical accuracy for reporting.

Can I migrate Case UI time entries and billing data to Salesforce?

Yes. Case UI time entries migrate as a Time_Entry__c custom object with Hours__c, Rate__c, Billing_Status__c, and Description__c fields, linked to the parent Case record. This preserves billable hour history. However, the downstream accounting connection (QuickBooks, PracticePanther, or your billing system) must be reconfigured post-migration — we export your billing setup as a CSV reference file for your admin. In addition, each Time_Entry__c record retains the original entry date and attorney reference, enabling accurate historical reporting within Salesforce reports and dashboards. After migration, your admin can map these fields to the appropriate accounting connector using the exported CSV as a guide.

What happens to Case UI custom fields in Salesforce?

Case UI custom fields (practice-area, statute of limitations, court venue, etc.) become Salesforce custom fields with the __c suffix. We generate a Setup manifest listing every field to create, its data type, and pick-list values. Your Salesforce admin creates these fields in Setup before data loads. Fields created mid-migration cause record failures — the manifest must be completed before the migration run.

Does the migration affect my Case UI account during cutover?

No. FlitStack AI uses scoped read access on Case UI — your team keeps working in Case UI throughout the migration. A delta-pickup window (24–48 hours after the main run) captures any matters, contacts, or time entries modified during cutover so Salesforce reflects Case UI's final state at go-live. Your Case UI account remains fully functional until you decide to decommission it.

How are Case UI's multiple-clients-per-matter associations handled in Salesforce?

Case UI natively supports N:N client-to-matter relationships. Salesforce Cases have one primary ContactId. We identify the primary client per matter using your specified rule (most recently modified or alphabetically), assign Case.ContactId, and map remaining clients to Account Contact Roles with role type (Plaintiff, Defendant, Insured). If your firm requires full N:N visibility, we can build a Matter_Client__c junction object — this requires Salesforce admin coordination before migration.

Case UI to Salesforce Sales Cloud Migration — Field-Level Mapping & Rollback

Overview

What this migration involves

Case UI is a practice-management platform built for solo practitioners and small law firms, storing matters, clients, calendar events, time entries, and documents in a flat relational model optimized for legal workflows. Salesforce Sales Cloud uses a normalized object hierarchy (Account → Contact → Case) with RecordTypeId, pick-list fields scoped by page layout, and a separate Activity model for Tasks and Events. The migration carries Case UI clients into Salesforce Accounts and Contacts, matters into Cases with custom fields for practice-area and billing configuration, and documents re-uploaded as Salesforce Files. The harder problems are mapping Case UI's billing计时 (time-entry) structure to Salesforce's custom fields, translating matter status values to Case Status pick-lists, and handling the N:N client-to-matter relationship that requires junction objects or the Account Contact Role model. Workflows, templates, and billing rules built in Case UI do not transfer — we export them as reference documents for your Salesforce admin to rebuild in Flow and custom settings.

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

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

Salesforce Sales Cloud

What's pulling them in

The AppExchange marketplace with 5,000+ prebuilt apps gives enterprises integrations for nearly every business workflow without custom development.
Native Einstein AI for lead scoring, opportunity insights, and predictive forecasting adds intelligence without a separate platform purchase.
Territory management, multi-currency support, and advanced forecasting satisfy the needs of complex B2B sales organizations with structured revenue teams.
Slack, Tableau, and CPQ are deeply integrated into the core platform, keeping the sales stack unified for teams already in the Salesforce ecosystem.
Organizations with a large, established Salesforce implementation choose it because switching costs — integrations, custom code, trained admins — are prohibitive.

Object mapping

How Case UI objects map to Salesforce Sales Cloud

Each row shows how a Case UI object lands in Salesforce Sales Cloud, 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

Salesforce Sales Cloud

Account

1:1

Fully supported

If a client already exists, we use fuzzy name and address match to avoid duplicates, logging merges for review. Additional fields like client type and billing email map to custom Account fields.

Case UI

Contact (primary attorney)

maps to

Salesforce Sales Cloud

Contact

1:1

Fully supported

We also check for duplicate contacts by email, merging or creating new records as needed. Contact roles such as Primary Attorney or Billing Contact are stored in custom fields (Contact_Role__c) for reporting.

Case UI

Matter

maps to

Salesforce Sales Cloud

Case

1:1

Fully supported

We preserve the matter open date in Original_Create_Date__c, map matter status to Case Status via value‑mapping, and retain court venue, statute of limitations, and billing arrangement fields as text or pick‑list fields on the Case.

Case UI

Matter Status

maps to

Salesforce Sales Cloud

Case Status (pick-list)

1:1

Fully supported

During mapping, we also verify that each status aligns with the appropriate RecordType and business hours configuration in Salesforce, adjusting the mapping as needed to prevent validation errors.

Case UI

Time Entry

maps to

Salesforce Sales Cloud

Custom Time Entry object or custom fields on Case

1:1

Fully supported

Each Time_Entry__c record also captures the matter ID in Source_System_ID__c. The migration validates that all linked Cases exist before inserting entries to avoid orphan records.

Case UI

Document / File

maps to

Salesforce Sales Cloud

Salesforce Files (ContentDocument / ContentVersion)

1:1

Fully supported

During the upload, we preserve the original file name and content version metadata, and we set the appropriate ShareType and Visibility to match your org's default File sharing settings.

Case UI

Calendar / Event

maps to

Salesforce Sales Cloud

Event

1:1

Fully supported

Each Event also records the Event Type (e.g., Deposition, Hearing) in a custom Type__c field, and the original Case UI event ID is stored in Source_System_ID__c for audit trails.

Case UI

Task

maps to

Salesforce Sales Cloud

Task

1:1

Fully supported

If a task's assigned user does not exist in Salesforce, we assign it to a fallback admin user and flag the record for later re-assignment. Custom fields such as Task_Category__c are migrated as well.

Case UI

Note

maps to

Salesforce Sales Cloud

Note

1:1

Fully supported

We also map the original note created date to the Salesforce Note CreatedDate field, and we preserve any attachments embedded in the note as separate Salesforce Files linked to the same Case record.

Case UI

Custom Fields

maps to

Salesforce Sales Cloud

Custom Fields (__c)

1:1

Mapping required

Case UI custom fields for practice-area specific data (statute of limitations, court venue, opposing counsel details) migrate as Salesforce custom fields with __c suffix. Data type preserved (text, pick-list, date, checkbox) during migration. Custom fields scoped per object — Contact custom fields do not collide with Case custom fields.

Case UI

Client-Matter Association (N:N)

maps to

Salesforce Sales Cloud

Account Contact Role / Junction Object

many:1

Fully supported

Case UI allows multiple clients per matter and multiple matters per client. Salesforce Cases support one primary Contact. We map the primary client to Case.ContactId and remaining clients to Account Contact Roles, preserving the association with role type (Plaintiff, Defendant, Insured).

Case UI

Billing Configuration

maps to

Salesforce Sales Cloud

Custom fields on Case

1:1

Fully supported

We also preserve the billing currency and rate configurations in custom fields, and we export a mapping spreadsheet for the billing admin to reference when setting up the QuickBooks or PracticePanther connector.

Case UI	Salesforce Sales Cloud	Compatibility
Client	Account1:1	Fully supported
Contact (primary attorney)	Contact1:1	Fully supported
Matter	Case1:1	Fully supported
Matter Status	Case Status (pick-list)1:1	Fully supported
Time Entry	Custom Time Entry object or custom fields on Case1:1	Fully supported
Document / File	Salesforce Files (ContentDocument / ContentVersion)1:1	Fully supported
Calendar / Event	Event1:1	Fully supported
Task	Task1:1	Fully supported
Note	Note1:1	Fully supported
Custom Fields	Custom Fields (__c)1:1	Mapping required
Client-Matter Association (N:N)	Account Contact Role / Junction Objectmany:1	Fully supported
Billing Configuration	Custom fields on Case1:1	Fully supported

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

Salesforce Sales Cloud gotchas

High

Workflow Rules and Process Builder are retired

High

Bulk API batch quota exhaustion during large imports

Medium

Storage overage billing is non-obvious

Medium

Account-Contact many-to-many relationship mapping

Low

Territory and team member import ordering dependencies

Case UI gotchas		Salesforce Sales Cloud gotchas
Severity	Issue	Severity	Issue
High	No public API documentation found	High	Workflow Rules and Process Builder are retired
Medium	On-Premise perpetual license has upgrade isolation risk	High	Bulk API batch quota exhaustion during large imports
Low	No verified public reviews or G2/Capterra feedback	Medium	Storage overage billing is non-obvious
		Medium	Account-Contact many-to-many relationship mapping
		Low	Territory and team member import ordering dependencies

Pair-specific challenges

N:N client-to-matter associations require junction object planning

Case UI natively supports multiple clients per matter and vice versa — a many-to-many relationship. Salesforce Cases have a single primary ContactId plus Account Contact Roles for secondary parties. When migrating, we identify the primary client per matter (most recently modified or by your specified rule), assign Case.ContactId, and surface remaining clients as Account Contact Roles with role type (Plaintiff, Defendant, Insured). If your firm requires a full N:N model, we can build a custom Matter_Client__c junction object with Matter__c and Client_Account__c lookups — this requires Salesforce admin coordination before data lands.
Case UI billing configuration has no Salesforce equivalent and requires rebuild

Case UI stores per-matter billing arrangements (hourly rate, flat fee, contingency percentage) as native fields. Salesforce has no native billing setup object on Cases. We migrate these as Billing_Arrangement__c, Standard_Rate__c, and Billing_Method__c custom fields, but the downstream accounting integration (QuickBooks, PracticePanther, or your firm's billing system) must be reconnected post-migration. FlitStack exports your billing configuration as a CSV reference file for your admin to use when setting up the billing connector.
Custom fields on Case require __c suffix and Setup pre-creation

Case UI custom fields (practice area, statute of limitations, court venue) use plain text names without namespace. Salesforce requires all custom fields to carry the __c suffix and be created in Setup before records load. If your Case UI instance has 15+ custom fields per object, we deliver a Setup manifest listing every field to create, its data type, and pick-list values — your Salesforce admin creates these before the migration run. Fields created mid-migration cause record-level failures and require rollback.
Case UI calendar events map to Salesforce Events but lose recurring-rule logic

Case UI calendar events map to Salesforce Events but lose recurring-rule logic. Case UI deposition schedules and court dates may use recurring-rule logic (RRULE-style recurrence). Salesforce Events support basic recurrence patterns but RRULE formatting does not import directly. We extract the next occurrence and the recurrence description as a custom Recurrence_Detail__c field on each Event — your team manually recreates complex recurrence in Salesforce calendar after migration. Additionally, if your firm relies on specific recurrence patterns such as monthly or annual reminders, you should recreate these using Salesforce's native recurrence builder or Flow-based automation after the data loads.
Workflows, conflict checks, and document templates do not migrate

Case UI workflows for conflict-of-interest checking, document auto-generation, and client intake automation live in Case UI's platform logic. Salesforce Flow is the destination equivalent, but automation rules are not data — they are configuration. FlitStack AI migrates data and schema only. We provide a Workflow Export document listing every active Case UI workflow with its trigger conditions and actions so your Salesforce admin can rebuild them in Flow or Apex after go-live.

Migration approach

Six steps for a successful Case UI to Salesforce Sales Cloud data migration

Pre-migration schema inventory and Salesforce Setup plan

We audit Case UI custom fields, matter types, practice-area pick-lists, and time-entry structure. From this inventory we generate a Salesforce Setup manifest: every custom field to create with __c suffix, data type, and pick-list values. We also identify the client-primary-matter rule (most recent, alphabetically first, or by your specification) for resolving N:N associations. Your Salesforce admin creates the custom fields in a sandbox before test migration runs.
Owner and user resolution by email match

Case UI attorney and staff records are matched against Salesforce users by email address. Unmatched owners are flagged before migration — your team either invites them to Salesforce first or assigns their records to a fallback owner (e.g., the admin user). No record lands in Salesforce without a resolved OwnerId. If a Case UI user has no corresponding Salesforce profile, FlitStack creates a temporary mapping record, and you can either provision the user in Salesforce beforehand or designate a placeholder UserId to hold the data until the account is created. This ensures referential integrity across Account, Contact, and Case records.
Migration sequencing: Accounts → Contacts → Cases → Activities

Salesforce requires Account records before Contacts (via AccountId) and Contacts before Cases (via ContactId). We sequence the migration so foreign keys resolve correctly: Clients → Accounts, then Contact records linked to Accounts, then Matters → Cases with ContactId for primary client, then Time Entries → Time_Entry__c linked to Cases. Documents and Notes attach after parent records exist. During this sequence we perform field updates in a single pass to avoid circular dependencies, and any error halts the run and reports the offending record for correction.
Sample migration with field-level diff before full run

A representative slice (typically 200–500 records spanning clients, matters, time entries, and documents) migrates into a Salesforce sandbox first. We generate a field-level diff comparing source values against destination fields so you can verify practice-area mapping, billing configuration transfer, and matter status translation before the full run commits. The diff report highlights any data truncation, pick‑list mismatches, or missing required fields, enabling you to adjust field mappings or Salesforce Setup configurations before the production migration run.
Delta-pickup window and rollback readiness

Full migration runs against Salesforce. A delta-pickup window (typically 24–48 hours) captures any Case UI records modified during cutover so Salesforce reflects the final state at go-live. Audit log captures every insert, update, and error. One-click rollback is available if reconciliation fails — FlitStack reverts the org to its pre-migration state and schedules a corrected re-run. During the delta window, any newly created contacts, updated matters, or revised time entries are automatically imported, ensuring zero data loss. The rollback option uses a snapshot taken at migration start, so you can revert without manual data cleanup.

Platform deep dives

Context on both ends of the pair

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.

Salesforce Sales Cloud

Destination

Strengths

Largest enterprise app ecosystem in CRM with 5,000+ AppExchange integrations covering nearly every vertical workflow.
Native Einstein AI delivers lead scoring, opportunity insights, and predictive forecasting without a third-party layer.
Advanced territory management, multi-currency, and flexible forecasting satisfy complex B2B revenue structures.
Deep platform extensibility: Custom Objects, Apex, Flow, and the Metadata API allow full schema customization.
Well-documented REST API, Bulk API, and Composite API with published rate limits for programmatic migration.

Weaknesses

Pricing model is layered and opaque in practice: per-seat fees plus storage overages, add-on subscriptions, and annual uplifts compound to 30–40% above sticker price.
Workflow Rules and Process Builder are deprecated, forcing all orgs onto Salesforce Flow — a migration task that catches many teams by surprise.
Steep administrative complexity: meaningful configuration requires a dedicated Salesforce admin or consultant.
API rate limits are edition-gated (100k/day base for Enterprise) and easily exhausted by large historical imports without throttling.
Data export is exportable via Data Loader but preserving relationship integrity across 30+ objects requires careful ETL sequencing.

	Case UI Source	Salesforce Sales Cloud Destination
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.	Largest enterprise app ecosystem in CRM with 5,000+ AppExchange integrations covering nearly every vertical workflow. Native Einstein AI delivers lead scoring, opportunity insights, and predictive forecasting without a third-party layer. Advanced territory management, multi-currency, and flexible forecasting satisfy complex B2B revenue structures. Deep platform extensibility: Custom Objects, Apex, Flow, and the Metadata API allow full schema customization. Well-documented REST API, Bulk API, and Composite API with published rate limits for programmatic migration.
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.	Pricing model is layered and opaque in practice: per-seat fees plus storage overages, add-on subscriptions, and annual uplifts compound to 30–40% above sticker price. Workflow Rules and Process Builder are deprecated, forcing all orgs onto Salesforce Flow — a migration task that catches many teams by surprise. Steep administrative complexity: meaningful configuration requires a dedicated Salesforce admin or consultant. API rate limits are edition-gated (100k/day base for Enterprise) and easily exhausted by large historical imports without throttling. Data export is exportable via Data Loader but preserving relationship integrity across 30+ objects requires careful ETL sequencing.

POPULAR PLATFORMS

POPULAR MIGRATIONS

POPULAR PLATFORMS

POPULAR MIGRATIONS

POPULAR PLATFORMS

POPULAR MIGRATIONS

POPULAR PLATFORMS

POPULAR MIGRATIONS

POPULAR PLATFORMS

POPULAR MIGRATIONS

Migrate from Case UI to Salesforce Sales Cloud

What this migration involves

Field-level fidelity

Schema-aware mapping

Relationships preserved

Full activity history

Attachments & notes

Two sides of the same decision

Case UI

Salesforce Sales Cloud

How Case UI objects map to Salesforce Sales Cloud

What specifically takes care here

Six steps for a successful Case UI to Salesforce Sales Cloud data migration

Context on both ends of the pair

How hard is this migration?

Estimate your Case UI to Salesforce Sales Cloud migration cost

What are you migrating?

Frequently asked questions about Case UI to Salesforce Sales Cloud data migrations

Can't find your answer?

Related migrations to explore

Move from Case UI.
Land in Salesforce Sales Cloud, intact.

Migrate from Case UI to Salesforce Sales Cloud

What this migration involves

Field-level fidelity

Schema-aware mapping

Relationships preserved

Full activity history

Attachments & notes

Two sides of the same decision

Case UI

Salesforce Sales Cloud

How Case UI objects map to Salesforce Sales Cloud

What specifically takes care here

Six steps for a successful Case UI to Salesforce Sales Cloud data migration

Context on both ends of the pair

How hard is this migration?

Estimate your Case UI to Salesforce Sales Cloud migration cost

Frequently asked questions about Case UI to Salesforce Sales Cloud data migrations

Can't find your answer?

How long does a Case UI to Salesforce Sales Cloud migration take?

Will my Case UI workflows, conflict checks, and document templates migrate to Salesforce Flow?

What does a Case UI matter become in Salesforce?

Can I migrate Case UI time entries and billing data to Salesforce?

What happens to Case UI custom fields in Salesforce?

Does the migration affect my Case UI account during cutover?

How are Case UI's multiple-clients-per-matter associations handled in Salesforce?

Related migrations to explore

Move from Case UI. Land in Salesforce Sales Cloud, intact.

Move from Case UI.
Land in Salesforce Sales Cloud, intact.