Data migration route
Centerbase to NetDocuments migration
Centerbase is a cloud practice management system, and NetDocuments is a cloud document management system. Documents and email move, filed under the matters they came from. Time, billing and trust have no place in a document system.
CenterbaseCloud- Documents: Carried across
- Emails: Carried across
- Matters: Carried with mapping
- Custom fields: Carried with mapping
- Templates: Carried with mapping
- Tasks: Confirmed in the analysis
NetDocumentsCloud- Contacts: Kept as a readable archive
- Notes: Kept as a readable archive
- Calendar: 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
- Intake: Kept as a readable archive
- 2 carried
- 3 mapped
- 1 to confirm
- 8 archived
What moves
What moves from Centerbase to NetDocuments
Each row is a kind of record Centerbase holds, whether NetDocuments has a place for it, and what is planned. On this route two kinds of record carry across, three kinds need mapping, eight kinds have no place in NetDocuments and are archived and one kind is confirmed in the analysis.
| 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. | Has a place in partAs a client and matter value with its workspace. Other matter details stay in practice management. | Carried with mapping |
| ContactsClients, other parties and referrers | HeldClients, parties and other contacts, with a saved conflict check history. | No place | 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 placeImported with profile values, folder, dates and access set per document. | 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 placeLoaded as email items profiled to the matter. | Carried across |
| NotesFile notes, matter notes and contact notes | Held | No placeFile notes are loaded as documents in the matter workspace. | Kept as a readable archive |
| CalendarAppointments, court dates and deadlines | HeldTwo-way sync with Outlook; court rules through LawToolBox. | No place | Kept as a readable archive |
| TasksTo-dos and workflow steps assigned to people | HeldTasks can be created by automated workflows. | To be confirmed | Confirmed in the analysis |
| 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. | Has a placeAs custom profile attributes, created in the repository before the load. | Carried with mapping |
| TemplatesPrecedents, document templates and automation | HeldDocument templates filled with client and matter data; bill templates. | Has a place in partLoaded as documents in a precedents cabinet or workspace. Automation is set up afresh. | 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
- NetDocuments has a place for this kind of record. It is loaded there and checked against Centerbase.
- Carried with mapping
- NetDocuments holds this differently, or in part. Each field or value is matched to its place before loading, and you see the mapping first.
- Confirmed in the analysis
- We could not confirm this from the two products’ own material, so it is checked against your data before the plan is fixed.
- Kept as a readable archive
- NetDocuments 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
The documents move. The accounts do not.
Moving from a matter system into a document management system is a documents job. NetDocuments has no place for time, invoices or trust, so there is no financial cutover on this route. What it does want is structure. Every document from Centerbase is filed into a workspace or folder for its client and matter, with a profile that says what it is. The client and matter list becomes that structure, which is why it is cleaned before any file is copied.
A document’s own details count for more here than anywhere. Created and modified dates, author, document type and version become searchable profile fields, and a wrong date on a few thousand files is hard to undo. Email filed to matters is carried as messages. Document copies can be run again, so the trial is repeated until counts and dates agree. Matter data that NetDocuments cannot hold goes to whatever replaces Centerbase for matters and billing, or into an archive.
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 NetDocuments 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 NetDocuments
Loading into NetDocuments means every document arrives with a profile. The cabinet, its profile attributes and the client and matter lookup tables are built first. Documents are then imported with an instruction file that says, line by line, which file gets which client, matter, author, document type, folder and access. Preparing that file from the old system’s data is most of the work.
Lookup tables before documents
Client and matter are validated attributes, with matter the child of client. A value missing from the lookup table cannot be used to profile a document. The tables are loaded from the practice management system first, closed matters included, and each matter is flagged open or closed so old ones stay out of pick lists.
Workspaces come from the profile
A workspace shows whatever is profiled to its matter. So the question is not where to put a folder tree but how to profile each file. Old folder names are often turned into a document type attribute, or kept as a workspace folder, and the mapping decides which for each one.
Import files are unforgiving
The import file is comma-separated text, and NetDocuments itself warns that opening one in Excel can strip leading zeros from numbers and alter dates. A matter number of 00123 that becomes 123 will not match its lookup value. The files are kept as plain text from start to finish and are not opened in a spreadsheet.
Folder limits and depth
A folder can hold any number of documents but no more than 500 subfolders. Deep trees copied from a file server also work against the way the system is searched. Where a matter arrives with hundreds of nested folders, the plan flattens them and keeps the lost path in the document name or an attribute.
Security at the right level
Access can be set on the cabinet, by profile value, on a workspace or on a single document. Restricted matters are best carried as workspace or profile-based security, so that new documents pick it up. Document-by-document access lists copied from an old system are loaded only where the restriction was real.
How NewLaw runs it
Four steps, in this order.
Nothing financial lands in NetDocuments 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 NetDocuments. 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 NetDocuments 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 NetDocuments. 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 NetDocuments
Loaded data is not yet a working system. This is what NewLaw sets up in NetDocuments, beyond the migration, so that people can work in it from the first day.
Beyond the load, NetDocuments has to be designed: how many cabinets the firm needs, which profile attributes every document must carry, and what a new matter’s workspace looks like on its first day. After that it is connected to the practice management system so client and matter lists stay current, and ndOffice and the email filing tools are set up for each person, with training on profiling.
Set-up decisions in NetDocuments
- Cabinet design: one for the firm, or several by purpose
- Profile attributes, lookup tables and the client and matter hierarchy
- Workspace layout with default folders, filters and saved searches
- User groups, cabinet membership and security for restricted matters
- A feed of new clients and matters from practice management
- ndOffice, ndMail and Outlook filing on every desk, with training
Questions
Centerbase to NetDocuments: 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 NetDocuments?
No. NetDocuments 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 NetDocuments has no place for?
On this route that is contacts, notes, calendar entries, time entries, billing records, trust ledgers, the firm’s accounts 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 NetDocuments?
Matters, custom fields and templates are carried with mapping, so each mapping is agreed with you first. Tasks are confirmed in the analysis. 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 NetDocuments
Other destinations from Centerbase
Other systems that move into NetDocuments
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 NetDocuments are the names and marks of their owners, used here only to identify the two systems.
Moving from Centerbase to NetDocuments?
Tell us what you are moving. You get a plan and a fixed price after the analysis.
We reply within one business day.