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

Data migration route

Server drives to Centerbase migration

Server drives 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.

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

What moves

What moves from Server drives to Centerbase

Each row is a kind of record Server drives 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 one kind is confirmed in the analysis.

Records in Server drives and their place in Centerbase
RecordIn Server drivesIn CenterbaseWhat is planned
DocumentsFiles stored in or linked from the systemHeldFiles in folders; path, name and dates are the only description.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 partMessages dragged from Outlook into matter folders as .msg files.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 in the matter folder.Has a placeCarried across
BillingInvoices, payments and debtor balancesHeld in partCopies of invoices saved as PDFs; 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 partA precedents folder of Word templates, with or without macros.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 Server drives.
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 Server drives 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 Server drives 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

Moving off a server drive is a job of interpretation. The files copy easily. Working out which matter each folder belongs to does not, because the tree was built by many hands over many years and the naming changed with every new secretary. The analysis reads the tree, proposes rules for matching folders to matters, and shows the firm what the rules fail to place.

  1. The folder tree is the index

    Each matter folder is matched to a matter in the new system by the client name and matter number in its path. Some match exactly. Others say only Smith or Old files 2011. The unmatched folders are listed with their size and last-modified date, and the firm assigns them, archives them or leaves them.

  2. Paths past 260 characters

    Windows has long limited a full path to 260 characters, and deep matter trees routinely pass it. Such files exist but Explorer and Word may refuse to open or copy them. They are counted in the analysis and shortened to suit the destination’s own limit.

  3. Permissions do not travel with files

    Who may open the Partners folder or a restricted matter is set in Windows permissions on the server. A copy of the files should not be assumed to carry any of that. The permissions on each top-level and matter folder are reported before the move and rebuilt as groups or matter security in the new system.

  4. Folders another system owns

    The same drive often holds the document store of a practice management or accounting system, in folders with coded names. Those files are indexed in that system’s database and mean little without it. They are moved through the system that owns them, and kept out of the loose-file scan.

  5. What accumulates over twenty years

    Server drives collect shortcuts, temporary Word files, copies named Final v3 and whole duplicated matter folders. Exact duplicates are identified and reported. The firm sets the rule for near-duplicates, since only a person can say whether Final or Final v3 is the one that went to court.

More about moving off Server drives

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 Server drives 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 Server drives: 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 Server drives, 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. Server drives 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 Server drives 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 fromServer drives
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 Server drives 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

Server drives to Centerbase: what firms ask

Our folders are a mess. Do we have to tidy them before the move?

No, and it is better not to rename things by hand beforehand. The analysis works from the tree as it stands and proposes matching rules. Staff time is better spent on the short list of folders the rules cannot place, and on deciding what is old enough to archive without filing it to a matter.

Will the dates on our documents be kept?

The modified date on each file is read from the server and passed to the new system where it accepts a document date. Created dates on a server are less reliable, because copying files between drives in the past can have changed them. The trial load compares document dates on sample matters against the old folders.

Can staff keep using the S: drive after go-live?

For reading, yes: the drive is kept read only as the fall-back record. Not for filing. If people can still save to the old drive, some will, and within a month the firm has two places to look for every document. The drive is switched to read only at cutover.

Do documents from Server drives 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 Server drives have a place in Centerbase?

Most of it does on paper. 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 Server drives data is loaded into Centerbase?

Emails and templates are carried with mapping, so each mapping is agreed with you first. 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

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

Moving from Server drives 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.