The hard part of this move is not the export. It is the difference in how the two systems think. Microsoft Dynamics 365 works in account and contact records; Neos works in case records. Get that mapping wrong and every report built on it afterwards is wrong too. This page covers the field map, what does not survive, what it costs, and the reconciliation step that decides whether anyone trusts Neos in month two.
The two systems, side by side
| Microsoft Dynamics 365 | Neos | |
|---|---|---|
| Primary record | Account and Contact | Case |
| Grouping | Account hierarchy and connections | Case type, plan and parties |
| Activity history | Activities: tasks, appointments, emails and phone calls | Notes, tasks and plan-driven deadlines |
| Documents | Notes, attachments, or SharePoint integration | Documents on the case |
| Getting data out | Dataverse export tooling and the Web API. | Vendor-assisted export plus API access. |
| Who administers it | A named Dynamics administrator. | An internal operations owner. |
| Pricing | Per-user platform licensing plus build. | Custom quoted. |
What breaks
- Microsoft Dynamics 365 works in account and contact records and Neos works in case records. That is a re-modelling exercise, and it is the first decision, not a mapping detail.
- Grouping changes: Account hierarchy and connections becomes Case type, plan and parties. Somebody has to define what a group means in the target before load.
- Activity history moves with partial fidelity. Microsoft Dynamics 365 stores it as activities: tasks, appointments, emails and phone calls; Neos expects notes, tasks and plan-driven deadlines.
- Plugins and Power Automate flows carry logic that no Dataverse export represents.
- Automations, reports, dashboards and permissions never transfer. Budget them as build work.
- Every connected system has to be repointed and retested: the DMS, billing, e-signature and the shared inbox.
Known hazards on each side
Leaving Microsoft Dynamics 365:
- Option sets and lookups need translating rather than copying.
- SharePoint-linked documents are references, not files, so document migration is a separate project.
- Plugins and Power Automate flows hold logic no export represents.
Arriving in Neos:
- Case plans generate deadlines, and the plan logic does not export with the dates.
- Party and provider records are richer than most targets expect.
- Legacy Needles data carried into Neos may hold two generations of field conventions.
The field map
| Concept | In Microsoft Dynamics 365 | In Neos | What to watch |
|---|---|---|---|
| Primary record | Account and Contact | Case | Different shape. Decide the mapping before any data moves. |
| Grouping | Account hierarchy and connections | Case type, plan and parties | The target groups records differently, so grouping is created rather than copied. |
| Activity history | Activities: tasks, appointments, emails and phone calls | Notes, tasks and plan-driven deadlines | Expect partial fidelity. Types, timestamps and authorship survive; structure often does not. |
| Documents | Notes, attachments, or SharePoint integration | Documents on the case | Usually a separate extract and load from the record data. |
| Owner and assignment | Assigned user or advisor fields | Assigned user or team fields | Map departed staff explicitly. Records assigned to nobody disappear from every view. |
| Custom fields | Firm-specific fields added over time | Created to match, or consciously dropped | The audit here is the work. Undocumented fields that reports depend on are the usual surprise. |
Cost and timeline
| Phase | Typical range |
|---|---|
| Data audit and cleanup | $3,000 to $25,000 |
| Migration execution | $5,000 to $50,000 |
| Target configuration | Two to six weeks |
| Ongoing administration | Absorbed by existing operations staff |
The upside of this direction is administrative. Microsoft Dynamics 365 assumes a named platform administrator and Neos does not, so the ongoing cost drops as well as the license. The trade is expressiveness: any workflow encoded in the platform has to be rebuilt or given up.
The five phases
- Audit Microsoft Dynamics 365. Count records per object, find duplicates and orphans, and decide what does not come with you. Get that decision signed off before mapping.
- Map against real records. Use the table above as the starting point, then walk fifty live records field by field.
- Dry run into a Neos sandbox. Load the full set, not a sample. Sample loads hide the failures that only appear at volume.
- Cut over on a quiet window. Freeze writes in Microsoft Dynamics 365, load, repoint every integration, unfreeze. Keep Microsoft Dynamics 365 read-only for at least a quarter.
- Reconcile. Compare Neos to Microsoft Dynamics 365 record by record and field by field, and produce a variance report.
The full version of this plan, with the failure evidence behind it, is in the CRM migration playbook.
The compliance clause
State retention rules and the firm's duties over the client file survive the migration. A matter that lands in the target without its history is a records gap, not a cosmetic issue. Keep the field map, the variance report and the mapping sign-offs with the records, because the decisions you made in phase two are part of the record too.
Where Caddi fits
Caddi does the mechanical half and then keeps doing it. Show it the task once and it reads Microsoft Dynamics 365, applies your field map, loads Neos, and then compares both sides record by record and hands back a variance report you can act on. Because it runs over APIs across your stack, the same agent covers the parts a migration tool ignores: documents filed to the right case with the right metadata, and the post-cutover hygiene that otherwise becomes someone's Monday.
Caddi automation for these systems: Neos.
Related migrations
- Clio Grow to Neos
- Clio Manage to Neos
- Filevine to Neos
- Litify to Neos
- Neos to Clio Grow
- Neos to Clio Manage
Migration without the manual pass
Move and reconcile Microsoft Dynamics 365 into Neos
Caddi reads Microsoft Dynamics 365, applies your field map, loads Neos, then compares both sides record by record and reports the variances.
Frequently asked questions
How do you migrate from Microsoft Dynamics 365 to Neos?
Audit the Microsoft Dynamics 365 data first, then map fields against fifty real records rather than against the schema, dry run the full set into a Neos sandbox, cut over on a quiet window with writes frozen, and reconcile record by record afterwards. Dataverse export tooling and the Web API. Neos then needs the records loaded in dependency order, with documents as a separate pass.
What does not transfer from Microsoft Dynamics 365 to Neos?
Microsoft Dynamics 365 works in account and contact records and Neos works in case records. That is a re-modelling exercise, and it is the first decision, not a mapping detail. Grouping changes: Account hierarchy and connections becomes Case type, plan and parties. Somebody has to define what a group means in the target before load. Activity history moves with partial fidelity. Microsoft Dynamics 365 stores it as activities: tasks, appointments, emails and phone calls; Neos expects notes, tasks and plan-driven deadlines.
How long does a Microsoft Dynamics 365 to Neos migration take?
Six to twelve weeks is realistic for a clean mid-size move, and three to six months where Neos is being implemented at the same time. Firms with years of history in Microsoft Dynamics 365 should budget several weeks of cleanup before any data moves.
Who administers Neos afterwards?
An internal operations owner. That is one of the reasons this move is lighter than a platform migration.
What are the compliance implications for law firms?
State retention rules and duties over the client file survive the migration. A gap in matter history is a finding, not a cosmetic issue, so keep the field map, the variance report and the sign-offs with the records.