Data migration route
Trialworks data to SQLite
Trialworks is a server-based case management system for personal injury work, and SQLite is a store of data kept as files the firm holds. This is not a move to a new working system: the route writes out what Trialworks holds and keeps it readable and open to queries.
TrialworksServer- Matters: Exported in full
- Contacts: Exported in full
- Notes: Exported in full
- Calendar: Exported in full
- Tasks: Exported in full
- Intake: Exported in full
- Documents: Exported with mapping
- Emails: Exported 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
SQLiteFiles- Templates: Kept as a readable archive
- 6 carried
- 2 mapped
- 5 to confirm
- 1 archived
What moves
What moves from Trialworks to SQLite
Each row is a kind of record Trialworks holds, whether SQLite has a place for it, and what is planned. On this route six kinds of record carry across, two kinds need mapping, one kind has no place in SQLite and is 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. | Has a placeA matters table keyed by matter number. | Exported in full |
| ContactsClients, other parties and referrers | HeldContacts and related contacts, with an option to bring contacts in from Outlook. | Has a placeContacts and their roles on matters as linked tables. | Exported in full |
| DocumentsFiles stored in or linked from the system | HeldFiles in the case folder on the server share, linked from the case. | Has a place in partListed in a table; the files themselves stay in folders beside the database. | Exported with mapping |
| 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 message files in folders, indexed in a table. | Exported with mapping |
| NotesFile notes, matter notes and contact notes | HeldQuick Notes and a History tab. | Has a placeA notes table linked to matters. | Exported in full |
| CalendarAppointments, court dates and deadlines | HeldDocket entries, which can be sent to Outlook. | Has a placeA table of dated entries, with no calendar view. | Exported in full |
| TasksTo-dos and workflow steps assigned to people | Held in partDocket entries double as reminders. | Has a placeA table of tasks and their status at the final date. | Exported in full |
| Time and expensesTime and expense entries, billed and unbilled | To be confirmed | Has a placeA table of time and expense entries. | Confirmed in the analysis |
| BillingInvoices, payments and debtor balances | To be confirmed | Has a placeInvoice and receipt tables; invoice PDFs kept as files. | Confirmed in the analysis |
| Trust moneyTrust or client account ledgers and balances | To be confirmed | Has a placeTrust transactions as rows, for look-up and not for accounting. | Confirmed in the analysis |
| Firm accountsGeneral ledger, office account and payables | To be confirmed | Has a placeLedger journals as rows, where the source held them. | Confirmed in the analysis |
| Custom fieldsFields and record types the firm added itself | To be confirmed | Has a placeColumns added to the table they belonged to. | Confirmed in the analysis |
| TemplatesPrecedents, document templates and automation | HeldDocument templates generated through Word or WordPerfect. | No placePrecedent files are kept in folders, not in the database. | Kept as a readable archive |
| IntakeLeads, enquiries, intake forms and pipelines | HeldAn Intakes tab, and a web intake option. | Has a placeAn enquiries table, where the source tracked them. | Exported in full |
What the plans mean
- Exported in full
- SQLite has a place for this kind of record. It is loaded there and checked against Trialworks.
- Exported with mapping
- SQLite 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
- SQLite 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
Not a new system. A complete copy the firm can query.
Writing Trialworks out to SQLite is not a migration into a new working system. Nobody will open a matter there on Monday morning. The aim is a complete, faithful copy that can be queried and reported on after the old system is gone. So the rules change. Nothing is cleaned or merged unless the firm asks, because an archive should show the records as they were. Every table and field is carried, including those a new system would have had no place for.
What makes an archive usable is the description that goes with it. The export is delivered with a plain account of each table: what it holds, how it joins to the others, what the codes mean. Record counts and financial totals are agreed to the reports in Trialworks as at the export date, so the archive can stand as the record. Documents are exported beside the data with a table linking each file to its matter. Access is restricted, since the archive holds everything the live system did.
Both ends are on equipment the firm controls, so the work is done on the firm’s own network with its IT provider. Disk space for a second full copy is checked first. The original in Trialworks stays untouched until the copy in SQLite has been checked.
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 SQLite
A SQLite archive suits a firm that wants the old system’s records kept, seldom consulted, and free of any server or subscription. Everything structured goes into one file. That simplicity moves the responsibility elsewhere: the file has no security of its own and no administrator watching it, so where it is stored and who can reach it are the real decisions.
One file, kept with the archive
Matters, contacts, time, invoices and trust transactions become tables in a single file. It is stored with the firm’s closed-matter records and can be copied like any document. A checksum recorded when the file is finalised lets anyone confirm, years later, that the copy they hold has not been altered, and the firm decides whether to keep one.
No logins inside the file
SQLite has no users or passwords. Anyone who can open the file can read every client’s ledger. Protection comes from where it is kept, such as a restricted folder or an encrypted volume, and that choice is the firm’s. It can suit an archive consulted by two people, and it is said plainly so nobody assumes otherwise.
Built for reading, not sharing
Only one program can write to the file at a time, and SQLite’s authors point people to a client/server database where many users share data over a network. A finished archive never meets that limit. It is the reason SQLite is used here for records that are closed and not for anything staff still update.
Documents stay outside it
Documents remain ordinary files in matter folders, and a table in the database lists each one with its matter, title, dates and path. Keeping them as files means they open with a double-click and can be handed to a client. The table is how a file is found by matter number instead of by guessing its name.
Someone has to open it
SQLite publishes its own command-line program for opening a database file, and other tools read the format too. None of that helps if nobody remembers how. Saved queries for the usual look-ups and a short note on which tool to use can sit in the same folder as the file, and the firm decides what it needs.
How NewLaw runs it
Four steps, in this order.
This route produces an archive, not a working system, so the steps are about completeness and proof.
Analysis
We read what Trialworks holds, table by table, and agree with you what the copy in SQLite must be able to answer later. Everything Trialworks holds is in scope unless you take it out.
Clean-up, if you want it
An archive should show the records as they were, so nothing is merged or corrected unless you ask. Where the copy is also meant for reporting, duplicate and inconsistent entries are tidied in a working copy and the original values are kept beside them.
Trial export
The data is written to SQLite as a trial and checked against Trialworks: record counts, totals where Trialworks holds money, the links between records, and a sample of documents opened from the export. Exceptions are listed for you to decide.
Final export
After the last day of work in Trialworks, the export is run a final time and checked again. There is nothing to go live. Trialworks is kept read only until you are satisfied the copy answers what you need, and it is handed over with a written description of its contents.
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 SQLite. 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
SQLite is a place to keep data, not a system staff work in each day. What is agreed is how the data is laid out, who can reach it, and what is handed over with it.
There is nothing to install on a server and nothing to license. The work is in making the file usable and safe to keep: naming it, documenting its tables, storing it where the firm’s records policy says archives go, and checking that a member of staff can open it and find a matter. Whether a second copy is held somewhere separate is the firm’s call.
What is agreed and set up
- File name, storage location and whether a second copy exists
- Whether a checksum is recorded for later verification
- Saved queries for matter, ledger and document look-ups
- Which tool staff will use to open the file
- Who may open the folder the file sits in
- Retention period and destruction date noted beside the file
Questions
Trialworks to SQLite: 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.
Does the copy in SQLite hold trust ledgers from Trialworks?
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.
What happens to records SQLite has no place for?
On this route that is templates. 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 is written out to SQLite?
Documents and emails are exported 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 who may open the archive and how long it is kept.
Other routes
Other routes from Trialworks and into SQLite
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 SQLite are the names and marks of their owners, used here only to identify the two systems.
Moving from Trialworks to SQLite?
Tell us what you are moving. You get a plan and a fixed price after the analysis.
We reply within one business day.