Migrate from LEAP to Microsoft Dynamics 365 Sales

LEAP Party records map 1:1 to Dynamics 365 Contacts. Each Party's name, email, phone, and address fields map to the corresponding Contact fields. The primary Matter association becomes a lookup on the Contact form. Multiple parties per Matter are handled via the Contact's Parent Customer ID pointing to the primary Account.

LEAP Parties with a status indicating they are not yet active clients route to Dynamics 365 Leads. The qualification logic uses LEAP's party status and last-activity date — active matters within 90 days keep the record as a Contact; inactive or prospect-status parties become Leads for re-qualification in Dynamics.

LEAP Parties flagged as organizational entities route to Dynamics 365 Accounts. The Account record preserves the organization's name, website, industry classification, and address. Each contact associated with the organization links via the Parent Customer ID lookup field on the Contact record, maintaining the relationship hierarchy between the organization and individual contacts.

LEAP Matters map to Dynamics 365 Opportunities with the Account as the parent customer. Matter name becomes the Opportunity name, Matter value or fee arrangement maps to the Amount field, and the Matter status maps to the Opportunity StageName via a value-mapping table. For Professional tier environments, a custom Matter__c table is created instead.

LEAP's matter workflow stages (e.g., Initial Advice, Discovery, Negotiating, Closed) map to Dynamics 365 Opportunity StageName values via a value-mapping table. Each stage's probability is applied from the Dynamics Sales Process. Where no exact stage match exists, a catch-all stage with a custom Stage_Reason__c field captures the original LEAP stage name.

LEAP activities attached to a Matter map to Dynamics 365 Activities — calls become Tasks with Type='Phone Call', emails become Email activities, and meetings become Appointments. Original timestamps, owners, and the parent Matter reference (via custom Matter_ID__c) are preserved on each activity.

LEAP documents linked to a Matter are re-hosted in the Matter's SharePoint document location in Dynamics 365. The original document name and Matter association are preserved. If SharePoint is not configured, documents are attached as Notes with a reference link back to the source file.

LEAP's trust ledger (receipts, journals, bank deposits) has no native Dynamics 365 equivalent. We create a custom Trust_Ledger_Entry__c table in Dataverse with fields for transaction type, amount, date, and reference to the related Contact. For full accounting capability, Business Central integration is recommended post-migration.

LEAP invoices map to Dynamics 365 Invoice records if Business Central is also in use. If Dynamics 365 Sales standalone is the destination, a custom Invoice__c table is created to preserve invoice number, date, amount, status, and Matter reference. Professional tier may require custom-field setup for invoice line items.

LEAP custom fields on Matters, Parties, or Activities require pre-creation of corresponding custom fields in Dynamics 365. Field types are matched — text to text, date to datetime, pick-list to OptionSet — and if LEAP uses a pick-list with values not present in Dynamics, a value-mapping row is added before migration runs.

LEAP staff and user records are resolved by email against Dynamics 365 SystemUser. The full name, role, and active/inactive status map across. Unmatched users are flagged before migration so the admin can either invite them to Dynamics 365 or assign their records to a fallback owner.

LEAP time entries linked to a Matter map to a custom Time_Entry__c record tied to the corresponding Opportunity/Contact, with fields for date, duration, description, and billing rate. The time entry also generates a Task activity to preserve the activity timeline in Dynamics 365.