Migrate from Legl to Twenty CRM

Legl Business records (company name, domain, address) map directly to Twenty Companies. The Legl businessId becomes a custom reference field (Source_Business_ID__c) for traceability. Legl business hierarchies (parent/child via hs_parent_company_id) map to Twenty's Parent Company link if present. If the Legl business includes a parent/child hierarchy, we map the top-level business to the primary Company and link subsidiaries via the Parent Company field for a clear organizational tree.

Legl Person records (name, email, phone, job title, address) map to Twenty People with direct field correspondence. Primary businessId links the Person to a Company record. Email uniqueness is preserved for Workspace Member matching during owner resolution. We also verify email uniqueness across the dataset to avoid duplicate Workspace Members and to ensure accurate ownership assignments during import.

Legl RiskAssessment records have structured fields: risk level, assessment date, template name, reviewer, and a PDF artifact URL. We create a Twenty custom object named RiskAssessment with matching custom fields. The PDF is downloaded and re-uploaded as a Twenty File attached to the record.

Legl EngageRequest tracks client onboarding status per department and reviewer. Fields include status, clientId, department, reviewer, and CDD completion flag. We create a Twenty custom object with a status pick-list mirroring Legl's state machine. Reviewer maps to a Twenty Workspace Member lookup.

Legl Payment records include amount, currency, status, bankAccountId, and createdAt timestamp. We create a Payment custom object in Twenty with amount, currency, and status fields. The Legl payment ID is stored as Source_Payment_ID__c for audit traceability. All payment amounts are normalized to the target currency, and any missing currency data defaults to the workspace's primary currency setting.

Legl bank account records map to a Twenty BankAccount custom object with fields for account reference and linked business. The relationship to Payment records is preserved by storing the BankAccount custom object ID on the Payment record. The BankAccount custom object also stores the associated Legl businessId for reference, allowing quick cross-checking during reconciliation.

Legl Workflows (internal escalations, client onboarding funnels, department-tailored processes) are JSON-defined automation objects with no direct Twenty equivalent. We export the full workflow JSON via GET /workflows as a rebuild reference document for your Twenty admin to reconstruct in Twenty's workflow builder.

Legl SanctionsReport records from /sanctionsReport endpoints contain match results and search metadata. These migrate to a Twenty custom object with match status and search timestamp fields, linked to the relevant Business (Company) record. The match status field captures whether the sanctions check returned a hit, partial match, or clear result, preserving the original verdict for compliance audits.

Legl CompanyReport records aggregate compliance data per business. Migrated as a Twenty custom object with report type, generated date, and linked Company reference. Report PDF artifacts are re-uploaded as Twenty Files. Each CompanyReport record also includes a link to the original PDF file, which is re-hosted in Twenty's file storage for convenient access by compliance officers.

Legl notes and file attachments on any object type migrate to Twenty Notes and Files respectively. Original timestamps and author references are preserved. Inline images in notes are extracted and rehosted as Twenty Files. File attachments retain their original file names and MIME types, and are stored under a dedicated Twenty Files folder for each migrated object type.

Legl Organisation metadata (GET /organisation) configures firm-level settings. These translate to Twenty workspace configuration items: workspace name, timezone, and currency defaults. User accounts map to Twenty Workspace Members invited before data import. We also map Legl user roles to Twenty workspace permissions, ensuring that access controls reflect the original firm hierarchy after migration.

Legl Ongoing Monitoring records (POST /DisableOngoingMonitoring) track continuous compliance checks per business. We create a Twenty custom object with monitoring status, linked Company, and last-check timestamp fields. The custom object also includes a link to the associated Company record, allowing compliance teams to view the monitoring history alongside other company details.