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

Data migration route

Egnyte data to Full data export

Egnyte is cloud file storage, and Full data export is a store of data kept as files the firm holds. What lands in Full data export is the register: every file’s name, place, dates and details, with the files themselves stored beside it.

FromEgnyteCloud
  1. Documents: Exported in full
  2. Emails: Exported with mapping
  3. Custom fields: Exported with mapping
  4. Notes: Confirmed in the analysis
  5. Tasks: Confirmed in the analysis
ToFull data exportFiles
  • 1 carried
  • 2 mapped
  • 2 to confirm
What the two products hold. The analysis confirms it field by field.

What moves

What moves from Egnyte to Full data export

Each row is a kind of record Egnyte holds, whether Full data export has a place for it, and what is planned. On this route one kind of record carries across, two kinds need mapping and two kinds are confirmed in the analysis.

Records in Egnyte and their place in Full data export
RecordIn EgnyteIn Full data exportWhat is planned
DocumentsFiles stored in or linked from the systemHeldFiles in the Shared folder tree and in users’ Private folders, with versions.Has a placeFiles under their original names, in client and matter folders.Exported in full
EmailsEmails saved to matters or to the storeHeld in partOnly where staff saved message files into folders.Has a place in partFiled emails as message files in the matter’s folder, if the source exposes them.Exported with mapping
NotesFile notes, matter notes and contact notesTo be confirmedHas a placeA notes table with matter, author and date for each note.Confirmed in the analysis
TasksTo-dos and workflow steps assigned to peopleTo be confirmedHas a placeA table of tasks with assignee, due date and status.Confirmed in the analysis
Custom fieldsFields and record types the firm added itselfHeld in partMetadata sections and properties, where an administrator has defined them.Has a placeExtra columns under their original field names.Exported with mapping

What the plans mean

Exported in full
Full data export has a place for this kind of record. It is loaded there and checked against Egnyte.
Exported with mapping
Full data export 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.

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 Egnyte are exported to storage the firm controls, and Full data export 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 Egnyte 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 Full data export, and opening the file to confirm it is the same one.

Egnyte is hosted by its maker and Full data export 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 Egnyte will release depends on its export tools, and that is confirmed in the analysis.

Where the data is now

An Egnyte domain is a folder tree, and moving it into a legal system is mostly a matter of teaching that tree which folder is which client and which matter. The files download with their paths and dates. What takes thought is everything the tree does not say: permissions on particular folders, private folders, links shared with clients, and any metadata the firm added.

  1. Shared and Private are separate

    Firm files live under the Shared folder. Administrators and power users may each also have a Private folder that colleagues do not see, and files created in draft mode are saved there. Client documents can end up in private folders. They are inventoried per user, and the owner decides what is matter material.

  2. Permissions are per folder

    Access is granted folder by folder to users and groups, and a subfolder can differ from its parent. A restricted matter is simply a folder most people are not on. The permissions are exported before extraction, so that restricted folders are known and their security can be reproduced in the destination.

  3. Metadata may or may not exist

    Egnyte lets administrators define metadata sections and have values inherit down a folder tree, but a domain can run without any. Where a firm did set client or matter properties on folders, those are a more reliable key than folder names. The analysis checks which the firm has and uses the stronger one.

  4. Versions and Trash

    Earlier versions of files are kept, and deleted items wait in Trash until they are purged. Both inflate the apparent volume. The firm chooses whether versions come across, and the counts are reported separately for current files, older versions and Trash.

  5. Links shared outside the firm

    Folders and files shared with clients by link, and upload links that clients use to send documents in, depend on the domain staying open. A list of active links and who holds them is produced before cutover, so the people who rely on them can be told where to go instead.

More about moving off Egnyte

Where it is going

A full export is judged by whether a stranger can use it. In five years the question will be something like: what was the trust balance on this matter the day it closed, and where is the signed agreement. The export is planned backwards from questions of that kind, and it is checked against the live system while the live system can still be opened.

  1. Tables that still join up

    Each kind of record becomes its own table: matters, contacts, time entries, invoices, trust transactions. The identifiers that link them are kept in every table, so a time entry can still be traced to its matter and its fee earner. An export that keeps the rows and drops the keys cannot be rejoined later.

  2. Documents with an index

    Documents are written to folders by client and matter under their original names. On their own they can be found only by name. An index listing each file with its matter number, title, author, dates and path is what lets someone find the right version of a lease among forty thousand files without the old system’s search. What the index records is settled in the analysis.

  3. Reports a person can read

    Raw tables do not satisfy an auditor or a former client. The firm decides which reports are also printed to PDF from the old system as at the final date: trust ledgers, matter ledgers, debtor lists and issued invoices are the usual candidates. They cannot be regenerated once the licence ends.

  4. What an export does not keep

    Screens, workflows, document automation, saved searches and user permissions belong to the software and stay with it. Figures the system calculated on the fly, such as a matter’s unbilled total, exist in an export only if they were captured as a report. The firm is told which of these are being let go.

  5. Checked while the source is open

    Record counts and financial totals in the export are reconciled to the live system: number of matters, sum of trust balances, total debtors, document count per matter on a sample. This is done before the subscription lapses or the server is turned off, because afterwards there is nothing left to compare against.

More about moving into Full data export

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 Egnyte holds, table by table, and agree with you what the copy in Full data export must be able to answer later. Everything Egnyte 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 Full data export as a trial and checked against Egnyte: record counts, totals where Egnyte 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 Egnyte, the export is run a final time and checked again. There is nothing to go live. Egnyte 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 Egnyte 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 fromEgnyte
Moving toFull data export

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 Egnyte holds

    What is in it, how its records link, and where each piece would sit in Full data export. 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

Full data export 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.

With no product to configure, the set-up is custody, and the decisions are the firm’s. Someone there owns the export, knows where it is kept and can open it. Access needs restricting, because it contains every client’s affairs in one place with none of the old system’s security. The firm sets a destruction date from its retention obligations and decides how the next custodian will learn to use it.

What is agreed and set up

  • Folder layout for tables, documents and reports
  • What the key to tables, columns and identifiers records
  • Where the copies are stored and who is custodian
  • Who may open it, as approved by a partner
  • Which look-ups staff must be able to do unaided
  • Retention period and the date it is next reviewed

Questions

Egnyte to Full data export: what firms ask

Our folders are already by client and matter. Is that enough?

It is a good start. The folder names are matched to the matter list from the practice management system, and whatever does not match is reported: misspelt names, closed matters with no number, general folders. Those are fixed in Egnyte before extraction or mapped by hand, and the trial load shows the result.

Do file dates and authors survive?

Modified dates travel with the files. Who uploaded or last edited a file is recorded by Egnyte, and where it can be exported as data it is loaded as author or kept as a property. Created dates are less reliable in any file store, and document dates are checked on the trial load.

Does the copy in Full data export hold documents from Egnyte?

Yes. Files under their original names, in client and matter folders. Documents are written out with the rest, and counts and totals are agreed to the reports in Egnyte as at the export date.

Does everything in Egnyte have a place in Full data export?

Most of it does on paper. Notes and tasks could not be confirmed from the two products’ own material, so those are checked in the analysis. Anything that turns out to have no place in Full data export is kept as a readable archive, and you see which before the move.

What has to be decided before Egnyte is written out to Full data export?

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

Egnyte and Full data export are the names and marks of their owners, used here only to identify the two systems.

Moving from Egnyte to Full data export?

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

We reply within one business day.