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

Data migration route

filePro Plus to Centerbase migration

filePro Plus is a database on a server the firm runs, and Centerbase is a cloud practice management system. Before anything moves into Centerbase, the tables in filePro Plus have to be read and explained.

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

What moves

What moves from filePro Plus to Centerbase

Each row is a kind of record filePro Plus holds, whether Centerbase has a place for it, and what is planned. On this route one kind needs mapping and thirteen kinds are confirmed in the analysis.

Records in filePro Plus and their place in Centerbase
RecordIn filePro PlusIn CenterbaseWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusTo be confirmedDepends on the application written for the firm.Has a placeLoaded under their client, with practice-specific custom fields.Confirmed in the analysis
ContactsClients, other parties and referrersTo be confirmedHas a placeClients, related parties and prospects.Confirmed in the analysis
DocumentsFiles stored in or linked from the systemTo be confirmedConfirmed per application; a character-based system may hold none.Has a placeInto Document Storage, or left in a connected NetDocuments, iManage or SharePoint store.Confirmed in the analysis
EmailsEmails saved to matters or to the storeTo be confirmedHas a place in partEmails saved to matters; mailboxes stay in Microsoft 365.Confirmed in the analysis
NotesFile notes, matter notes and contact notesTo be confirmedHas a placeConfirmed in the analysis
CalendarAppointments, court dates and deadlinesTo be confirmedHas a placeConfirmed in the analysis
TasksTo-dos and workflow steps assigned to peopleTo be confirmedHas a placeConfirmed in the analysis
Time and expensesTime and expense entries, billed and unbilledTo be confirmedHas a placeConfirmed in the analysis
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 itselfHeldEvery file, field and screen was defined by the application’s developer.Has a placeCreated and placed on page layouts before records are loaded.Carried with mapping
TemplatesPrecedents, document templates and automationTo be confirmedOutput formats produce letters and forms; whether they are worth moving is per system.Has a place in partTemplates are rebuilt to merge Centerbase client and matter data.Confirmed in the analysis
IntakeLeads, enquiries, intake forms and pipelinesTo be confirmedHas a placeEnquiries are held as Potential New Client records; loading open ones is confirmed in the analysis.Confirmed in the analysis

What the plans mean

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

A home-built database, read table by table.

A database like filePro Plus has no standard layout. Someone at the firm, or a contractor long gone, decided what the tables are and how they join. The analysis starts by reading that structure and writing it down in plain terms: this table is clients, this one is matters, this column is the fee earner. The firm confirms the reading before any mapping to Centerbase is proposed, because one wrong guess about a join misplaces every record that depends on it.

Home-built systems hold free text where a product would hold a field: a status typed six different ways, dates in whatever form the person entering them preferred. These are put into one format during clean-up, and the values that cannot be interpreted are listed. Documents are usually on a file share beside the database, linked by a path stored in a table. Each path is tested, and missing files are reported, before the documents are loaded.

filePro Plus runs on the firm’s own equipment, so the data is collected there: a copy of the database and the folders its documents sit in, taken with the firm’s IT provider or over a remote session. Centerbase is hosted by its maker, so loading depends on the import tools and access it provides. The old machine is kept, read only, as the fall-back record.

Where the data is now

A filePro application has often been in service for decades, and one person in the office knows its menus by heart. Moving off it means recovering a description of the data from the application itself and from whoever still supports it, then checking the extracted figures against reports the old system prints.

  1. Find who wrote the application

    The firm’s supplier is often a small developer or reseller, not fP Technologies. Where they are still trading, their knowledge of the file layouts saves a good deal of time. If not, the analysis establishes whether the definitions can be read from the application’s own design screens. The firm is asked early for any contract, manual or contact name it still has.

  2. Each file has its own layout

    A filePro application is a collection of files, each with a defined list of fields, lengths and edit types, up to 999 fields in a record. There is no single schema document unless the developer wrote one. The layouts are captured file by file and turned into a data dictionary the firm can read.

  3. Logic sits in processing tables

    Balances, ageing and totals are often worked out by processing code when a screen opens or a report runs, and are not stored. Links between files are also expressed there as lookups. The code is read to find them, and calculated figures are taken from printed reports as control totals.

  4. Fixed-length fields

    Fields are fixed in length, so names and addresses may be cut short or split across lines in ways the developer chose. Dates and money follow the edit rules set for each field. Every field type is converted by a stated rule, and a sample of converted records is read against the old screens.

  5. The machine it runs on

    Some installations run on a Unix or Linux server reached through terminal software, which the firm’s current IT provider may never have managed. The analysis records where the application and data directories are, and the firm’s IT provider is asked whether the server can stay powered until the fall-back period ends.

More about moving off filePro Plus

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 filePro Plus holds 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 filePro Plus: 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 filePro Plus, 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. filePro Plus 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 filePro Plus 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 fromfilePro Plus
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 filePro Plus 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

filePro Plus to Centerbase: what firms ask

Nobody supports our filePro system any more. Is the data recoverable?

Often, as long as the system still starts and someone can sign in. The data is on the server in the application’s files. What is confirmed in the analysis is whether the field definitions can be read from the application, and how much of the meaning can be recovered: which codes mean what, and which files are still in use.

How do we know nothing was lost in the conversion?

By comparing against the old system’s own reports. Before extraction the firm prints the reports it trusts: client list, open files, debtors, trust balances if the system holds them. After each trial load the same totals are produced from the new system. Differences are traced record by record until they are explained.

Does the old system hold our documents as well?

That depends on the application. Many character-based systems hold only data, with letters produced by merging into a word processor and saved on a server drive. If so, the documents are a separate source to be matched to the client and file numbers that come out of filePro. The analysis checks both.

Do documents from filePro Plus keep their folders and dates 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 filePro Plus before the plan is fixed. Documents that have no place in Centerbase are exported into folders by client and matter.

Does everything in filePro Plus have a place in Centerbase?

Most of it does on paper. Matters, contacts, documents, emails, notes, calendar entries, tasks, time entries, billing records, trust ledgers, the firm’s accounts, templates and intake 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 filePro Plus data is loaded into Centerbase?

Custom fields are carried with mapping, so each mapping is agreed with you first. Matters, contacts, documents, emails, notes, calendar entries, tasks, time entries, billing records, trust ledgers, the firm’s accounts, templates and intake 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

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

Moving from filePro Plus 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.