Data migration route
Google Drive to Litify migration
Google Drive is cloud file storage, and Litify is a cloud case management system. The move is matching each file in Google Drive to its case in Litify.
Google DriveCloud- Documents: Carried across
- Emails: Carried with mapping
- Templates: Carried with mapping
LitifyCloud- 1 carried
- 2 mapped
What moves
What moves from Google Drive to Litify
Each row is a kind of record Google Drive holds, whether Litify has a place for it, and what is planned. On this route one kind of record carries across and two kinds need mapping.
| Record | What is planned | ||
|---|---|---|---|
| DocumentsFiles stored in or linked from the system | HeldUploaded files plus Google Docs, Sheets and Slides, which are not files until exported. | 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 to Drive as files; mail itself is in Gmail. | Has a place in partShown on the activity timeline. How old email is loaded is confirmed in the analysis. | Carried with mapping |
| TemplatesPrecedents, document templates and automation | Held in partPrecedents kept as files or as Google Docs that staff copy. | 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 Google Drive.
- 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. Google Drive 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 Google Drive 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 Google Drive is kept running until the checks on Litify are finished.
Where the data is now
Leaving Google Drive
Two things set a move off Google Drive apart from a move off any other drive. Much of the content is in Google’s own formats and has to be converted on the way out. And ownership is personal unless the firm used shared drives, so the files for one matter can be scattered across the accounts of everyone who ever worked on it.
Docs, Sheets and Slides convert
A Google Doc has no file behind it. On the way out it is saved as Word or PDF, a Sheet as Excel. The document’s revision history stays in Google, and links from one Doc to another still point back there. How layout, comments and suggestions come through is checked on a sample. The firm picks the output format per document type.
My Drive files belong to people
Every file in My Drive has one owner. A matter folder shared across the firm can contain files owned by six different accounts, some of them former staff. An administrator can transfer a user’s files to a new owner, and that is done for leavers before their accounts are touched.
Shortcuts are not the file
A shortcut in a matter folder points to a file stored somewhere else, often in another person’s drive. Copied naively it arrives as an empty pointer. Shortcuts are resolved to the real document during collection, and where the target can no longer be reached the gap is reported.
Names Windows cannot hold
Drive lets two files in one folder share a name, and Windows does not. Windows and SharePoint also refuse certain characters in names. Both are looked for in the analysis. Duplicated names are numbered and refused characters replaced by an agreed rule before loading, with the changes listed against the original names.
Old versions of uploads expire
For an uploaded file such as a PDF or Word document, Drive may delete an earlier version after 30 days or once there are 100 newer ones, unless someone marked it Keep forever. Earlier drafts the firm assumes are there may not be. What exists is counted in the analysis.
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 Google Drive and checking each trial against Google Drive.
Analysis
We read what Google Drive 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 Google Drive: 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 Google Drive, a final pass over a weekend picks up what changed since the trial. Google Drive 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 Google Drive 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 Google Drive 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
Google Drive to Litify: what firms ask
What happens to our Google Docs when we move to a system that uses Word?
Each Doc is converted to a Word file, or to PDF where it is a finished document that should not change. Documents with heavy tables, drawings or linked Sheets are the ones checked by eye on a sample. The originals stay in Google, read only, until the firm is satisfied.
Some matter files are owned by people who have left. Are they lost?
Not if the account still exists, even suspended. A Workspace administrator can transfer its files to a current user, and that is done first. Where an account was deleted some time ago its My Drive files are gone, and the analysis will show the affected matters by the gaps in their folders.
Do we move Gmail and Calendar as well?
They are separate from Drive and are scoped separately. A firm can keep Google Workspace for mail and calendar and move only its matter files into a practice or document system. If emails need to sit on matters, the question is which mailboxes and labels are filed, and that is answered in the analysis.
Do documents from Google Drive 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 Google Drive have a place in Litify?
On paper, yes: each kind of record Google Drive holds 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 Google Drive data is loaded into Litify?
Emails and templates 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 Google Drive 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.
Google Drive and Litify are the names and marks of their owners, used here only to identify the two systems.
Moving from Google Drive 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.