Migrate from Assembly Neos to Microsoft Dynamics 365 Sales

Neos matters are the primary case record. We map matter fields to Opportunity fields plus a set of custom fields (Case_Number__c, Opposing_Counsel__c, Court__c, Jurisdiction__c, Statute_of_Limitations__c) that capture legal context Dynamics 365 Sales does not store natively. The matter name becomes the Opportunity Name; estimated value becomes Amount; matter status maps to Opportunity Stage via a value map.

Neos contacts who are active clients map to Dynamics 365 Contacts. Neos contacts who are prospective parties (named in a matter but not yet engaged) map to Leads. We split on the Neos contact_type field: 'Client' or 'Party' routes to Contact; 'Prospect' or 'Witness' routes to Lead. Email address determines uniqueness; duplicates merge by email match.

Neos parties carry a legal role (Plaintiff, Defendant, Opposing Counsel, Expert Witness, Insurer). Dynamics 365 has no native legal-role field on contact-opportunity links. We map parties to Opportunity Contact Roles using the built-in Role field for common roles, and extend with a custom pick-list (Legal_Role__c) on the Opportunity Contact Role entity for roles that do not fit standard options.

Neos tasks map directly to Dynamics 365 Tasks. Subject, description, due date, status, and priority carry over. The parent regard_objectid links the task to the corresponding Contact or Opportunity in Dynamics 365. Task owners resolve by email match to Dynamics 365 users; unmatched owners assign to a fallback user flagged in the pre-migration report.

Neos calendar entries (court dates, filing deadlines, client meetings) map to Dynamics 365 Appointments. Subject, start time, end time, location, and attendees carry over. Court dates and filing deadlines preserve the original timestamp as the appointment start time. Client-facing meetings create Dynamics 365 Appointments linked to the corresponding Contact.

Neos documents are re-hosted to the Dynamics 365-connected SharePoint library. Each matter maps to a SharePoint folder named after the Opportunity (case) ID. PDFs and Word documents attach as SharePoint list items linked to the Opportunity. Inline notes from Neos migrate as Dynamics 365 Notes attached to the parent record.

Neos billing records (invoices, trust ledger entries, cost tracking, disbursements) have no native equivalent in Dynamics 365 Sales. We export billing records to a custom Dataverse table (Legal_Billing__c) linked to the Opportunity by a lookup field. Firms that use QuickBooks Online can reconcile this custom table with QBO after migration; firms using Business Central can build a Power Automate flow to sync invoices. Billing data is preserved — it is not discarded — but it requires destination-side design work.

Neos custom fields on matters (case-type, lien amount, insurance carrier, referral source) require corresponding custom fields in Dynamics 365. We deliver a custom field creation plan as part of the pre-migration schema setup: each Neos custom field becomes a custom Opportunity field with a matching data type (text, picklist, number, date, boolean). Picklist fields require a value-by-value map between Neos options and Dynamics 365 options.

Neos user records map to Dynamics 365 SystemUser by email address. Each user must have a Dynamics 365 license assigned before migration; we flag any Neos user whose email has no matching Dynamics 365 account and route their assigned matters to a designated fallback owner. User roles and permissions are not migrated — they are destination-side configuration.

Neos stores insurance carrier, policy number, lien holder, and lien amount per matter. These have no native Dynamics 365 fields. We map them to a custom Insurance_Lien__c table linked to the Opportunity, with fields for Carrier__c, Policy_Number__c, Lien_Holder__c, and Lien_Amount__c. This preserves the full insurance picture for post-migration review.

Neos case-type checklists and milestones have no direct Dynamics 365 equivalent. We decompose each active checklist item into a Dynamics 365 Task linked to the Opportunity, preserving the item name, due date, and assigned user. Completed checklist items are logged as Note records on the Opportunity for audit continuity.

The Neos internal record ID is stored on every destination record as Source_System_ID__c. This enables delta-run de-duplication, rollback targeting, and cross-referencing between the Neos archive and Dynamics 365 after cutover. It is created on every destination entity (Contact, Opportunity, Task, Insurance_Lien__c, Legal_Billing__c).