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

Data migration route

Local folders to Centerbase migration

Local folders are plain files on equipment the firm controls, and Centerbase is a cloud practice management system. The move is about deciding which folder is which matter, then filing every document against it.

FromLocal foldersFiles
  1. Documents: Carried across
  2. Notes: Carried across
  3. Emails: Carried with mapping
  4. Templates: Carried with mapping
  5. Time and expenses: Confirmed in the analysis
  6. Billing: Confirmed in the analysis
ToCenterbaseCloud
  • 2 carried
  • 2 mapped
  • 2 to confirm
What the two products hold. The analysis confirms it field by field.

What moves

What moves from Local folders to Centerbase

Each row is a kind of record Local folders hold, whether Centerbase has a place for it, and what is planned. On this route two kinds of record carry across, two kinds need mapping and two kinds are confirmed in the analysis.

Records in Local folders and their place in Centerbase
RecordIn Local foldersIn CenterbaseWhat is planned
DocumentsFiles stored in or linked from the systemHeldFiles in one user’s folders, with no sharing or 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 storeHeld in partSaved .msg files, and Outlook data files stored under Documents.Has a place in partEmails saved to matters; mailboxes stay in Microsoft 365.Carried with mapping
NotesFile notes, matter notes and contact notesHeld in partFile notes kept as Word documents or text files.Has a placeCarried across
Time and expensesTime and expense entries, billed and unbilledHeld in partTimesheets kept as spreadsheets, where a practitioner works that way.Has a placeConfirmed in the analysis
BillingInvoices, payments and debtor balancesHeld in partInvoices as Word or PDF files; no ledger.Has a placeThe vendor says billing history can be migrated; the depth is set in the analysis.Confirmed in the analysis
TemplatesPrecedents, document templates and automationHeld in partPersonal precedents and Word templates saved by the user.Has a place in partTemplates are rebuilt to merge Centerbase client and matter data.Carried with mapping

What the plans mean

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

Folders become matters with documents.

Files in Local folders are organised the way the firm’s people organised them: by client, by year, by lawyer, sometimes all three. Centerbase wants every document on a matter. The analysis reads the folder tree and proposes a rule, for example that the second folder level is the matter, then lists every folder the rule does not fit. Those exceptions are the real work. A folder called Misc or Old Files has to be given a home by someone who knows the firm.

Folder names carry what a matter record should hold properly: client name, matter description, sometimes a file number. Where the names are consistent, matters and contacts can be created from them. Where they are not, the matter list is built first, in a spreadsheet the firm corrects, and the documents are loaded against it. File dates are preserved, so a document still shows when it was written and not when it was moved.

With Local folders the files are already on equipment the firm controls, so there is no export step: they are read where they are. Upload speed sets the pace for a large store. The originals stay in place, unchanged, until the firm has checked the copy in Centerbase.

Where the data is now

Collecting from local folders means going machine by machine, and person by person, because nobody else knows what is there. Volumes are small next to a server drive. The value can be high: the only signed copy of a deed, a partner’s twenty years of precedents, the working files of every matter a sole practitioner has open.

  1. An inventory per computer

    Every PC, Mac and laptop in scope is scanned for documents outside the system folders, including machines kept at home and the one in the storeroom nobody has started in a year. Each user profile on a shared computer is scanned separately. The result is a list by machine that the firm signs off.

  2. Local drafts against the shared copy

    Where the firm also has a server or cloud drive, a local file is often a later draft of something filed there, or an older one. Files are compared by content. Identical copies are dropped, and the differing ones are shown side by side with their dates so the lawyer can say which is current.

  3. Folders that only look local

    A OneDrive, Dropbox or Google Drive folder appears in Explorer like any other, but its contents belong to the cloud account and may not be on the disk in full. Those are collected from the service. Scanning them as local folders double counts files and can copy empty placeholders.

  4. Mail archives under Documents

    Outlook’s default location for data files is an Outlook Files folder inside Documents. A scan for documents will find them, sometimes many gigabytes each. They are set aside and handled as mail, matched to matters by folder and correspondent, not loaded as single enormous files.

  5. One person’s own system

    A lawyer’s local folders follow a private logic: by year, by court, by the other side’s surname. The owner spends half an hour explaining it, and the mapping to matters is written from that conversation. Where the owner has left the firm, folders are matched on client names and dates alone.

More about moving off Local folders

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.

No financial cutover is planned on this route, so a load can be run again until it is right. If the analysis finds financial records with a place in Centerbase, they get a rehearsed cutover of their own.

  1. Analysis

    We read what Local folders hold and how it is organised, then agree with you where each kind of record will sit in Centerbase. Anything with no place there stays behind or is archived, and you see which before the move.

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

  3. Trial load

    A trial is loaded into Centerbase and checked against Local folders: 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.

  4. Cutover

    After a short freeze on changes in Local folders, a final pass over a weekend picks up what changed since the trial. If the analysis found financial records to move, their cutover is rehearsed on a full trial load first. Local folders are 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 Local folders 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 fromLocal folders
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 Local folders 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

Local folders to Centerbase: what firms ask

I am a sole practitioner and everything is on my laptop. Where do we start?

With a full copy of the laptop’s user folders taken to a second disk, before anything else. Then a list of your open matters, even handwritten. Folders are matched to that list, the rest is treated as closed files, and you check a sample in the new system before the laptop copy is retired.

Do you need to take our computers away?

No. It is the files that are needed, not the machines. Whether they are collected at each desk or remotely with the firm’s IT provider, and at what hours, is agreed in the analysis. A laptop needs to be switched on, signed in and on the office network or a reliable connection for as long as its copy takes.

What about personal files mixed in with work?

They stay where they are. Each person is shown the list of top-level folders found on their machine and marks the ones that are private. Those paths are excluded before any file is copied. Installed programs and system files are left out in any case.

Do documents from Local folders keep their folders and dates in Centerbase?

Centerbase stores documents. Into Document Storage, or left in a connected NetDocuments, iManage or SharePoint store. Each file is placed under the client and matter it came from, and created and modified dates are carried, so a document still shows when it was written. The trial load is checked by count and by opening a sample.

Does everything in Local folders have a place in Centerbase?

Most of it does on paper. Time entries and billing 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 Local folders data is loaded into Centerbase?

Emails and templates are carried with mapping, so each mapping is agreed with you first. Time entries and billing records are confirmed in the analysis. The firm also decides which closed matters and how many versions of a document are in scope.

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

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

Moving from Local folders 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.