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

Data migration route

Claris FileMaker Pro to Filevine migration

Claris FileMaker Pro is a desktop database, and Filevine is a cloud case management system. Before anything moves into Filevine, the tables in Claris FileMaker Pro have to be read and explained.

FromClaris FileMaker ProDesktop
  1. Documents: Carried across
  2. Custom fields: Carried with mapping
  3. Matters: Confirmed in the analysis
  4. Contacts: 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
ToFilevineCloud
  • 1 carried
  • 1 mapped
  • 12 to confirm
What the two products hold. The analysis confirms it field by field.

What moves

What moves from Claris FileMaker Pro to Filevine

Each row is a kind of record Claris FileMaker Pro holds, whether Filevine has a place for it, and what is planned. On this route one kind of record carries across, one kind needs mapping and twelve kinds are confirmed in the analysis.

Records in Claris FileMaker Pro and their place in Filevine
RecordIn Claris FileMaker ProIn FilevineWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusTo be confirmedDepends entirely on what the firm built.Has a placeLoaded as projects of a defined project type.Confirmed in the analysis
ContactsClients, other parties and referrersTo be confirmedMost firm-built systems start with a client table, but it is confirmed per system.Has a placeContact cards, linked to projects.Confirmed in the analysis
DocumentsFiles stored in or linked from the systemHeld in partContainer fields can hold files, embedded, stored externally or by reference.Has a placeDocs section with folders. Templated project folders can be set per type.Carried across
EmailsEmails saved to matters or to the storeTo be confirmedHas a placeHeld in the activity feed of the project.Confirmed in the analysis
NotesFile notes, matter notes and contact notesTo be confirmedHas a placeHeld as notes in the activity feed.Confirmed in the analysis
CalendarAppointments, court dates and deadlinesTo be confirmedHas a placeDeadlines and calendar events.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 place in partNeeds the Billing product enabled.Confirmed in the analysis
BillingInvoices, payments and debtor balancesTo be confirmedHas a place in partNeeds the Billing product enabled.Confirmed in the analysis
Trust moneyTrust or client account ledgers and balancesTo be confirmedHas a place in partTrust accounts sit in Payments by Filevine. Loading history is confirmed in the analysis.Confirmed 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 table and field was defined by the firm or its developer.Has a placeCustom sections and fields per project type.Carried with mapping
TemplatesPrecedents, document templates and automationTo be confirmedLetters may be produced from layouts with merge fields; confirmed per system.Has a place in partTemplates are rebuilt as Filevine document templates. They are not converted.Confirmed in the analysis
IntakeLeads, enquiries, intake forms and pipelinesTo be confirmedHas a place in partLeads belong in Lead Docket, which passes signed clients to Filevine.Confirmed in the analysis

What the plans mean

Carried across
Filevine has a place for this kind of record. It is loaded there and checked against Claris FileMaker Pro.
Carried with mapping
Filevine 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 Claris FileMaker Pro 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 Filevine 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.

Claris FileMaker Pro 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. Filevine 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

With a firm-built system there is no vendor manual describing the data, so the first job is to write one. The design is read out of the FileMaker files themselves, then walked through with the person who knows the system best. Only after that can anyone say what it holds, which parts are still used, and where each field will go.

  1. Read the design from the file

    FileMaker can produce a Database Design Report, or save a copy of the file as XML, setting out every table, field, relationship, layout and script. Either needs an account with full access privileges. That report is the starting document for the analysis, and it can turn up tables nobody remembers.

  2. Layouts are not tables

    Staff know the system by its screens. A single matter layout may draw on five related tables through portals and lookups. Exports run table by table, so each screen is traced back to the tables behind it and the key fields that join them are carried through, or the links are lost.

  3. Documents in container fields

    A container field can hold a document embedded in the database, stored in an external folder that FileMaker manages, or only as a reference to a file elsewhere. Each kind is extracted differently. References are tested, because a path recorded in 2012 may point to a server that no longer exists.

  4. Calculated and summary fields

    A matter balance or total hours shown on screen may be a calculation, not stored data. An export gives the result as it stood that day. The firm chooses between bringing the figure as a fixed number and bringing the underlying entries so the new system can work it out again.

  5. Free typing and private conventions

    Home-built systems rarely validate what is typed. The same court appears under six spellings, dates sit in text fields, and one field has been reused for something else since 2015. Clean-up therefore takes longer here than for a packaged product, and the firm sees the proposed standard values first.

More about moving off Claris FileMaker Pro

Where it is going

Loading a firm into Filevine depends on the project types being built first. Until the sections and fields exist there is nowhere for the data to go, so configuration and migration are planned together. The old system’s parties, insurers, providers and key dates are mapped to sections, and its notes and emails are loaded into each project’s activity feed.

  1. Project types before data

    Each area of practice needs a project type with its sections, fields and phases defined in the Customs Editor. Changes made there apply to every project of that type. The types are drafted from the old system’s data, tested with a few real cases, and only then is the bulk load run.

  2. One contact card per person

    Contacts are held as contact cards. A doctor or adjuster who appears on many projects is best loaded as one card, not one for each project. Duplicates in the old system are merged before loading where they can be identified. Loading them as they are produces several cards for the same person, and staff then pick the wrong one when adding a party.

  3. Lists become collection items

    Anything the old system held as a list against a matter, such as providers, liens, insurance policies or expenses, is loaded as items in a collection section. Each column needs a matching field. Totals per project are compared with the old system afterwards, since those figures feed the settlement and disbursal sheets.

  4. History goes into the feed

    File notes, emails and completed tasks from the old system are loaded into the activity feed with their original dates and authors. Authors must exist as users or be recorded in the text. The feed is long on an old case, so staff are shown how to filter it before go-live.

  5. Billing is a separate switch

    The Billing section only appears once Billing is enabled for the firm. Time entries, invoices and trust balances from the old system need that in place before they can be loaded. A firm that leaves it off can still record case costs in a collection section built for the purpose.

More about moving into Filevine

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 Filevine, they get a rehearsed cutover of their own.

  1. Analysis

    We read what Claris FileMaker Pro holds and how it is organised, then agree with you where each kind of record will sit in Filevine. 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 Filevine and checked against Claris FileMaker Pro: 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 Claris FileMaker Pro, 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. Claris FileMaker Pro 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 Claris FileMaker Pro 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 fromClaris FileMaker Pro
Moving toFilevine

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 Claris FileMaker Pro holds

    What is in it, how its records link, and where each piece would sit in Filevine. 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 Filevine

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

Filevine arrives as a platform to be configured, and most of the implementation is design. Someone has to decide what a project looks like for each kind of work the firm does, what moves it from one phase to the next, and who can see what. Those decisions are made with the people who run the files, then built and tested.

Set-up decisions in Filevine

  • Design project types, sections and fields for each practice area
  • Define phases and the tasks each phase should trigger
  • Build document templates that fill from project fields
  • Set teams, permissions and protected sections for restricted matters
  • Decide whether Billing and Payments are switched on
  • Connect Lead Docket so signed leads become projects

Questions

Claris FileMaker Pro to Filevine: what firms ask

The person who built our system has gone. Can it still be moved?

Usually, provided someone holds a full access account for the files. With that, the design can be read without the developer. Without it, data can still be exported from whatever the firm’s own logins can see, but the scripts and hidden tables cannot be inspected, and the analysis takes longer and says so.

Our system does things no legal product does. What happens to those?

Each one is listed in the analysis and put in one of three groups: the new system does it differently, the new system can be configured to do it, or it will stop. The third group is the one to discuss with the partners early. A custom register can also be kept as an exported spreadsheet.

Can we keep FileMaker for reference afterwards?

Yes. The files can be left on the server, or a copy opened in FileMaker Pro on one PC, with accounts changed to read only so nothing new is entered. That is the fall-back record. It depends on keeping a working FileMaker licence and a machine that runs it, which the firm should note for later years.

Do documents from Claris FileMaker Pro keep their folders and dates in Filevine?

Filevine stores documents. Docs section with folders. Templated project folders can be set per type. Each file is placed under the client and matter it came from, and created and modified dates are carried, so a document still shows when it was written. The trial load is checked by count and by opening a sample.

Does everything in Claris FileMaker Pro have a place in Filevine?

Most of it does on paper. Matters, contacts, 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 Filevine is kept as a readable archive, and you see which before the move.

What has to be decided before Claris FileMaker Pro data is loaded into Filevine?

Custom fields are carried with mapping, so each mapping is agreed with you first. Matters, contacts, 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

Claris FileMaker Pro and Filevine are the names and marks of their owners, used here only to identify the two systems.

Moving from Claris FileMaker Pro to Filevine?

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

We reply within one business day.