Migrate from Lawcus to HubSpot

Lawcus Clients map directly to HubSpot Contacts. Lawcus contact properties (name, email, phone, address, custom fields) map to HubSpot contact properties. Lawcus allows multiple roles per contact (client, opposing counsel, etc.) — HubSpot stores the primary role on the contact record and additional roles as association notes.

Lawcus Companies map to HubSpot Companies. Company name, domain, industry, phone, and address fields map directly. HubSpot's company record links to contacts and deals, replacing Lawcus's contact-company association model where companies may not exist as separate records. We preserve the Lawcus company ID as a custom property on the HubSpot company for reconciliation purposes.

Lawcus Matters are the core legal record — they contain case details, status, practice area, responsible attorney, time entries, documents, and client associations. HubSpot Deals have pipeline stages, amounts, close dates, and deal name. We map Matter status (Open/Closed/On Hold) to HubSpot deal stage values, preserve practice area as a custom deal property, and store matter ID as a custom field for traceability.

Lawcus matter statuses (Open, Pending, Closed, On Hold) map to HubSpot deal stage values. Each pipeline in HubSpot can have its own stage set — we create a standard mapping and apply value-by-value translation during migration. Stage-transition timestamps from Lawcus matter history are preserved as custom datetime fields on the HubSpot deal.

Lawcus Leads are separate from Clients and track intake prospects. In HubSpot, leads live on the Contact record with lifecycle_stage values. We map Lawcus lead status (New, Contacted, Qualified, Converted) to HubSpot lifecycle stages (subscriber, lead, MQL, SQL) so the full lead journey is preserved on the contact record.

Lawcus activities (calls, emails, meetings, notes) attached to matters or contacts map to HubSpot Engagements. Original timestamps, owners, and parent-record links (contact ID or matter ID) are preserved. HubSpot's engagement timeline on the contact record surfaces the full communication history.

Lawcus tasks tied to matters or contacts migrate as HubSpot Tasks. Task subject, due date, completion status, priority, and owner are mapped directly. Lawcus task completion timestamps map to HubSpot's task closed date field. Overdue task flags and task notes are preserved as part of the task record during migration.

Lawcus time entries track billable hours against matters. HubSpot has no native time-tracking object. We migrate time entries as a custom object linked to the HubSpot Deal (mapped from the Lawcus Matter), storing hours, date, description, and billing rate as custom properties. Alternatively, time data can be stored as a custom property on the deal record for simpler setups.

Lawcus custom fields on contacts, matters, and leads map to HubSpot custom properties. HubSpot property names use lowercase with hyphens (e.g., bar_admission_date). We create HubSpot custom properties matching Lawcus field types (text, number, date, pick-list) before migration and map values during the data load.

Lawcus users (attorneys, staff) map to HubSpot users by email match. Lawcus roles (Admin, Member, Custom) do not have a HubSpot equivalent — role-based permissions are rebuilt in HubSpot's native roles and access scopes. Unmatched users are flagged before migration for admin resolution.

Lawcus documents attached to matters or contacts are downloaded and re-uploaded to HubSpot's file storage. Files are linked to the corresponding contact or deal record. Large document volumes may require staged upload; file size limits per HubSpot's storage quotas apply.

Lawcus workflows automate matter progressions, task creation, and client communications based on legal events. HubSpot has no equivalent — workflows must be rebuilt in HubSpot's workflow builder. We export your Lawcus workflow definitions as a reference document for your HubSpot admin to use during the rebuild phase.