Data migration route
Microsoft Dynamics 365 to Centerbase migration
Microsoft Dynamics 365 is a cloud CRM and intake system, and Centerbase is a cloud practice management system. Contacts and intake history move, and the matters themselves start life in Centerbase.
Microsoft Dynamics 365Cloud- Contacts: Carried across
- Documents: Carried across
- Notes: Carried across
- Calendar: Carried across
- Tasks: Carried across
- Intake: Carried across
- Emails: Carried with mapping
- Custom fields: Carried with mapping
- Templates: Carried with mapping
CenterbaseCloud- 6 carried
- 3 mapped
What moves
What moves from Microsoft Dynamics 365 to Centerbase
Each row is a kind of record Microsoft Dynamics 365 holds, whether Centerbase has a place for it, and what is planned. On this route six kinds of record carry across and three kinds need mapping.
| Record | What is planned | ||
|---|---|---|---|
| ContactsClients, other parties and referrers | HeldAccounts and contacts, with leads held separately. | Has a placeClients, related parties and prospects. | 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 placeInto Document Storage, or left in a connected NetDocuments, iManage or SharePoint store. | Carried across |
| EmailsEmails saved to matters or to the store | Held in partEmails tracked against a record are stored as activities. | Has a place in partEmails saved to matters; mailboxes stay in Microsoft 365. | Carried with mapping |
| 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 place | 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 placeCreated and placed on page layouts before records are loaded. | Carried with mapping |
| TemplatesPrecedents, document templates and automation | Held in partEmail and Word templates. | Has a place in partTemplates are rebuilt to merge Centerbase client and matter data. | Carried with mapping |
| IntakeLeads, enquiries, intake forms and pipelines | HeldLeads, opportunities, marketing lists and campaigns. | Has a placeEnquiries are held as Potential New Client records; loading open ones is confirmed in the analysis. | Carried across |
What the plans mean
- Carried across
- Centerbase has a place for this kind of record. It is loaded there and checked against Microsoft Dynamics 365.
- Carried with mapping
- Centerbase 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
Contacts and enquiries move. Matters begin in the new system.
A CRM knows people: who enquired, who referred them, what was sent and when. It does not know matters the way a practice system does. So the move from Microsoft Dynamics 365 to Centerbase is mostly a contacts job, and contacts are where duplicates live. The same person appears as a lead, a client and a referrer, sometimes under three email addresses. They are merged before extraction where they can be identified, because Centerbase will invoice and receipt against these records.
Pipelines, campaigns and automations seldom have a direct equivalent in a practice system. Open enquiries can be loaded as contacts with a note of their stage, or opened as matters if the firm wants them worked from the first day. Intake forms and email sequences are set up again in whatever Centerbase or its intake tool provides. Past correspondence is kept as notes or documents on the contact, so the history of a relationship can still be read.
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 Centerbase 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 Centerbase
Centerbase takes practice, billing, trust and accounting data together, so loading a firm into it is a finance project as much as a matter load. Clients come first because matters inherit from them. The chart of accounts, bank accounts and accounting basis are fixed before balances go in. Because the product is configured per firm, the fields and layouts are designed before the trial load, not after.
Clients carry the billing rules
Billing arrangements, rates and accounting preferences are held on the client and passed to its matters. Source systems that create a fresh client for every matter leave duplicates behind. Those are merged during clean-up, so that each real client exists once and its terms are set in one place.
The ledger comes too
Centerbase has a full general ledger and runs on a cash or accrual basis. A firm arriving from a billing system with QuickBooks beside it is consolidating two sets of records. The accountant decides the basis and the opening date, and the trial balance loaded is agreed to the old books.
Trust and retainers are separate
A matter can hold multiple trust and retainer accounts. Source systems often blur the two, recording an advance on fees as trust or the reverse. Each balance is classified before loading, and client-level funds that were never tied to a matter are assigned to one or held at client level.
Decide the document home
Documents can go into built-in Document Storage, or stay in NetDocuments, iManage or SharePoint and be connected. Centerbase can create a standard folder structure when a matter is opened. That structure is agreed first, so migrated documents are filed into the same folders that new matters will get.
Fields are designed, not assumed
With unlimited custom fields, nearly every source field can have a home. That is a reason for restraint. Each one must be created and placed on a layout, and a page crowded with unused fields slows people down. The firm chooses which fields earn a place and which become a note.
How NewLaw runs it
Four steps, in this order.
Nothing financial lands in Centerbase on this route, which makes it repeatable: a load can be run again until it is right.
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 Centerbase. 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 Centerbase 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 Centerbase. 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 Centerbase
Loaded data is not yet a working system. This is what NewLaw sets up in Centerbase, beyond the migration, so that people can work in it from the first day.
Setting up Centerbase is largely configuration. Bill templates, rate tables and the pre-bill approval chain have to match how the firm bills today, or the first billing cycle exposes the gaps. The chart of accounts and bank accounts are built with the finance team. Workflows that open matters, create folders and assign first tasks are written last, once the fields they depend on are settled.
Set-up decisions in Centerbase
- Bill templates and billing arrangements for each client type
- Rate tables, timekeepers and the pre-bill approval chain
- Chart of accounts, bank accounts and cash or accrual basis
- Custom fields, page layouts and automated workflows by practice
- Document storage choice and the standard matter folder structure
- Outlook and Microsoft 365 connection for email and calendar
Questions
Microsoft Dynamics 365 to Centerbase: 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 Centerbase?
Centerbase stores documents. Into Document Storage, or left in a connected NetDocuments, iManage or SharePoint store. 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 Centerbase?
On paper, yes: each kind of record Microsoft Dynamics 365 holds has a place in Centerbase. 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 Centerbase?
Emails, 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 Centerbase
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 Centerbase are the names and marks of their owners, used here only to identify the two systems.
Moving from Microsoft Dynamics 365 to Centerbase?
Tell us what you are moving. You get a plan and a fixed price after the analysis.
We reply within one business day.