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

Data migration route

Primafact to Sync.com migration

Primafact is a server-based document management system for litigation work, and Sync.com is cloud file storage. Storage only has folders, so the move decides what of each document’s profile is kept in names and what in an index.

FromPrimafactServer
  1. Documents: Carried across
  2. Emails: Carried with mapping
  3. Notes: Carried with mapping
  4. Templates: Carried with mapping
ToSync.comCloud
  1. Matters: Kept as a readable archive
  2. Tasks: Kept as a readable archive
  3. Custom fields: Kept as a readable archive
Readable archiveNo place in Sync.com
  • 1 carried
  • 3 mapped
  • 3 archived
What the two products hold. The analysis confirms it field by field.

What moves

What moves from Primafact to Sync.com

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

Records in Primafact and their place in Sync.com
RecordIn PrimafactIn Sync.comWhat 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.No placeA matter is a folder in Files or Vault.Kept as a readable archive
DocumentsFiles stored in or linked from the systemHeldPaged documents in binders, with profile fields, searchable text and markup.Has a placeFiles and folders within the path limit; some file types are skipped by the apps.Carried across
EmailsEmails saved to matters or to the storeHeld in partEmails can be imported from Outlook as documents.Has a place in partMessage files such as .msg or .eml, filed in the matter’s folder.Carried with mapping
NotesFile notes, matter notes and contact notesHeldAnnotations and notes attached to documents and pages.Has a place in partOnly as a document written out to the matter’s folder.Carried with mapping
TasksTo-dos and workflow steps assigned to peopleHeld in partReview workflow only: an Inbox, team flags and document discussions.No placeKept as a readable archive
Custom fieldsFields and record types the firm added itselfHeldProfile fields, annotation colour labels and team flag labels are set by the firm.No placeKept as a readable archive
TemplatesPrecedents, document templates and automationHeld in partCase templates set binder structure, coding and permissions for new cases.Has a place in partPrecedents load as ordinary files.Carried with mapping

What the plans mean

Carried across
Sync.com has a place for this kind of record. It is loaded there and checked against Primafact.
Carried with mapping
Sync.com 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
Sync.com 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

Profiles flatten into folders and an index.

A document management system knows things about a file that a folder cannot hold: its profile, its versions, who may open it. Moving from Primafact to Sync.com flattens that. Client and matter become folder levels. Document type may become a subfolder. Versions become separate files with a suffix, or only the latest is kept. Each of these is a choice the firm makes before the export, and the result is tested on a sample of real matters.

What the folders cannot carry goes into an index: a spreadsheet listing every exported file with its document number, author, dates, type and original location. With it, a document cited by number in an old email can still be found. Access restrictions do not transfer by themselves. Restricted workspaces are exported to separate folders, and permissions are set on those in Sync.com before anyone else is given access.

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. Sync.com 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

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 firm that moves its files to Sync is usually doing so for confidentiality, and the load has to respect how the service is built to deliver it. Files are encrypted before they leave the computer. Nobody at Sync can look inside the account to confirm what arrived, so the checking is done from the firm’s side, against the list of what was sent.

  1. Files or Vault

    Open matters belong in Files, where they sync to the people working on them. Closed matters can go to Vault, which holds them in the cloud without putting a copy on every laptop. The firm supplies its open and closed matter lists so each folder is sent to the right side.

  2. A 248 character path limit

    Sync sets a maximum path length of 248 characters to stay compatible between Windows and Mac, and its apps skip anything longer. That is tighter than most systems a firm will be coming from. Folder names are shortened in the plan, and Sync’s own guidance favours a tree only a few levels deep.

  3. What the apps leave out

    The desktop apps do not upload shortcut files, temporary Office files or names containing a slash, and they warn against several other characters on Windows. A copy to Vault produces a transfer report listing what was skipped. That report is reconciled against the source file list after every load.

  4. Permissions come from the top folder

    Sharing is set on a folder and flows down to all of its contents. A matter that needs different access from the rest of a client’s work cannot simply sit one level down with tighter settings. It becomes its own shared folder, and those exceptions are identified before the tree is built.

  5. Shared folders count against storage

    A shared folder is added to each member’s account and normally counts towards their quota, and it syncs to their computer as a real folder. Sharing the whole client tree with every person can fill both. Shares are sized to teams, and the allowance needed per user is worked out from the document volumes.

More about moving into Sync.com

How NewLaw runs it

Four steps, in this order.

Nothing financial lands in Sync.com on this route, which makes it repeatable: a load can be run again until it is right.

  1. Analysis

    We read what Primafact holds and how it is organised, then agree with you where each kind of record will sit in Sync.com. Anything with no place there stays behind or is archived, and you see which before the move.

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

  3. Trial load

    A trial is loaded into Sync.com 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.

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

Step 1 of 5: Start with the route

Moving fromPrimafact
Moving toSync.com

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 Sync.com. 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

Sync.com is storage, not an application, so there is no product to configure. What is agreed and set up is the folder structure, who can open what, and how the result is handed to the firm.

A Sync set-up comes down to accounts and shares. A team plan gives an administrator control over users, two-factor authentication and password resets, which matters more than usual in a service the provider says it cannot see into. The shared folders are then created to match the firm’s teams and its restricted matters.

What is agreed and set up

  • Administrator account and a user for each staff member
  • Two-factor authentication enforced across the firm
  • Team shared folders with view or edit permission per person
  • Which matters live in Files and which in Vault
  • Rules for client links: passwords, expiry dates, upload rights
  • Desktop app installed, with a filing guide for new matters

Questions

Primafact to Sync.com: 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 Sync.com?

Sync.com stores documents. Files and folders within the path limit; some file types are skipped by the apps. 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.

What happens to records Sync.com has no place for?

On this route that is matters, tasks and custom fields. 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 data is loaded into Sync.com?

Emails, notes 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.

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

Moving from Primafact to Sync.com?

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

We reply within one business day.