Migrate from Legl to Pipedrive

Legl Business records map directly to Pipedrive Organization records through a one-to-one field translation. Business name becomes Organization name, and the registered address maps to the organization's address fields using standard address parsing. The Legl business_id is stored as a custom field (Original_Legl_ID__c) on the Pipedrive Organization for traceability, allowing your team to reference the original Legl record for audits or compliance reviews after migration completes.

Legl Business records with an associated contact person create a corresponding Pipedrive Person record linked to the Organization. Name, email, and phone extract from the contact fields in the Legl Business object and become the Person's name, email, and phone fields.

EngageRequest is Legl's primary work-order object. It transforms into a Pipedrive Deal: the EngageRequest title or matter description becomes the Deal name, the request_type maps to a Pipedrive custom field (EngageRequest_Type__c), and the EngageRequest status maps to a Pipedrive Deal stage via value-mapping defined per request type.

Legl EngageRequest priority values (urgent, high, medium, low) map to a Pipedrive custom picklist field (EngageRequest_Priority__c) on the Deal. The value-mapping is 1:1 — no transformation of the priority label — and your team defines the Pipedrive picklist options before migration runs.

Legl RiskAssessment records have no Pipedrive equivalent object. FlitStack extracts the assessment result (risk_level, score, status) and writes it as read-only custom fields (Risk_Level__c, Compliance_Score__c, Assessment_Status__c) on the associated Pipedrive Deal or Organization. The automated trigger logic does not migrate.

Legl Payment records for an EngageRequest merge into the corresponding Pipedrive Deal's amount field. When multiple payments exist for a single EngageRequest, FlitStack sums them to calculate the Deal amount. Payment date and payment reference number become custom fields (First_Payment_Date__c, Payment_Reference__c) on the Deal, preserving payment history for billing reconciliation after migration.

Legl BankAccount records used for KYC and payment processing attach to the Pipedrive Organization as read-only custom fields (Bank_Name__c, Account_Number_Last4__c). Consistent with data-minimization practices, full account numbers are not migrated — only the last four digits are transferred for reference and account identification purposes in Pipedrive.

Legl workflows encode legal-specific conditional logic (CDD-stage routing, risk-threshold triggers, matter-type escalations) that has no Pipedrive equivalent. Workflow definitions are exported as a JSON reference file for your team to rebuild in Pipedrive Automations. The automated trigger behavior does not transfer.

Legl users and reviewers resolve to Pipedrive users by email address match. Unmatched Legl owners are flagged before migration — your team either invites them to Pipedrive or reassigns their records to an existing Pipedrive user. No deal or organization lands without an owner.

Legl BusinessReport records (KYB summaries, sanctions-check results) are exported as PDF references and attached as notes to the corresponding Pipedrive Organization. The structured report data does not map to Pipedrive fields — it is preserved as a linked document for admin reference.