Data migration route
Microsoft Graph to Centerbase migration
Microsoft Graph is a cloud specialist tool, and Centerbase is a cloud practice management system. This is a narrow move: the records Microsoft Graph holds are matched to the people and matters in Centerbase.
Microsoft GraphCloud- Contacts: Carried across
- Documents: Carried across
- Notes: Carried across
- Calendar: Carried across
- Tasks: Carried across
- Emails: Carried with mapping
- Custom fields: Carried with mapping
CenterbaseCloud- 5 carried
- 2 mapped
What moves
What moves from Microsoft Graph to Centerbase
Each row is a kind of record Microsoft Graph holds, whether Centerbase has a place for it, and what is planned. On this route five kinds of record carry across and two kinds need mapping.
| Record | What is planned | ||
|---|---|---|---|
| ContactsClients, other parties and referrers | HeldEach user’s Outlook contacts, and the firm’s directory of users. | Has a placeClients, related parties and prospects. | Carried across |
| DocumentsFiles stored in or linked from the system | HeldFiles in each user’s OneDrive and in SharePoint document libraries. | 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 | HeldMessages and attachments in every Exchange Online mailbox, by folder. | Has a place in partEmails saved to matters; mailboxes stay in Microsoft 365. | Carried with mapping |
| NotesFile notes, matter notes and contact notes | Held in partOneNote notebooks, where staff keep notes there. | Has a place | Carried across |
| CalendarAppointments, court dates and deadlines | HeldEach user’s Outlook calendar and any shared calendars. | Has a place | Carried across |
| TasksTo-dos and workflow steps assigned to people | Held in partPersonal tasks in To Do and team plans in Planner. | Has a place | Carried across |
| Custom fieldsFields and record types the firm added itself | Held in partOutlook categories on items; columns on SharePoint libraries. | Has a placeCreated and placed on page layouts before records are loaded. | Carried with mapping |
What the plans mean
- Carried across
- Centerbase has a place for this kind of record. It is loaded there and checked against Microsoft Graph.
- 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
A narrow move, checked like a large one.
A source like Microsoft Graph holds one kind of record well: an address book, a calendar, a set of signed documents. None of it is organised by matter. The work is matching each contact to a contact in Centerbase, and each appointment or signed document to the matter it belongs to. Where a match cannot be made from a name, an email address or a reference, the record is listed for the firm to place by hand or leave behind.
The volume is small and the load is quick, which makes it tempting to skip the checks. They still apply. Contacts are compared with what Centerbase already holds, so the move does not create a second copy of every client. Dates are checked for time zones, a common fault in calendar data. Signed documents arrive with their completion date and, where the service provides one, the audit record as a separate file.
Both are hosted by their makers, so nothing is collected from the firm’s office. What can be taken out of Microsoft Graph 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 Graph is kept running until the checks on Centerbase are finished.
Where the data is now
Leaving Microsoft Graph
Firms seldom leave Microsoft 365. They keep it for mail and move the matter-related part of what is in it into a practice or document system. So the work is selection: which mailboxes, which folders, which libraries, from what date. Access through Microsoft’s interface is granted by the firm’s administrator, who decides what can be read.
Consent sets the reach
An administrator approves the access. Application permissions are powerful: one granted for mail can read every mailbox in the firm. How far that reach is narrowed to the mailboxes and sites in scope, and when the access is removed, are the firm’s decisions, made with its administrator before anything is read.
Mailboxes are not matter files
Each mailbox mixes client work with staff matters, newsletters and private messages. The firm chooses between filing whole folders the owner already organised by matter, filing by correspondent and reference, or filing only from a date forward. Partners’ mailboxes usually get their own conversation before anything is read.
Shared mailboxes and leavers
Much matter correspondence sits outside personal mailboxes: in accounts@ and reception@ shared mailboxes, and in the mailboxes of former staff that were converted or kept on a licence. These are listed from the tenant, so the scope is drawn from what exists and not from the current staff list.
Files in two kinds of place
Documents are in personal OneDrives and in SharePoint libraries, including the ones behind Teams. Both are reached the same way, but they are scoped differently: OneDrives person by person, libraries site by site. A file shared from one person’s OneDrive is collected once, from its owner.
Microsoft sets the pace
Microsoft throttles heavy use of the interface and tells the calling software to wait. A large mailbox estate cannot be read in an afternoon however fast the connection. The trial load measures the real rate for this tenant, and the cutover window is planned from that figure.
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 Graph 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 Graph: 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 Graph, a final pass over a weekend picks up what changed since the trial. Microsoft Graph 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 Graph 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 Graph 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 Graph to Centerbase: what firms ask
Does this mean you can read all our email?
Only what the firm’s administrator consents to, for as long as that consent stands. Which permission is granted, which mailboxes are in scope and when the access ends are the firm’s decisions, settled before any mailbox is read. The consent stays visible in the Microsoft 365 admin tools, where the administrator can revoke it.
Will email be removed from our mailboxes when it is filed to matters?
Not as part of the move. Filing to a matter copies the message, and the original stays in the mailbox, in the folder it was in. Whether staff later tidy their mailboxes, and how the new system files incoming mail from then on, is a separate set-up decision.
We are staying on Microsoft 365. Do calendars and contacts need to move?
Usually the calendars stay where they are and the new system connects to them. Contacts are different. Clients held in people’s personal Outlook contact lists are worth gathering into the practice system once, merged against the client records already there, so the firm ends up with a single entry for each client.
Do documents from Microsoft Graph 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 Graph have a place in Centerbase?
On paper, yes: each kind of record Microsoft Graph 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 Graph data is loaded into Centerbase?
Emails and custom fields 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 Graph 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 Graph and Centerbase are the names and marks of their owners, used here only to identify the two systems.
Moving from Microsoft Graph 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.