Data migration route
Egnyte to SmartAdvocate migration
Egnyte is cloud file storage, and SmartAdvocate is a cloud case management system for personal injury work. The move is matching each file in Egnyte to its case in SmartAdvocate.
EgnyteCloud- Documents: Carried across
- Emails: Carried across
- Custom fields: Carried with mapping
- Notes: Confirmed in the analysis
- Tasks: Confirmed in the analysis
SmartAdvocateCloud- 2 carried
- 1 mapped
- 2 to confirm
What moves
What moves from Egnyte to SmartAdvocate
Each row is a kind of record Egnyte holds, whether SmartAdvocate 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.
| Record | What is planned | ||
|---|---|---|---|
| DocumentsFiles stored in or linked from the system | HeldFiles in the Shared folder tree and in users’ Private folders, with versions. | Has a placeDocuments page, by category and subcategory. | Carried across |
| EmailsEmails saved to matters or to the store | Held in partOnly where staff saved message files into folders. | Has a placeEmails are attached to cases. | Carried across |
| NotesFile notes, matter notes and contact notes | To be confirmed | Has a place | Confirmed in the analysis |
| TasksTo-dos and workflow steps assigned to people | To be confirmed | Has a place | Confirmed in the analysis |
| Custom fieldsFields and record types the firm added itself | Held in partMetadata sections and properties, where an administrator has defined them. | Has a place in partConfirmed in the analysis for each field with no standard home. | Carried with mapping |
What the plans mean
- Carried across
- SmartAdvocate has a place for this kind of record. It is loaded there and checked against Egnyte.
- Carried with mapping
- SmartAdvocate 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
Every document goes to the case it belongs to.
A case management system expects each document to sit on a case, usually in a category such as correspondence, medical records or court documents. Egnyte organises files its own way, by profile or by folder. So the move needs two rules: which case a file belongs to, and which category it goes in. The first comes from client and matter references or folder names. The second comes from a document type or a subfolder, and where neither exists the files arrive uncategorised and are marked as such.
Cases must exist in SmartAdvocate before documents can be attached to them. If the system is already live, files are matched to its case list and the unmatched ones are reported. If it is new, the case list is created first. Dates, authors and file names are kept. Email comes across as message files. Where several versions of a document exist, the firm chooses between loading the latest and loading them all.
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 SmartAdvocate are finished.
Where the data is now
Leaving Egnyte
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.
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.
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.
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.
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.
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.
Where it is going
Arriving in SmartAdvocate
SmartAdvocate keeps injury detail in structured fields and screens, so mapping counts for more than usual: the more precisely the old data is placed, the more of those screens are filled on the first day. Parties, incidents, insurers, providers and bills are loaded to their own screens, and the vendor’s implementation team runs conversions into it.
Map to fields, not notes
The case summary, dashboards and settlement screen read from structured fields. Injury details, insurance limits and provider bills dumped into a note leave those screens empty. The mapping takes each old field to its SmartAdvocate counterpart, and only what truly has no counterpart is loaded as a note.
Case types and statuses
Cases are loaded against case types and statuses that drive WorkPlans and reports. These are agreed with the firm before the trial load, and old statuses are translated to the new list. A status with no match is not guessed at. It is listed, and someone who knows the files decides.
Document categories
Documents are searched by category, subcategory, sender, recipient and date as well as by folder. The old system’s folders are translated into categories on the way in. Files that arrive uncategorised can still be found by description, but they fall outside the category views staff are trained to use.
Working with the vendor’s conversion
SmartAdvocate’s implementation team converts client data into the system and trains staff through its own classes. The firm’s side of that is supplying a clean source, checking the converted cases against the old system, and deciding what to do with the exceptions. Independent help is used on those tasks.
Choosing Server or Cloud
The firm decides before loading whether it will run the Server edition on its own Windows server or use the hosted Cloud edition. Either way the data load is the same. What differs is who looks after backups, updates and remote access afterwards, and that is settled with the firm’s IT provider.
How NewLaw runs it
Four steps, in this order.
Nothing financial lands in SmartAdvocate on this route, which makes it repeatable: a load can be run again until it is right. The maker of SmartAdvocate says that it, or its partners, load firms into the product. Where the firm uses that service, NewLaw’s part is the work around it: the analysis, the clean-up in Egnyte and checking each trial against Egnyte.
Analysis
We read what Egnyte holds and how it is organised, then agree with you where each kind of record will sit in SmartAdvocate. 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 SmartAdvocate 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.
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
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 Egnyte holds
What is in it, how its records link, and where each piece would sit in SmartAdvocate. 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 SmartAdvocate
Loaded data is not yet a working system. The maker of SmartAdvocate runs or arranges the set-up of its product, so this is what has to be decided and put in place in SmartAdvocate, whoever does the work, before people rely on it from the first day.
Setting up SmartAdvocate is a matter of deciding how much of its detail the firm will use from the start. Case types, statuses and WorkPlans come first because they drive everything else. Templates follow. The vendor trains staff through its own classes, and the decisions below are best made before the first of those.
Set-up decisions in SmartAdvocate
- Choose the Server or Cloud edition with IT
- Define case types, statuses and staff roles
- Build WorkPlans and Automated Procedures for each case type
- Convert letters and forms into templates with merge codes
- Install the Outlook plugin and agree email filing habits
- Set up intake screens, lead sources and dashboards
Questions
Egnyte to SmartAdvocate: 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 SmartAdvocate?
SmartAdvocate stores documents. Documents page, by category and subcategory. 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 SmartAdvocate?
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 SmartAdvocate is kept as a readable archive, and you see which before the move.
What has to be decided before Egnyte data is loaded into SmartAdvocate?
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.
Other routes
Other routes from Egnyte and into SmartAdvocate
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.
Egnyte and SmartAdvocate are the names and marks of their owners, used here only to identify the two systems.
Moving from Egnyte to SmartAdvocate?
Tell us what you are moving. You get a plan and a fixed price after the analysis.
We reply within one business day.