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

Data migration route

Primafact data to Microsoft SQL Server

Primafact is a server-based document management system for litigation work, and Microsoft SQL Server is a database on a server the firm runs. What lands in Microsoft SQL Server 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
  7. Templates: Exported with mapping
ToMicrosoft SQL ServerServer
  • 3 carried
  • 4 mapped
What the two products hold. The analysis confirms it field by field.

What moves

What moves from Primafact to Microsoft SQL Server

Each row is a kind of record Primafact holds, whether Microsoft SQL Server has a place for it, and what is planned. On this route three kinds of record carry across and four kinds need mapping.

Records in Primafact and their place in Microsoft SQL Server
RecordIn PrimafactIn Microsoft SQL ServerWhat 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 table of matters linked to clients, parties and fee earners.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 partAs files in folders with an index table; storing files in the database is possible.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 with an index table, or as rows of header fields.Exported with mapping
NotesFile notes, matter notes and contact notesHeldAnnotations and notes attached to documents and pages.Has a placeRows of text linked to matters and contacts.Exported in full
TasksTo-dos and workflow steps assigned to peopleHeld in partReview workflow only: an Inbox, team flags and document discussions.Has a placeRows with assignee, due date and status.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 placeAs added columns, or a table of field names and values.Exported with mapping
TemplatesPrecedents, document templates and automationHeld in partCase templates set binder structure, coding and permissions for new cases.Has a place in partPrecedent files can be stored; automation does not run here.Exported with mapping

What the plans mean

Exported in full
Microsoft SQL Server has a place for this kind of record. It is loaded there and checked against Primafact.
Exported with mapping
Microsoft SQL Server holds this differently, or in part. Each field or value is matched to its place before loading, and you see the mapping first.

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 Microsoft SQL Server 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 Microsoft SQL Server, 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 Microsoft SQL Server 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

There are two ways to put a retired system into SQL Server, and they suit different firms. The old system’s own database can be restored as it is. Or the data can be loaded into a new set of tables designed to be read by people. The first is quicker and harder to use. Which suits is worked out in the analysis, and the choice is the firm’s.

  1. Restored copy or rebuilt schema

    Where the old practice system already kept its data in SQL Server, a backup can be restored onto a new server. The tables keep the vendor’s names and codes, which can be cryptic, and reading them takes someone who knows that product’s database. A rebuilt schema uses plain names such as Matter and TrustTransaction.

  2. No screens come with it

    A database has no matter screen. Someone has to ask it questions in SQL or through a reporting tool. Saved views can be set up for the things the firm will really look up: a matter with its parties, its ledger, its time entries and its list of documents. Which are worth having is agreed in the analysis.

  3. Documents sit beside the database

    Files are normally kept in folders on the same server, with a table recording each document’s matter, title, dates and path. Storing the files inside the database is possible but makes it far larger. On the Express edition, the cap on database size rules that out for most firms’ document stores.

  4. The edition follows the size

    A firm’s tables may fit within the Express limit once documents are kept outside the database. A long trust and time history at a larger firm may not. The size of the source data is measured in the analysis, and the edition is chosen from that figure with the firm’s IT provider.

  5. Backups and a test restore

    An archive that is never backed up is one disk failure from gone. Backups belong to the firm’s IT provider: a full one once the load is finished, and a schedule if anything is still being added. It is worth restoring one to a second machine as a test, because a backup that has never been restored is only a hope.

More about moving into Microsoft SQL Server

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 Microsoft SQL Server 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 Microsoft SQL Server 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 toMicrosoft SQL Server

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 Microsoft SQL Server. 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

Microsoft SQL Server 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.

Standing up SQL Server as an archive is IT work shared with the firm’s provider. A server or instance is chosen, logins are created for the few people who need to read the data, and nobody is given rights to change it. Views and a handful of reports are built for the common questions, and the IT provider owns the backup routine.

What is agreed and set up

  • Server, instance and edition agreed with the IT provider
  • Read-only logins and roles for named staff
  • Views for matter, ledger, time and document look-ups
  • Backup schedule and who tests a restore
  • Plain names and descriptions for tables and columns
  • Excel or Power BI connected for reporting

Questions

Primafact to Microsoft SQL Server: 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 Microsoft SQL Server hold documents from Primafact?

In part. As files in folders with an index table; storing files in the database is possible. What Microsoft SQL Server can hold is written out once its mapping is agreed, and the rest is kept beside the data as files that open without Primafact.

Does everything in Primafact have a place in Microsoft SQL Server?

On paper, yes: each kind of record Primafact holds has a place in Microsoft SQL Server. Whether every field fits is a separate question, and the analysis answers it field by field. Anything with no place comes across as a note or stays behind, and you see which before the move.

What has to be decided before Primafact is written out to Microsoft SQL Server?

Documents, emails, custom fields and templates 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 Microsoft SQL Server are the names and marks of their owners, used here only to identify the two systems.

Moving from Primafact to Microsoft SQL Server?

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

We reply within one business day.