Data migration route
OneDrive to Litify migration
OneDrive is cloud file storage, and Litify is a cloud case management system. The move is matching each file in OneDrive to its case in Litify.
OneDriveCloud- Documents: Carried across
- Emails: Carried with mapping
- Templates: Carried with mapping
- Notes: Confirmed in the analysis
LitifyCloud- 1 carried
- 2 mapped
- 1 to confirm
What moves
What moves from OneDrive to Litify
Each row is a kind of record OneDrive holds, whether Litify has a place for it, and what is planned. On this route one kind of record carries across, two kinds need mapping and one kind is confirmed in the analysis.
| Record | What is planned | ||
|---|---|---|---|
| DocumentsFiles stored in or linked from the system | HeldFiles in one user’s drive, with version history and sharing per file or folder. | Has a placeLoaded to the document component and attached to matters. | Carried across |
| EmailsEmails saved to matters or to the store | Held in partOnly messages saved as .msg or .eml files; mailboxes are in Exchange Online. | Has a place in partShown on the activity timeline. How old email is loaded is confirmed in the analysis. | Carried with mapping |
| NotesFile notes, matter notes and contact notes | Held in partOneNote notebooks stored in OneDrive, which sync by their own mechanism. | To be confirmed | Confirmed in the analysis |
| TemplatesPrecedents, document templates and automation | Held in partPrecedents sit in a folder as normal Word files. | Has a place in partTemplates are rebuilt in Litify’s document generation. | 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 OneDrive.
- 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.
- 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. OneDrive 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 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.
Both are hosted by their makers, so nothing is collected from the firm’s office. What can be taken out of OneDrive 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 OneDrive is kept running until the checks on Litify are finished.
Where the data is now
Leaving OneDrive
Firm files in OneDrive are firm files held in personal storage, and that shapes the whole move. There is no single place to collect from. Each person has a drive, arranged the way its owner likes, with folders shared sideways between colleagues. The analysis starts with a plain list of which drives hold matter files.
One drive per person
A matter may have its pleadings in the partner’s OneDrive, its correspondence in the secretary’s and its research in a clerk’s. Each drive is inventoried separately and the folders are matched to matters by name. Where the same matter turns up in more than one drive, the firm chooses how the copies are combined.
Leavers’ drives are on a timer
When a user account is deleted, Microsoft keeps that person’s OneDrive for a retention period, 30 days unless the firm changed it, and then removes it. The manager is given access in the meantime. A departed fee earner’s drive is dealt with first, because that timer does not wait for the project.
Desktop and Documents may be inside
Where known folder redirection is on, a person’s Desktop, Documents and Pictures are in their OneDrive. Collecting the whole drive brings holiday photos and personal paperwork with the matter files. Each person marks what is the firm’s, and private folders are excluded by path before collection.
Shared items live elsewhere
A folder that appears under Shared in someone’s OneDrive is stored in the drive of the person who shared it. It is collected once, from its owner. Counting it again from every colleague who can see it is how a document total ends up several times too large.
OneNote notebooks are a special case
A notebook saved in OneDrive syncs through OneNote, not through the sync app, and shows on disk only as a small link file. Lawyers who keep matter notes in OneNote need those notebooks exported from OneNote itself. Copying the folder brings the link and none of the pages.
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 OneDrive and checking each trial against OneDrive.
Analysis
We read what OneDrive holds 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 OneDrive: 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 OneDrive, a final pass over a weekend picks up what changed since the trial. OneDrive 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 OneDrive 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 OneDrive 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
OneDrive to Litify: what firms ask
A solicitor left last month and her matters were in her OneDrive. Is it too late?
Probably not, but it is urgent. After an account is deleted the drive is kept for a retention period, 30 days by default, and then sits in a recycle bin for a further period before it is gone. An administrator can give another user access now. It should be raised in the first conversation, ahead of any other planning.
Will our file names change?
Only where the destination cannot accept them. Moving out of OneDrive, most names are already safe because OneDrive is stricter than a Windows folder. The exceptions are very long paths, which a desktop system or a server drive may not open, and those are listed with the shortened names proposed.
Do earlier versions of documents come with them?
OneDrive keeps version history within limits an administrator sets, so there are often earlier versions to bring. Document management systems can usually receive them as versions. A destination that files plain documents against a matter generally takes the latest only, and the firm decides whether earlier ones are kept as extra files.
Do documents from OneDrive 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 OneDrive have a place in Litify?
Most of it does on paper. Notes 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 Litify is kept as a readable archive, and you see which before the move.
What has to be decided before OneDrive data is loaded into Litify?
Emails and templates are carried with mapping, so each mapping is agreed with you first. Notes 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 OneDrive 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.
OneDrive and Litify are the names and marks of their owners, used here only to identify the two systems.
Moving from OneDrive 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.