Data migration route
AdvoLogix to Google Drive migration
AdvoLogix is a cloud practice management system, and Google Drive is cloud file storage. Documents move into a folder for each client and matter, and the data behind them is kept as an export.
AdvoLogixCloud- Documents: Carried across
- Emails: Carried with mapping
- Notes: Carried with mapping
- Templates: Carried with mapping
- Trust money: Confirmed in the analysis
Google DriveCloud- Matters: Kept as a readable archive
- Contacts: Kept as a readable archive
- Calendar: Kept as a readable archive
- Tasks: Kept as a readable archive
- Time and expenses: Kept as a readable archive
- Billing: Kept as a readable archive
- Custom fields: Kept as a readable archive
- Intake: Kept as a readable archive
- 1 carried
- 3 mapped
- 1 to confirm
- 8 archived
What moves
What moves from AdvoLogix to Google Drive
Each row is a kind of record AdvoLogix holds, whether Google Drive has a place for it, and what is planned. On this route one kind of record carries across, three kinds need mapping, eight kinds have no place in Google Drive and are archived and one kind is confirmed in the analysis.
| Record | What is planned | ||
|---|---|---|---|
| MattersMatters or cases, with their numbers, types, parties and status | HeldMatters are the central record, with stage, status and a closed flag. | No placeA matter is a folder inside a shared drive. | Kept as a readable archive |
| ContactsClients, other parties and referrers | HeldSalesforce accounts and contacts, linked to matters as participants with roles. | No placeContacts belong in Google Contacts, not Drive. | Kept as a readable archive |
| DocumentsFiles stored in or linked from the system | HeldSalesforce files on the matter, or a linked NetDocuments, iManage, SharePoint or Google Drive store. | Has a placeAny file type, stored as uploaded or converted to Google formats. | Carried across |
| EmailsEmails saved to matters or to the store | Held in partEmails sent from a matter are logged. Mailbox filing depends on an email integration. | Has a place in partAs .eml or .msg files in the matter folder; not as Gmail messages. | Carried with mapping |
| NotesFile notes, matter notes and contact notes | HeldComments recorded against the matter. | Has a place in partAs a Doc or Word file in the matter’s folder. | Carried with mapping |
| CalendarAppointments, court dates and deadlines | HeldA Matter Calendar, with date calculation rules. | No placeCalendar entries belong in Google Calendar. | Kept as a readable archive |
| TasksTo-dos and workflow steps assigned to people | HeldActivity plans and task checklists generate tasks on a matter. | No place | Kept as a readable archive |
| Time and expensesTime and expense entries, billed and unbilled | HeldTime entries with timekeepers, rate groups and UTBMS codes. Expenses are tracked too. | No place | Kept as a readable archive |
| BillingInvoices, payments and debtor balances | Held in partTime, expenses and fees become billings, split between billing parties. | No place | Kept as a readable archive |
| Trust moneyTrust or client account ledgers and balances | To be confirmed | No place | Confirmed in the analysis |
| Custom fieldsFields and record types the firm added itself | HeldCustom fields are added to matters and participants through Salesforce set-up. | No place | Kept as a readable archive |
| TemplatesPrecedents, document templates and automation | HeldAdvoDoc document assembly templates. A HotDocs integration is also listed. | Has a place in partPrecedents load as files; the load does not rebuild Word automation in Docs. | Carried with mapping |
| IntakeLeads, enquiries, intake forms and pipelines | HeldIntake records and intake forms, converted to matters. | No place | Kept as a readable archive |
What the plans mean
- Carried across
- Google Drive has a place for this kind of record. It is loaded there and checked against AdvoLogix.
- Carried with mapping
- Google Drive 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.
- Kept as a readable archive
- Google Drive has no place for it. It is exported in a format that opens without AdvoLogix and handed to the firm as a read-only archive.
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
Out of the system, into folders the firm can read.
File storage has folders and files and nothing else. Moving from AdvoLogix into Google Drive means turning matters into a folder tree, usually client, then matter, then the folders used inside it. The naming rule is agreed first, because it is hard to change once thousands of folders exist: whether the matter number leads, how closed matters are separated, what happens to characters Google Drive does not allow in a name.
Everything that is not a document needs somewhere to go. Contacts, notes, time, invoices and trust ledgers have no place in a folder, so they are exported as spreadsheets and reports and stored alongside, often as a summary file in each matter folder and a full set in an archive area. Firms choose this route to keep a readable copy of a system they are retiring, or as a staging step. The export is checked either way: folders against matters, files against the document register in AdvoLogix.
Both are hosted by their makers, so nothing is collected from the firm’s office. What can be taken out of AdvoLogix 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 AdvoLogix is kept running until the checks on Google Drive are finished.
Where the data is now
Leaving AdvoLogix
A move off AdvoLogix is a move out of a Salesforce org. The matter data is spread across the vendor’s packaged objects, standard Salesforce objects and whatever the firm’s administrator added over the years. An inventory of that org comes first: which objects hold live data, which fields are the firm’s own, and where the documents physically are.
Participants carry the relationships
A client, an opposing party or an expert is a Salesforce account or contact joined to the matter by a participant record with a role. Some participants are typed in as free text with no contact behind them. Both kinds are extracted, and the free-text ones are matched to real contacts or created as new ones before loading.
Documents may sit elsewhere
Files can be held as Salesforce files on the matter, or in NetDocuments, iManage, SharePoint or Google Drive through an integration. Many orgs have a mix, with older matters in one place and newer ones in another. Each matter is checked for where its files are before any document count is agreed.
Billings are derived records
Time and expense entries generate billing records, which can be split between billing parties and edited without changing the source entry. The two can therefore disagree by design. Which one is the record of truth for unbilled work is decided in the analysis, and totals are reconciled per matter against that choice.
Every org is configured differently
Matter stages, statuses, page layouts and automation are set by each firm’s Salesforce administrator. Two firms on the same product rarely share a field list. The mapping is written from the firm’s own org, including fields nobody remembers adding, and unused ones are listed for the firm to drop.
Where the books are kept
The help centre describes no ledger inside the matter application. An integration with Accounting Seed, a separate Salesforce application with its own objects, is offered for firms that keep their books on the platform. If the destination has built-in accounting, opening balances are taken from wherever the books were actually kept, not from the matter records.
Where it is going
Arriving in Google Drive
Putting a firm’s matter files into Google Drive means choosing shared drives over personal ones and then deciding how many shared drives there should be. That second decision is driven by Google’s limits and by who is allowed to see what, since access is granted mainly at the level of the whole shared drive.
Shared drives, not My Drive
Files loaded into a shared drive belong to the firm and remain when the person who loaded them leaves. Anything loaded into someone’s My Drive belongs to that person. Matter files therefore go to shared drives, and My Drive is left for personal working papers.
One drive cannot hold everything
Google caps a shared drive at 500,000 items, counting folders, shortcuts and anything in the trash, and at 100 levels of nested folders. A firm with twenty years of matters can pass the item cap in a single drive. The split is planned up front, commonly by practice group, or by open and closed matters.
Membership is the main control
Every member of a shared drive can see all of it unless a Manager restricts a particular folder. Matters that only certain people may open are simpler to protect in a shared drive of their own. The firm supplies the list of restricted matters and partners’ private folders before the drives are created.
The daily upload limit
Each user can upload 750 GB to Drive in 24 hours, and then has to wait. For a large document set that limit sets the shortest time the load can take. The total size is measured in the analysis, so the firm knows before the freeze whether its documents fit inside a weekend.
Keep Office files as Office files
Word and Excel files can be stored in Drive as they are or converted to Google formats. Unless the firm asks otherwise they are loaded unconverted, so court documents and automated precedents arrive as they left. The firm decides afterwards which templates are worth rebuilding as Google Docs.
How NewLaw runs it
Four steps, in this order.
Nothing financial lands in Google Drive on this route, which makes it repeatable: a load can be run again until it is right.
Analysis
We read what AdvoLogix holds and how it is organised, then agree with you where each kind of record will sit in Google Drive. 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 Google Drive and checked against AdvoLogix: 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 AdvoLogix, a final pass over a weekend picks up what changed since the trial. AdvoLogix 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 AdvoLogix 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 AdvoLogix holds
What is in it, how its records link, and where each piece would sit in Google Drive. 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
Structure, permissions and handover
Google Drive is storage, not an application, so there is no product to configure. What is agreed and set up is the folder structure, who can open what, and how the result is handed to the firm.
A Drive set-up for a law firm is a small number of deliberate choices made in the Workspace Admin console and then left alone. Which shared drives exist, who manages each, whether staff may share outside the firm, and whether people work from the browser or from Drive for desktop. Staff also need to be shown where a new matter folder goes.
What is agreed and set up
- Shared drives by practice group, with a naming pattern
- Managers and member access levels for each shared drive
- External sharing rules set in the Admin console
- Drive for desktop on PCs that need Explorer access
- A standard subfolder set copied into every new matter
- Transfer of leavers’ My Drive files as a standing procedure
Questions
AdvoLogix to Google Drive: what firms ask
Is AdvoLogix the same thing as Mitratech CaseCloud?
For practical purposes, yes. Mitratech introduced CaseCloud in November 2024 and describes it as built on Salesforce and AdvoLogix technologies. The help centre and many of the component names still say AdvoLogix. A firm that installed the product under the old name is holding the same kind of data in the same kind of org.
Do we lose our Salesforce history if we leave?
Salesforce keeps field history only where tracking was switched on, so what exists varies by org. Emails, tasks and events logged on a matter can be extracted with it. Field-level change history usually has no equivalent in a legal system, and it either comes across as a note or stays behind.
Can our time entries and rates come across?
Time entries, timekeepers and UTBMS codes are structured records with fields of their own. Rates are harder, because they are held in rate groups applied to matters and can be changed on a single matter. The analysis lists the rate that actually applied to each matter, so unbilled time is valued the same way after the move.
Do trust balances in AdvoLogix have a place in Google Drive?
That is confirmed in the analysis. We could not establish it from the two products’ own material, so it is checked against your data in AdvoLogix before the plan is fixed. If Google Drive turns out to have no place for trust ledgers, they are kept as a readable archive and the firm decides where trust accounting runs.
What happens to records Google Drive has no place for?
On this route that is matters, contacts, calendar entries, tasks, time entries, billing records, custom fields and intake records. They are exported from AdvoLogix in formats that open without it, spreadsheets and PDFs, and handed to the firm as a read-only archive. You see the list before the move.
What has to be decided before AdvoLogix data is loaded into Google Drive?
Emails, notes and templates are carried with mapping, so each mapping is agreed with you first. Trust ledgers 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 AdvoLogix and into Google Drive
Other destinations from AdvoLogix
Other systems that move into Google Drive
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.
AdvoLogix and Google Drive are the names and marks of their owners, used here only to identify the two systems.
Moving from AdvoLogix to Google Drive?
Tell us what you are moving. You get a plan and a fixed price after the analysis.
We reply within one business day.