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

Data migration route

Egnyte data to Microsoft SQL Server

Egnyte is cloud file storage, 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.

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

What moves

What moves from Egnyte to Microsoft SQL Server

Each row is a kind of record Egnyte holds, whether Microsoft SQL Server has a place for it, and what is planned. On this route three kinds need mapping and two kinds are confirmed in the analysis.

Records in Egnyte and their place in Microsoft SQL Server
RecordIn EgnyteIn Microsoft SQL ServerWhat is planned
DocumentsFiles stored in or linked from the systemHeldFiles in the Shared folder tree and in users’ Private folders, with versions.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 partOnly where staff saved message files into folders.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 notesTo be confirmedHas a placeRows of text linked to matters and contacts.Confirmed in the analysis
TasksTo-dos and workflow steps assigned to peopleTo be confirmedHas a placeRows 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 placeAs added columns, or a table of field names and values.Exported with mapping

What the plans mean

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.
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 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 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 Microsoft SQL Server, and opening the file to confirm it is the same one.

Egnyte is hosted by its maker and Microsoft SQL Server 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

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 Egnyte holds, table by table, and agree with you what the copy in Microsoft SQL Server 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 Microsoft SQL Server 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 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 Egnyte 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

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

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

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

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 Microsoft SQL Server is kept as a readable archive, and you see which before the move.

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

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

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