Data migration route
Centerbase to Google Drive migration
Centerbase is a cloud practice management system, and Google Drive is cloud file storage. Documents move into a folder for each client and matter, and the data behind them is kept as an export.
CenterbaseCloud- Documents: Carried across
- Emails: Carried with mapping
- Notes: Carried with mapping
- Templates: Carried with mapping
Google DriveCloud- Matters: Kept as a readable archive
- Contacts: Kept as a readable archive
- Calendar: Kept as a readable archive
- Tasks: Kept as a readable archive
- Time and expenses: Kept as a readable archive
- Billing: Kept as a readable archive
- Trust money: Kept as a readable archive
- Firm accounts: Kept as a readable archive
- Custom fields: Kept as a readable archive
- Intake: Kept as a readable archive
- 1 carried
- 3 mapped
- 10 archived
What moves
What moves from Centerbase to Google Drive
Each row is a kind of record Centerbase holds, whether Google Drive has a place for it, and what is planned. On this route one kind of record carries across, three kinds need mapping and ten kinds have no place in Google Drive and are archived.
| Record | What is planned | ||
|---|---|---|---|
| MattersMatters or cases, with their numbers, types, parties and status | HeldMatters sit under clients and inherit client-level billing and accounting settings. | No placeA matter is a folder inside a shared drive. | Kept as a readable archive |
| ContactsClients, other parties and referrers | HeldClients, parties and other contacts, with a saved conflict check history. | No placeContacts belong in Google Contacts, not Drive. | Kept as a readable archive |
| DocumentsFiles stored in or linked from the system | HeldBuilt-in Document Storage, or NetDocuments, iManage or SharePoint connected to matters. | Has a placeAny file type, stored as uploaded or converted to Google formats. | Carried across |
| EmailsEmails saved to matters or to the store | Held in partEmails and attachments filed to a matter through the Outlook integration. | Has a place in partAs .eml or .msg files in the matter folder; not as Gmail messages. | Carried with mapping |
| NotesFile notes, matter notes and contact notes | Held | Has a place in partAs a Doc or Word file in the matter’s folder. | Carried with mapping |
| CalendarAppointments, court dates and deadlines | HeldTwo-way sync with Outlook; court rules through LawToolBox. | No placeCalendar entries belong in Google Calendar. | Kept as a readable archive |
| TasksTo-dos and workflow steps assigned to people | HeldTasks can be created by automated workflows. | No place | Kept as a readable archive |
| Time and expensesTime and expense entries, billed and unbilled | HeldIncludes passive time capture from Outlook and Word. | No place | Kept as a readable archive |
| BillingInvoices, payments and debtor balances | HeldElectronic pre-bill approval, multi-payor bills and LEDES formats. | No place | Kept as a readable archive |
| Trust moneyTrust or client account ledgers and balances | HeldSeveral trust and retainer accounts can be held under one matter or at client level. | No place | Kept as a readable archive |
| Firm accountsGeneral ledger, office account and payables | HeldFull general ledger on a cash or accrual basis, with online banking and payables. | No place | Kept as a readable archive |
| Custom fieldsFields and record types the firm added itself | HeldUnlimited custom fields and configurable page layouts. | No place | Kept as a readable archive |
| TemplatesPrecedents, document templates and automation | HeldDocument templates filled with client and matter data; bill templates. | Has a place in partPrecedents load as files; the load does not rebuild Word automation in Docs. | Carried with mapping |
| IntakeLeads, enquiries, intake forms and pipelines | HeldWeb form enquiries arrive as Potential New Client records. | No place | Kept as a readable archive |
What the plans mean
- Carried across
- Google Drive has a place for this kind of record. It is loaded there and checked against Centerbase.
- Carried with mapping
- Google Drive holds this differently, or in part. Each field or value is matched to its place before loading, and you see the mapping first.
- Kept as a readable archive
- Google Drive has no place for it. It is exported in a format that opens without Centerbase and handed to the firm as a read-only archive.
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
Out of the system, into folders the firm can read.
File storage has folders and files and nothing else. Moving from Centerbase into Google Drive means turning matters into a folder tree, usually client, then matter, then the folders used inside it. The naming rule is agreed first, because it is hard to change once thousands of folders exist: whether the matter number leads, how closed matters are separated, what happens to characters Google Drive does not allow in a name.
Everything that is not a document needs somewhere to go. Contacts, notes, time, invoices and trust ledgers have no place in a folder, so they are exported as spreadsheets and reports and stored alongside, often as a summary file in each matter folder and a full set in an archive area. Firms choose this route to keep a readable copy of a system they are retiring, or as a staging step. The export is checked either way: folders against matters, files against the document register in Centerbase.
Both are hosted by their makers, so nothing is collected from the firm’s office. What can be taken out of Centerbase 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 Centerbase is kept running until the checks on Google Drive are finished.
Where the data is now
Leaving Centerbase
No two Centerbase sites look alike, because the product is configured around each firm. A firm leaving it is moving its own design as much as its data: the fields it added, the workflows it automated, the way bills are approved. The analysis begins by documenting that configuration, since the meaning of many records depends on it, and then deals with the general ledger and trust accounts.
Each site is configured
Custom fields are unlimited and page layouts are designed per firm, so the same information may be stored in quite different places from one Centerbase site to the next. A field list is extracted with usage counts. Fields that were added and abandoned are common in a long-lived site, and the firm decides which are worth carrying.
Settings inherited from clients
Billing arrangements, rate tables and accounting preferences are set on the client and applied to its matters. A destination that holds these on the matter needs them copied down to every matter, and one that has no rate tables needs rates entered another way. Either route is tested on a client with unusual terms.
Several trusts per matter
One matter can have more than one trust or retainer account, and funds can also be tracked at client level. Many systems allow a single trust ledger per matter. Where that is so, the firm decides how the separate balances are shown, and each one is still reconciled to its Centerbase figure before cutover.
Pre-bills in the approval chain
Pre-bills move electronically through reviewers, collecting mark-ups as they go. A pre-bill caught mid-approval at cutover has edits that live nowhere else. It is simplest to finish the billing cycle before the freeze, so that what moves is either unbilled time or a finished invoice.
Where documents really are
Documents may be in Centerbase’s own Document Storage, or in NetDocuments, iManage or SharePoint with Centerbase supplying the matter link. Only the first set has to be extracted. For the others the files stay put and the work is re-attaching each workspace to its matter in the new system.
Where it is going
Arriving in Google Drive
Putting a firm’s matter files into Google Drive means choosing shared drives over personal ones and then deciding how many shared drives there should be. That second decision is driven by Google’s limits and by who is allowed to see what, since access is granted mainly at the level of the whole shared drive.
Shared drives, not My Drive
Files loaded into a shared drive belong to the firm and remain when the person who loaded them leaves. Anything loaded into someone’s My Drive belongs to that person. Matter files therefore go to shared drives, and My Drive is left for personal working papers.
One drive cannot hold everything
Google caps a shared drive at 500,000 items, counting folders, shortcuts and anything in the trash, and at 100 levels of nested folders. A firm with twenty years of matters can pass the item cap in a single drive. The split is planned up front, commonly by practice group, or by open and closed matters.
Membership is the main control
Every member of a shared drive can see all of it unless a Manager restricts a particular folder. Matters that only certain people may open are simpler to protect in a shared drive of their own. The firm supplies the list of restricted matters and partners’ private folders before the drives are created.
The daily upload limit
Each user can upload 750 GB to Drive in 24 hours, and then has to wait. For a large document set that limit sets the shortest time the load can take. The total size is measured in the analysis, so the firm knows before the freeze whether its documents fit inside a weekend.
Keep Office files as Office files
Word and Excel files can be stored in Drive as they are or converted to Google formats. Unless the firm asks otherwise they are loaded unconverted, so court documents and automated precedents arrive as they left. The firm decides afterwards which templates are worth rebuilding as Google Docs.
How NewLaw runs it
Four steps, in this order.
Nothing financial lands in Google Drive on this route, which makes it repeatable: a load can be run again until it is right.
Analysis
We read what Centerbase holds and how it is organised, then agree with you where each kind of record will sit in Google Drive. 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 Google Drive and checked against Centerbase: 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 Centerbase, a final pass over a weekend picks up what changed since the trial. Centerbase 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 Centerbase 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 Centerbase holds
What is in it, how its records link, and where each piece would sit in Google Drive. 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
Google Drive is storage, not an application, so there is no product to configure. What is agreed and set up is the folder structure, who can open what, and how the result is handed to the firm.
A Drive set-up for a law firm is a small number of deliberate choices made in the Workspace Admin console and then left alone. Which shared drives exist, who manages each, whether staff may share outside the firm, and whether people work from the browser or from Drive for desktop. Staff also need to be shown where a new matter folder goes.
What is agreed and set up
- Shared drives by practice group, with a naming pattern
- Managers and member access levels for each shared drive
- External sharing rules set in the Admin console
- Drive for desktop on PCs that need Explorer access
- A standard subfolder set copied into every new matter
- Transfer of leavers’ My Drive files as a standing procedure
Questions
Centerbase to Google Drive: what firms ask
We keep our accounts in Centerbase. Do we have to change accounting systems as well?
Only if the destination does not have a general ledger. Centerbase holds the firm’s books and its trust records together, so the two leave together. Where the new system is practice management only, an accounting package is chosen and opened first, and opening balances are taken at a closed period end.
Can our financial history be loaded into Centerbase, or just balances?
The vendor describes moving practice management, billing, trust and accounting data, with a test migration validated before go-live. How many years of transactions are worth loading is a separate question. It is settled in the analysis by looking at what the source can supply cleanly and what the firm really reports on.
Our documents are in iManage. Does anything change for them?
The documents do not move. Centerbase connects to iManage and to NetDocuments, so the files stay in the document system the firm already uses. The work is matching each workspace to the right client and matter number, which is why matter numbering is fixed before the trial load.
Do trust balances in Centerbase have a place in Google Drive?
No. Google Drive does not keep trust ledgers. Trust records from Centerbase are exported as ledgers and statements that open without it, and the firm settles where its trust accounting runs from the cutover date before the move is planned.
What happens to records Google Drive has no place for?
On this route that is matters, contacts, calendar entries, tasks, time entries, billing records, trust ledgers, the firm’s accounts, custom fields and intake records. They are exported from Centerbase in formats that open without it, spreadsheets and PDFs, and handed to the firm as a read-only archive. You see the list before the move.
What has to be decided before Centerbase data is loaded into Google Drive?
Emails, notes 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 Centerbase and into Google Drive
Other destinations from Centerbase
Other systems that move into Google Drive
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.
Centerbase and Google Drive are the names and marks of their owners, used here only to identify the two systems.
Moving from Centerbase to Google Drive?
Tell us what you are moving. You get a plan and a fixed price after the analysis.
We reply within one business day.