Migrate from Enkrypt Legal-PRO to Zoho CRM

Enkrypt Client records map 1:1 to Zoho Contacts, with the client company name stored in Zoho Account.Name via a lookup. If Enkrypt stores multiple contacts per client firm, each contact becomes a separate Zoho Contact linked to the same Account.

Primary email address and primary phone number on the Enkrypt Client record map directly to Zoho Contact.Email and Contact.Phone through our standard field mapping. Any secondary phone numbers, alternate contact numbers, or additional communication channels stored in Enkrypt require a custom field created on the Zoho Contact module. We document these secondary contact fields in the schema plan for your admin to configure before migration.

Enkrypt Matter records map to Zoho Cases for support-style tracking, or to a custom 'Matters' module if your firm needs a more law-specific structure. We match on Matter ID and client lookup to ensure the Case links to the correct Zoho Contact.

Enkrypt matter lifecycle statuses—typically Active, Pending, Closed, and On-Hold—map to corresponding Zoho Case.Status pick-list values through our standard value-mapping process. Any custom status values defined in your Enkrypt configuration (such as Under Review, Awaiting Signature, or Litigation Hold) require new pick-list entries to be created in Zoho's Case module before migration executes. We identify all custom statuses during the schema audit and include them in the schema plan for your admin to configure.

Enkrypt document metadata and file attachments are re-uploaded to Zoho as record attachments on the corresponding Contact or Case record, maintaining the original file names and upload timestamps. Zoho's standard file size limits apply—25MB per file by default—and any documents exceeding this limit are flagged during the migration audit and set aside for manual review. Your migration team can then decide whether to compress and re-upload oversized files, store them in an integrated document management system, or adjust Zoho's file size settings.

Enkrypt encrypted message threads are processed to preserve sender identification, timestamp, and message body content as Zoho Notes attached to the linked Contact or Case record. The original encryption status is preserved by storing an encryption flag as a custom Note field (Is_Encrypted__c) for compliance reference and audit purposes. If decryption is available from the Enkrypt export, the decrypted message body is stored in the Note content; otherwise, the record includes a placeholder with a manual-review task.

Enkrypt appointments and calendar events migrate as Zoho Events, preserving the original start time, end time, subject line, and attendee information. Attendees are linked to their corresponding Zoho Contact records via email matching. Owner assignment for each migrated Event is resolved by matching the Enkrypt appointment creator's email address to their Zoho User account. Any unmatched creators are flagged for your admin to assign to a fallback owner before the migration run completes.

Enkrypt trust accounting and billing records have no native Zoho CRM equivalent, requiring custom field configuration. We migrate key financial data—including current billing balance, last payment date, trust account status, and billing arrangement type—as custom fields on the Case record. Detailed transaction history, including deposits, withdrawals, and disbursements, is preserved as Notes on the Case with a Trust_Transaction__c marker. Full financial reconciliation capabilities require Zoho Books integration as a separate post-migration step.

Any Enkrypt custom fields configured on Matter records—such as opposing counsel details, court jurisdiction, statute of limitations dates, or billing arrangement type—are created as custom fields on the Zoho Cases module during migration. Our process preserves the exact data type for each custom field: pick-list fields retain their value options, date fields maintain date formatting, text fields preserve character limits, and number/currency fields keep decimal precision. The complete custom field schema is documented in the Zoho schema plan for admin approval before data migration begins.

Enkrypt user IDs and attorney assignments resolve to Zoho Users through email address matching, ensuring proper record ownership after migration. Any attorneys or staff members in Enkrypt who do not have matching email addresses in your Zoho organization are flagged in a pre-migration resolution report. Your Zoho administrator can use this report to invite new users to your Zoho organization, map them to their Enkrypt counterparts, or assign records to a designated fallback owner before migration execution begins.