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

Data migration route

Claris FileMaker Pro data to SQLite

Claris FileMaker Pro is a desktop database, and SQLite is a store of data kept as files the firm holds. The move is technical: tables, column types and keys, checked row for row.

FromClaris FileMaker ProDesktop
  1. Documents: Exported with mapping
  2. Custom fields: Exported 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
ToSQLiteFiles
  • 2 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 SQLite

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

Records in Claris FileMaker Pro and their place in SQLite
RecordIn Claris FileMaker ProIn SQLiteWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusTo be confirmedDepends entirely on what the firm built.Has a placeA matters table keyed by matter number.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 placeContacts and their roles on matters as linked tables.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 place in partListed in a table; the files themselves stay in folders beside the database.Exported with mapping
EmailsEmails saved to matters or to the storeTo be confirmedHas a place in partAs message files in folders, indexed in a table.Confirmed in the analysis
NotesFile notes, matter notes and contact notesTo be confirmedHas a placeA notes table linked to matters.Confirmed in the analysis
CalendarAppointments, court dates and deadlinesTo be confirmedHas a placeA table of dated entries, with no calendar view.Confirmed in the analysis
TasksTo-dos and workflow steps assigned to peopleTo be confirmedHas a placeA table of tasks and their status at the final date.Confirmed in the analysis
Time and expensesTime and expense entries, billed and unbilledTo be confirmedHas a placeA table of time and expense entries.Confirmed in the analysis
BillingInvoices, payments and debtor balancesTo be confirmedHas a placeInvoice and receipt tables; invoice PDFs kept as files.Confirmed in the analysis
Trust moneyTrust or client account ledgers and balancesTo be confirmedHas a placeTrust transactions as rows, for look-up and not for accounting.Confirmed in the analysis
Firm accountsGeneral ledger, office account and payablesTo be confirmedHas a placeLedger journals as rows, where the source held them.Confirmed 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 placeColumns added to the table they belonged to.Exported with mapping
TemplatesPrecedents, document templates and automationTo be confirmedLetters may be produced from layouts with merge fields; confirmed per system.No placePrecedent files are kept in folders, not in the database.Confirmed in the analysis
IntakeLeads, enquiries, intake forms and pipelinesTo be confirmedHas a placeAn enquiries table, where the source tracked them.Confirmed in the analysis

What the plans mean

Exported with mapping
SQLite 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

Database to database, structure first.

Moving from Claris FileMaker Pro to SQLite is the most mechanical route there is, and the easiest to check. Each table is recreated with matching columns, the rows are copied, and the counts are compared. The care goes into types. Dates, currency and long text are stored differently from one database to another, and a careless conversion cuts notes short or shifts a date by a day. Every column’s type is mapped on purpose and tested on real rows.

A home-built database usually has screens, reports and scripts on top of its tables, and those do not move with the data. If people still work in Claris FileMaker Pro day to day, the firm needs to know what will replace the screens before the tables are moved. If the aim is an archive or a reporting copy, the tables are enough, and they are delivered with a written description of what each one holds and how they join.

Both ends are on equipment the firm controls, so the work is done on the firm’s own network with its IT provider. Disk space for a second full copy is checked first. The original in Claris FileMaker Pro stays untouched until the copy in SQLite has been checked.

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

A SQLite archive suits a firm that wants the old system’s records kept, seldom consulted, and free of any server or subscription. Everything structured goes into one file. That simplicity moves the responsibility elsewhere: the file has no security of its own and no administrator watching it, so where it is stored and who can reach it are the real decisions.

  1. One file, kept with the archive

    Matters, contacts, time, invoices and trust transactions become tables in a single file. It is stored with the firm’s closed-matter records and can be copied like any document. A checksum recorded when the file is finalised lets anyone confirm, years later, that the copy they hold has not been altered, and the firm decides whether to keep one.

  2. No logins inside the file

    SQLite has no users or passwords. Anyone who can open the file can read every client’s ledger. Protection comes from where it is kept, such as a restricted folder or an encrypted volume, and that choice is the firm’s. It can suit an archive consulted by two people, and it is said plainly so nobody assumes otherwise.

  3. Built for reading, not sharing

    Only one program can write to the file at a time, and SQLite’s authors point people to a client/server database where many users share data over a network. A finished archive never meets that limit. It is the reason SQLite is used here for records that are closed and not for anything staff still update.

  4. Documents stay outside it

    Documents remain ordinary files in matter folders, and a table in the database lists each one with its matter, title, dates and path. Keeping them as files means they open with a double-click and can be handed to a client. The table is how a file is found by matter number instead of by guessing its name.

  5. Someone has to open it

    SQLite publishes its own command-line program for opening a database file, and other tools read the format too. None of that helps if nobody remembers how. Saved queries for the usual look-ups and a short note on which tool to use can sit in the same folder as the file, and the firm decides what it needs.

More about moving into SQLite

How NewLaw runs it

Four steps, in this order.

This route produces an archive, not a working system, so the steps are about completeness and proof.

  1. Analysis

    We read what Claris FileMaker Pro holds, table by table, and agree with you what the copy in SQLite must be able to answer later. Everything Claris FileMaker Pro holds is in scope unless you take it out.

  2. Clean-up, if you want it

    An archive should show the records as they were, so nothing is merged or corrected unless you ask. Where the copy is also meant for reporting, duplicate and inconsistent entries are tidied in a working copy and the original values are kept beside them.

  3. Trial export

    The data is written to SQLite as a trial and checked against Claris FileMaker Pro: record counts, totals where Claris FileMaker Pro holds money, the links between records, and a sample of documents opened from the export. Exceptions are listed for you to decide.

  4. Final export

    After the last day of work in Claris FileMaker Pro, the export is run a final time and checked again. There is nothing to go live. Claris FileMaker Pro is kept read only until you are satisfied the copy answers what you need, and it is handed over with a written description of its contents.

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 toSQLite

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

Structure, permissions and handover

SQLite is a place to keep data, not a system staff work in each day. What is agreed is how the data is laid out, who can reach it, and what is handed over with it.

There is nothing to install on a server and nothing to license. The work is in making the file usable and safe to keep: naming it, documenting its tables, storing it where the firm’s records policy says archives go, and checking that a member of staff can open it and find a matter. Whether a second copy is held somewhere separate is the firm’s call.

What is agreed and set up

  • File name, storage location and whether a second copy exists
  • Whether a checksum is recorded for later verification
  • Saved queries for matter, ledger and document look-ups
  • Which tool staff will use to open the file
  • Who may open the folder the file sits in
  • Retention period and destruction date noted beside the file

Questions

Claris FileMaker Pro to SQLite: 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.

Does the copy in SQLite hold documents from Claris FileMaker Pro?

In part. Listed in a table; the files themselves stay in folders beside the database. What SQLite can hold is written out once its mapping is agreed, and the rest is kept beside the data as files that open without Claris FileMaker Pro.

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

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 SQLite is kept as a readable archive, and you see which before the move.

What has to be decided before Claris FileMaker Pro is written out to SQLite?

Documents and custom fields are exported 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 who may open the archive and how long it is kept.

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

Moving from Claris FileMaker Pro to SQLite?

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

We reply within one business day.