Data migration route
Primafact to Clio Manage migration
Primafact is a server-based document management system for litigation work, and Clio Manage is a cloud practice management system. Documents and email move out of a store organised by profile and onto the matters they belong to.
PrimafactServer- Matters: Carried across
- Documents: Carried across
- Emails: Carried across
- Notes: Carried across
- Tasks: Carried across
- Custom fields: Carried with mapping
- Templates: Carried with mapping
Clio ManageCloud- 5 carried
- 2 mapped
What moves
What moves from Primafact to Clio Manage
Each row is a kind of record Primafact holds, whether Clio Manage has a place for it, and what is planned. On this route five kinds of record carry across and two kinds need mapping.
| Record | What is planned | ||
|---|---|---|---|
| MattersMatters or cases, with their numbers, types, parties and status | Held in partCases exist as containers for binders, not as matter records with parties and status. | Has a placeImported from a matters template, after contacts. | Carried across |
| DocumentsFiles stored in or linked from the system | HeldPaged documents in binders, with profile fields, searchable text and markup. | Has a placeFiled under the matter; Clio scopes document migration separately from data. | Carried across |
| EmailsEmails saved to matters or to the store | Held in partEmails can be imported from Outlook as documents. | Has a placeHeld as communications on the matter, with phone logs. | Carried across |
| NotesFile notes, matter notes and contact notes | HeldAnnotations and notes attached to documents and pages. | Has a placeMatter notes and contact notes each have a template. | Carried across |
| TasksTo-dos and workflow steps assigned to people | Held in partReview workflow only: an Inbox, team flags and document discussions. | Has a placeTasks have a migration template. | Carried across |
| Custom fieldsFields and record types the firm added itself | HeldProfile fields, annotation colour labels and team flag labels are set by the firm. | Has a placeCreated first, then filled from the custom field templates. | Carried with mapping |
| TemplatesPrecedents, document templates and automation | Held in partCase templates set binder structure, coding and permissions for new cases. | Has a placeRebuilt as Clio document templates with its merge fields. | Carried with mapping |
What the plans mean
- Carried across
- Clio Manage has a place for this kind of record. It is loaded there and checked against Primafact.
- Carried with mapping
- Clio Manage 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
Profiled documents become matter documents.
A document management system files by profile: client, matter, author, document type, version. A practice management system files by matter. The move from Primafact to Clio Manage is a translation from one to the other, and it depends on the client and matter numbers in Primafact matching matters that exist in Clio Manage. Where they do not match, documents have nowhere to land. So the matter list is settled first and the documents follow it.
Versions and security each need a decision. Some practice systems keep every version of a document, others keep the latest and treat the rest as separate files. A restricted workspace has to become a restricted matter, or the restriction is lost on the way. Filed email comes across as message files against the matter. A document store holds no ledgers, so this route has no financial cutover.
Primafact 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. Clio Manage 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
Leaving Primafact
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.
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.
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.
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.
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.
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.
Where it is going
Arriving in Clio Manage
Clio Manage is loaded through its migration templates, one spreadsheet per kind of record, imported in a fixed order with contacts first. Clio’s own migration guide is plain about the limit: balances come across, financial history does not. So a load into Clio is planned as records plus opening positions, with the old system kept for the history behind them.
Matters link by client name
The matters template ties each matter to its client by an exact match on first name, last name or company name. A client spelt two ways in the old system becomes two contacts, or a matter assigned to an unknown client. This is why contact clean-up is finished before the first trial load, not after it.
Decide the numbering scheme first
Clio numbers imported matters itself unless the account is set to manual numbering, in which case the old number is supplied in the template. That setting and the firm’s preferred scheme are decided before any matter is loaded. The Client Reference field is available for an old file number the firm still wants to see.
Balances, one line each
Under Clio’s standard migration, an outstanding balance arrives as one line per matter and a trust balance as one line per matter or contact. Past invoices, billed time, payments and trust transactions are listed as data that cannot be migrated. The trust total is reconciled against the old system’s closing report on the trial load.
Custom fields must exist
Matter and contact custom fields are created in Clio before their values are imported, each with a field type. Accounts set up for a particular practice area come with preconfigured fields and matter templates, which affects the mapping. We compare those with the old system’s fields and add only what is missing.
Rates and permissions by hand
Billable rates for users, clients and matters are not part of an import. Neither are user permissions or settings. They are entered in Clio during set-up from a schedule the firm confirms, and a sample of imported unbilled time is checked against that schedule before the trial load is signed off.
How NewLaw runs it
Four steps, in this order.
Nothing financial lands in Clio Manage on this route, which makes it repeatable: a load can be run again until it is right.
Analysis
We read what Primafact holds and how it is organised, then agree with you where each kind of record will sit in Clio Manage. Anything with no place there stays behind or is archived, and you see which before the move.
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.
Trial load
A trial is loaded into Clio Manage and checked against Primafact: 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.
Cutover
There is no financial cutover on this route. After a short freeze on changes in Primafact, a final pass over a weekend picks up what changed since the trial. Primafact 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 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
What happens after you send it
- A free first call
We go through your answers with you and ask about anything they leave open.
- An analysis of what Primafact holds
What is in it, how its records link, and where each piece would sit in Clio Manage. Anything with no place there comes across as a note or stays behind, and you see which before the move.
- 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 Clio Manage
Loaded data is not yet a working system. This is what NewLaw sets up in Clio Manage, beyond the migration, so that people can work in it from the first day.
Much of a Clio Manage set-up is firm-wide settings. The numbering scheme, practice areas, matter stages, billing preferences and trust accounts apply to everyone, so they are agreed once and early. Trust and accounting features are not the same in every country Clio sells in, so the firm’s own region is checked first. Document templates and custom fields follow. Email and document integrations are then installed for each user and tested on a real matter.
Set-up decisions in Clio Manage
- Matter numbering scheme, practice areas and matter stages
- Custom fields for matters and contacts, by practice area
- Document templates with merge fields, uploaded from Word or PDF
- Billing settings, user and client rates, and trust accounts
- Roles and permissions for each user
- Outlook add-in, Clio Drive and the accounting connection
Questions
Primafact to Clio Manage: 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.
Do documents from Primafact keep their folders and dates in Clio Manage?
Clio Manage stores documents. Filed under the matter; Clio scopes document migration separately from data. 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 Primafact have a place in Clio Manage?
On paper, yes: each kind of record Primafact holds has a place in Clio Manage. 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 data is loaded into Clio Manage?
Custom fields and templates are carried with mapping, so each mapping is agreed with you first. The firm also decides which closed matters and how many versions of a document are in scope.
Other routes
Other routes from Primafact and into Clio Manage
Other destinations from Primafact
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.
Choose your systems
Technology stack selection
Decide which practice management system your firm runs, with the evidence and the cost beside it.
About four weeks for a firm of about 15 people. Fixed price, set after a free first call.
Move your data
Data migration
Your data is cleaned up before anything moves, then a trial load is checked against the old system.
Fixed price, agreed after the analysis.
Set up your new system
Implementation
Your new system set up around the way your firm works: configuration, document automation and training.
A small firm of 1 to 10 users typically takes 4 to 8 weeks. A mid-sized firm of 10 to 50 users takes 8 to 16 weeks.
Put AI to work
AI advisory and enablement
A small group of your people learn to use an approved AI tool on real work, under written rules.
Two to four weeks for a small first group. Fixed price, set after a free first call.
Primafact and Clio Manage are the names and marks of their owners, used here only to identify the two systems.
Moving from Primafact to Clio Manage?
Tell us what you are moving. You get a plan and a fixed price after the analysis.
We reply within one business day.