Data migration route
USB drives to Litify migration
USB drives are plain files on equipment the firm controls, and Litify is a cloud case management system. The move is matching each file in USB drives to its case in Litify.
USB drivesFiles- Documents: Carried across
- Emails: Carried with mapping
LitifyCloud- 1 carried
- 1 mapped
What moves
What moves from USB drives to Litify
Each row is a kind of record USB drives hold, whether Litify has a place for it, and what is planned. On this route one kind of record carries across and one kind needs mapping.
| Record | What is planned | ||
|---|---|---|---|
| DocumentsFiles stored in or linked from the system | HeldLoose files and folders; no sharing, versions or access control on FAT formats. | Has a placeLoaded to the document component and attached to matters. | Carried across |
| EmailsEmails saved to matters or to the store | Held in partSaved message files or copied Outlook data files, where someone put them there. | Has a place in partShown on the activity timeline. How old email is loaded is confirmed in the analysis. | Carried with mapping |
What the plans mean
- Carried across
- Litify has a place for this kind of record. It is loaded there and checked against USB drives.
- Carried with mapping
- Litify holds this differently, or in part. Each field or value is matched to its place before loading, and you see the mapping first.
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. USB drives organise 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 Litify 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.
With USB drives the files are already on equipment the firm controls, so there is no export step: they are read where they are. Upload speed sets the pace for a large store. The originals stay in place, unchanged, until the firm has checked the copy in Litify.
Where the data is now
Leaving USB drives
Each USB drive is its own small puzzle, and the first task is to say what it is. A working copy of matter files is handled one way. The backup of an old practice system is a database to be restored, not a set of documents. Material received from a client belongs to one matter and may need to be kept exactly as it was received.
Identify each drive first
Every drive is labelled and listed, and its contents are classed as loose documents, a system backup, or third-party material for a known matter. A stick holding a .bak or other backup file goes to whoever is handling that old system, because the documents inside cannot be reached by copying.
Copy once, then put it away
Flash drives can fail without warning, and each reading is a small risk. It is safer to copy a drive once and do the sorting and matching on the copy than to keep going back to the stick. How the copy is made and checked is agreed with the firm’s IT provider, and the drive goes back in the safe.
Times shift on FAT drives
FAT file systems store times in local time and record the modified time only to the nearest two seconds. The same document on a stick and on the server can show dates an hour apart after a daylight saving change. Matching dates is therefore an unreliable way to find duplicates on these drives.
Encrypted drives need their password
A drive protected with BitLocker To Go or a hardware keypad opens only with its password or recovery key. Where the person who set it has left, the firm’s IT provider may hold a recovery key. If nobody does, the contents cannot be read, and that is recorded against the drive.
Material from clients and other parties
Drives received in a matter are evidence of what was handed over. The original folder structure and file dates are preserved in the copy, and the files are filed to the matter as a set under the date received. What happens to the physical drive, kept or returned, follows the firm’s own file rules.
Where it is going
Arriving in Litify
Loading a firm into Litify is done inside a Salesforce environment that has been configured for that firm, normally by Litify or one of its implementation partners. The data work fits around that project. Old records are mapped to parties, roles, intakes and matters and loaded into the Salesforce objects behind them, and documents are loaded separately and attached.
The design comes first
Case types, stages and page layouts are decided during discovery, before any load. A load into a half-configured environment has to be repeated when a field changes. The data mapping is written against the agreed design and updated whenever the design moves, so the two stay in step.
One party, many roles
Contacts from the old system become parties, and each appearance on a matter becomes a role. Duplicate contacts turn into duplicate parties with their roles divided between them. Duplicates are merged before the load where they can be identified, since separating them afterwards means pointing every role at the right party again.
Open enquiries load as intakes
Leads and enquiries that have not signed belong in intakes, not matters. They are loaded with their source and status so that conversion reports start from a true position. Old declined enquiries are loaded only if the firm wants them for conflict checking, and are marked so they do not count as live.
Documents load after records
Files are loaded into the document component once the matters exist, because each one is attached to a matter record. Folder structure is set per case type beforehand. Large injury files with medical records and video take time to transfer, and that time is planned into the cutover weekend.
Validation rules reject bad rows
A configured environment enforces required fields and validation rules, and old data seldom satisfies all of them. Rows that fail are reported by the load. They are fixed in the source and run again, or the rule is relaxed for migrated records, and the firm decides which for each rule.
How NewLaw runs it
Four steps, in this order.
Nothing financial lands in Litify on this route, which makes it repeatable: a load can be run again until it is right. The maker of Litify 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 USB drives and checking each trial against USB drives.
Analysis
We read what USB drives hold and how it is organised, then agree with you where each kind of record will sit in Litify. 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 Litify and checked against USB drives: 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 USB drives, a final pass over a weekend picks up what changed since the trial. USB drives are 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 USB drives 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 USB drives holds
What is in it, how its records link, and where each piece would sit in Litify. 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 Litify
Loaded data is not yet a working system. The maker of Litify runs or arranges the set-up of its product, so this is what has to be decided and put in place in Litify, whoever does the work, before people rely on it from the first day.
A Litify implementation is a configuration project on Salesforce, run by Litify or an implementation partner with the firm’s own project team. Discovery sessions with each department come first. The decisions that follow shape the system: what an intake asks, how a matter moves through its stages, who sees what, and which other systems are connected.
Set-up decisions in Litify
- Define intake questionnaires and the rules for conversion
- Set case types, matter stages and page layouts
- Build matter plans that create tasks at each stage
- Design document folders and generation templates per case type
- Configure user roles and sharing for restricted matters
- Decide on timekeeping, billing and accounting integrations
Questions
USB drives to Litify: what firms ask
We have a box of old USB drives and no idea what is on them. Is it worth including them?
Usually it is worth the listing, which is quick. Each drive is summarised: how many files, what kinds, what date range, which client names appear. The firm then chooses which drives are loaded, which are kept as they are, and which hold nothing but copies of files already on the server.
One drive has a backup from the system we used ten years ago. Can that be brought in?
Possibly. It depends on whether the backup can be restored, which needs a copy of the old software or a database engine that reads its format. That is tested on its own before any promise is made. If it restores, its matters and documents are treated like any other source system.
Is it safe to plug unknown drives into our network?
That is a question for the firm’s IT provider, and the cautious answer is no. A drive of unknown origin can carry malicious software as well as documents. How unknown drives are read, and on which machine, is agreed with the IT provider before any of them is opened.
Do documents from USB drives keep their folders and dates in Litify?
Litify stores documents. Loaded to the document component and attached to matters. 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 USB drives have a place in Litify?
On paper, yes: each kind of record USB drives hold has a place in Litify. Whether every field fits is a separate question, and the analysis answers it field by field. Anything with no place comes across as a note or stays behind, and you see which before the move.
What has to be decided before USB drives data is loaded into Litify?
Emails 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.
Other routes
Other routes from USB drives and into Litify
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.
USB drives and Litify are the names and marks of their owners, used here only to identify the two systems.
Moving from USB drives to Litify?
Tell us what you are moving. You get a plan and a fixed price after the analysis.
We reply within one business day.