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

Data migration route

filePro Plus to Clio Manage migration

filePro Plus is a database on a server the firm runs, and Clio Manage is a cloud practice management system. Before anything moves into Clio Manage, 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
ToClio ManageCloud
  • 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 Clio Manage

Each row is a kind of record filePro Plus holds, whether Clio Manage 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 Clio Manage
RecordIn filePro PlusIn Clio ManageWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusTo be confirmedDepends on the application written for the firm.Has a placeImported from a matters template, after contacts.Confirmed in the analysis
ContactsClients, other parties and referrersTo be confirmedHas a placePeople and companies, with related contacts linked to matters by a separate template.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 placeFiled under the matter; Clio scopes document migration separately from data.Confirmed in the analysis
EmailsEmails saved to matters or to the storeTo be confirmedHas a placeHeld as communications on the matter, with phone logs.Confirmed in the analysis
NotesFile notes, matter notes and contact notesTo be confirmedHas a placeMatter notes and contact notes each have a template.Confirmed in the analysis
CalendarAppointments, court dates and deadlinesTo be confirmedHas a placeCalendar events have a migration template.Confirmed in the analysis
TasksTo-dos and workflow steps assigned to peopleTo be confirmedHas a placeTasks have a migration template.Confirmed in the analysis
Time and expensesTime and expense entries, billed and unbilledTo be confirmedHas a place in partUnbilled time entries load; billed time entries do not, by Clio’s migration guide.Confirmed in the analysis
BillingInvoices, payments and debtor balancesTo be confirmedHas a place in partAn outstanding balance loads as one line per matter; past invoices do not.Confirmed in the analysis
Trust moneyTrust or client account ledgers and balancesTo be confirmedHas a place in partA trust balance loads as one line per matter or contact; past transactions do not.Confirmed in the analysis
Firm accountsGeneral ledger, office account and payablesTo be confirmedNo placeNot in Clio Manage. Books sit in a linked accounting package, or in Clio Accounting where Clio offers it.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 first, then filled from the custom field templates.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 placeRebuilt as Clio document templates with its merge fields.Confirmed in the analysis
IntakeLeads, enquiries, intake forms and pipelinesTo be confirmedNo placeLeads and intake forms belong in Clio Grow.Confirmed in the analysis

What the plans mean

Carried with mapping
Clio Manage 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 Clio Manage 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. Clio Manage 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

Clio Manage is loaded through its migration templates, one spreadsheet per kind of record, imported in a fixed order with contacts first. Clio’s own migration guide is plain about the limit: balances come across, financial history does not. So a load into Clio is planned as records plus opening positions, with the old system kept for the history behind them.

  1. Matters link by client name

    The matters template ties each matter to its client by an exact match on first name, last name or company name. A client spelt two ways in the old system becomes two contacts, or a matter assigned to an unknown client. This is why contact clean-up is finished before the first trial load, not after it.

  2. Decide the numbering scheme first

    Clio numbers imported matters itself unless the account is set to manual numbering, in which case the old number is supplied in the template. That setting and the firm’s preferred scheme are decided before any matter is loaded. The Client Reference field is available for an old file number the firm still wants to see.

  3. Balances, one line each

    Under Clio’s standard migration, an outstanding balance arrives as one line per matter and a trust balance as one line per matter or contact. Past invoices, billed time, payments and trust transactions are listed as data that cannot be migrated. The trust total is reconciled against the old system’s closing report on the trial load.

  4. Custom fields must exist

    Matter and contact custom fields are created in Clio before their values are imported, each with a field type. Accounts set up for a particular practice area come with preconfigured fields and matter templates, which affects the mapping. We compare those with the old system’s fields and add only what is missing.

  5. Rates and permissions by hand

    Billable rates for users, clients and matters are not part of an import. Neither are user permissions or settings. They are entered in Clio during set-up from a schedule the firm confirms, and a sample of imported unbilled time is checked against that schedule before the trial load is signed off.

More about moving into Clio Manage

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 Clio Manage, 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 Clio Manage. 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 Clio Manage 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 toClio Manage

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 Clio Manage. 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 Clio Manage

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

Much of a Clio Manage set-up is firm-wide settings. The numbering scheme, practice areas, matter stages, billing preferences and trust accounts apply to everyone, so they are agreed once and early. Trust and accounting features are not the same in every country Clio sells in, so the firm’s own region is checked first. Document templates and custom fields follow. Email and document integrations are then installed for each user and tested on a real matter.

Set-up decisions in Clio Manage

  • Matter numbering scheme, practice areas and matter stages
  • Custom fields for matters and contacts, by practice area
  • Document templates with merge fields, uploaded from Word or PDF
  • Billing settings, user and client rates, and trust accounts
  • Roles and permissions for each user
  • Outlook add-in, Clio Drive and the accounting connection

Questions

filePro Plus to Clio Manage: 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 Clio Manage?

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 Clio Manage are exported into folders by client and matter.

Does everything in filePro Plus have a place in Clio Manage?

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 Clio Manage 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 Clio Manage?

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 Clio Manage are the names and marks of their owners, used here only to identify the two systems.

Moving from filePro Plus to Clio Manage?

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

We reply within one business day.