Migrate from The Plaintiff to HubSpot

The Plaintiff's contact record maps 1:1 to HubSpot's contact object. Standard fields including first name, last name, email address, phone number, and job title migrate directly as HubSpot standard properties. The mapping preserves data integrity by maintaining field-level correspondence between source and destination. The Plaintiff contact ID is stored as Source_System_ID__c for traceability and to support deduplication during subsequent delta migration runs.

The Plaintiff allows a contact to have multiple associated companies with one flagged as primary. HubSpot enforces a single primary associated company. We migrate the primary company link first; secondary company associations are stored in a custom multi-select property or as HubSpot account-contact relationship records if the portal is Enterprise-tier.

The Plaintiff's company record maps to HubSpot's company object with a 1:1 field correspondence. Company name, domain, website, industry (value-mapped to HubSpot's pick-list options), number of employees, and annual revenue all migrate as standard HubSpot company properties. Industry values use the agreed value-mapping table to align with HubSpot's predefined pick-list entries. Parent-company relationships transfer via the Parent Company association field, preserving organizational hierarchies during the migration.

The Plaintiff's deal is the primary case record. Case number migrates as deal name or a custom case_number property; case title migrates as the HubSpot deal name. Deal amount maps to the Amount property. The case record holds all the legal metadata that becomes HubSpot custom properties.

The Plaintiff's case status pick-list (Active, Pending, Closed, Dismissed, Settled) maps to HubSpot deal stage values. We apply a value-by-value mapping during migration: Active maps to the earliest pipeline stage, Closed maps to a terminal Won or Lost stage depending on disposition. Stage-entered dates are preserved in custom datetime fields.

The Plaintiff's judge name field has no HubSpot native equivalent. We create a HubSpot custom text property called Judge_Name__c on the deal object. This enables filtering deals by assigned judge in HubSpot's reporting views, list filters, and workflow triggers. Legal teams can segment matters by judicial assignment for workload analysis and scheduling purposes.

Opposing counsel information migrates as a HubSpot custom text property on the deal. If opposing counsel is also tracked as a contact in The Plaintiff, we link that contact record to the deal via the contact roles feature or a custom pick-list property referencing the contact's email.

Court location migrates as a HubSpot custom text property. If The Plaintiff uses a structured pick-list for court names, we map it to a custom pick-list property in HubSpot so reporting by court jurisdiction is possible without manual data entry.

Filing date migrates as a HubSpot custom date property on the deal. HubSpot's native CreatedDate reflects the migration timestamp rather than the original filing date, so the actual filing date is preserved in Filing_Date__c. This distinction is critical for tracking case age, calculating deadlines, and maintaining audit-ready historical records that reflect the true case timeline from initiation.

Case type (contract, tort, IP, family, etc.) migrates as a HubSpot custom pick-list property on the deal. HubSpot requires pick-list options to exist before data lands, so we create all case type values as HubSpot pick-list options before the migration run. Value mapping translates each The Plaintiff case type to its corresponding HubSpot pick-list entry, enabling consistent categorization and reporting across practice areas.

The Plaintiff's call logs on a contact record map to HubSpot call engagements. The call subject, duration (as a custom number property), and disposition migrate. Original timestamps and owner assignment are preserved. Call recordings do not transfer unless The Plaintiff exposes them via a public URL in the export.

Email history attached to a contact in The Plaintiff migrates as HubSpot email engagements. The complete email record transfers including subject line, body content, timestamp, and sender/recipient details. HTML formatting is preserved to maintain original message appearance. These emails appear in HubSpot's engagement timeline on the contact record, providing full visibility into client communication history for case review and follow-up planning.

Scheduled meetings from The Plaintiff map to HubSpot meeting engagements with original start and end times preserved. Meeting title, location (as a custom property since HubSpot meetings lack a native location field), and outcome migrate. Attendees are resolved by email match against HubSpot contact and user records.

The Plaintiff's attorney and staff user records resolve to HubSpot owners by email matching. Users who exist in HubSpot receive their assigned records. Users who do not exist in HubSpot are flagged before migration so your team can invite them or assign their records to a fallback owner.