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

Data migration route

Centerbase to Filevine migration

Centerbase is a cloud practice management system, and Filevine is a cloud case management system. Matter records move into cases, and the firm decides where its accounting runs from the cutover date.

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

What moves

What moves from Centerbase to Filevine

Each row is a kind of record Centerbase holds, whether Filevine has a place for it, and what is planned. On this route seven kinds of record carry across, six kinds need mapping and one kind is confirmed in the analysis.

Records in Centerbase and their place in Filevine
RecordIn CenterbaseIn FilevineWhat 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 placeLoaded as projects of a defined project type.Carried across
ContactsClients, other parties and referrersHeldClients, parties and other contacts, with a saved conflict check history.Has a placeContact cards, linked to projects.Carried across
DocumentsFiles stored in or linked from the systemHeldBuilt-in Document Storage, or NetDocuments, iManage or SharePoint connected to matters.Has a placeDocs section with folders. Templated project folders can be set per type.Carried across
EmailsEmails saved to matters or to the storeHeld in partEmails and attachments filed to a matter through the Outlook integration.Has a placeHeld in the activity feed of the project.Carried across
NotesFile notes, matter notes and contact notesHeldHas a placeHeld as notes in the activity feed.Carried across
CalendarAppointments, court dates and deadlinesHeldTwo-way sync with Outlook; court rules through LawToolBox.Has a placeDeadlines and calendar events.Carried across
TasksTo-dos and workflow steps assigned to peopleHeldTasks can be created by automated workflows.Has a placeCarried across
Time and expensesTime and expense entries, billed and unbilledHeldIncludes passive time capture from Outlook and Word.Has a place in partNeeds the Billing product enabled.Carried with mapping
BillingInvoices, payments and debtor balancesHeldElectronic pre-bill approval, multi-payor bills and LEDES formats.Has a place in partNeeds the Billing product enabled.Carried with mapping
Trust moneyTrust or client account ledgers and balancesHeldSeveral trust and retainer accounts can be held under one matter or at client level.Has a place in partTrust accounts sit in Payments by Filevine. Loading history is confirmed in the analysis.Carried with mapping
Firm accountsGeneral ledger, office account and payablesHeldFull general ledger on a cash or accrual basis, with online banking and payables.To be confirmedConfirmed in the analysis
Custom fieldsFields and record types the firm added itselfHeldUnlimited custom fields and configurable page layouts.Has a placeCustom sections and fields per project type.Carried with mapping
TemplatesPrecedents, document templates and automationHeldDocument templates filled with client and matter data; bill templates.Has a place in partTemplates are rebuilt as Filevine document templates. They are not converted.Carried with mapping
IntakeLeads, enquiries, intake forms and pipelinesHeldWeb form enquiries arrive as Potential New Client records.Has a place in partLeads belong in Lead Docket, which passes signed clients to Filevine.Carried with mapping

What the plans mean

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

Matters become cases. The ledgers need a home.

Going from a practice management system to a case management system is a move towards the file and away from the ledger. Matters, parties, documents, notes and deadlines have a natural place in Filevine. Time, invoices, trust and the general ledger often do not, or only in part, and the table above shows which. Before the move is planned the firm settles where billing and trust accounting will run, because that decides what is loaded and what is archived.

Case systems are usually built around a practice area, with their own stages, roles and document sets. A general matter from Centerbase has to be given a case type in Filevine, and that choice drives which fields and workflows it gets. The mapping is agreed type by type. Financial history with no place in Filevine is exported as reports and ledgers the firm can open without Centerbase, and kept as the record of what was billed and held.

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 Filevine are finished.

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

Loading a firm into Filevine depends on the project types being built first. Until the sections and fields exist there is nowhere for the data to go, so configuration and migration are planned together. The old system’s parties, insurers, providers and key dates are mapped to sections, and its notes and emails are loaded into each project’s activity feed.

  1. Project types before data

    Each area of practice needs a project type with its sections, fields and phases defined in the Customs Editor. Changes made there apply to every project of that type. The types are drafted from the old system’s data, tested with a few real cases, and only then is the bulk load run.

  2. One contact card per person

    Contacts are held as contact cards. A doctor or adjuster who appears on many projects is best loaded as one card, not one for each project. Duplicates in the old system are merged before loading where they can be identified. Loading them as they are produces several cards for the same person, and staff then pick the wrong one when adding a party.

  3. Lists become collection items

    Anything the old system held as a list against a matter, such as providers, liens, insurance policies or expenses, is loaded as items in a collection section. Each column needs a matching field. Totals per project are compared with the old system afterwards, since those figures feed the settlement and disbursal sheets.

  4. History goes into the feed

    File notes, emails and completed tasks from the old system are loaded into the activity feed with their original dates and authors. Authors must exist as users or be recorded in the text. The feed is long on an old case, so staff are shown how to filter it before go-live.

  5. Billing is a separate switch

    The Billing section only appears once Billing is enabled for the firm. Time entries, invoices and trust balances from the old system need that in place before they can be loaded. A firm that leaves it off can still record case costs in a collection section built for the purpose.

More about moving into Filevine

How NewLaw runs it

Four steps, in this order.

Trust money moves on this route, so the trust cutover gets a rehearsal of its own.

  1. Analysis

    We read what Centerbase holds and how its records link, then agree with you, field by field, where each piece will sit in Filevine. 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 Centerbase, before extraction. It is not always possible to find every one, so some may carry across.

  3. Trial load

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

  4. Cutover

    Changes in Centerbase are frozen for an agreed window, the data is collected a final time and Filevine goes live over a weekend. The trust and financial cutover is rehearsed on a full trial load first, because it cannot be re-run the way a document load can. 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

Step 1 of 5: Start with the route

Moving fromCenterbase
Moving toFilevine

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

Loaded data is not yet a working system. This is what NewLaw sets up in Filevine, beyond the migration, so that people can work in it from the first day.

Filevine arrives as a platform to be configured, and most of the implementation is design. Someone has to decide what a project looks like for each kind of work the firm does, what moves it from one phase to the next, and who can see what. Those decisions are made with the people who run the files, then built and tested.

Set-up decisions in Filevine

  • Design project types, sections and fields for each practice area
  • Define phases and the tasks each phase should trigger
  • Build document templates that fill from project fields
  • Set teams, permissions and protected sections for restricted matters
  • Decide whether Billing and Payments are switched on
  • Connect Lead Docket so signed leads become projects

Questions

Centerbase to Filevine: 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 Filevine?

In part. Trust accounts sit in Payments by Filevine. Loading history is confirmed in the analysis. The analysis sets out which trust records have a place in Filevine and which are kept as an archive, and the trust cutover is rehearsed on a full trial load before the real one.

Does everything in Centerbase have a place in Filevine?

Most of it does on paper. The firm’s accounts 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 Filevine is kept as a readable archive, and you see which before the move.

What has to be decided before Centerbase data is loaded into Filevine?

Time entries, billing records, trust ledgers, custom fields, templates and intake records are carried with mapping, so each mapping is agreed with you first. The firm’s accounts 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

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

Moving from Centerbase to Filevine?

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

We reply within one business day.