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

Data migration route

Egnyte to Smokeball migration

Egnyte is cloud file storage, and Smokeball is a practice management system that runs on the desktop and keeps its data in its maker’s cloud. The move is about deciding which folder is which matter, then filing every document against it.

FromEgnyteCloud
  1. Documents: Carried across
  2. Emails: Carried across
  3. Custom fields: Carried with mapping
  4. Notes: Confirmed in the analysis
  5. Tasks: Confirmed in the analysis
ToSmokeballDesktop and cloud
  • 2 carried
  • 1 mapped
  • 2 to confirm
What the two products hold. The analysis confirms it field by field.

What moves

What moves from Egnyte to Smokeball

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

Records in Egnyte and their place in Smokeball
RecordIn EgnyteIn SmokeballWhat 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 and folders import into a matter with the folder structure kept.Carried across
EmailsEmails saved to matters or to the storeHeld in partOnly where staff saved message files into folders.Has a placeKept in the matter with other files.Carried across
NotesFile notes, matter notes and contact notesTo be confirmedHas a placeAs memos; not importable on the Bill plan.Confirmed in the analysis
TasksTo-dos and workflow steps assigned to peopleTo be confirmedHas a placeNot importable on the Bill plan.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 place in partValues need a matching field in the matter type’s layouts.Carried with mapping

What the plans mean

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

Folders become matters with documents.

Files in Egnyte are organised the way the firm’s people organised them: by client, by year, by lawyer, sometimes all three. Smokeball wants every document on a matter. The analysis reads the folder tree and proposes a rule, for example that the second folder level is the matter, then lists every folder the rule does not fit. Those exceptions are the real work. A folder called Misc or Old Files has to be given a home by someone who knows the firm.

Folder names carry what a matter record should hold properly: client name, matter description, sometimes a file number. Where the names are consistent, matters and contacts can be created from them. Where they are not, the matter list is built first, in a spreadsheet the firm corrects, and the documents are loaded against it. File dates are preserved, so a document still shows when it was written and not when it was moved.

Both are hosted by their makers, so nothing is collected from the firm’s office. What can be taken out of Egnyte depends on its export tools and on what its maker provides on request, and that is confirmed during the analysis, before a date is set. The subscription to Egnyte is kept running until the checks on Smokeball are finished.

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

Smokeball has a data import tool that reads spreadsheets of staff, contacts, matters, balances, unbilled time, invoices, memos, tasks and calendar events. Some of those are only available on the higher plans. Documents are brought in separately, with their folders. Before the first trial, every incoming matter is given a Smokeball matter type, since nothing else about the matter can be placed without one.

  1. Every matter needs a type

    Smokeball’s matter types are specific to an area of law and a state or jurisdiction, and each brings its own fields. The old system’s matter types are mapped to them one by one. It is worth getting right the first time: changing a matter’s type later can drop the details held in layouts the new type does not have.

  2. The plan decides what loads

    Matter roles, tags, critical dates and archive details import only on the Grow and Prosper+ plans. Memos, tasks and calendar events do not import on the Bill plan. The firm’s plan is confirmed before the mapping is written, so nobody maps the other side’s solicitor to a role that the subscription cannot hold.

  3. Leave auto-numbering until after

    Smokeball’s guidance for firms still bringing matters in is to wait before setting up automatic Internal References. Imported matters arrive with the numbers they already had. Once the load is accepted, the reference format and the counter’s starting number are set so the first new matter follows on from the last old one.

  4. Documents arrive by folder

    Importing a folder into a matter keeps its subfolders, and default folders can also be defined per matter type. The firm decides which wins where they differ: the old structure as it was, or its new standard layout with old folders mapped into it.

  5. An opening balance per matter

    Matter account balances are on the import list, along with unbilled time and expenses, invoices and billed invoice entries. Past trust transactions are not on that list. The trust position is therefore loaded as an opening balance for each matter and rehearsed on a full trial, with the transaction history kept in the old system.

More about moving into Smokeball

How NewLaw runs it

Four steps, in this order.

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

  1. Analysis

    We read what Egnyte holds and how it is organised, then agree with you where each kind of record will sit in Smokeball. 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 Smokeball and checked against Egnyte: 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 Egnyte, a final pass over a weekend picks up what changed since the trial. Egnyte 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 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 toSmokeball

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

Setting up Smokeball

Loaded data is not yet a working system. This is what NewLaw sets up in Smokeball, beyond the migration, so that people can work in it from the first day.

A Smokeball set-up is partly on the firm’s PCs and partly in firm settings. The desktop app and its Word and Outlook add-ins go on each Windows machine. In settings, the firm chooses the matter types it will use, defines default folders for each and sets its numbering. Trust accounts and the accounting connection are configured before the first invoice is raised.

Set-up decisions in Smokeball

  • Matter types in use, with default document folders for each
  • Internal Reference format and the starting number for new matters
  • Trust account details and the link to the accounting package
  • Staff roles and permissions, including who sees billing and trust
  • Firm precedents and letterhead rebuilt as Smokeball templates
  • Desktop app, Word and Outlook add-ins on every PC

Questions

Egnyte to Smokeball: 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.

Do documents from Egnyte keep their folders and dates in Smokeball?

Smokeball stores documents. Files and folders import into a matter with the folder structure kept. 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 Egnyte have a place in Smokeball?

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

What has to be decided before Egnyte data is loaded into Smokeball?

Custom fields are carried with mapping, so each mapping is agreed with you first. Notes and tasks are confirmed in the analysis. 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

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

Moving from Egnyte to Smokeball?

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

We reply within one business day.