Data migration route
filePro Plus to Gladiate migration
filePro Plus is a database on a server the firm runs, and Gladiate is a cloud case management system for personal injury work. Before anything moves into Gladiate, the tables in filePro Plus have to be read and explained.
filePro PlusServer- Matters: Confirmed in the analysis
- Contacts: Confirmed in the analysis
- Documents: Confirmed in the analysis
- Emails: Confirmed in the analysis
- Notes: Confirmed in the analysis
- Calendar: Confirmed in the analysis
- Tasks: Confirmed in the analysis
- Time and expenses: Confirmed in the analysis
- Billing: Confirmed in the analysis
- Trust money: Confirmed in the analysis
- Firm accounts: Confirmed in the analysis
- Custom fields: Confirmed in the analysis
- Templates: Confirmed in the analysis
- Intake: Confirmed in the analysis
GladiateCloud- 14 to confirm
What moves
What moves from filePro Plus to Gladiate
Each row is a kind of record filePro Plus holds, whether Gladiate has a place for it, and what is planned. On this route fourteen kinds are confirmed in the analysis.
| Record | What is planned | ||
|---|---|---|---|
| MattersMatters or cases, with their numbers, types, parties and status | To be confirmedDepends on the application written for the firm. | Has a placePersonal injury cases. | Confirmed in the analysis |
| ContactsClients, other parties and referrers | To be confirmed | Has a placeClients, leads and referral sources. | Confirmed in the analysis |
| DocumentsFiles stored in or linked from the system | To be confirmedConfirmed per application; a character-based system may hold none. | Has a placeFiled to the firm’s folder structure. | Confirmed in the analysis |
| EmailsEmails saved to matters or to the store | To be confirmed | To be confirmed | Confirmed in the analysis |
| NotesFile notes, matter notes and contact notes | To be confirmed | To be confirmed | Confirmed in the analysis |
| CalendarAppointments, court dates and deadlines | To be confirmed | Has a placeEvents sync with Outlook and Google Calendar. | Confirmed in the analysis |
| TasksTo-dos and workflow steps assigned to people | To be confirmed | Has a placeTasks and task plans. | Confirmed in the analysis |
| Time and expensesTime and expense entries, billed and unbilled | To be confirmed | To be confirmed | Confirmed in the analysis |
| BillingInvoices, payments and debtor balances | To be confirmed | To be confirmed | Confirmed in the analysis |
| Trust moneyTrust or client account ledgers and balances | To be confirmed | To be confirmed | Confirmed in the analysis |
| Firm accountsGeneral ledger, office account and payables | To be confirmed | To be confirmed | Confirmed in the analysis |
| Custom fieldsFields and record types the firm added itself | HeldEvery file, field and screen was defined by the application’s developer. | To be confirmed | Confirmed in the analysis |
| TemplatesPrecedents, document templates and automation | To be confirmedOutput formats produce letters and forms; whether they are worth moving is per system. | Has a place in partFirm templates are set up again in Gladiate. Old templates are not converted. | Confirmed in the analysis |
| IntakeLeads, enquiries, intake forms and pipelines | To be confirmed | Has a placeLeads and client sign-up. | Confirmed in the analysis |
What the plans mean
- 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 Gladiate 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. Gladiate 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
Leaving filePro Plus
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.
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.
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.
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.
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.
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.
Where it is going
Arriving in Gladiate
Gladiate is a destination for personal injury firms, and what it expects is injury data: a client, an incident, coverage, providers and a case status. Loading a firm into it means shaping the old system’s records into that pattern and preparing the templates, task plans and folder structure that the vendor’s onboarding asks each firm to supply.
Injury fields come first
Coverage, liability and medical details are what the product is designed to put in front of staff. In the old system they may be in custom fields, notes or a spreadsheet. They are pulled into columns during the analysis, so a loaded case shows its insurer and policy details and not an empty panel.
Templates and task plans
The vendor’s onboarding has each firm set up its own document templates, task plans, litigation deadlines and questionnaires. These are prepared from what the firm uses now. Merge fields in old templates are replaced with Gladiate’s, and task plans are written down stage by stage before anyone builds them.
A folder structure per case
Documents are filed in a folder structure the firm defines. The old system’s folders or categories are mapped to it once, and every case is loaded to the same pattern. Files with no clear category go to a holding folder on the case and are listed, not scattered.
What it may not hold
Time records, invoices and trust ledgers are not described on the vendor’s public pages. A firm that needs those carried over has it confirmed in the analysis. If there is no place for them, balances stay in the accounting package and the detailed history is kept in the old system, read only.
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 Gladiate, they get a rehearsed cutover of their own.
Analysis
We read what filePro Plus holds and how it is organised, then agree with you where each kind of record will sit in Gladiate. Anything with no place there stays behind or is archived, and you see which before the move.
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.
Trial load
A trial is loaded into Gladiate 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.
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
What happens after you send it
- A free first call
We go through your answers with you and ask about anything they leave open.
- An analysis of what filePro Plus holds
What is in it, how its records link, and where each piece would sit in Gladiate. Anything with no place there comes across as a note or stays behind, and you see which before the move.
- 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 Gladiate
Loaded data is not yet a working system. This is what NewLaw sets up in Gladiate, beyond the migration, so that people can work in it from the first day.
Gladiate is delivered ready for injury work, so set-up is about making it the firm’s own. The vendor’s onboarding covers templates, task plans, folder structure, litigation deadlines and client questionnaires. Each of those is a decision the firm has to make, and it goes faster when current practice has been written down beforehand.
Set-up decisions in Gladiate
- Set up and test the firm’s document templates
- Write task plans for each stage of a case
- Agree one folder structure for case documents
- Enter litigation deadlines for the firm’s jurisdictions
- Prepare client questionnaires, surveys and scheduled case updates
- Connect Outlook or Google calendars for two-way sync
Questions
filePro Plus to Gladiate: 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 Gladiate?
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 Gladiate are exported into folders by client and matter.
Does everything in filePro Plus have a place in Gladiate?
Most of it does on paper. Matters, contacts, documents, emails, notes, calendar entries, tasks, time entries, billing records, trust ledgers, the firm’s accounts, custom fields, 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 Gladiate 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 Gladiate?
Matters, contacts, documents, emails, notes, calendar entries, tasks, time entries, billing records, trust ledgers, the firm’s accounts, custom fields, 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.
Other routes
Other routes from filePro Plus and into Gladiate
Other destinations from filePro Plus
Other systems that move into Gladiate
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.
Choose your systems
Technology stack selection
Decide which practice management system your firm runs, with the evidence and the cost beside it.
About four weeks for a firm of about 15 people. Fixed price, set after a free first call.
Move your data
Data migration
Your data is cleaned up before anything moves, then a trial load is checked against the old system.
Fixed price, agreed after the analysis.
Set up your new system
Implementation
Your new system set up around the way your firm works: configuration, document automation and training.
A small firm of 1 to 10 users typically takes 4 to 8 weeks. A mid-sized firm of 10 to 50 users takes 8 to 16 weeks.
Put AI to work
AI advisory and enablement
A small group of your people learn to use an approved AI tool on real work, under written rules.
Two to four weeks for a small first group. Fixed price, set after a free first call.
filePro Plus and Gladiate are the names and marks of their owners, used here only to identify the two systems.
Moving from filePro Plus to Gladiate?
Tell us what you are moving. You get a plan and a fixed price after the analysis.
We reply within one business day.