Data migration route
Time Matters to Centerbase migration
Time Matters is a server-based practice management system, and Centerbase is a cloud one. Both run a whole practice, so this is a full move, and the financial records set the timetable.
Time MattersServer- Matters: Carried across
- Contacts: Carried across
- Documents: Carried across
- Notes: Carried across
- Calendar: Carried across
- Tasks: Carried across
- Time and expenses: Carried across
- Billing: Carried across
- Emails: Carried with mapping
- Custom fields: Carried with mapping
- Templates: Carried with mapping
- Trust money: Confirmed in the analysis
- Intake: Confirmed in the analysis
CenterbaseCloud- 8 carried
- 3 mapped
- 2 to confirm
What moves
What moves from Time Matters to Centerbase
Each row is a kind of record Time Matters holds, whether Centerbase has a place for it, and what is planned. On this route eight kinds of record carry across, three kinds need mapping and two kinds are confirmed in the analysis.
| Record | What is planned | ||
|---|---|---|---|
| MattersMatters or cases, with their numbers, types, parties and status | Held | Has a placeLoaded under their client, with practice-specific custom fields. | Carried across |
| ContactsClients, other parties and referrers | Held | Has a placeClients, related parties and prospects. | Carried across |
| DocumentsFiles stored in or linked from the system | HeldDocuments are created, searched and tied to clients and matters. | 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 | HeldEmails and attachments are managed against matters. | Has a place in partEmails saved to matters; mailboxes stay in Microsoft 365. | Carried with mapping |
| NotesFile notes, matter notes and contact notes | HeldNotes and phone calls are separate records. | Has a place | Carried across |
| CalendarAppointments, court dates and deadlines | HeldCalled Events. | Has a place | Carried across |
| TasksTo-dos and workflow steps assigned to people | HeldCalled ToDos. | Has a place | Carried across |
| Time and expensesTime and expense entries, billed and unbilled | HeldTime and expenses. | Has a place | Carried across |
| BillingInvoices, payments and debtor balances | Held in partBasic billing; advanced billing in the Billing Matters edition. | Has a placeThe vendor says billing history can be migrated; the depth is set in the analysis. | Carried across |
| Trust moneyTrust or client account ledgers and balances | To be confirmed | Has a placeMultiple trust and retainer accounts per matter or client. | Confirmed in the analysis |
| Custom fieldsFields and record types the firm added itself | HeldForms, fields and record layouts are set by the firm. | Has a placeCreated and placed on page layouts before records are loaded. | Carried with mapping |
| TemplatesPrecedents, document templates and automation | HeldMerge Templates, AutoEntry Forms, Triggers and Chains. | Has a place in partTemplates are rebuilt to merge Centerbase client and matter data. | Carried with mapping |
| IntakeLeads, enquiries, intake forms and pipelines | To be confirmed | Has a placeEnquiries are held as Potential New Client records; loading open ones is confirmed in the analysis. | Confirmed in the analysis |
What the plans mean
- Carried across
- Centerbase has a place for this kind of record. It is loaded there and checked against Time Matters.
- 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.
- 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.
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 whole practice moves, accounts included.
A move between two practice management systems is the widest kind there is. Time Matters and Centerbase each keep matters, contacts, documents, time and money in one place, but no two systems link those records the same way. In one, a client is a contact with a role on the matter. In another, every matter carries its own client card. Most of the analysis goes into those links, because a matter that arrives without its client or its documents is the first thing staff find.
The financial side decides the dates. Unbilled time, debtor balances and trust ledgers have to agree with Time Matters’s own reports as at one day, and a new system usually wants them as opening balances, not as years of transactions. So the firm decides early how much history comes across as live records and how much is kept as reports. Matter and document loads can be repeated until they are right. The money is loaded once.
Time Matters runs on the firm’s own equipment, so the data is collected there: a copy of the database and the folders its documents sit in, taken with the firm’s IT provider or over a remote session. Centerbase is hosted by its maker, so loading depends on the import tools and access it provides. The old machine is kept, read only, as the fall-back record.
Where the data is now
Leaving Time Matters
Firms that have used Time Matters for years have usually reshaped it, and that is what takes thought when leaving. The standard records, which are contacts, matters, events, to-dos, notes, phone calls, emails and documents, move in a predictable way. What differs in every installation is the firm’s own forms, added fields, Triggers and Chains, and the analysis spends most of its time there.
Forms the firm redesigned
Record forms, field labels and layouts can be changed by the firm. A field that the default form calls one thing may carry a different label, and a different meaning, on the firm’s version. The mapping is made from the firm’s own form definitions, never from the default names.
Triggers and Chains
Triggers start tasks or events when a date or status changes, and Chains join steps into a sequence. AutoEntry Forms cut down repeated entry. The records they created come across, but the rules do not, so the processes that still matter are written down with the staff who use them and rebuilt in the destination.
Every record type is separate
Events, ToDos, phone calls, notes, emails and documents are distinct kinds of record, each tied to a matter or contact. Phone records in particular have no equivalent in many systems, and are loaded as dated notes. Counts for each record type are checked against Time Matters matter by matter.
Billing may be elsewhere
Time and expenses are recorded here, but invoices and ledgers may be kept in PCLaw or QuickBooks through a link, or in Billing Matters. The move identifies which, and treats that program as a second source. Matters are paired across the two using the reference the link relies on.
Supported versions turn over
The vendor retires versions on a published schedule, release by release, so a firm that has not upgraded for a few years may be on one that is out of support. It can still be moved. Its backup is checked early, since vendor help with a failed restore may not be on offer for a retired release.
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.
Financial records move on this route, so the balances are rehearsed before the real cutover.
Analysis
We read what Time Matters holds and how its records link, then agree with you, field by field, where each piece will sit in Centerbase. Anything with no place there comes across as a note or stays behind, and you see which before the move.
Clean-up
Duplicate contacts and matters are merged where they can be identified, and inconsistent entries are put into one format, in Time Matters, before extraction. It is not always possible to find every one, so some may carry across.
Trial load
The data is loaded into Centerbase as a trial and checked against Time Matters: record counts, financial totals, the links between records, document dates. Exceptions are listed for you to decide.
Cutover
Changes in Time Matters are frozen for an agreed window, the data is collected a final time and Centerbase goes live over a weekend. The financial cutover is rehearsed on a full trial load first, so that opening balances agree with the reports in Time Matters as at the cutover date. Time Matters 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 Time Matters 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 Time Matters 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
Time Matters to Centerbase: what firms ask
Do our documents come across with their matter links?
Each document in Time Matters has a record that ties it to a client or matter. The record supplies the matter, description and date, and the file supplies the content. Both are needed. Where a record refers to a file that has been moved or deleted, it is reported before the trial load.
Can we keep our custom fields?
The ones in use, yes, if the destination has custom fields for matters and contacts. Every field the firm added is listed in the analysis with how often it is filled. Fields that held structured data move as fields. Those used as scratch space usually become part of a note, by the firm’s choice.
We link Time Matters to PCLaw. Do they move together?
They should be planned together even if they go live a few days apart. The link keeps clients, matters and time in step between the two, and both feed the new system. One matter list is built from both, with PCLaw as the authority for money and Time Matters for the rest.
Do trust balances in Time Matters have a place in Centerbase?
That is confirmed in the analysis. We could not establish it from the two products’ own material, so it is checked against your data in Time Matters before the plan is fixed. If Centerbase turns out to have no place for trust ledgers, they are kept as a readable archive and the firm decides where trust accounting runs.
Does everything in Time Matters have a place in Centerbase?
Most of it does on paper. Trust ledgers and intake records could not be confirmed from the two products’ own material, so those are checked in the analysis. Anything that turns out to have no place in Centerbase is kept as a readable archive, and you see which before the move.
What has to be decided before Time Matters data is loaded into Centerbase?
Emails, custom fields and templates are carried with mapping, so each mapping is agreed with you first. Trust ledgers and intake records are confirmed in the analysis. The firm also sets the cutover date and how much financial history comes across as live records.
Other routes
Other routes from Time Matters and into Centerbase
Other destinations from Time Matters
Other systems that move 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.
Time Matters and Centerbase are the names and marks of their owners, used here only to identify the two systems.
Moving from Time Matters 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.