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

Data migration route

filePro Plus to SmartAdvocate migration

filePro Plus is a database on a server the firm runs, and SmartAdvocate is a cloud case management system for personal injury work. Before anything moves into SmartAdvocate, 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
ToSmartAdvocateCloud
  • 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 SmartAdvocate

Each row is a kind of record filePro Plus holds, whether SmartAdvocate 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 SmartAdvocate
RecordIn filePro PlusIn SmartAdvocateWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusTo be confirmedDepends on the application written for the firm.Has a placeCases by case type, with master and member relationships.Confirmed in the analysis
ContactsClients, other parties and referrersTo be confirmedHas a placeConfirmed in the analysis
DocumentsFiles stored in or linked from the systemTo be confirmedConfirmed per application; a character-based system may hold none.Has a placeDocuments page, by category and subcategory.Confirmed in the analysis
EmailsEmails saved to matters or to the storeTo be confirmedHas a placeEmails are attached to cases.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 placeAppointments and critical deadlines.Confirmed 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 placeTracked time entries.Confirmed in the analysis
BillingInvoices, payments and debtor balancesTo be confirmedHas a place in partInvoices for hourly matters. Past invoices are scoped in the analysis.Confirmed in the analysis
Trust moneyTrust or client account ledgers and balancesTo be confirmedTo be confirmedConfirmed in the analysis
Firm accountsGeneral ledger, office account and payablesTo be confirmedTo be confirmedConfirmed 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 place in partConfirmed in the analysis for each field with no standard home.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 with SmartAdvocate merge codes.Confirmed in the analysis
IntakeLeads, enquiries, intake forms and pipelinesTo be confirmedHas a placeIntake and lead records.Confirmed in the analysis

What the plans mean

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

SmartAdvocate keeps injury detail in structured fields and screens, so mapping counts for more than usual: the more precisely the old data is placed, the more of those screens are filled on the first day. Parties, incidents, insurers, providers and bills are loaded to their own screens, and the vendor’s implementation team runs conversions into it.

  1. Map to fields, not notes

    The case summary, dashboards and settlement screen read from structured fields. Injury details, insurance limits and provider bills dumped into a note leave those screens empty. The mapping takes each old field to its SmartAdvocate counterpart, and only what truly has no counterpart is loaded as a note.

  2. Case types and statuses

    Cases are loaded against case types and statuses that drive WorkPlans and reports. These are agreed with the firm before the trial load, and old statuses are translated to the new list. A status with no match is not guessed at. It is listed, and someone who knows the files decides.

  3. Document categories

    Documents are searched by category, subcategory, sender, recipient and date as well as by folder. The old system’s folders are translated into categories on the way in. Files that arrive uncategorised can still be found by description, but they fall outside the category views staff are trained to use.

  4. Working with the vendor’s conversion

    SmartAdvocate’s implementation team converts client data into the system and trains staff through its own classes. The firm’s side of that is supplying a clean source, checking the converted cases against the old system, and deciding what to do with the exceptions. Independent help is used on those tasks.

  5. Choosing Server or Cloud

    The firm decides before loading whether it will run the Server edition on its own Windows server or use the hosted Cloud edition. Either way the data load is the same. What differs is who looks after backups, updates and remote access afterwards, and that is settled with the firm’s IT provider.

More about moving into SmartAdvocate

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 SmartAdvocate, they get a rehearsed cutover of their own. The maker of SmartAdvocate says that it, or its partners, load firms into the product. Where the firm uses that service, NewLaw’s part is the work around it: the analysis, the clean-up in filePro Plus and checking each trial against filePro Plus.

  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 SmartAdvocate. 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 SmartAdvocate 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 toSmartAdvocate

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

Loaded data is not yet a working system. The maker of SmartAdvocate runs or arranges the set-up of its product, so this is what has to be decided and put in place in SmartAdvocate, whoever does the work, before people rely on it from the first day.

Setting up SmartAdvocate is a matter of deciding how much of its detail the firm will use from the start. Case types, statuses and WorkPlans come first because they drive everything else. Templates follow. The vendor trains staff through its own classes, and the decisions below are best made before the first of those.

Set-up decisions in SmartAdvocate

  • Choose the Server or Cloud edition with IT
  • Define case types, statuses and staff roles
  • Build WorkPlans and Automated Procedures for each case type
  • Convert letters and forms into templates with merge codes
  • Install the Outlook plugin and agree email filing habits
  • Set up intake screens, lead sources and dashboards

Questions

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

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

Does everything in filePro Plus have a place in SmartAdvocate?

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 SmartAdvocate 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 SmartAdvocate?

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

Moving from filePro Plus to SmartAdvocate?

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

We reply within one business day.