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

Data migration route

CasePacer to Centerbase migration

CasePacer is a cloud case management system for personal injury work, and Centerbase is a cloud practice management system. Case records move into matters, and time, billing and trust are set up in Centerbase, often from a separate accounts package.

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

What moves

What moves from CasePacer to Centerbase

Each row is a kind of record CasePacer holds, whether Centerbase has a place for it, and what is planned. On this route eight kinds of record carry across, one kind needs mapping and five kinds are confirmed in the analysis.

Records in CasePacer and their place in Centerbase
RecordIn CasePacerIn CenterbaseWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldCases, with master cases connecting related mass tort claims.Has a placeLoaded under their client, with practice-specific custom fields.Carried across
ContactsClients, other parties and referrersHeldHas a placeClients, related parties and prospects.Carried across
DocumentsFiles stored in or linked from the systemHeldCloud storage reached through CP Hub as a mapped drive. CP Link tracks versions.Has a placeInto Document Storage, or left in a connected NetDocuments, iManage or SharePoint store.Carried across
EmailsEmails saved to matters or to the storeTo be confirmedEmail integration is advertised. What is stored against a case was not confirmed.Has a place in partEmails saved to matters; mailboxes stay in Microsoft 365.Confirmed in the analysis
NotesFile notes, matter notes and contact notesHeldNotes and an activity log on each case.Has a placeCarried across
CalendarAppointments, court dates and deadlinesHeldCalendar inside the case, with Outlook syncing.Has a placeCarried across
TasksTo-dos and workflow steps assigned to peopleHeldTask workflows that run automatically.Has a placeCarried across
Time and expensesTime and expense entries, billed and unbilledHeldTime and expense tracking by case.Has a placeCarried across
BillingInvoices, payments and debtor balancesTo be confirmedHas a placeThe vendor says billing history can be migrated; the depth is set in the analysis.Confirmed in the analysis
Trust moneyTrust or client account ledgers and balancesTo be confirmedHas a placeMultiple trust and retainer accounts per matter or client.Confirmed in the analysis
Firm accountsGeneral ledger, office account and payablesTo be confirmedHas a placeGeneral ledger with chart of accounts; opening trial balance agreed with the accountant.Confirmed in the analysis
Custom fieldsFields and record types the firm added itselfTo be confirmedHas a placeCreated and placed on page layouts before records are loaded.Confirmed in the analysis
TemplatesPrecedents, document templates and automationHeldDocument templates and task workflows.Has a place in partTemplates are rebuilt to merge Centerbase client and matter data.Carried with mapping
IntakeLeads, enquiries, intake forms and pipelinesHeld in partIntake is part of the case workflow. Clients complete smart forms in CP Direct.Has a placeEnquiries are held as Potential New Client records; loading open ones is confirmed in the analysis.Carried across

What the plans mean

Carried across
Centerbase has a place for this kind of record. It is loaded there and checked against CasePacer.
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

Cases come across. The accounts are set up new.

A case management system holds the working file: parties, notes, deadlines, documents and the fields a practice area needs. It is not usually the firm’s ledger, so time, invoices and trust often sit in an accounting package beside it. Moving to Centerbase brings those two sources together. The case records come from CasePacer. Opening balances for debtors and trust, where they move at all, come from the accounts package and are agreed to its reports.

Case systems are heavy with custom fields, and that is where the mapping work is. A personal injury or immigration file can carry dozens of fields that a general practice system has no standard place for. Each one is matched to a field in Centerbase, created there as a custom field, or written into a note on the matter. The firm sees which before the load. Workflows and task templates are rebuilt, not copied.

Both are hosted by their makers, so nothing is collected from the firm’s office. What can be taken out of CasePacer 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 CasePacer is kept running until the checks on Centerbase are finished.

Where the data is now

A CasePacer move is a personal injury or mass tort data set leaving a cloud system: cases, parties, insurers, treatment and settlement figures, and a large volume of documents. The size of the docket matters more than the number of users, because a mass tort firm can hold thousands of near-identical claims under a handful of master cases.

  1. Master cases and their claims

    A mass tort is held as a master case with the individual claims connected beneath it. That connection is what lets the firm see one litigation as a whole. Each destination models this differently, as related matters, a project or a group, so the structure is agreed first and the claims are loaded against it.

  2. Files seen through CP Hub

    Staff open documents through CP Hub, a mapped drive in File Explorer, so the folder layout they see is the working structure. That layout is recorded case by case before extraction, and the folder a document sat in is kept, since paralegals find medical records and pleadings by where they were filed.

  3. Version history in CP Link

    CP Link keeps versions of a document as it is edited. Whether earlier versions can be extracted, and whether the destination keeps versions at all, is settled in the analysis. Where they cannot be carried as versions, the current one is loaded and the earlier ones are filed beside it with a dated name.

  4. Client uploads from CP Direct

    Clients send photos, videos and documents from their phones through CP Direct, and answer questionnaires that write straight into the case. Those uploads arrive without a firm naming convention. They are marked as client-supplied in the new system, so evidence from the plaintiff is not mixed in with correspondence the firm produced.

More about moving off CasePacer

Where it is going

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.

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

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

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

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

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

More about moving into Centerbase

How NewLaw runs it

Four steps, in this order.

Financial records move on this route, so the balances are rehearsed before the real cutover.

  1. Analysis

    We read what CasePacer 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.

  2. Clean-up

    Duplicate contacts and matters are merged where they can be identified, and inconsistent entries are put into one format, in CasePacer, before extraction. It is not always possible to find every one, so some may carry across.

  3. Trial load

    The data is loaded into Centerbase as a trial and checked against CasePacer: record counts, financial totals, the links between records, document dates. Exceptions are listed for you to decide.

  4. Cutover

    Changes in CasePacer 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 CasePacer as at the cutover date. CasePacer 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 CasePacer 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 fromCasePacer
Moving toCenterbase

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

  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

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

CasePacer to Centerbase: what firms ask

How are master cases handled in a system that has no such thing?

The claims become ordinary cases and the connection is rebuilt with whatever the destination offers: a related-matter link, a group field, or a parent record. Reports that ran across the whole litigation are rebuilt on that link. The trial load is checked by counting claims under each master case on both sides.

Will the folders we see in File Explorer look the same afterwards?

The folder names and the documents in them can be reproduced. How staff reach them will change, because the mapped drive belongs to CasePacer. Some destinations offer a desktop sync or a document add-in, and others work only in the browser. That difference is shown to the firm before it chooses, not after.

Do closed cases have to move?

No. Settled cases can come across in full, come across as a summary with their documents, or stay in an export the firm keeps. The usual test is how often a closed case is reopened for a lien query or a later claim. That choice is the firm’s, and the scope is written down before the trial load.

Do trust balances in CasePacer 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 CasePacer 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 CasePacer have a place in Centerbase?

Most of it does on paper. Emails, billing records, trust ledgers, the firm’s accounts and custom fields 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 CasePacer data is loaded into Centerbase?

Templates are carried with mapping, so each mapping is agreed with you first. Emails, billing records, trust ledgers, the firm’s accounts and custom fields are confirmed in the analysis. The firm also sets the cutover date and how much financial history comes across as live records.

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

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

Moving from CasePacer 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.