Data migration route
Microsoft Dynamics 365 data to Full data export
Microsoft Dynamics 365 is a cloud CRM and intake system, and Full data export is a store of data kept as files the firm holds. This is not a move to a new working system: the route writes out what Microsoft Dynamics 365 holds and keeps it readable and open to queries.
Microsoft Dynamics 365Cloud- Contacts: Exported in full
- Documents: Exported in full
- Notes: Exported in full
- Calendar: Exported in full
- Tasks: Exported in full
- Emails: Exported with mapping
- Custom fields: Exported with mapping
- Templates: Exported with mapping
- Intake: Exported with mapping
Full data exportFiles- 5 carried
- 4 mapped
What moves
What moves from Microsoft Dynamics 365 to Full data export
Each row is a kind of record Microsoft Dynamics 365 holds, whether Full data export has a place for it, and what is planned. On this route five kinds of record carry across and four kinds need mapping.
| Record | What is planned | ||
|---|---|---|---|
| ContactsClients, other parties and referrers | HeldAccounts and contacts, with leads held separately. | Has a placeA contacts table and a table of each contact’s role on each matter. | Exported in full |
| DocumentsFiles stored in or linked from the system | Held in partNote attachments sit in Dataverse file storage; documents are often kept in SharePoint. | Has a placeFiles under their original names, in client and matter folders. | Exported in full |
| EmailsEmails saved to matters or to the store | Held in partEmails tracked against a record are stored as activities. | Has a place in partFiled emails as message files in the matter’s folder, if the source exposes them. | Exported with mapping |
| NotesFile notes, matter notes and contact notes | HeldNotes on a record’s timeline, with optional attachments. | Has a placeA notes table with matter, author and date for each note. | Exported in full |
| CalendarAppointments, court dates and deadlines | Held in partAppointments are activities on a record’s timeline. | Has a placeA table of appointments and key dates; nothing shows it as a diary. | Exported in full |
| TasksTo-dos and workflow steps assigned to people | HeldTasks are a type of activity. | Has a placeA table of tasks with assignee, due date and status. | Exported in full |
| Custom fieldsFields and record types the firm added itself | HeldCustom columns and custom tables are part of most implementations. | Has a placeExtra columns under their original field names. | Exported with mapping |
| TemplatesPrecedents, document templates and automation | Held in partEmail and Word templates. | Has a place in partTemplate files only; the merge fields in them will not run. | Exported with mapping |
| IntakeLeads, enquiries, intake forms and pipelines | HeldLeads, opportunities, marketing lists and campaigns. | Has a place in partAn enquiries table, where the source tracked leads. | Exported with mapping |
What the plans mean
- Exported in full
- Full data export has a place for this kind of record. It is loaded there and checked against Microsoft Dynamics 365.
- Exported with mapping
- Full data export holds this differently, or in part. Each field or value is matched to its place before loading, and you see the mapping first.
The table states what the two products hold and what NewLaw plans for. It is not a promise that every record moves: that is settled against your own data in the analysis.
This kind of move
Not a new system. A complete copy the firm can query.
Writing Microsoft Dynamics 365 out to Full data export is not a migration into a new working system. Nobody will open a matter there on Monday morning. The aim is a complete, faithful copy that can be queried and reported on after the old system is gone. So the rules change. Nothing is cleaned or merged unless the firm asks, because an archive should show the records as they were. Every table and field is carried, including those a new system would have had no place for.
What makes an archive usable is the description that goes with it. The export is delivered with a plain account of each table: what it holds, how it joins to the others, what the codes mean. Record counts and financial totals are agreed to the reports in Microsoft Dynamics 365 as at the export date, so the archive can stand as the record. Documents are exported beside the data with a table linking each file to its matter. Access is restricted, since the archive holds everything the live system did.
Microsoft Dynamics 365 is hosted by its maker and Full data export sits on equipment the firm controls. The data leaves a service that was backed up for the firm and arrives somewhere the firm must back up itself, so backup and access are arranged before the export is copied in. What Microsoft Dynamics 365 will release depends on its export tools, and that is confirmed in the analysis.
Where the data is now
Leaving Microsoft Dynamics 365
No two Dynamics systems are alike. The product is a platform, and what a firm has is whatever its implementer built: renamed tables, added columns, custom tables, workflows. A move begins by reading that design from the system itself. The data then comes out of Dataverse table by table, with the notes, activities and SharePoint documents collected alongside.
Start from the customisations
Accounts may have been renamed Clients, opportunities turned into Pitches, and a custom Matter table added beside them. None of that is in Microsoft’s documentation. The list of tables, columns and relationships is exported from the firm’s own environment first, and the field mapping is written against what is there.
Excel export is for views
The built-in Export to Excel takes the rows and columns of one view, and Microsoft notes that an export can time out depending on the number of rows, columns and lookups. It suits a spot check. A full extraction needs each table with its record identifiers, so the links between records survive.
Notes, attachments and timeline
What users see as one timeline is several tables underneath: notes, emails, phone calls, appointments, tasks. Files attached to notes and emails are held in Dataverse file storage, apart from the database rows. Each activity type is extracted with its link to the account, contact or custom record it belongs to.
Documents may be in SharePoint
Where document management is switched on, the documents shown on a record are files in a SharePoint folder and are not in Dynamics at all. They are moved as a SharePoint migration, using the links between folders and records to work out which client or matter each folder belongs to.
Online or on-premises
The online apps and the on-premises edition share most features but are reached differently. An on-premises system keeps its data in SQL Server databases on servers the firm controls. Which edition and version the firm runs is the first fact established, because it decides how the data is read.
Where it is going
Arriving in Full data export
A full export is judged by whether a stranger can use it. In five years the question will be something like: what was the trust balance on this matter the day it closed, and where is the signed agreement. The export is planned backwards from questions of that kind, and it is checked against the live system while the live system can still be opened.
Tables that still join up
Each kind of record becomes its own table: matters, contacts, time entries, invoices, trust transactions. The identifiers that link them are kept in every table, so a time entry can still be traced to its matter and its fee earner. An export that keeps the rows and drops the keys cannot be rejoined later.
Documents with an index
Documents are written to folders by client and matter under their original names. On their own they can be found only by name. An index listing each file with its matter number, title, author, dates and path is what lets someone find the right version of a lease among forty thousand files without the old system’s search. What the index records is settled in the analysis.
Reports a person can read
Raw tables do not satisfy an auditor or a former client. The firm decides which reports are also printed to PDF from the old system as at the final date: trust ledgers, matter ledgers, debtor lists and issued invoices are the usual candidates. They cannot be regenerated once the licence ends.
What an export does not keep
Screens, workflows, document automation, saved searches and user permissions belong to the software and stay with it. Figures the system calculated on the fly, such as a matter’s unbilled total, exist in an export only if they were captured as a report. The firm is told which of these are being let go.
Checked while the source is open
Record counts and financial totals in the export are reconciled to the live system: number of matters, sum of trust balances, total debtors, document count per matter on a sample. This is done before the subscription lapses or the server is turned off, because afterwards there is nothing left to compare against.
How NewLaw runs it
Four steps, in this order.
This route produces an archive, not a working system, so the steps are about completeness and proof.
Analysis
We read what Microsoft Dynamics 365 holds, table by table, and agree with you what the copy in Full data export must be able to answer later. Everything Microsoft Dynamics 365 holds is in scope unless you take it out.
Clean-up, if you want it
An archive should show the records as they were, so nothing is merged or corrected unless you ask. Where the copy is also meant for reporting, duplicate and inconsistent entries are tidied in a working copy and the original values are kept beside them.
Trial export
The data is written to Full data export as a trial and checked against Microsoft Dynamics 365: record counts, totals where Microsoft Dynamics 365 holds money, the links between records, and a sample of documents opened from the export. Exceptions are listed for you to decide.
Final export
After the last day of work in Microsoft Dynamics 365, the export is run a final time and checked again. There is nothing to go live. Microsoft Dynamics 365 is kept read only until you are satisfied the copy answers what you need, and it is handed over with a written description of its contents.
Fixed price, agreed after the analysis. How NewLaw moves legal data
Start
Start this migration
Tell us what is in Microsoft Dynamics 365 and roughly how much of it. The first step is the analysis, and the price is fixed once it is done.
Step 1 of 5
What happens after you send it
- A free first call
We go through your answers with you and ask about anything they leave open.
- An analysis of what Microsoft Dynamics 365 holds
What is in it, how its records link, and where each piece would sit in Full data export. Anything with no place there comes across as a note or stays behind, and you see which before the move.
- A fixed price in writing
Set after the analysis, so it reflects what is in your data. You have it before any work starts.
Beyond the data
Structure, permissions and handover
Full data export is a place to keep data, not a system staff work in each day. What is agreed is how the data is laid out, who can reach it, and what is handed over with it.
With no product to configure, the set-up is custody, and the decisions are the firm’s. Someone there owns the export, knows where it is kept and can open it. Access needs restricting, because it contains every client’s affairs in one place with none of the old system’s security. The firm sets a destruction date from its retention obligations and decides how the next custodian will learn to use it.
What is agreed and set up
- Folder layout for tables, documents and reports
- What the key to tables, columns and identifiers records
- Where the copies are stored and who is custodian
- Who may open it, as approved by a partner
- Which look-ups staff must be able to do unaided
- Retention period and the date it is next reviewed
Questions
Microsoft Dynamics 365 to Full data export: what firms ask
Our Dynamics was heavily customised. Does that make a move harder?
It makes the analysis longer. Custom tables and columns are read from the system and listed with how many records use each one. The firm then says which still matter. Fields with a home in the destination are mapped, and the rest come across as notes or stay in the read-only copy of the old system.
Can a practice management system replace what we do in Dynamics?
For client and matter records, yes. Pipeline tracking, marketing lists and relationship mapping depend on whether the destination has a CRM or intake module. Where it does not, firms either keep a smaller CRM beside it or accept simpler tracking. The analysis lists each function and where it would sit.
Does the copy in Full data export hold documents from Microsoft Dynamics 365?
Yes. Files under their original names, in client and matter folders. Documents are written out with the rest, and counts and totals are agreed to the reports in Microsoft Dynamics 365 as at the export date.
Does everything in Microsoft Dynamics 365 have a place in Full data export?
On paper, yes: each kind of record Microsoft Dynamics 365 holds has a place in Full data export. Whether every field fits is a separate question, and the analysis answers it field by field. Anything with no place comes across as a note or stays behind, and you see which before the move.
What has to be decided before Microsoft Dynamics 365 is written out to Full data export?
Emails, custom fields, templates and intake records are exported with mapping, so each mapping is agreed with you first. The firm also decides who may open the archive and how long it is kept.
Other routes
Other routes from Microsoft Dynamics 365 and into Full data export
Where to start
Before and after the move.
Choosing the system comes before a migration. Setting it up and putting AI to work come after.
Choose your systems
Technology stack selection
Decide which practice management system your firm runs, with the evidence and the cost beside it.
About four weeks for a firm of about 15 people. Fixed price, set after a free first call.
Move your data
Data migration
Your data is cleaned up before anything moves, then a trial load is checked against the old system.
Fixed price, agreed after the analysis.
Set up your new system
Implementation
Your new system set up around the way your firm works: configuration, document automation and training.
A small firm of 1 to 10 users typically takes 4 to 8 weeks. A mid-sized firm of 10 to 50 users takes 8 to 16 weeks.
Put AI to work
AI advisory and enablement
A small group of your people learn to use an approved AI tool on real work, under written rules.
Two to four weeks for a small first group. Fixed price, set after a free first call.
Microsoft Dynamics 365 and Full data export are the names and marks of their owners, used here only to identify the two systems.
Moving from Microsoft Dynamics 365 to Full data export?
Tell us what you are moving. You get a plan and a fixed price after the analysis.
We reply within one business day.