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

Data migration route

Centerbase to Dropbox migration

Centerbase is a cloud practice management system, and Dropbox is cloud file storage. Documents move into a folder for each client and matter, and the data behind them is kept as an export.

FromCenterbaseCloud
  1. Documents: Carried across
  2. Emails: Carried with mapping
  3. Notes: Carried with mapping
  4. Templates: Carried with mapping
ToDropboxCloud
  1. Matters: Kept as a readable archive
  2. Contacts: Kept as a readable archive
  3. Calendar: Kept as a readable archive
  4. Tasks: Kept as a readable archive
  5. Time and expenses: Kept as a readable archive
  6. Billing: Kept as a readable archive
  7. Trust money: Kept as a readable archive
  8. Firm accounts: Kept as a readable archive
  9. Custom fields: Kept as a readable archive
  10. Intake: Kept as a readable archive
Readable archiveNo place in Dropbox
  • 1 carried
  • 3 mapped
  • 10 archived
What the two products hold. The analysis confirms it field by field.

What moves

What moves from Centerbase to Dropbox

Each row is a kind of record Centerbase holds, whether Dropbox has a place for it, and what is planned. On this route one kind of record carries across, three kinds need mapping and ten kinds have no place in Dropbox and are archived.

Records in Centerbase and their place in Dropbox
RecordIn CenterbaseIn DropboxWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldMatters sit under clients and inherit client-level billing and accounting settings.No placeA matter is a folder named by the firm’s convention.Kept as a readable archive
ContactsClients, other parties and referrersHeldClients, parties and other contacts, with a saved conflict check history.No placeKept as a readable archive
DocumentsFiles stored in or linked from the systemHeldBuilt-in Document Storage, or NetDocuments, iManage or SharePoint connected to matters.Has a placeFiles in folders; the folder path is the only index.Carried across
EmailsEmails saved to matters or to the storeHeld in partEmails and attachments filed to a matter through the Outlook integration.Has a place in partAs .msg or .eml files filed in the matter folder.Carried with mapping
NotesFile notes, matter notes and contact notesHeldHas a place in partAs documents saved to the matter folder.Carried with mapping
CalendarAppointments, court dates and deadlinesHeldTwo-way sync with Outlook; court rules through LawToolBox.No placeKept as a readable archive
TasksTo-dos and workflow steps assigned to peopleHeldTasks can be created by automated workflows.No placeKept as a readable archive
Time and expensesTime and expense entries, billed and unbilledHeldIncludes passive time capture from Outlook and Word.No placeKept as a readable archive
BillingInvoices, payments and debtor balancesHeldElectronic pre-bill approval, multi-payor bills and LEDES formats.No placeKept as a readable archive
Trust moneyTrust or client account ledgers and balancesHeldSeveral trust and retainer accounts can be held under one matter or at client level.No placeKept as a readable archive
Firm accountsGeneral ledger, office account and payablesHeldFull general ledger on a cash or accrual basis, with online banking and payables.No placeKept as a readable archive
Custom fieldsFields and record types the firm added itselfHeldUnlimited custom fields and configurable page layouts.No placeKept as a readable archive
TemplatesPrecedents, document templates and automationHeldDocument templates filled with client and matter data; bill templates.Has a place in partPrecedents load as ordinary files in a precedents folder.Carried with mapping
IntakeLeads, enquiries, intake forms and pipelinesHeldWeb form enquiries arrive as Potential New Client records.No placeKept as a readable archive

What the plans mean

Carried across
Dropbox has a place for this kind of record. It is loaded there and checked against Centerbase.
Carried with mapping
Dropbox holds this differently, or in part. Each field or value is matched to its place before loading, and you see the mapping first.
Kept as a readable archive
Dropbox has no place for it. It is exported in a format that opens without Centerbase and handed to the firm as a read-only archive.

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

Out of the system, into folders the firm can read.

File storage has folders and files and nothing else. Moving from Centerbase into Dropbox means turning matters into a folder tree, usually client, then matter, then the folders used inside it. The naming rule is agreed first, because it is hard to change once thousands of folders exist: whether the matter number leads, how closed matters are separated, what happens to characters Dropbox does not allow in a name.

Everything that is not a document needs somewhere to go. Contacts, notes, time, invoices and trust ledgers have no place in a folder, so they are exported as spreadsheets and reports and stored alongside, often as a summary file in each matter folder and a full set in an archive area. Firms choose this route to keep a readable copy of a system they are retiring, or as a staging step. The export is checked either way: folders against matters, files against the document register in Centerbase.

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 Dropbox 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 matter files into Dropbox is a matter of getting the tree right, since the tree is all there is. No field holds a matter number or a client name. The folder names carry that, so the naming rule is agreed first: what a client folder is called, what a matter folder is called, and which subfolders every matter gets.

  1. Team folders before files

    Team folders are shared with groups, and each group is given an editor or view-only role. The groups and the top-level folders are created before the load so that files arrive already restricted. Loading first and sharing afterwards leaves a period in which the wrong people can see everything.

  2. Keep paths under 260 characters

    Dropbox’s naming guidance asks for full paths shorter than 260 characters. Matter trees from document systems often exceed that once the client name, matter description and subfolders are joined. Long paths are measured early and cut back by rule, usually by trimming the matter description and keeping the number.

  3. Characters that get swapped

    On Windows, the desktop app replaces restricted characters in names with an underscore. A file called Smith v Jones: Affidavit becomes something slightly different on some machines. Names are cleaned before loading so that the file has one name everywhere and matches the index kept from the old system.

  4. Matter data has nowhere to go

    Parties, matter type, responsible lawyer, open and closed dates: none of it has a field here. If the firm is leaving a practice management system and keeping only documents, that data can be kept as an exported spreadsheet beside the folders, so they can still be read against it. Whether one is produced is decided in the analysis.

  5. History starts on loading day

    Version history in Dropbox begins when a file arrives. Earlier versions from the old system come across as separately named files in the matter folder, or stay behind. The firm sees a sample matter loaded with its earlier versions as named copies before choosing.

More about moving into Dropbox

How NewLaw runs it

Four steps, in this order.

Nothing financial lands in Dropbox on this route, which makes it repeatable: a load can be run again until it is right.

  1. Analysis

    We read what Centerbase holds and how it is organised, then agree with you where each kind of record will sit in Dropbox. 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 Dropbox and checked against Centerbase: 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

    There is no financial cutover on this route. After a short freeze on changes in Centerbase, a final pass over a weekend picks up what changed since the trial. 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 toDropbox

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

Dropbox is storage, not an application, so there is no product to configure. What is agreed and set up is the folder structure, who can open what, and how the result is handed to the firm.

Beyond the load, a firm on Dropbox needs the account arranged so the files belong to the firm and not to individuals. That means a team plan with an administrator, groups that match how the firm works, and a decision about which folders sync to every computer. A written filing rule tells staff where each new matter folder goes.

What is agreed and set up

  • Team folders for clients, precedents and administration
  • Groups by team, each with an editor or viewer role
  • Which folders sync to PCs and which stay online-only
  • Rules for sharing links and folders with clients
  • A written naming rule for client and matter folders
  • Steps for removing a leaver without losing their folders

Questions

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

No. Dropbox does not keep trust ledgers. Trust records from Centerbase are exported as ledgers and statements that open without it, and the firm settles where its trust accounting runs from the cutover date before the move is planned.

What happens to records Dropbox has no place for?

On this route that is matters, contacts, calendar entries, tasks, time entries, billing records, trust ledgers, the firm’s accounts, custom fields and intake records. They are exported from Centerbase in formats that open without it, spreadsheets and PDFs, and handed to the firm as a read-only archive. You see the list before the move.

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

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

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

Moving from Centerbase to Dropbox?

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

We reply within one business day.