Migrate from Enkrypt Legal-PRO to Microsoft Dynamics 365 Sales

Enkrypt clients map to Dynamics 365 Accounts (for organization clients) and Contacts (for individual contacts). When a client is a law firm or corporation, it lands as an Account with the responsible attorney as a related Contact. Address, phone, and email fields migrate directly.

Enkrypt Matters do not map to any native Dynamics 365 object without customization. We create a custom Matter table on Dataverse with lookup fields to Account and Contact. Matter type, status, responsible attorney, and billing arrangement become custom fields on the Matter record. Billing-method options (hourly, flat-fee, contingency) require value mapping to a custom pick-list.

Enkrypt documents migrate as Dynamics 365 Notes with the file re-hosted as an attachment. File size limits apply (Dynamics 365 default 25MB per file). Original upload date and author migrate as custom datetime and owner fields. Folder hierarchy in Enkrypt is preserved as a custom text field on the Note.

Enkrypt's encrypted client-attorney message threads have no native Dynamics 365 equivalent. Each thread migrates as a Note with the original message body, sender, recipient, and sent-timestamp preserved in custom datetime fields. Thread-level metadata (thread ID, encryption key reference) is stored as text fields for audit purposes.

Enkrypt trust-accounting records require a fully custom Trust Account table in Dynamics 365 with fields for client ledger balance, operating account balance, IOLTA account, and transaction history. Field-level security is configured so only billing-administrator roles can view trust data. This table has no direct equivalent in standard Dynamics 365 Sales and must be provisioned before migration.

Individual trust-account transactions (deposits, withdrawals, transfers) map to a custom Trust Transaction sub-table linked to the parent Trust Account record. Transaction type (client payment, expense, IOLTA transfer) requires value mapping to the custom pick-list created in Dynamics 365. Running balance is recalculated post-migration using Dynamics 365 calculated fields.

Enkrypt billing records (invoices, payments, adjustments) do not map to standard Dynamics 365 objects. We map them to a custom Invoice Line Items table related to the Matter, with fields for billing date, amount, payment status, and invoice number. Integration with Dynamics 365 Business Central is recommended for full accounts-receivable functionality.

Enkrypt scheduling entries map directly to Dynamics 365 Appointments as Activity records. Original start and end times, attendee information (client or attorney), location details, and the appointment description all migrate into their corresponding Dynamics 365 Activity fields. The owner field resolves by matching the user's email address against existing Dynamics 365 users to maintain correct assignment and access permissions.

Enkrypt custom fields on any object become Dataverse custom fields with the __c suffix. Field type is mapped: text → String, number → Whole Number or Decimal, date → DateTime, pick-list → Picklist. Enkrypt's JSON-based custom field metadata is exported as a rebuild reference for the Dynamics 365 admin.

Enkrypt user records for attorneys, paralegals, and administrators map directly to Dynamics 365 SystemUser records using email address as the matching key. Active or inactive status in Enkrypt maps to the IsDisabled field in Dynamics 365. Role-based permissions and Enkrypt's access-level configurations require manual rebuilding in Dynamics 365 Security Roles after migration completes.

Enkrypt action items and to-dos migrate as Dynamics 365 Tasks with the original due date, priority level, assigned user, and status all preserved during transfer. The open or completed status from Enkrypt maps to the StateCode field where Open equals 0 and Completed equals 1. Any notes attached to the original task in Enkrypt also migrate along with the task record.

The responsible attorney linked to an Enkrypt matter is matched to a Dynamics 365 Contact record using email address resolution. Once matched, the Contact is associated to the corresponding Matter record through a many-to-many relationship that FlitStack creates as a Dataverse many-to-many relationship entity, enabling flexible bidirectional linking between attorneys and their assigned matters.