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

Data migration route

Filevine data to SQLite

Filevine is a cloud case management system, and SQLite is a store of data kept as files the firm holds. This is not a move to a new working system: the route writes out what Filevine holds and keeps it readable and open to queries.

FromFilevineCloud
  1. Matters: Exported in full
  2. Contacts: Exported in full
  3. Notes: Exported in full
  4. Calendar: Exported in full
  5. Tasks: Exported in full
  6. Time and expenses: Exported in full
  7. Billing: Exported in full
  8. Trust money: Exported in full
  9. Intake: Exported in full
  10. Documents: Exported with mapping
  11. Emails: Exported with mapping
  12. Custom fields: Exported with mapping
  13. Firm accounts: Confirmed in the analysis
ToSQLiteFiles
  1. Templates: Kept as a readable archive
Readable archiveNo place in SQLite
  • 9 carried
  • 3 mapped
  • 1 to confirm
  • 1 archived
What the two products hold. The analysis confirms it field by field.

What moves

What moves from Filevine to SQLite

Each row is a kind of record Filevine holds, whether SQLite has a place for it, and what is planned. On this route nine kinds of record carry across, three kinds need mapping, one kind has no place in SQLite and is archived and one kind is confirmed in the analysis.

Records in Filevine and their place in SQLite
RecordIn FilevineIn SQLiteWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldCalled projects. Each has a project type, a phase and sections.Has a placeA matters table keyed by matter number.Exported in full
ContactsClients, other parties and referrersHeldContact cards, collected on each project’s Contacts section.Has a placeContacts and their roles on matters as linked tables.Exported in full
DocumentsFiles stored in or linked from the systemHeldDocs section per project, with folders, named versions and searchable text.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 storeHeldProject emails are stored in the activity feed.Has a place in partAs message files in folders, indexed in a table.Exported with mapping
NotesFile notes, matter notes and contact notesHeldNotes are posted to the activity feed.Has a placeA notes table linked to matters.Exported in full
CalendarAppointments, court dates and deadlinesHeldDeadlines, deadline chains and project calendars.Has a placeA table of dated entries, with no calendar view.Exported in full
TasksTo-dos and workflow steps assigned to peopleHeldTasks in the activity feed. Phases can create auto-tasks.Has a placeA table of tasks and their status at the final date.Exported in full
Time and expensesTime and expense entries, billed and unbilledHeld in partTimekeeping is part of Billing, which must be enabled for the firm.Has a placeA table of time and expense entries.Exported in full
BillingInvoices, payments and debtor balancesHeld in partInvoices and payments through the Billing and Payments products.Has a placeInvoice and receipt tables; invoice PDFs kept as files.Exported in full
Trust moneyTrust or client account ledgers and balancesHeld in partPayments by Filevine includes trust accounts and a trust reconciliation report.Has a placeTrust transactions as rows, for look-up and not for accounting.Exported in full
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 itselfHeldCustom sections and fields are built in the Customs Editor.Has a placeColumns added to the table they belonged to.Exported with mapping
TemplatesPrecedents, document templates and automationHeldDocument generation templates that fill from project data.No placePrecedent files are kept in folders, not in the database.Kept as a readable archive
IntakeLeads, enquiries, intake forms and pipelinesHeld in partLeads and intake are handled by Lead Docket, a separate Filevine product.Has a placeAn enquiries table, where the source tracked them.Exported in full

What the plans mean

Exported in full
SQLite has a place for this kind of record. It is loaded there and checked against Filevine.
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.
Kept as a readable archive
SQLite has no place for it. It is exported in a format that opens without Filevine and handed to the firm as a read-only archive.

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

Not a new system. A complete copy the firm can query.

Writing Filevine out to SQLite is not a migration into a new working system. Nobody will open a matter there on Monday morning. The aim is a complete, faithful copy that can be queried and reported on after the old system is gone. So the rules change. Nothing is cleaned or merged unless the firm asks, because an archive should show the records as they were. Every table and field is carried, including those a new system would have had no place for.

What makes an archive usable is the description that goes with it. The export is delivered with a plain account of each table: what it holds, how it joins to the others, what the codes mean. Record counts and financial totals are agreed to the reports in Filevine as at the export date, so the archive can stand as the record. Documents are exported beside the data with a table linking each file to its matter. Access is restricted, since the archive holds everything the live system did.

Filevine is hosted by its maker and SQLite sits on equipment the firm controls. The data leaves a service that was backed up for the firm and arrives somewhere the firm must back up itself, so backup and access are arranged before the export is copied in. What Filevine will release depends on its export tools, and that is confirmed in the analysis.

Where the data is now

No two Filevine set-ups are alike, because each firm designs its own project types and sections. A move off it starts by reading that design: every section, every field, and how many projects actually use them. Much of the firm’s history is in the activity feed as a single stream, and the plan has to say what happens to that.

  1. Sections are the data model

    Static sections hold one set of fields per project. Collection sections hold many items, each with its own fields, such as a row per medical provider. They extract as separate tables. Each one is mapped to a destination record, a set of custom fields or a document, and the firm sees which before the trial load.

  2. The activity feed

    Notes, emails, texts, faxes, reminders and tasks all live in one feed per project, and firms tag them with hashtags. Most systems keep those things in different places. Items are split by type on the way out, so emails become emails and tasks become tasks, with the original date and author kept on each.

  3. Phases and auto-tasks

    A project’s phase can trigger automatic tasks through taskflows. The phase itself maps to a status or stage. Automation does not move, and open auto-tasks are loaded as plain tasks so work in progress still shows on someone’s list. Workflows are then rebuilt in the destination from the firm’s own list of what each phase should trigger.

  4. Archived projects still exist

    Projects cannot be deleted, only moved to the Archived phase, where they drop out of searches and reports unless specifically included. An extract that follows the default view will miss them. Archived projects are counted on their own, and the firm decides how many years of them the new system should hold.

  5. Hashtags instead of folders

    Many firms organise documents and notes with hashtags as much as with folders. A destination built on folders or categories has nowhere obvious for a tag. The most used tags are listed with counts, and each becomes a folder, a document category or text in the name, so a search for it still finds the item.

More about moving off Filevine

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 Filevine holds, table by table, and agree with you what the copy in SQLite must be able to answer later. Everything Filevine 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 Filevine: record counts, totals where Filevine 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 Filevine, the export is run a final time and checked again. There is nothing to go live. Filevine 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 Filevine 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 fromFilevine
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 Filevine 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

Filevine to SQLite: what firms ask

Can we take our custom sections with us when we leave?

The data in them, yes. Every static and collection section extracts as fields and rows. The section design itself belongs to Filevine and has to be recreated in whatever the destination offers. Sections that hold only a handful of records are usually better turned into notes than rebuilt.

What happens to everything in the activity feed?

It is separated by type. Notes become file notes, emails become emails where the destination stores them, texts become notes or a transcript, and tasks become tasks. Dates and authors are kept, and hashtags are carried in the text. The count of feed items per project is checked against the load, and any shortfall is listed.

We are moving to Filevine. Do matter numbers carry over?

The old matter number can be kept on the project, in the project name, a number field or both, so that paper files and old correspondence still match. Filevine also gives each project its own ID. Staff are told which number to quote, and searches are tested for the old one.

Does the copy in SQLite hold trust ledgers from Filevine?

Yes. Trust transactions as rows, for look-up and not for accounting. Trust ledgers are written out with the rest, and counts and totals are agreed to the reports in Filevine as at the export date.

What happens to records SQLite has no place for?

On this route that is templates. They are exported from Filevine in formats that open without it, spreadsheets and PDFs, and handed to the firm as a read-only archive. You see the list before the move.

What has to be decided before Filevine is written out to SQLite?

Documents, emails and custom fields are exported with mapping, so each mapping is agreed with you first. The firm’s accounts 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

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

Moving from Filevine 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.