Migrate from Enkrypt Legal-PRO to HubSpot

Enkrypt client records map directly to HubSpot Contacts. Client name, email, phone, address, and firm association fields map to their HubSpot Contact equivalents. Primary matter count preserved as a custom number field on the contact for reporting parity. We also ensure that any client identifiers from Enkrypt are stored in a custom property for reference and deduplication.

Enkrypt matters map to HubSpot Deals using a dedicated matter-status pipeline. The HubSpot pipeline stages replicate Enkrypt's matter lifecycle: Intake, Active, Pending, Closed. Matter type (e.g., litigation, corporate, family) maps to the deal name prefix or a custom pick-list field.

Enkrypt matter records may list multiple client contacts (e.g., opposing counsel, co-counsel, key stakeholders). These merge into HubSpot Deal Contact Roles — each contact associated to the deal with a role label (e.g., Primary Client, Opposing Party, Co-Counsel). If a matter includes contacts with multiple roles, we store the additional role information in a custom multi-select field on the deal to preserve full relationship context.

Enkrypt's threaded secure messages map to HubSpot Engagements. The most recent message body lands as a HubSpot Email engagement on the contact record; message history preserved as a chronological series of Note records attached to the matter-deal for audit continuity.

Enkrypt appointment records map directly to HubSpot Meetings. Original start time, end time, location, description, and attendee list (as HubSpot contact associations) are preserved. Attorney owner maps to the HubSpot Meeting owner. Any recurring appointment series are split into individual meeting records, each linked to the same deal to maintain scheduling history.

Enkrypt document attachments on matters download and re-upload to HubSpot Files attached to the corresponding deal record. File size limits apply per HubSpot tier (25MB per file on most plans). Original file names and upload timestamps are preserved in the HubSpot file metadata.

Enkrypt trust accounting balances and time-entry amounts do not have a native HubSpot equivalent. We create custom number fields on the Deal object: Total_Billed_Amount__c, Time_Entries__c, Trust_Balance__c. Billable hours summary maps to a custom field for reporting alongside deal amount. These custom fields also allow for detailed billing reports in HubSpot's analytics and can be used to trigger workflow actions when certain thresholds are met.

Enkrypt firms or organizations linked to clients map to HubSpot Companies. Company name, address, industry, and website fields transfer directly. Multi-contact firms (multiple attorneys at the same firm) associate the Company to all relevant Contact records. If an Enkrypt firm record contains additional properties such as tax ID or billing terms, these are stored as custom properties on the HubSpot Company for completeness.

Enkrypt matter status values (e.g., Open, Pending Review, Closed Won, Closed Lost) map to HubSpot Deal Stage values per the matter pipeline. Each status-to-stage mapping is defined value-by-value during migration planning to ensure reporting alignment. We also validate that any custom status labels in Enkrypt are accounted for and create corresponding stage options in HubSpot to avoid data loss.

Enkrypt matter owners resolved by email match against HubSpot Users. Unmatched owners are flagged before migration — your team either invites them to HubSpot or assigns their matters to a fallback owner. No deal lands without a HubSpot OwnerId. During the final audit, we verify that each OwnerId is active and has the appropriate CRM permissions to own deals.

Enkrypt custom fields on matters (e.g., Court District, Case Number, Assigned Judge) create HubSpot custom properties on the Deal object. Field data types are preserved: text fields to text, pick-lists to pick-lists, dates to date fields. Custom property API names use HubSpot's internal naming convention.

Enkrypt leads or prospects that have not yet opened a matter map to HubSpot Contacts with lifecycle_stage set to 'lead'. When a matter is opened, the contact's lifecycle stage updates to 'customer' via a HubSpot workflow trigger. This automation ensures that the contact record reflects the current relationship status and enables targeted communications based on the client lifecycle.