Migrate from Lexis Affinity to Microsoft Dynamics 365 Sales

Lexis Affinity clients map directly to Dynamics 365 Sales accounts. The primary client address, contact information, and organizational details transfer to the account record. Multi-client matters (shared clients across matters) require Account Contact Relationships in Dynamics 365. Additionally, client-specific custom fields such as billing preferences or industry codes are mapped to custom fields on the account record, preserving data fidelity.

Person-level contacts in Lexis Affinity map 1:1 to Dynamics 365 contacts. Email, phone, job title, and address fields map to their Dynamics 365 equivalents. The contact's primary account link is established from the client mapping. Any Lexis Affinity custom fields attached to the contact record, such as bar number or preferred contact method, are migrated as custom fields on the Dynamics 365 contact, ensuring no data is lost.

Lexis Affinity matters translate to Dynamics 365 opportunities — the matter name becomes the opportunity name, and the matter's primary client links to the opportunity's account. Matter status (open, closed, on-hold) maps to opportunity stage values via a value-mapping table.

For firms that need full matter hierarchy preserved (parent matters, related matters, practice area), FlitStack AI creates a custom Matter table in Dataverse with self-referential lookup fields. The opportunity record links to the matter record for legal context. The custom Matter table includes columns for matter number, responsible attorney, practice area, and status, all populated from Lexis Affinity. This enables Power Automate flows to reference matter relationships without altering the standard opportunity schema.

Billable hours logged in Lexis Affinity become records in a custom TimeEntry table in Dynamics 365 Dataverse. Each time entry links to the matter (opportunity) and contact (fee-earner). Hourly rate and billing status transfer as custom fields for reporting continuity.

Trust account balances and ledgers have no native Dynamics 365 equivalent. FlitStack AI preserves trust account data as custom currency fields on the account record and creates a custom TrustAccountTransaction table for ledger-level detail. Reconciliation logic must be handled outside Dynamics 365 or via Power Apps.

Lexis Affinity documents are exported and re-uploaded to SharePoint, with the document library structured to mirror the matter folder hierarchy. Dynamics 365 records link to the SharePoint document location via the native SharePoint integration. File size limits (default 25MB per file) apply.

Lexis Affinity billing records (invoices, payments, write-offs) are preserved as custom fields on the opportunity record. Invoice number, total amount, outstanding balance, and payment status transfer for financial reference. Full invoicing requires Dynamics 365 Finance or Business Central. The migration also captures any billing notes or client-specific invoicing instructions as text fields, ensuring that historical billing context is available in Dynamics 365 for audit and reporting purposes.

Lexis Affinity workflows (conflict checks, matter opening, document assembly) have no direct equivalent in Dynamics 365 Sales. FlitStack AI exports workflow definitions as documentation for your Dynamics 365 admin to rebuild in Power Automate. The migration data layer is preserved so rebuilt workflows can reference migrated IDs.

Lexis Affinity custom fields (client properties, matter metadata, billing flags) migrate as custom fields on the corresponding Dynamics 365 entity or as custom columns in Dataverse tables. Field types are mapped: text to text, pick-list to choice, date to datetime.

Court dates, deadlines, appointments, and meetings from Lexis Affinity calendar transfer to Dynamics 365 activities (appointments). Original timestamps and assigned users are preserved. Recurring events are mapped as individual activity records. Each activity includes the original Lexis Affinity calendar entry ID stored in a custom field for cross-referencing. If a recurring pattern is detected, FlitStack AI documents the recurrence rule so your admin can recreate it using Power Automate or the Dynamics 365 recurrence engine.

Conflict check results and check dates are stored as custom fields on the contact or account record for reference. Full conflict-checking workflows must be rebuilt in Dynamics 365 using Power Automate or a dedicated legal compliance tool. The migrated conflict data includes the check performed date, the responsible attorney, and any flags such as conflicts identified or cleared, enabling your compliance team to review historical checks without re-running them manually.