CRM migration
Field-level mapping, validation, and rollback between Case UI and HubSpot. We move data and schema; workflows are rebuilt natively in HubSpot.
Case UI
Source
HubSpot
Destination
Compatibility
12 of 12
objects map 1:1 between Case UI and HubSpot.
Complexity
BStandard
Timeline
48–72 hours
Overview
Case UI organizes legal practice data around cases, clients, and matter records with a flat property model suited for solo practitioners and small law firms. HubSpot structures data around Contacts, Companies, Deals, and Tickets with a property-based schema that supports custom objects and lifecycle-stage tracking. The migration carries Case UI client records, case objects, billing properties, and custom legal fields into HubSpot's object graph, mapping matter identifiers to Deals and client records to Contacts with their associated company hierarchy. HubSpot's native lifecycle stages replace Case UI's client status flags, requiring a value-mapping plan for active, pending, and closed matter states. Custom fields like statute of limitations, court jurisdiction, and billing arrangements migrate as HubSpot custom properties on the Contact or Deal object. Workflows, email templates, and legal-specific automations do not transfer — FlitStack exports Case UI workflow definitions as a rebuild reference for your HubSpot admin. We use Case UI's API and CSV exports to extract data, apply field-level transformations, and load into HubSpot via the Contacts API and import tools, with a delta-pickup window capturing any records modified during cutover.
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 Case UI object lands in HubSpot, 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
HubSpot
Contact + Company
1:1Case UI client records map to HubSpot Contacts with their primary firm data as a linked Company record. Client name splits into firstname and lastname on the Contact. If the client is a business entity, the company name maps to the Company object and the contact maps as a secondary Contact under that Company.
Case UI
Client Contact Info
HubSpot
Contact properties
1:1Client email, phone, address, and website properties map directly to HubSpot Contact properties with the same names. Multiple phone numbers on a Case UI client record map to HubSpot's phone and mobilephone properties. Email addresses are validated for format and duplicates before import, while address fields are split into street, city, state, and zip components when possible. Website URLs are preserved as-is and will display in the Contact's website property.
Case UI
Client Status
HubSpot
Contact.lifecycle_stage
1:1Case UI client status values (active, pending, closed, archived) map to HubSpot lifecycle_stage values via a value-mapping table. Active maps to 'customer'; pending maps to 'lead'; closed maps to a custom 'former_client' lifecycle value; archived maps to 'evangelist' for reference.
Case UI
Case / Matter
HubSpot
Deal
1:1Each Case UI case record maps to a HubSpot Deal. The dealname uses Case UI's matter title or case number. Case-type categories (family law, criminal defense, civil litigation) map to HubSpot pipeline names or a custom deal property for routing.
Case UI
Case Status
HubSpot
Deal.stage
1:1Case UI case status values (open, pending, waiting_on_client, closed_won, closed_lost) map to HubSpot Deal stage values via per-pipeline value mapping. Stage probabilities and forecast categories are applied from HubSpot's standard stage configuration. The mapping is documented in a config file your admin can review and adjust before migration, preserving original status labels for audit purposes.
Case UI
Billing Rate / Fee Arrangement
HubSpot
Deal custom properties
1:1Case UI billing rate (hourly, flat fee, contingency) and fee amount migrate to HubSpot Deal custom properties (Billing_Type__c, Fee_Amount__c) since HubSpot has no native billing arrangement field. Original billing currency is preserved. Billing type is a picklist for straightforward reporting, and fee amounts map to the Deal's amount field with currency metadata preserved.
Case UI
Responsible Attorney
HubSpot
Deal.ownerId
1:1Case UI assigns a responsible attorney to each case. Owner resolution matches the attorney email in Case UI to a HubSpot user by email. Unmatched attorneys are flagged before migration — the firm either creates HubSpot user accounts or assigns records to a fallback owner.
Case UI
Case Custom Fields
HubSpot
Deal custom properties
1:1Statute of limitations date, court jurisdiction, opposing counsel, case number, and referral source from Case UI migrate as HubSpot custom properties on the Deal object (Statute_of_Limitations__c, Court_Jurisdiction__c, Opposing_Counsel__c, Case_Number__c, Referral_Source__c). These custom fields are created in HubSpot's UI or via API before migration, and they support date, text, and picklist types matching the original data formats. After migration, they appear on the Deal record for immediate use and reporting.
Case UI
Client-Billing Contact
HubSpot
Contact billing properties
1:1Case UI stores a separate billing contact on the client record. The billing contact name, email, and address migrate as custom properties on the HubSpot Contact (Billing_Contact_Name__c, Billing_Contact_Email__c) since HubSpot does not have a native billing contact sub-record for billing reconciliation.
Case UI
Case Activity Log
HubSpot
Deal engagements (notes, tasks, emails)
1:1Case UI activity logs, time entries, and notes migrate as HubSpot Deal engagements. Notes map to HubSpot Notes. Time entries map to Tasks with the duration recorded in the task description. Original timestamps and attorney attribution are preserved for audit and reporting.
Case UI
Document Attachments
HubSpot
Deal files
1:1Case UI document attachments on case records re-upload to HubSpot Files linked to the corresponding Deal. File size limits apply (HubSpot's 25MB per file). Inline document references in notes are downloaded and rehosted as HubSpot File attachments to preserve original file names and metadata.
Case UI
Lead Source
HubSpot
Contact.hubspot_sourcetracking
1:1Case UI stores a lead or referral source on the client record. This maps to HubSpot's hs_analytics_source field on the Contact for source reporting continuity. If Case UI uses a custom source taxonomy, it migrates as a custom pick-list field.
| Case UI | HubSpot | Compatibility | |
|---|---|---|---|
| Client | Contact + Company1:1 | Fully supported | |
| Client Contact Info | Contact properties1:1 | Fully supported | |
| Client Status | Contact.lifecycle_stage1:1 | Fully supported | |
| Case / Matter | Deal1:1 | Fully supported | |
| Case Status | Deal.stage1:1 | Fully supported | |
| Billing Rate / Fee Arrangement | Deal custom properties1:1 | Fully supported | |
| Responsible Attorney | Deal.ownerId1:1 | Fully supported | |
| Case Custom Fields | Deal custom properties1:1 | Fully supported | |
| Client-Billing Contact | Contact billing properties1:1 | Fully supported | |
| Case Activity Log | Deal engagements (notes, tasks, emails)1:1 | Fully supported | |
| Document Attachments | Deal files1:1 | Fully supported | |
| Lead Source | Contact.hubspot_sourcetracking1: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.
Case UI gotchas
No public API documentation found
On-Premise perpetual license has upgrade isolation risk
No verified public reviews or G2/Capterra feedback
HubSpot gotchas
Marketing Contacts billing model is migration-critical
Feature tier gating is not visible until onboarding
Mandatory onboarding fees inflate year-one cost
HubSpot CSV importer cannot migrate engagements or attachments
Custom objects require Enterprise and a pre-existing schema
Pair-specific challenges
Migration approach
Extract Case UI data via API or CSV export
For Case UI Cloud, FlitStack connects via Case UI's API to extract clients, cases, custom fields, and activity logs. For Case UI On-Premise, we guide your team through running the built-in CSV export for all objects. We validate record counts and field completeness against Case UI's record totals before mapping begins. Any missing records or truncated fields are flagged immediately so your team can investigate data quality in Case UI before migration.
Design HubSpot pipeline and custom property schema
Based on the Case UI case-type count, we deliver a HubSpot pipeline configuration plan — one pipeline per case type, with suggested stage names mapped from Case UI case statuses. We also produce a custom property manifest for all Case UI custom fields that have no HubSpot native equivalent, including billing_type, statute_of_limitations, court_jurisdiction, and opposing_counsel. Your HubSpot admin creates the pipelines and custom properties, or FlitStack creates them using HubSpot's API on your behalf with your approval.
Map contacts and companies, then link to deals
We migrate Case UI client records as HubSpot Contacts with their associated Company records. Client status maps to HubSpot lifecycle_stage via the value-mapping table. Then Case UI cases migrate as HubSpot Deals, linked to the Contact record via the original client_id. Responsible attorney email resolves to HubSpot user by email match; unresolved attorneys are flagged with the record for your team to assign a HubSpot owner before the final migration run.
Run a sample migration with field-level diff
A representative slice of 100–500 records migrates first — spanning contacts, companies, deals across case types, and a sample of attachments. We generate a field-level diff comparing source Case UI values to destination HubSpot values so you can verify that case types mapped to the correct pipelines, client status values routed to the expected lifecycle stages, and billing properties landed in the custom fields. Sample migration approval gates the full run.
Execute full migration with delta-pickup and rollback readiness
The full migration loads all Case UI records into HubSpot. A delta-pickup window (typically 24–48 hours after initial load) captures any records created or modified in Case UI during the cutover window so HubSpot reflects Case UI's final state at go-live. An audit log records every operation. One-click rollback is available if reconciliation against the Case UI export totals reveals discrepancies — no data is permanently committed until you approve the reconciliation report.
Platform deep dives
Case UI
Source
Strengths
Weaknesses
HubSpot
Destination
Strengths
Weaknesses
Complexity grading
Standard CRM migration. 3 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 Case UI and HubSpot.
Object compatibility
3 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
Case UI: Not publicly documented.
Data volume sensitivity
Case UI 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 Case UI to HubSpot migration scoping. Not seeing yours? Book a call.
Walk through your Case UI to HubSpot migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationAdjacent paths
Other ways to leave Case UI
Other ways to arrive at HubSpot
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.