Skip to content
NEWLAW.COM
+61 1300 495 281
Let’s talk

Data migration route

Centerbase data to Full data export

Centerbase is a cloud practice management system, and Full data export is a store of data kept as files the firm holds. This is not a move to a new working system: the route writes out what Centerbase holds and keeps it readable and open to queries.

FromCenterbaseCloud
  1. Matters: Exported in full
  2. Contacts: Exported in full
  3. Documents: Exported in full
  4. Notes: Exported in full
  5. Calendar: Exported in full
  6. Tasks: Exported in full
  7. Time and expenses: Exported in full
  8. Billing: Exported in full
  9. Trust money: Exported in full
  10. Emails: Exported with mapping
  11. Firm accounts: Exported with mapping
  12. Custom fields: Exported with mapping
  13. Templates: Exported with mapping
  14. Intake: Exported with mapping
ToFull data exportFiles
  • 9 carried
  • 5 mapped
What the two products hold. The analysis confirms it field by field.

What moves

What moves from Centerbase to Full data export

Each row is a kind of record Centerbase holds, whether Full data export has a place for it, and what is planned. On this route nine kinds of record carry across and five kinds need mapping.

Records in Centerbase and their place in Full data export
RecordIn CenterbaseIn Full data exportWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldMatters sit under clients and inherit client-level billing and accounting settings.Has a placeA matters table keyed by the original matter number.Exported in full
ContactsClients, other parties and referrersHeldClients, parties and other contacts, with a saved conflict check history.Has a placeA contacts table and a table of each contact’s role on each matter.Exported in full
DocumentsFiles stored in or linked from the systemHeldBuilt-in Document Storage, or NetDocuments, iManage or SharePoint connected to matters.Has a placeFiles under their original names, in client and matter folders.Exported in full
EmailsEmails saved to matters or to the storeHeld in partEmails and attachments filed to a matter through the Outlook integration.Has a place in partFiled emails as message files in the matter’s folder, if the source exposes them.Exported with mapping
NotesFile notes, matter notes and contact notesHeldHas a placeA notes table with matter, author and date for each note.Exported in full
CalendarAppointments, court dates and deadlinesHeldTwo-way sync with Outlook; court rules through LawToolBox.Has a placeA table of appointments and key dates; nothing shows it as a diary.Exported in full
TasksTo-dos and workflow steps assigned to peopleHeldTasks can be created by automated workflows.Has a placeA table of tasks with assignee, due date and status.Exported in full
Time and expensesTime and expense entries, billed and unbilledHeldIncludes passive time capture from Outlook and Word.Has a placeA time entries table with fee earner, matter, units, rate and billed status.Exported in full
BillingInvoices, payments and debtor balancesHeldElectronic pre-bill approval, multi-payor bills and LEDES formats.Has a placeInvoice, line and receipt tables; invoice PDFs can be kept beside them.Exported in full
Trust moneyTrust or client account ledgers and balancesHeldSeveral trust and retainer accounts can be held under one matter or at client level.Has a placeA trust transactions table; ledger reports can be kept as PDF beside it.Exported in full
Firm accountsGeneral ledger, office account and payablesHeldFull general ledger on a cash or accrual basis, with online banking and payables.Has a place in partJournals and account balances, where the source held a general ledger.Exported with mapping
Custom fieldsFields and record types the firm added itselfHeldUnlimited custom fields and configurable page layouts.Has a placeExtra columns under their original field names.Exported with mapping
TemplatesPrecedents, document templates and automationHeldDocument templates filled with client and matter data; bill templates.Has a place in partTemplate files only; the merge fields in them will not run.Exported with mapping
IntakeLeads, enquiries, intake forms and pipelinesHeldWeb form enquiries arrive as Potential New Client records.Has a place in partAn enquiries table, where the source tracked leads.Exported with mapping

What the plans mean

Exported in full
Full data export has a place for this kind of record. It is loaded there and checked against Centerbase.
Exported with mapping
Full data export 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

Not a new system. A complete copy the firm can query.

Writing Centerbase out to Full data export is not a migration into a new working system. Nobody will open a matter there on Monday morning. The aim is a complete, faithful copy that can be queried and reported on after the old system is gone. So the rules change. Nothing is cleaned or merged unless the firm asks, because an archive should show the records as they were. Every table and field is carried, including those a new system would have had no place for.

What makes an archive usable is the description that goes with it. The export is delivered with a plain account of each table: what it holds, how it joins to the others, what the codes mean. Record counts and financial totals are agreed to the reports in Centerbase as at the export date, so the archive can stand as the record. Documents are exported beside the data with a table linking each file to its matter. Access is restricted, since the archive holds everything the live system did.

Centerbase is hosted by its maker and Full data export sits on equipment the firm controls. The data leaves a service that was backed up for the firm and arrives somewhere the firm must back up itself, so backup and access are arranged before the export is copied in. What Centerbase will release depends on its export tools, and that is confirmed in the analysis.

Where the data is now

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.

  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. 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.

More about moving off Centerbase

Where it is going

A full export is judged by whether a stranger can use it. In five years the question will be something like: what was the trust balance on this matter the day it closed, and where is the signed agreement. The export is planned backwards from questions of that kind, and it is checked against the live system while the live system can still be opened.

  1. Tables that still join up

    Each kind of record becomes its own table: matters, contacts, time entries, invoices, trust transactions. The identifiers that link them are kept in every table, so a time entry can still be traced to its matter and its fee earner. An export that keeps the rows and drops the keys cannot be rejoined later.

  2. Documents with an index

    Documents are written to folders by client and matter under their original names. On their own they can be found only by name. An index listing each file with its matter number, title, author, dates and path is what lets someone find the right version of a lease among forty thousand files without the old system’s search. What the index records is settled in the analysis.

  3. Reports a person can read

    Raw tables do not satisfy an auditor or a former client. The firm decides which reports are also printed to PDF from the old system as at the final date: trust ledgers, matter ledgers, debtor lists and issued invoices are the usual candidates. They cannot be regenerated once the licence ends.

  4. What an export does not keep

    Screens, workflows, document automation, saved searches and user permissions belong to the software and stay with it. Figures the system calculated on the fly, such as a matter’s unbilled total, exist in an export only if they were captured as a report. The firm is told which of these are being let go.

  5. Checked while the source is open

    Record counts and financial totals in the export are reconciled to the live system: number of matters, sum of trust balances, total debtors, document count per matter on a sample. This is done before the subscription lapses or the server is turned off, because afterwards there is nothing left to compare against.

More about moving into Full data export

How NewLaw runs it

Four steps, in this order.

This route produces an archive, not a working system, so the steps are about completeness and proof.

  1. Analysis

    We read what Centerbase holds, table by table, and agree with you what the copy in Full data export must be able to answer later. Everything Centerbase holds is in scope unless you take it out.

  2. Clean-up, if you want it

    An archive should show the records as they were, so nothing is merged or corrected unless you ask. Where the copy is also meant for reporting, duplicate and inconsistent entries are tidied in a working copy and the original values are kept beside them.

  3. Trial export

    The data is written to Full data export as a trial and checked against Centerbase: record counts, totals where Centerbase holds money, the links between records, and a sample of documents opened from the export. Exceptions are listed for you to decide.

  4. Final export

    After the last day of work in Centerbase, the export is run a final time and checked again. There is nothing to go live. Centerbase is kept read only until you are satisfied the copy answers what you need, and it is handed over with a written description of its contents.

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

Step 1 of 5: Start with the route

Moving fromCenterbase
Moving toFull data export

The route comes from this page. Four short steps follow. Nothing you send commits your firm to anything.

What happens after you send it

  1. A free first call

    We go through your answers with you and ask about anything they leave open.

  2. An analysis of what Centerbase holds

    What is in it, how its records link, and where each piece would sit in Full data export. Anything with no place there comes across as a note or stays behind, and you see which before the move.

  3. 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

Full data export is a place to keep data, not a system staff work in each day. What is agreed is how the data is laid out, who can reach it, and what is handed over with it.

With no product to configure, the set-up is custody, and the decisions are the firm’s. Someone there owns the export, knows where it is kept and can open it. Access needs restricting, because it contains every client’s affairs in one place with none of the old system’s security. The firm sets a destruction date from its retention obligations and decides how the next custodian will learn to use it.

What is agreed and set up

  • Folder layout for tables, documents and reports
  • What the key to tables, columns and identifiers records
  • Where the copies are stored and who is custodian
  • Who may open it, as approved by a partner
  • Which look-ups staff must be able to do unaided
  • Retention period and the date it is next reviewed

Questions

Centerbase to Full data export: 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.

Does the copy in Full data export hold trust ledgers from Centerbase?

Yes. A trust transactions table; ledger reports can be kept as PDF beside it. Trust ledgers are written out with the rest, and counts and totals are agreed to the reports in Centerbase as at the export date.

Does everything in Centerbase have a place in Full data export?

On paper, yes: each kind of record Centerbase holds has a place in Full data export. 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 Centerbase is written out to Full data export?

Emails, the firm’s accounts, custom fields, templates and intake records are exported with mapping, so each mapping is agreed with you first. The firm also decides who may open the archive and how long it is kept.

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.

How we do itDiscovery to rollout, step by step

Centerbase and Full data export are the names and marks of their owners, used here only to identify the two systems.

Moving from Centerbase to Full data export?

Tell us what you are moving. You get a plan and a fixed price after the analysis.

We reply within one business day.