Migrate from Legl to Microsoft Dynamics 365 Sales

Legl Organization maps directly to Dynamics 365 Account. Legl's flat organization model requires no parent-child hierarchy setup unless your Legl data contains parent-company references, in which case those map to Account.ParentAccountId. Legl organization IDs are stored as new_legl_organizationid__c for traceability.

Legl Person maps to Dynamics 365 Contact. The key dependency is that Legl Persons carry an organisationId — the corresponding Account must migrate first so Dynamics can resolve AccountId on each Contact. Multiple Persons per Legl organization collapse to individual Contacts all linked to the same Account.

Legl EngageRequest is the client-onboarding/CDD record with no native Dynamics equivalent. FlitStack creates a new_cddrequest custom table in Dynamics with fields for cdd_status, reviewer, engage_request_id, and dates. Status values (pending_review, manual_cdd_required, approved, rejected) map via value_mapping to pick-list values in the custom entity.

Legl RiskAssessment tracks ongoing compliance risk scores and event-risk flags. Migrated as a new_riskassessment custom table linked to Account. Fields include assessment_status, risk_score, risk_level, assessment_date, and Legl template reference. The custom entity uses a lookup to Account so each assessment ties to the correct business.

Legl Workflow records define the steps in onboarding and compliance processes. Dynamics has no native workflow-log equivalent. FlitStack exports workflow definitions as a JSON reference document and advises rebuilding process steps in Power Automate. The Workflow record data itself is archived as a custom entity new_legl_workflowreference for audit purposes only.

Legl BankAccount stores payment method records linked to an organization. Migrates as a new_bankaccount custom entity with a lookup to Account. Fields include bank_name, account_reference, and status. Dynamics 365 Sales does not natively store payment method data, so this is a reference entity for compliance records.

Legl sanctions-check results have no native Dynamics equivalent. FlitStack creates new_sanctionscheck as a custom entity on Account, storing the sanctions_report_id, check_date, result (clear, hit, pending), and Legl source reference. Status values map via value_mapping to a custom pick-list in Dynamics. The sanctions check result values are transformed from Legl's response format to match the custom pick-list defined in Dynamics.

Legl stores address fields (address_line1, address_line2, address_city, address_postal_code, address_country) as sub-fields on Organization. These merge into Dynamics 365 Account's composite address fields (Address1Street, Address1City, Address1PostalCode, Address1Country) using Legl address_line1 as the primary street line and address_line2 as address2 if present.

Legl Person address fields merge into Dynamics 365 Contact's Address1 composite address fields, mirroring the Organization-to-Account address mapping. If Legl stores multiple addresses per person, the primary address migrates to Address1 and any secondary address is stored as a custom text field new_secondaryaddress__c.

Legl workflow reviewer IDs and owner references resolve to Dynamics SystemUser records by email match. Unmatched Legl users are flagged before migration — your team either creates corresponding Dynamics users first or assigns their records to a designated fallback owner. No record lands in Dynamics without a resolved owner.

Legl BusinessReport records contain company-report and registry-search results. These migrate as new_legl_businessreport custom entities linked to Account, storing report_id, report_type, retrieve_date, and a copy of key result flags as custom fields. Binary report files are re-uploaded to Dynamics 365 SharePoint integration.

Legl's ongoing-monitoring disable flag and schedule references have no native Dynamics equivalent. FlitStack creates new_ongoingmonitoring as a custom entity on Account, storing monitoring_enabled (boolean), monitoring_id, and last_check_date. This preserves the compliance-monitoring state from Legl as a reference record in Dynamics. The monitoring configuration details are carried forward as custom fields on the new entity.