Data migration route
Microsoft Dynamics 365 to SmartAdvocate migration
Microsoft Dynamics 365 is a cloud CRM and intake system, and SmartAdvocate is a cloud case management system for personal injury work. Contacts and intake history move, and open enquiries become leads or cases in SmartAdvocate.
Microsoft Dynamics 365Cloud- Contacts: Carried across
- Documents: Carried across
- Emails: Carried across
- Notes: Carried across
- Calendar: Carried across
- Tasks: Carried across
- Intake: Carried across
- Custom fields: Carried with mapping
- Templates: Carried with mapping
SmartAdvocateCloud- 7 carried
- 2 mapped
What moves
What moves from Microsoft Dynamics 365 to SmartAdvocate
Each row is a kind of record Microsoft Dynamics 365 holds, whether SmartAdvocate has a place for it, and what is planned. On this route seven kinds of record carry across and two kinds need mapping.
| Record | What is planned | ||
|---|---|---|---|
| ContactsClients, other parties and referrers | HeldAccounts and contacts, with leads held separately. | Has a place | Carried across |
| 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 placeDocuments page, by category and subcategory. | Carried across |
| EmailsEmails saved to matters or to the store | Held in partEmails tracked against a record are stored as activities. | Has a placeEmails are attached to cases. | Carried across |
| NotesFile notes, matter notes and contact notes | HeldNotes on a record’s timeline, with optional attachments. | Has a place | Carried across |
| CalendarAppointments, court dates and deadlines | Held in partAppointments are activities on a record’s timeline. | Has a placeAppointments and critical deadlines. | Carried across |
| TasksTo-dos and workflow steps assigned to people | HeldTasks are a type of activity. | Has a place | Carried across |
| Custom fieldsFields and record types the firm added itself | HeldCustom columns and custom tables are part of most implementations. | Has a place in partConfirmed in the analysis for each field with no standard home. | Carried with mapping |
| TemplatesPrecedents, document templates and automation | Held in partEmail and Word templates. | Has a place in partTemplates are rebuilt with SmartAdvocate merge codes. | Carried with mapping |
| IntakeLeads, enquiries, intake forms and pipelines | HeldLeads, opportunities, marketing lists and campaigns. | Has a placeIntake and lead records. | Carried across |
What the plans mean
- Carried across
- SmartAdvocate has a place for this kind of record. It is loaded there and checked against Microsoft Dynamics 365.
- Carried with mapping
- SmartAdvocate 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
Intake history moves. The pipeline is rebuilt.
Intake data is the front end of a case. A lead in Microsoft Dynamics 365 carries the first conversation, the screening answers, the referrer and often a signed retainer. Many case management systems have an intake stage of their own, so a lead can land as a prospective case with that history attached. Where SmartAdvocate has no such stage, open enquiries are loaded as contacts with their status in a note, and the firm decides which to open as cases.
Screening questions are the mapping work. Each intake form is a set of fields, and each field has to find a place on the case or be kept as a note. Referral sources are tidied into one list first, because they are usually typed by hand and reporting depends on them. Marketing automations, email sequences and web forms do not move as data. They are set up again in SmartAdvocate or in the tool that feeds it.
Both are hosted by their makers, so nothing is collected from the firm’s office. What can be taken out of Microsoft Dynamics 365 depends on its export tools and on what its maker provides on request, and that is confirmed during the analysis, before a date is set. The subscription to Microsoft Dynamics 365 is kept running until the checks on SmartAdvocate are finished.
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 SmartAdvocate
SmartAdvocate keeps injury detail in structured fields and screens, so mapping counts for more than usual: the more precisely the old data is placed, the more of those screens are filled on the first day. Parties, incidents, insurers, providers and bills are loaded to their own screens, and the vendor’s implementation team runs conversions into it.
Map to fields, not notes
The case summary, dashboards and settlement screen read from structured fields. Injury details, insurance limits and provider bills dumped into a note leave those screens empty. The mapping takes each old field to its SmartAdvocate counterpart, and only what truly has no counterpart is loaded as a note.
Case types and statuses
Cases are loaded against case types and statuses that drive WorkPlans and reports. These are agreed with the firm before the trial load, and old statuses are translated to the new list. A status with no match is not guessed at. It is listed, and someone who knows the files decides.
Document categories
Documents are searched by category, subcategory, sender, recipient and date as well as by folder. The old system’s folders are translated into categories on the way in. Files that arrive uncategorised can still be found by description, but they fall outside the category views staff are trained to use.
Working with the vendor’s conversion
SmartAdvocate’s implementation team converts client data into the system and trains staff through its own classes. The firm’s side of that is supplying a clean source, checking the converted cases against the old system, and deciding what to do with the exceptions. Independent help is used on those tasks.
Choosing Server or Cloud
The firm decides before loading whether it will run the Server edition on its own Windows server or use the hosted Cloud edition. Either way the data load is the same. What differs is who looks after backups, updates and remote access afterwards, and that is settled with the firm’s IT provider.
How NewLaw runs it
Four steps, in this order.
Nothing financial lands in SmartAdvocate on this route, which makes it repeatable: a load can be run again until it is right. The maker of SmartAdvocate says that it, or its partners, load firms into the product. Where the firm uses that service, NewLaw’s part is the work around it: the analysis, the clean-up in Microsoft Dynamics 365 and checking each trial against Microsoft Dynamics 365.
Analysis
We read what Microsoft Dynamics 365 holds and how it is organised, then agree with you where each kind of record will sit in SmartAdvocate. Anything with no place there stays behind or is archived, and you see which before the move.
Clean-up
Duplicate clients, matters and folders are merged where they can be identified, and naming is put into one format, before anything is copied. It is not always possible to find every one, so some may carry across.
Trial load
A trial is loaded into SmartAdvocate and checked against Microsoft Dynamics 365: record and file counts, the links between records, document dates, and a sample opened by your own people. Exceptions are listed for you to decide.
Cutover
There is no financial cutover on this route. After a short freeze on changes in Microsoft Dynamics 365, a final pass over a weekend picks up what changed since the trial. Microsoft Dynamics 365 is kept read only as the fall-back record.
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 SmartAdvocate. 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
Setting up SmartAdvocate
Loaded data is not yet a working system. The maker of SmartAdvocate runs or arranges the set-up of its product, so this is what has to be decided and put in place in SmartAdvocate, whoever does the work, before people rely on it from the first day.
Setting up SmartAdvocate is a matter of deciding how much of its detail the firm will use from the start. Case types, statuses and WorkPlans come first because they drive everything else. Templates follow. The vendor trains staff through its own classes, and the decisions below are best made before the first of those.
Set-up decisions in SmartAdvocate
- Choose the Server or Cloud edition with IT
- Define case types, statuses and staff roles
- Build WorkPlans and Automated Procedures for each case type
- Convert letters and forms into templates with merge codes
- Install the Outlook plugin and agree email filing habits
- Set up intake screens, lead sources and dashboards
Questions
Microsoft Dynamics 365 to SmartAdvocate: 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.
Do documents from Microsoft Dynamics 365 keep their folders and dates in SmartAdvocate?
SmartAdvocate stores documents. Documents page, by category and subcategory. Each file is placed under the client and matter it came from, and created and modified dates are carried, so a document still shows when it was written. The trial load is checked by count and by opening a sample.
Does everything in Microsoft Dynamics 365 have a place in SmartAdvocate?
On paper, yes: each kind of record Microsoft Dynamics 365 holds has a place in SmartAdvocate. 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 data is loaded into SmartAdvocate?
Custom fields and templates are carried with mapping, so each mapping is agreed with you first. The firm also decides which closed matters and how many versions of a document are in scope.
Other routes
Other routes from Microsoft Dynamics 365 and into SmartAdvocate
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 SmartAdvocate are the names and marks of their owners, used here only to identify the two systems.
Moving from Microsoft Dynamics 365 to SmartAdvocate?
Tell us what you are moving. You get a plan and a fixed price after the analysis.
We reply within one business day.