Data migration route
Trialworks to Google Drive migration
Trialworks is a server-based case management system for personal injury work, 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.
TrialworksServer- Documents: Carried across
- Emails: Carried with mapping
- Notes: Carried with mapping
- Templates: Carried with mapping
- Time and expenses: Confirmed in the analysis
- Billing: Confirmed in the analysis
- Trust money: Confirmed in the analysis
- Firm accounts: Confirmed in the analysis
- Custom fields: 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
- Intake: Kept as a readable archive
- 1 carried
- 3 mapped
- 5 to confirm
- 5 archived
What moves
What moves from Trialworks to Google Drive
Each row is a kind of record Trialworks 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, five kinds have no place in Google Drive and are archived and five kinds are confirmed in the analysis.
| Record | What is planned | ||
|---|---|---|---|
| MattersMatters or cases, with their numbers, types, parties and status | HeldCases laid out in tabs, with case types, categories and status codes. | No placeA matter is a folder inside a shared drive. | Kept as a readable archive |
| ContactsClients, other parties and referrers | HeldContacts and related contacts, with an option to bring contacts in from Outlook. | No placeContacts belong in Google Contacts, not Drive. | Kept as a readable archive |
| DocumentsFiles stored in or linked from the system | HeldFiles in the case folder on the server share, linked from the case. | 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 partOutlook integration, with a FileIT tool for filing to a case. | 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 | HeldQuick Notes and a History tab. | Has a place in partAs a Doc or Word file in the matter’s folder. | Carried with mapping |
| CalendarAppointments, court dates and deadlines | HeldDocket entries, which can be sent to Outlook. | No placeCalendar entries belong in Google Calendar. | Kept as a readable archive |
| TasksTo-dos and workflow steps assigned to people | Held in partDocket entries double as reminders. | No place | Kept as a readable archive |
| Time and expensesTime and expense entries, billed and unbilled | To be confirmed | No place | Confirmed in the analysis |
| BillingInvoices, payments and debtor balances | To be confirmed | No place | Confirmed in the analysis |
| Trust moneyTrust or client account ledgers and balances | To be confirmed | No place | Confirmed in the analysis |
| Firm accountsGeneral ledger, office account and payables | To be confirmed | No place | Confirmed in the analysis |
| Custom fieldsFields and record types the firm added itself | To be confirmed | No place | Confirmed in the analysis |
| TemplatesPrecedents, document templates and automation | HeldDocument templates generated through Word or WordPerfect. | 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 | HeldAn Intakes tab, and a web intake option. | 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 Trialworks.
- 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 Trialworks 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 Trialworks 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 Trialworks.
Trialworks runs on the firm’s own equipment, so the data is collected there: a copy of the database and the folders its documents sit in, taken with the firm’s IT provider or over a remote session. Google Drive is hosted by its maker, so loading depends on the import tools and access it provides. The old machine is kept, read only, as the fall-back record.
Where the data is now
Leaving Trialworks
Trialworks stores a firm’s cases in SQL Server and its documents in Windows folders, and the two are read together. The tab layout is consistent from firm to firm, which helps. Risk sits in the folders, where years of files may or may not be linked to the case, and in docket entries that live partly in Outlook.
SQL Server plus a file share
Case records are in a Microsoft SQL Server database and documents are files on the Trialworks share, organised by case. A backup of one without the other is half a system. Both are captured together, and the share is scanned for files that sit in a case folder but are not linked to the case record.
Medical and Cost tabs
Treatment information is entered on the Medical tab and case expenses on the Cost tab, with invoices and cheque copies attached. In the destination those become provider records, bills and disbursements. Totals per case are compared after the trial load, and attached invoices are filed with the cost they support.
Docket entries and Outlook
Deadlines and reminders are docket entries, and many firms send them to Outlook calendars. An entry can have several people assigned. The destination’s calendar and task list are loaded from the docket, not from Outlook, so that completed and past-due entries are marked correctly and nothing is duplicated.
Libraries of codes
Case types, categories, status and priority codes, contact types, docket activities, client roles and divisions are all lists the firm maintains. They collect misspellings and entries nobody uses. The lists are cleaned in Trialworks before extraction where possible, because every stray code becomes a stray option in the new system’s dropdowns.
Settlement and negotiation history
Negotiations have their own tab, settlement information records amounts and payments, and fee and referral percentages are kept on the case. Those figures decide what the firm is owed. They are mapped as data, and each settled case is checked against its closing statement.
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 Trialworks 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 Trialworks: 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 Trialworks, a final pass over a weekend picks up what changed since the trial. Trialworks 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 Trialworks 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 Trialworks 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
Trialworks to Google Drive: what firms ask
Is Trialworks being discontinued?
Assembly Software has stated that it has no plans to end support and that there is no end-of-life date. It has also built Neos as the cloud product that follows Trialworks. A firm can stay, move to Neos or move elsewhere, and the timing is its own decision.
Do documents saved straight into the case folder come across?
Yes, if they are found. Files saved through Trialworks are linked to the case and carry a description. Anything dragged into the folder in Windows has no link. Both are collected. The unlinked ones arrive in the right case with only their file name, and the firm is given a count per case.
What does Neos not take from Trialworks?
Assembly’s own guidance lists a few Case Info fields that do not transfer, including case budget, storage date and case password, and says insurance and medical detail moves to documents on the Case Docs tab. A firm that relies on any of these raises it before conversion, whichever destination it chooses.
Do trust balances in Trialworks 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 Trialworks 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 and intake records. They are exported from Trialworks 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 Trialworks data is loaded into Google Drive?
Emails, notes and templates are carried with mapping, so each mapping is agreed with you first. Time entries, billing records, trust ledgers, the firm’s accounts and custom fields 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 Trialworks and 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.
Trialworks and Google Drive are the names and marks of their owners, used here only to identify the two systems.
Moving from Trialworks 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.