Skip to content
Get a quote

MyCase to HubSpot migration

Moving from MyCase to HubSpot transforms your law firm's case-centric data into HubSpot's contact-centric CRM model. FlitStack AI maps every client contact, matter, custom field, and document attachment — preserving original create dates and attorney assignments so your HubSpot reporting reflects the full engagement history from day one.

Short answer

FlitStack AI migrates contacts, companies, deals, custom properties on deals and custom properties on contacts from MyCase to HubSpot, with their history and the associations between records. Every field is mapped and validated, a sample run is checked with you before the full migration, and the whole move can be rolled back in one click. Typical timeline: 48–72 hours for under 25,000 records.

By

Source MyCase
DestinationHubSpot
ContactCompanyDealCustom Properties on DealCustom Properties on Contact
Mapped field by field · sample run · one-click rollback

What moves from MyCase to HubSpot?

MyCase organizes legal practice data around matters (cases), clients, and documents with a firm-centric data model optimized for law firms.

Read the full summary

HubSpot organizes around contacts, companies, deals, and tickets in a marketing-and-sales CRM model. These fundamental architectural differences drive most of the mapping complexity: MyCase's case-to-contact relationships become HubSpot's contact-to-company associations, and MyCase's matter statuses (Open, Pending, Closed) map to HubSpot's deal pipeline stages or custom pick‑list fields. We migrate contacts, companies, matters, custom fields, documents, calendar events, and user assignments while preserving original create dates, timestamps, and attorney assignments so HubSpot reporting reflects the full engagement history from day one. We do not migrate MyCase workflows, billing configurations, QuickBooks sync settings, or court e‑filing integrations — those are destination‑side rebuilds. Our migration mechanism reads from MyCase's API (rate‑limited at 25 requests per second per the API documentation) and writes to HubSpot's REST API, running a sample migration first to validate field‑level accuracy and then executing a delta‑pickup window before final cutover to capture any changes made during the transition.

direct

Contact (Client) → Contact

MyCase clients map directly to HubSpot contacts.

How it maps

Each client contact record migrates with name, email, phone, address, and primary matter association. Client type (individual vs. business) determines whether a Company record is also created in HubSpot. If the client type is Business, FlitStack also creates a corresponding Company record and links the contact to it via a primary association.

split

Contact (Business Client) → Company

When MyCase contact type is 'Business', the organization name maps to a HubSpot Company record.

How it maps

The individual contact at that business maps as a HubSpot Contact linked to the Company via primary association. If multiple individuals exist for the same organization, each becomes a separate Contact record, all associated with the same Company.

transformed

Matter (Case) → Deal

MyCase matters map to HubSpot Deals.

How it maps

Matter status (Open, Pending, Closed, On Hold) maps to a HubSpot Deal stage via value mapping. Matter number and case type are preserved as custom properties on the Deal record. All matter-level custom fields are also transferred as custom properties on the Deal, preserving data such as practice area, court jurisdiction, and opposing counsel.

custom_field_required

Matter Custom Fields → Custom Properties on Deal

Any MyCase custom fields defined on a matter (e.g., practice area, court jurisdiction, opposing counsel) become HubSpot custom properties on the Deal.

How it maps

Field type is preserved: text, number, date, and pick‑list map to their HubSpot equivalents. If a custom field contains a list of values, FlitStack creates a corresponding pick‑list property in HubSpot and maps each value individually.

custom_field_required

Contact Custom Fields → Custom Properties on Contact

MyCase custom fields on contacts (e.g., referral source, client since date, bar number for attorney contacts) become HubSpot contact custom properties.

How it maps

Client‑specific metadata is preserved as read‑only or editable custom properties based on field settings. If a contact has multiple values for a pick‑list field, each value is imported as a separate entry in the HubSpot property.

direct

Document / Attachment → HubSpot Files

MyCase Drive files attached to matters are downloaded and re-uploaded to the corresponding HubSpot Deal record.

How it maps

File size limits apply (HubSpot default 25MB per file). Folder hierarchy in MyCase Drive is not preserved — flat file list on the Deal record.

What moves12 objects
MyCaseHubSpot
  • ContactContact1:1
  • ContactCompanysplit
  • MatterDealtransformed
  • Matter Custom FieldsCustom Properties on Dealtransformed
  • Contact Custom FieldsCustom Properties on Contacttransformed
  • DocumentHubSpot Files1:1

+ 6 more in the mapping below

How MyCase and HubSpot differ

The differences that decide how each record is mapped. These are what a CSV export and a native importer don't resolve for you.

DimensionMyCaseHubSpot
Primary data entityMatter (Case) — matter_id, matter_name, status, responsible_attorneyContact or Deal — lifecycle stage, deal stage, owner
Record naming conventionMatter (matter_name, matter_number) / Client (contact_id)Contact (firstname, lastname) / Company (name) / Deal (dealname)
Custom fieldsCustom fields per object, accessible via API as custom_field_* keysCustom properties with hubspot_ prefix in API, custom properties UI in CRM
Document storageMyCase Drive (drag-and-drop file management per matter)HubSpot Files (re-uploaded to contact or company records)
User/owner modelUsers with roles (Attorney, Paralegal, Admin) assigned per matterUsers with HubSpot roles; owner_id assigned to contacts/deals
Billing integrationQuickBooks Online sync; time entries and invoicing native to MyCaseNo native billing; integrations rebuilt separately
API rate limit25 requests per second per client (MyCase API documentation)Tiered rate limits by HubSpot plan; 100+ requests/second on Enterprise

MyCase to HubSpot field mapping

The 30 most-used fields of 31 mapped for this pair. Custom fields are added from your own schema during scoping. Download the full mapping (CSV) ↓ or open it in the field mapping template.

Field mapping5 shown
MyCaseHubSpot
  1. first_nameContact firstnameContact
  2. last_nameContact lastnameContact
  3. emailContact emailContact
  4. phoneContact phoneContact
  5. mobile_phoneContact mobilephoneContact
MyCase fieldHubSpot fieldMappingNote
Contact.first_nameContact.firstnamedirect
Contact.last_nameContact.lastnamedirect
Contact.emailContact.emaildirect
Contact.phoneContact.phonedirect
Contact.mobile_phoneContact.mobilephonedirect
Contact.addressContact.addressdirect
Contact.cityContact.citydirect
Contact.stateContact.statedirect
Contact.zip_codeContact.zipdirect
Contact.company_nameCompany.nametransformedBusiness-type contacts generate a Company record; individual contacts may link to an existing Company or remain unassociated.
Contact.client_typeContact.contact_typevalue_mappingMyCase client type values (Individual, Business, Government) map to HubSpot contact property values.
Contact.created_dateContact.createdatecustom_field_requiredOriginal create date preserved as a custom datetime field since HubSpot CreatedDate is set at migration time.
Contact.mycase_idContact.hs_object_idcustom_field_requiredMyCase contact ID stored on HubSpot record for traceability and delta-run de-duplication.
Matter.matter_nameDeal.dealnamedirect
Matter.matter_numberDeal.Matter_Number__ccustom_field_requiredMatter number stored as a custom text field for reference and reconciliation.
Matter.statusDeal.dealstagevalue_mappingMyCase status values (Open, Pending, On Hold, Closed Won, Closed Lost) map to HubSpot Deal stage values via value mapping.
Matter.matter_typeDeal.Matter_Type__ccustom_field_requiredPractice area or matter type preserved as a custom pick-list field on the Deal.
Matter.responsible_attorneyDeal.owner_idtransformedAttorney resolved by email match to HubSpot user; unmatched attorneys flagged for manual assignment.
Matter.open_dateDeal.closedatetransformedMatter open date mapped to Deal close date field; verify business meaning with your team.
Matter.descriptionDeal.descriptiondirect
Matter.mycase_idDeal.Source_System_ID__ccustom_field_requiredMyCase matter ID stored on Deal for traceability and delta-run de-duplication.
Matter.created_dateDeal.Original_Create_Date__ccustom_field_requiredOriginal matter create date preserved as a custom datetime for reporting continuity.
Document.file_nameFile.namedirect
Document.file_urlFile.urltransformedFiles downloaded from MyCase Drive and re-uploaded to HubSpot Files; original URL not preserved.
Calendar.event_titleEngagement.subjectdirect
Calendar.start_timeEngagement.hs_meeting_start_timedirect
Calendar.end_timeEngagement.hs_meeting_end_timedirect
Calendar.attendeesEngagement.hs_attendeesdirect
Task.task_titleEngagement.subjectdirect
Task.due_dateEngagement.hs_timestampdirect

What to watch for in a MyCase to HubSpot migration

The issues we plan around on this pair: limits and data-model gaps that the official import tools leave to you.

high

MyCase billing and time entries have no HubSpot equivalent

MyCase stores time entries, invoices, flat-fee billing records, and IOLTA trust accounting data that has no direct equivalent in HubSpot CRM.

How we handle it

HubSpot has no native billing, invoicing, or trust accounting model. FlitStack preserves time entry history as notes on the associated Deal record, but the financial records themselves remain in MyCase. Firms must decide whether to keep MyCase active for billing purposes or migrate to a separate accounting platform post-migration. This is a high-impact decision point before migration scoping.

high

Matter-to-contact relationships require explicit mapping logic

MyCase permits a single contact to be linked to multiple matters (for example, a client with three active cases).

How we handle it

HubSpot's DealContactRelation object supports such many‑to‑many links but each association must be created as a distinct junction record. During migration FlitStack creates a Deal‑to‑Contact link for every matter‑contact pair present in MyCase. If a contact in your data is associated with more than ten matters, the migration process runs extra validation checks to confirm that each junction record is generated correctly and that no associations are dropped or duplicated.

medium

MyCase custom fields per matter require destination custom property creation

MyCase's custom field model allows firms to define arbitrary custom fields on matters (e.g., Court_Jurisdiction__c, Opposing_Counsel__c, Trial_Date__c).

How we handle it

HubSpot requires these to be pre-created as custom properties on the Deal object before data lands. The field type must match: MyCase text fields become HubSpot text properties, pick‑lists become HubSpot pick‑list properties. If your MyCase setup has more than 30 custom matter fields, pre‑creating all of them in HubSpot before migration day is the longest planning step.

medium

MyCase API rate limit constrains migration throughput

MyCase's API documentation sets a rate limit of 25 requests per second per client.

How we handle it

When migrating 25,000 or more matter records that carry multi‑field payloads, the limit extends the overall migration duration considerably. FlitStack respects this ceiling by throttling outbound calls and automatically retrying any HTTP 429 responses with exponential backoff. For large‑volume transfers the migration may be split across several windows or scheduled during off‑peak hours so that each batch completes within the allowed request rate. This approach keeps the process stable and avoids hitting the limit mid‑run.

low

QuickBooks sync configuration does not migrate

MyCase's bidirectional QuickBooks Online sync — encompassing chart of accounts mapping, invoice templates, and payment‑recording rules — is a MyCase‑specific integration that cannot be replicated directly in HubSpot.

How we handle it

If your firm depends on this sync for accounts payable, trust accounting, or client billing, you will need to assess HubSpot's separate QuickBooks integration after migration. Until that alternative workflow is tested and confirmed functional, MyCase should remain active for all billing activities to avoid interruption of your accounting processes.

How the migration runs

  1. Audit MyCase data and confirm HubSpot schema readiness

    FlitStack connects to MyCase via API using your credentials and inventories all contacts, matters, custom fields, documents, calendar events, and user accounts.

    What this step covers

    We deliver a data audit report listing record counts per object, custom field definitions, and matter-contact association counts. You then create the corresponding custom properties in HubSpot for any MyCase custom fields that don't have a direct HubSpot equivalent. This step confirms scope and flags any data quality issues (duplicate contacts, missing email addresses) before migration begins.

  2. Resolve users and attorney assignments by email

    MyCase user accounts (attorneys, paralegals, admins) are matched against HubSpot user email addresses.

    What this step covers

    FlitStack generates a match report identifying which MyCase users have a corresponding HubSpot user and which do not. Unmatched users are assigned to a fallback HubSpot user or held for manual owner assignment post‑migration. No Deal or Contact lands without a valid HubSpot owner. During matching, FlitStack also records the original MyCase role for audit purposes, and if a fallback owner is used, the original attorney name is stored in a custom property on the record.

  3. Run sample migration with field-level diff

    A representative slice of records — typically 100–300 contacts and 50–100 matters — migrates to HubSpot in a test environment.

    What this step covers

    FlitStack generates a field-level diff report comparing source MyCase values against destination HubSpot values for every mapped field. You review the diff to verify matter status mapping, contact-company associations, custom property values, and owner assignments before the full migration runs.

  4. Execute full migration with delta-pickup window

    The full migration runs against HubSpot, respecting MyCase's 25 req/s API rate limit.

    What this step covers

    Documents are downloaded from MyCase Drive and re-uploaded to HubSpot Files, linked to the corresponding Deal records. A delta-pickup window (24–48 hours after initial run) captures any records modified in MyCase during the migration window. FlitStack's audit log records every operation, and one-click rollback is available if reconciliation fails.

  5. Validate record counts, associations, and file links

    Post‑migration, FlitStack generates a validation report comparing MyCase source counts against HubSpot destination counts for contacts, companies, deals, engagements, and files.

    What this step covers

    Association counts (matter‑to‑contact links) are spot‑checked against the source, and a sample of migrated files is opened to verify readability. The report also includes field‑level reconciliation for key properties such as status, owner, and custom fields. You then confirm the deal pipeline view in HubSpot matches the expected matter distribution before signing off. Any discrepancies are investigated and corrected before the migration is marked complete.

MyCase HubSpot
  1. Connect
  2. Map
  3. Sample
  4. Migrate
  5. Verify
  • Contacts48,210 / 48,210 Done
  • Companies9,134 / 9,134 Done
  • Deals6,377 / 11,920 In progress
Example run
Restore points · HubSpotRollback ready
  1. Before sample runRestore point 01Restore
  2. Before full migrationRestore point 02Restore
  3. After verificationRestore point 03Current
Example

How long it takes, and what drives the quote

48–72 hours for under 25,000 recordsTypical, smaller accounts
7–10 days for over 100,000 records or heavy custom-field setupsLarge or heavily customised accounts

A quote scales with record count (contacts, matters, companies), custom field count on each object, and the complexity of matter-to-contact relationship resolution. MyCase setups with 50+ custom fields per matter or complex multi-contact matter structures fall in the upper range because each relationship requires explicit mapping logic. Standard matter fields (status, type, responsible attorney) map directly; billing-specific fields and QuickBooks sync configuration do not migrate and are excluded from scope. A discovery call confirms the exact field inventory before quoting. The final price is confirmed after reviewing the data extract and any data‑cleaning steps required. Every quote is scoped with you; there is no self-serve pricing.

Get a quote for MyCase to HubSpot →

Why teams move from MyCase to HubSpot

  • MyCase is built for law firms and caps out on marketing automation and sales pipeline features. Teams that need HubSpot's inbound marketing tools, sales forecasting, and Breeze AI capabilities can't access those in MyCase without a full platform switch. The legal-centric data model makes it difficult to run standard sales or marketing workflows that HubSpot handles natively.
  • Growing firms report that MyCase's integration ecosystem is limited compared to HubSpot's marketplace of 1,000+ integrations. When the firm needs Salesforce, Marketo, or advanced BI tools that MyCase doesn't support natively, migration becomes a prerequisite for the rest of the tech stack.
  • MyCase billing is tightly coupled to QuickBooks Online — firms that want to move away from QuickBooks or use HubSpot's native billing integrations find themselves constrained. The one-way sync behavior (documented in MyCase reviews) creates reconciliation work that compounds over time.
  • Post‑acquisition by AffiniPay (parent of LawPay), some law firms have raised concerns about the long‑term product roadmap and pricing trajectory for MyCase. HubSpot, as a large independent public company, provides a different risk profile for firms that prioritize sustained platform investment, transparent pricing, and a broad ecosystem of integrations. For firms evaluating long‑term CRM commitments, HubSpot's scale and market position may offer greater confidence in future development and support.

Questions, answered

MyCase to HubSpot migration questions

How long does a MyCase to HubSpot migration take?

Most MyCase-to-HubSpot migrations complete in 48–72 hours of clock time for under 25,000 total records (contacts plus matters). Larger firms with 100,000+ records or 50+ custom matter fields extend to 7–10 days. MyCase's API rate limit of 25 requests per second is the primary throughput constraint. The longest planning step is pre-creating HubSpot custom properties to match MyCase's custom field inventory.

Will my MyCase workflows migrate to HubSpot?

No. MyCase workflows, automated task triggers, and matter templates do not migrate. HubSpot's automation model (workflows, sequences, enrollment triggers) is fundamentally different from MyCase's task-based workflow system. FlitStack can export your MyCase workflow definitions as a PDF reference document for your HubSpot admin to rebuild manually. Billing rules and QuickBooks sync configuration are also excluded — those are separate integration decisions post-migration.

What happens to MyCase billing data and time entries in HubSpot?

MyCase time entries, invoices, flat-fee billing records, and trust accounting data do not have an equivalent object in HubSpot. HubSpot has no native billing, invoicing, or trust accounting model. FlitStack preserves time entry descriptions as notes on the associated Deal for reference, but the financial records stay in MyCase. Firms must decide whether to keep MyCase active for billing or set up a separate accounting workflow using HubSpot's integrations.

Can I migrate MyCase custom fields to HubSpot?

Yes. MyCase custom fields on contacts and matters map to HubSpot custom properties. The field type is preserved: text fields become HubSpot text properties, pick-list fields become HubSpot pick-list properties, date fields become HubSpot date properties. The requirement is that these custom properties must be pre-created in HubSpot before the migration runs — FlitStack provides the full list of required custom properties based on your MyCase setup.

What happens to documents in MyCase Drive during migration?

MyCase Drive files attached to matters are downloaded and re-uploaded to HubSpot Files, linked to the corresponding Deal record. The folder hierarchy from MyCase Drive is not preserved — files land in a flat list on the Deal record. File size limits apply (HubSpot default 25MB per file). We recommend migrating documents for active matters only; archived matter documents can be migrated separately or kept in MyCase for reference.

Does the migration affect my MyCase account during cutover?

No. FlitStack uses scoped read access on MyCase via API — your team continues working in MyCase during the migration. A delta-pickup window (24–48 hours after the initial migration run) captures any matters, contacts, or calendar events modified in MyCase during the cutover. We recommend scheduling the final delta run as close to go-live as possible so HubSpot reflects MyCase's final state at switchover.

How does MyCase's QuickBooks integration affect the migration decision?

MyCase's bidirectional QuickBooks Online sync — including invoice recording, payment application, and trust accounting reconciliation — is a MyCase-specific integration. This configuration does not migrate to HubSpot. If your firm depends on QuickBooks for accounting, you will need to evaluate HubSpot's separate QuickBooks integration post-migration. Until that integration is confirmed functional, keeping MyCase active for billing-only access is the recommended approach to avoid disruption to your accounting workflow.

What happens to multi-contact matters in HubSpot?

MyCase allows a single matter to be associated with multiple contacts (e.g., opposing counsel, co-counsel, client representatives). HubSpot supports this via the DealContactRelation junction object — each matter-to-contact association migrates as a separate link between the HubSpot Deal and each related Contact. If a matter has more than 10 associated contacts, FlitStack flags this during scoping so you can decide which associations to preserve versus collapse to primary contacts only.

Get a quote

Moving from MyCase to HubSpot?

Tell us roughly how many records and objects you have. We scope the mapping and the HubSpot setup with you, then send a quote.

Get a quote