Migrate from Enkrypt Legal-PRO to Pipedrive

Enkrypt clients map directly to Pipedrive People. Client primary contact name, email, phone, and address fields transfer as Person fields. Multiple contacts per client collapse to one primary Person record; additional contacts import as related Persons under the same Organization.

If the Enkrypt client represents a company (e.g., corporate client versus individual), it maps to Pipedrive Organization. The Organization name, website, and industry fields carry over. Legal-entity name and client-type classification migrate as custom fields on the Organization. We also map the organization's primary address to the Organization's address fields, preserving location data for territory segmentation.

Enkrypt matters map to Pipedrive Deals. Matter name becomes Deal title, matter number becomes a custom field, and matter status (open, closed, pending) maps to a Pipedrive pipeline stage. Multiple matter types in Enkrypt (litigation, transactional, advisory) require separate Pipedrive pipelines with their own stage sets.

Enkrypt matter statuses (Active, Pending Review, Closed, On Hold) map to Pipedrive stage names per pipeline. Stage probability does not apply to legal matters but can be set to zero for informational purposes. We preserve original status-transition timestamps as custom datetime fields.

Pipedrive has no trust accounting module. Enkrypt trust account balances and ledger entries are preserved as custom fields on the Organization or Deal for reference only — they cannot drive Pipedrive workflows or reporting. Rebuilt trust accounting must use a dedicated legal billing tool post-migration.

Enkrypt invoices and billing records have no direct Pipedrive equivalent. Invoice numbers, amounts, and billing dates are preserved as Activities (Notes) attached to the relevant Deal or Person. Actual invoice generation and payment tracking must be rebuilt in a billing tool or Pipedrive's billing integration.

Enkrypt documents attached to matters download and re-upload to Pipedrive Files associated with the corresponding Deal. File metadata (document type, upload date, author) is preserved in a custom field on the Pipedrive File reference. Large document libraries increase migration time due to download-reupload overhead.

Enkrypt's secure client messaging threads do not have a native Pipedrive equivalent. Thread summaries (most recent message date, participant count, thread topic) migrate as Activities on the related Person record. Individual message content requires a separate export and reference handling.

Enkrypt appointments and calendar events map to Pipedrive Activities (type: Call, Meeting, or Task) with original start/end times, attendees, and owner preserved. Cancelled appointments migrate with status flagged in a custom field. If an appointment repeats on a schedule, the recurrence pattern is noted in the activity description, and a series identifier links related activities for reference.

Enkrypt staff members resolve to Pipedrive users by email match. Unmatched users are flagged before migration — teams either invite them to Pipedrive first or assign records to a fallback owner. Role-based visibility settings are not migrated and must be configured in Pipedrive separately.

Enkrypt custom fields on matters (e.g., Court District, Opposing Counsel, Matter Type subcategory) require Pipedrive custom fields on the Deal object. Custom field types (text, picklist, date, number) are matched during schema setup. Pipedrive's hashed key system means custom field names must be created with exact spelling before migration.

Enkrypt custom client properties (e.g., Client Classification, Referral Source, Billing Arrangement) migrate as Pipedrive custom fields on Person or Organization. Field type mapping applies: picklist values require Pipedrive custom field options created before import. We also preserve any default value set in Enkrypt, applying it to the Pipedrive custom field defaults. This ensures that records without an explicit value inherit the original default.