Migrate from Captorra to HubSpot

Captorra case records require a HubSpot custom object or ticket mapping — there is no native legal-case equivalent

HubSpot's standard objects (contacts, companies, deals, tickets) were not designed for legal case management. Captorra case records — with fields for case type, assigned attorney, opposing counsel, court jurisdiction, and case-stage history — cannot map directly to any standard HubSpot object. We create a Case custom object (HubSpot Enterprise required) with properties for every Captorra case field. On Starter or Professional plans where custom objects are unavailable, we map cases to HubSpot tickets with extensive custom fields — but ticket pipelines do not support legal-stage semantics like 'discovery', 'deposition', or 'settlement'. Your team should decide on the target object before migration planning begins.

Captorra referral-source tracking collapses to a contact or company property — multi-source leads require consolidation

Captorra tracks referral source per lead with the ability to record multiple referral origins. HubSpot's contact model stores a single primary source in hs_analytics_source_data_1 or a custom pick-list property. If a Captorra lead has multiple referral sources, we preserve the primary source on the contact and store secondary sources in a custom multi-select property (referral_sources__c). Your HubSpot admin should decide whether the full referral chain is needed for reporting or whether a single primary source suffices. This decision affects the field mapping configuration before migration runs.

Captorra staff/attorney assignments may not have HubSpot user accounts — unmatched owners require fallback assignment

Captorra staff members (attorneys, paralegals, intake specialists) are assigned to case records. Not all Captorra staff will have HubSpot user accounts, especially in firms where Captorra is used only for intake while attorneys use a separate practice-management system. We resolve Captorra staff by email against HubSpot users; staff without a matching HubSpot account are flagged before migration. Unmatched staff assignments are preserved as a custom contact-lookup property on the case record (assigned_attorney__c) rather than a HubSpot owner field. Your firm must decide whether all case-assigned staff need HubSpot access before migration day.

Captorra intake forms and workflow automation do not migrate — legal-process logic requires manual rebuild in HubSpot

Captorra workflows handle intake routing, form-field logic, case-stage triggers, and attorney assignment rules. HubSpot has no equivalent workflow translation — every Captorra workflow, intake form, and automation must be manually rebuilt in HubSpot's workflow builder or HubSpot's form tool. We export your Captorra workflow definitions as a structured reference document that your HubSpot admin can use to recreate logic. This is a configuration task outside the data-migration scope and should be planned in parallel with — not after — the data migration.

Captorra Microsoft Office and legal-tool integrations have no HubSpot equivalent — connected workflows break

Captorra integrates with Microsoft Office (Outlook, Word) and legal-specific tools through its partner ecosystem. HubSpot does not natively replicate these integrations. Documents stored in Captorra's file management system can be migrated as HubSpot Files, but the integration links to Microsoft Office applications (mail merge, document generation) do not transfer. Any Zapier or native integrations between Captorra and other tools will need to be rebuilt using HubSpot's integration ecosystem or the HubSpot API. An integration audit before migration helps identify which connected workflows need alternative solutions.