CRM migration

Migrate from Case UI to HubSpot

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

Case UI logo

Case UI

Source

HubSpot

Destination

HubSpot logo

Compatibility

100%

12 of 12

objects map 1:1 between Case UI and HubSpot.

Complexity

BStandard

Timeline

48–72 hours

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

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.

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

HubSpot logo

HubSpot

What's pulling them in

  • Lowest barrier to entry of any major CRM — the free tier with unlimited contacts lets teams validate fit before committing to a paid plan, according to G2 and Capterra reviewers.
  • Native integration between the CRM and sales engagement tools (sequences, email tracking, dialer) means no separate sync configuration, a theme across G2 Sales Hub reviews.
  • Pipeline visualization, deal tracking, and automated workflows are consistently praised as intuitive and easy to set up without developer involvement.
  • Strong onboarding for new team members — reviewers on Capterra and G2 highlight how quickly new reps become productive without formal training.
  • The HubSpot platform ecosystem (Marketing, Sales, Service, CMS hubs) allows growing companies to consolidate tools without building new integrations.

Object mapping

How Case UI objects map to HubSpot

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

maps to

HubSpot

Contact + Company

1:1
Fully supported

Case 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

maps to

HubSpot

Contact properties

1:1
Fully supported

Client 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

maps to

HubSpot

Contact.lifecycle_stage

1:1
Fully supported

Case 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

maps to

HubSpot

Deal

1:1
Fully supported

Each 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

maps to

HubSpot

Deal.stage

1:1
Fully supported

Case 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

maps to

HubSpot

Deal custom properties

1:1
Fully supported

Case 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

maps to

HubSpot

Deal.ownerId

1:1
Fully supported

Case 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

maps to

HubSpot

Deal custom properties

1:1
Fully supported

Statute 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

maps to

HubSpot

Contact billing properties

1:1
Fully supported

Case 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

maps to

HubSpot

Deal engagements (notes, tasks, emails)

1:1
Fully supported

Case 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

maps to

HubSpot

Deal files

1:1
Fully supported

Case 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

maps to

HubSpot

Contact.hubspot_sourcetracking

1:1
Fully supported

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

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

HubSpot logo

HubSpot gotchas

High

Marketing Contacts billing model is migration-critical

High

Feature tier gating is not visible until onboarding

Medium

Mandatory onboarding fees inflate year-one cost

Medium

HubSpot CSV importer cannot migrate engagements or attachments

Medium

Custom objects require Enterprise and a pre-existing schema

Pair-specific challenges

  • HubSpot lifecycle stages require value-mapping from Case UI client status

    Case UI tracks client status as a flat flag (active, pending, closed, archived) on the client record. HubSpot has no native equivalent — it uses lifecycle_stage with values subscriber, lead, MQL, SQL, customer, evangelist. We map Case UI's client status to HubSpot lifecycle stages via a value-mapping table during migration, but the firm should review which lifecycle stage best represents each Case UI status before migration runs. Mis-mapping can affect HubSpot's contact reporting and marketing automation enrollment triggers.

  • Case UI case types map to HubSpot pipelines, requiring pre-migration pipeline setup

    HubSpot's deal pipeline model lets each pipeline have its own stage names and probabilities. If Case UI has multiple case types (family law, criminal defense, civil litigation), each type becomes a separate HubSpot pipeline. Pipelines must be created in HubSpot before data lands — the migration plan delivered by FlitStack includes a pipeline configuration blueprint based on the Case UI case-type count. Firms with more than five case types may need to consolidate types into fewer pipelines to keep HubSpot's UI manageable for their team.

  • Billing arrangements and custom legal properties need HubSpot custom field creation

    Case UI stores legal-specific properties — statute of limitations, court jurisdiction, billing type, opposing counsel, referral source — that have no HubSpot native equivalents. These migrate as HubSpot custom properties on the Deal object (or Contact for client-level properties). Custom fields must be created in HubSpot before migration, or FlitStack creates them as part of the migration schema setup. Custom property counts affect pricing: setups with more than 50 custom properties across objects fall into the upper pricing tier.

  • Document attachments re-uploaded to HubSpot Files lose Case UI's folder hierarchy

    Case UI organizes documents by case folder structure. HubSpot Files stores attachments at the record level (Contact, Deal, Ticket) without a native folder hierarchy per object. We re-upload all Case UI case attachments to HubSpot Files linked to the corresponding Deal, but the folder tree is flattened. Firms that rely on a specific document organization should export the Case UI folder structure separately and recreate it in HubSpot's file manager or a connected document storage tool post-migration.

  • On-Premise Case UI requires CSV export instead of API extraction

    Case UI On-Premise ($1,499 perpetual license) does not expose a public API for automated data extraction. Migration uses Case UI's built-in CSV export for clients, cases, and custom fields. Multi-file CSV exports require additional reconciliation to link client IDs to case records before field mapping can proceed. Firms on On-Premise should run a full export during the planning phase to confirm data completeness before committing to migration timing. And ensure all field names are exported correctly for mapping.

Migration approach

Six steps for a successful Case UI to HubSpot data migration

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

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

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

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

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

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.
HubSpot logo

HubSpot

Destination

Strengths

  • Genuinely useful free CRM tier with no seat limit on contact records.
  • All-in-one sales engagement layer (sequences, email tracking, calling, dialer) embedded natively in the CRM, eliminating a separate integration.
  • Intuitive interface and fast onboarding for individual reps, per G2 and Capterra reviews.
  • Workflow automation triggers across contacts, deals, and tickets with a visual builder.
  • API coverage for all standard objects including custom objects at Enterprise tier.

Weaknesses

  • Pricing model is contact-based at the marketing layer — importing all records as marketing contacts can multiply the monthly bill by 4×.
  • Feature tier cliffs are frequent surprises: sequences, calling, advanced reporting, and quoting are all gated, often requiring plan upgrades mid-implementation.
  • Mandatory onboarding fees at Professional ($1,500) and Enterprise ($3,500) are not prominently disclosed on the pricing page.
  • API rate limits are restrictive for bulk migration — burst limits of 100-200 req/10sec and search endpoint limits of 4 req/sec require careful job queuing.
  • Custom objects, additional pipelines, and advanced forecasting are Enterprise-only, making cost projections difficult for growing teams.

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

  • 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 HubSpot 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 HubSpot data migrations

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

Can't find your answer?

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 consultation

Most Case UI to HubSpot migrations complete in 48–72 hours of clock time for firms with under 25,000 records across clients, cases, and activities. Larger firms with 100,000+ records or multiple case types requiring separate HubSpot pipelines extend to 5–8 days. The longest planning step is designing the HubSpot pipeline and custom property schema before data extraction begins — that work runs in parallel with Case UI data review.

Adjacent paths

Related migrations to explore

Ready when you are

Move from Case UI.
Land in HubSpot, 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