Migrate from Lexis Affinity to HubSpot

Lexis Affinity clients map directly to HubSpot contacts. We map client name, email, phone, address, and organizational affiliation as standard HubSpot contact properties. For clients that are organizations rather than individuals, we create a HubSpot company record first and link the contact via the company association.

When a Lexis Affinity client represents a law firm, corporation, or government entity, we create a HubSpot company record. The company name, domain, industry, and address map to HubSpot company properties. Individual attorney contacts link to the company via HubSpot's contact-company association model.

Lexis Affinity matters (cases) map to HubSpot deals. The matter name becomes the deal name. Matter status (Open, Closed, Pending) maps to HubSpot deal stage via value mapping. Practice area, responsible attorney, court/jurisdiction, and filing date become HubSpot custom properties since HubSpot deals have no native legal fields.

Lexis Affinity matter status values (Open, On Hold, Pending Court, Closed, Archived) map to HubSpot deal stage values via value-by-value mapping. Each Lexis Affinity status maps to a corresponding HubSpot pipeline stage. Stage change timestamps are preserved as HubSpot custom datetime fields for audit continuity.

Lexis Affinity trust account balances have no native HubSpot equivalent. We create a numeric custom property (Trust_Balance__c) on the deal record and populate it with the Lexis Affinity trust ledger balance at migration time. Trust accounting ledgers requiring line-item detail are exported as a separate reference file.

Lexis Affinity time entries map to HubSpot activities (tasks) with Type='Time Entry'. We preserve the original date, duration, description, billing code (LEDES), and billable/non-billable flag as task properties. Billable hours sum to the deal's billed_amount custom property. The LEDES code property enables firms to maintain LEDES 1998B or LEDES 2018 billing code references for e-billing to insurance carriers and clients after migration.

Lexis Affinity invoices carry amounts, status (Draft, Sent, Paid, Overdue), and payment dates. We create HubSpot custom properties (Invoice_Amount__c, Invoice_Status__c, Invoice_Date__c, Payment_Date__c) on the deal. Invoice line items are preserved in a CSV reference export since HubSpot has no native billing line-item model.

Lexis Affinity documents attached to matters are downloaded and re-uploaded to HubSpot Files. Each file is associated to the corresponding deal via HubSpot's file-association mechanism. Document names and matter folder context are preserved in HubSpot file properties. The original Lexis Affinity folder path (e.g., Correspondence, Pleadings, Discovery) is stored as a custom property on the HubSpot file for reference and reconstruction of folder logic.

Lexis Affinity calendar events (court dates, deadlines, appointments) map to HubSpot meetings with original start/end times preserved. Lexis Affinity tasks map to HubSpot tasks with original due dates and subject matter intact. Owner resolution by email match ensures calendar events and tasks land with the correct HubSpot user account. Unresolved owners are flagged in a pre-migration report for manual assignment.

Lexis Affinity notes attached to matters or clients map to HubSpot notes. Rich-text formatting including bold, italics, bullet points, and hyperlinks is preserved where HubSpot's note rendering supports it. Original create timestamps and owner email are carried over to maintain the note's audit trail and provenance in HubSpot. The source matter ID is stored for traceability.

Lexis Affinity matter custom fields (e.g., case number, opposing counsel, jurisdiction code, insurance carrier) create HubSpot deal custom properties. Field type awareness drives the mapping: text fields map to single-line text, dates map to date pickers, currency amounts map to number fields with decimal precision.

Lexis Affinity conflict check records document the results of legal conflict-of-interest searches against clients, parties, and related entities. HubSpot has no conflict check equivalent and cannot represent conflict search results natively. We export all conflict check records as a structured CSV reference file for manual re-entry or integration with a third-party legal conflict-check tool (such as CounterSight, Foundation, or Reveal) post-migration. Conflict checks must be re-run in your chosen tool before new matters proceed.

Lexis Affinity workflows automate legal processes such as matter intake routing, conflict-check triggers, billing rule automation, and court deadline calendar notifications. HubSpot's workflow engine cannot import Lexis Affinity automation definitions and does not support conflict-check logic natively. We export all workflow definitions as a structured JSON reference document including trigger conditions, action sequences, and rule logic that your HubSpot admin can use as a rebuild specification in HubSpot's workflow tool.