CRM migration
Field-level mapping, validation, and rollback between MyCase and HubSpot. We move data and schema; workflows are rebuilt natively in HubSpot.
MyCase
Source
HubSpot
Destination
Compatibility
11 of 12
objects map 1:1 between MyCase and HubSpot.
Complexity
BStandard
Timeline
48–72 hours
Overview
MyCase organizes legal practice data around matters (cases), clients, and documents with a firm-centric data model optimized for law firms. 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.
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 MyCase 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.
MyCase
Contact (Client)
HubSpot
Contact
1:1MyCase clients map directly to HubSpot contacts. 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.
MyCase
Contact (Business Client)
HubSpot
Company
1:manyWhen MyCase contact type is 'Business', the organization name maps to a HubSpot Company record. 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.
MyCase
Matter (Case)
HubSpot
Deal
1:1MyCase matters map to HubSpot Deals. 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.
MyCase
Matter Custom Fields
HubSpot
Custom Properties on Deal
1:1Any MyCase custom fields defined on a matter (e.g., practice area, court jurisdiction, opposing counsel) become HubSpot custom properties on the Deal. 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.
MyCase
Contact Custom Fields
HubSpot
Custom Properties on Contact
1:1MyCase custom fields on contacts (e.g., referral source, client since date, bar number for attorney contacts) become HubSpot contact custom properties. 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.
MyCase
Document / Attachment
HubSpot
HubSpot Files
1:1MyCase Drive files attached to matters are downloaded and re-uploaded to the corresponding HubSpot Deal record. File size limits apply (HubSpot default 25MB per file). Folder hierarchy in MyCase Drive is not preserved — flat file list on the Deal record.
MyCase
Calendar Event
HubSpot
Engagement (Meeting)
1:1MyCase calendar events associated with matters map to HubSpot engagements with type 'meeting'. Original start/end times, invitees, and matter association are preserved. Recurring events are expanded into individual engagement records. All meeting descriptions and location details are also transferred as part of the engagement record.
MyCase
Task
HubSpot
Engagement (Task)
1:1MyCase tasks linked to matters map to HubSpot engagement tasks on the corresponding Deal. Task status (complete/incomplete), due date, and assignee are preserved. Uncompleted tasks migrate as open HubSpot tasks. If a task has a description or notes, those are imported as the engagement task's body, allowing full context to be available in HubSpot.
MyCase
User (Attorney/Staff)
HubSpot
HubSpot User
1:1MyCase users are resolved by email match against HubSpot users. Responsible attorney assignments on matters become owner assignments on HubSpot Deals. Unmatched users are flagged for manual assignment before migration. If a user is unmatched, FlitStack records the original MyCase role and ID in a custom property on the record for later reference.
MyCase
Billing / Time Entry
HubSpot
No Equivalent
1:1MyCase time entries, invoices, and billing records do not map to HubSpot objects. HubSpot has no native billing or invoicing model. Time entry history is preserved as notes on the Deal for reference, but billing must be handled in MyCase or rebuilt in a separate accounting system.
MyCase
Workflow / Automation
HubSpot
HubSpot Workflows
1:1MyCase workflows and automated task triggers do not migrate. The workflow definitions can be exported as a PDF reference document for your team to rebuild in HubSpot's workflow builder. This is a manual process — FlitStack does not migrate automation logic.
MyCase
QuickBooks Sync Config
HubSpot
No Equivalent
1:1MyCase's QuickBooks Online integration configuration does not transfer. If you use QuickBooks for accounting, you will need to set up the HubSpot-QuickBooks integration separately post-migration. MyCase billing data remains in MyCase for historical reference. All billing-related records, such as invoices and trust transactions, stay in MyCase and can be exported as PDF for archiving if needed.
| MyCase | HubSpot | Compatibility | |
|---|---|---|---|
| Contact (Client) | Contact1:1 | Fully supported | |
| Contact (Business Client) | Company1:many | Fully supported | |
| Matter (Case) | Deal1:1 | Fully supported | |
| Matter Custom Fields | Custom Properties on Deal1:1 | Fully supported | |
| Contact Custom Fields | Custom Properties on Contact1:1 | Fully supported | |
| Document / Attachment | HubSpot Files1:1 | Fully supported | |
| Calendar Event | Engagement (Meeting)1:1 | Fully supported | |
| Task | Engagement (Task)1:1 | Fully supported | |
| User (Attorney/Staff) | HubSpot User1:1 | Fully supported | |
| Billing / Time Entry | No Equivalent1:1 | Fully supported | |
| Workflow / Automation | HubSpot Workflows1:1 | Fully supported | |
| QuickBooks Sync Config | No Equivalent1: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.
MyCase gotchas
QuickBooks sync is strictly one-directional
Advanced API access is tier-gated
Document migration requires offline file transfer
Bulk rate updates on historical time entries are not supported
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
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. 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.
Resolve users and attorney assignments by email
MyCase user accounts (attorneys, paralegals, admins) are matched against HubSpot user email addresses. 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.
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. 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.
Execute full migration with delta-pickup window
The full migration runs against HubSpot, respecting MyCase's 25 req/s API rate limit. 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.
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. 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.
Platform deep dives
MyCase
Source
Strengths
Weaknesses
HubSpot
Destination
Strengths
Weaknesses
Complexity grading
Standard CRM migration. 2 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 MyCase and HubSpot.
Object compatibility
2 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
MyCase: 25 requests per second per client.
Data volume sensitivity
MyCase 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 MyCase to HubSpot migration scoping. Not seeing yours? Book a call.
Walk through your MyCase 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 MyCase
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.