Migrate from Enkrypt Legal-PRO to Odoo CRM

Enkrypt client records map directly to Odoo res.partner. The partner_type field in Odoo (customer, vendor, employee) should be set to 'customer' for all migrated client records. This classification ensures proper segmentation in Odoo's contact management and reporting. Enkrypt client IDs are preserved in Odoo's x_studio_source_system_id custom field for delta-run de-duplication, cross-reference during reconciliation, and maintaining the link between the original Enkrypt record and the new Odoo res.partner entry. This source system ID field is essential for future incremental syncs and audit trails.

Enkrypt matters that represent client engagements or potential matters map to Odoo crm.lead (opportunity). The matter name becomes the lead name, matter status maps to Odoo stage via value_mapping, and the associated client becomes the partner_id lookup on the lead. Matter type (e.g., litigation, corporate, real estate) can be stored as a custom field on crm.lead for segmentation.

Enkrypt matters that represent active, multi-task case work split into Odoo project.matter records. Each Enkrypt matter becomes a project with tasks derived from case milestones or document categories. This split applies when the firm tracks billable hours, task lists, or milestone deliverables within the matter — these map to project.tasks in Odoo.

Enkrypt file attachments (contracts, briefs, correspondence) migrate as Odoo ir.attachment records linked to the corresponding res.partner or crm.lead via res_model and res_id fields. File binary data is re-uploaded to Odoo's filestore. Inline images in documents are extracted and re-hosted as attachment files.

Enkrypt activity logs (calls logged, emails sent, notes recorded) map to Odoo mail.activity records. The activity_type field maps to Odoo activity types (call, email, meeting, upload_document). Original timestamps, user assignments, and activity notes are preserved. The res_model and res_id on the activity link it to the correct partner or lead.

Enkrypt user accounts are resolved by email match against Odoo res.users. Unmatched attorneys are flagged before migration. Active Enkrypt users without an Odoo account can be provisioned as Odoo users with the same email, or their records can be assigned to a fallback user (e.g., managing partner) until Odoo accounts are created.

Enkrypt custom fields defined on the Client object are created as custom fields on res.partner in Odoo using Odoo Studio or direct model inheritance. Field types are mapped: text → char/text, picklist → selection, number → float/integer, date → date. The custom field API name follows Odoo's naming convention (x_studio_field_name or x_field_name for direct).

Enkrypt custom fields on the Matter object are created as custom fields on crm.lead in Odoo. Matter-specific properties like practice_area, referral_source, or client_priority become custom selection or char fields on the lead. Fields that represent monetary values (billing_rate, matter_budget) map to Odoo float fields.

Enkrypt organizations or client groups that represent companies map to the company_id field on res.partner. The organization's primary contact within the group becomes the main res.partner record with child contacts linked via parent_id. This preserves the hierarchical relationship in Odoo's partner model.

Enkrypt trust accounting and billing records do not have a direct Odoo CRM equivalent. They migrate as custom financial records for reference, but trust accounting logic must be rebuilt using Odoo's accounting module (account.move, account.payment). We preserve the trust account balance and transaction history as a reference custom field on the client partner record.