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

Data migration route

Primafact data to SQLite

Primafact is a server-based document management system for litigation work, and SQLite is a store of data kept as files the firm holds. What lands in SQLite is the register: every file’s name, place, dates and details, with the files themselves stored beside it.

FromPrimafactServer
  1. Matters: Exported in full
  2. Notes: Exported in full
  3. Tasks: Exported in full
  4. Documents: Exported with mapping
  5. Emails: Exported with mapping
  6. Custom fields: Exported with mapping
ToSQLiteFiles
  1. Templates: Kept as a readable archive
Readable archiveNo place in SQLite
  • 3 carried
  • 3 mapped
  • 1 archived
What the two products hold. The analysis confirms it field by field.

What moves

What moves from Primafact to SQLite

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

Records in Primafact and their place in SQLite
RecordIn PrimafactIn SQLiteWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeld in partCases exist as containers for binders, not as matter records with parties and status.Has a placeA matters table keyed by matter number.Exported in full
DocumentsFiles stored in or linked from the systemHeldPaged documents in binders, with profile fields, searchable text and markup.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 storeHeld in partEmails can be imported from Outlook as documents.Has a place in partAs message files in folders, indexed in a table.Exported with mapping
NotesFile notes, matter notes and contact notesHeldAnnotations and notes attached to documents and pages.Has a placeA notes table linked to matters.Exported in full
TasksTo-dos and workflow steps assigned to peopleHeld in partReview workflow only: an Inbox, team flags and document discussions.Has a placeA table of tasks and their status at the final date.Exported in full
Custom fieldsFields and record types the firm added itselfHeldProfile fields, annotation colour labels and team flag labels are set by the firm.Has a placeColumns added to the table they belonged to.Exported with mapping
TemplatesPrecedents, document templates and automationHeld in partCase templates set binder structure, coding and permissions for new cases.No placePrecedent files are kept in folders, not in the database.Kept as a readable archive

What the plans mean

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

The files, and a register of what each one is.

A database is a poor place to keep documents and a good place to keep facts about them. On this route the files from Primafact are exported to storage the firm controls, and SQLite receives the register: one row per file, with its path, size, dates, author and whatever profile or folder details existed. That register is what makes a large export searchable. It also proves completeness, since the row count and total size can be agreed to the source.

How useful the register is depends on how much Primafact knows about each file. A document management system has a profile to carry. A plain folder has only a path and dates, and the client or matter has to be read out of folder names. Where versions or an audit history exist, each becomes a table of its own. The export is checked by picking documents at random in the source, finding them through SQLite, and opening the file to confirm it is the same one.

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 Primafact stays untouched until the copy in SQLite has been checked.

Where the data is now

What a firm holds in Primafact is evidence and the work done on it. Moving the documents themselves is the easy part. The value is in how they were arranged into binders and what reviewers wrote on them, and almost no general document system stores an annotation against a page. How that work is preserved has to be written into the plan.

  1. Binders, tabs and sections

    A case’s documents are arranged into binders with tabs and sections, in the order counsel wants them for a brief or production. That order is deliberate. It is carried across as numbered folders or as a tabbed PDF of each binder, so the arrangement can still be read where the destination sorts only by name or date.

  2. Annotations belong to pages

    Reviewers attach annotations to particular pages, with colour labels, and build chronologies from them. A document store has nowhere to put a note tied to page 214. Annotation lists and chronologies are exported as reports and saved to the matter, and highlights are kept by exporting the marked-up PDF.

  3. One document, several binders

    The same document can appear in more than one binder, for example in the productions binder and an expert brief. A file-by-file export would write it out twice. Copies are identified so the destination holds one file, and each binder’s contents are recorded as a list that refers to it.

  4. Profile fields and title aliases

    Each document carries profile fields, which firms use for things like service status, and can show a title alias that differs from its file name. These are the document’s metadata. They are mapped to the destination’s profile or to the file name, with the document date preserved exactly, since chronologies sort on it.

  5. Server, workstations, scan station

    The software is installed in three places, and the firm’s documents are held on its own equipment. Extraction needs the program still installed, because binders and reports are exported through Primafact itself. The old installation is kept until every active case has been checked in its new home.

More about moving off Primafact

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

Primafact to SQLite: what firms ask

Can annotations move into iManage, NetDocuments or SharePoint?

Not as annotations. Those systems store documents and their profiles, and have no record for a reviewer’s note on a page. The practical answer is to export annotation reports and chronologies as documents, and marked-up PDFs with the highlights visible, and file them with the originals.

Do we need to move closed cases out of Primafact?

Often not. A closed case’s productions have usually been exported already as tabbed PDFs. If those are on the matter in the practice management or document system, the working binders can stay in the old installation, kept read only. Active cases are the ones that need their structure and review work preserved.

Is Primafact a practice management system?

No. It manages the documents in a litigation file and the review work on them, and its feature pages describe no ledger, time recording or client records. Firms run it beside a practice or case management system, and a move usually sends the documents to that system or to a document management product.

Does the copy in SQLite hold documents from Primafact?

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

What happens to records SQLite has no place for?

On this route that is templates. They are exported from Primafact 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 Primafact is written out to SQLite?

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

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

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