Migrate from Enkrypt Legal-PRO to HighLevel

Enkrypt's client records map directly to HighLevel Contacts, preserving name, email, phone, and address fields as-is. The original Enkrypt client identifier is stored in a custom field (Source_System_ID__c) for traceability and to support delta‑run de‑duplication. Multi‑party associations where several attorneys work on the same client surface as HighLevel contact tags rather than a native many‑to‑many relationship, ensuring each attorney retains visibility without duplicating the contact.

Enkrypt matters have lifecycle stages (Open, Pending, Closed Won, Closed Lost) that map to HighLevel Opportunity stage names per pipeline. Each matter type in Enkrypt (e.g., Litigation, Transaction, Consultation) becomes a separate HighLevel pipeline so stage pick-list values are scoped correctly.

Enkrypt matter stage names are mapped value‑by‑value to HighLevel Opportunity Stage values within each pipeline. Probability percentages and forecast category assignments are reapplied according to HighLevel's stage model, preserving the expected close rate for each stage. Stage‑entered timestamps are stored as custom datetime fields (Original_Stage_Entered__c) so historical timing data remains available for reporting after migration.

HighLevel lacks a native trust‑accounting ledger, so Enkrypt trust‑account entries (deposit, withdrawal, balance, client attribution) are migrated as a custom object (Trust_Entry__c) using the same field names and data types. Each entry is linked to the corresponding migrated Opportunity via a lookup field (Opportunity_Lookup__c). Original entry dates and amounts are preserved, but the running balance is not recalculated; your finance team must perform a three‑way reconciliation against the bank statement after migration to confirm accuracy.

Enkrypt stores documents as secure attachments. We extract file metadata (name, type, upload date, attorney owner) and write it to a custom field on the parent Contact or Opportunity. The files themselves are re-uploaded to HighLevel's file storage or to the designated Google Drive / Dropbox integration.

Enkrypt appointment records (date, time, attorney, client, matter reference) map to HighLevel Calendar events, with the appointment type prefixed to the event title for straightforward identification. Original timestamps and attorney‑owner attribution are preserved in the event’s start/end time and assigned‑user fields. After migration, HighLevel’s native calendar integration with Google Calendar and Outlook is re‑connected, and any recurring appointment series is recreated using HighLevel’s recurring‑event rules to maintain schedule continuity.

Enkrypt's encrypted messaging threads have no native HighLevel equivalent. Thread summaries (date range, participant count, last message date) are written as HighLevel Notes on the Contact record. The full thread body is preserved in an attached file for compliance reference.

Enkrypt invoice records (line items, amounts, status, payment date) are migrated as a custom object (Billing_Record__c) linked to the HighLevel Contact via a lookup field (Contact_Lookup__c). Invoice number, date, total amount, and status are stored in matching custom fields, preserving the original data for reporting. HighLevel’s built‑in invoicing is basic; firms needing advanced legal billing should integrate a third‑party platform after migration.

Enkrypt's client portal access log (login date, documents viewed, messages sent) is summarized as tags on the Contact record, using a naming convention such as Portal_Login_2023 and Doc_Viewed_<document‑type>. In addition, the original login timestamp is stored in a custom datetime field (Portal_Login_Date__c) for audit purposes. Portal access controls (role‑based permissions, session limits) are not replicated because HighLevel’s white‑label portal requires separate configuration and may use different permission models.

Enkrypt allows custom fields per matter type (e.g., Court Name, Filing Deadline, Opposing Counsel). Each custom field becomes a HighLevel custom field on the Opportunity object. Field type mapping follows Enkrypt's data types: text → string, number → number, date → date, picklist → dropdown.