Skip to content
NEWLAW.COM
+61 1300 495 281
Let’s talk

Data migration route

Trialworks to Server drives migration

Trialworks is a server-based case management system for personal injury work, and Server drives are plain files on equipment the firm controls. Documents move into a folder for each client and matter, and the data behind them is kept as an export.

FromTrialworksServer
  1. Documents: Carried across
  2. Emails: Carried with mapping
  3. Notes: Carried with mapping
  4. Templates: Carried with mapping
  5. Time and expenses: Confirmed in the analysis
  6. Billing: Confirmed in the analysis
  7. Trust money: Confirmed in the analysis
  8. Firm accounts: Confirmed in the analysis
  9. Custom fields: Confirmed in the analysis
ToServer drivesFiles
  1. Matters: Kept as a readable archive
  2. Contacts: Kept as a readable archive
  3. Calendar: Kept as a readable archive
  4. Tasks: Kept as a readable archive
  5. Intake: Kept as a readable archive
Readable archiveNo place in Server drives
  • 1 carried
  • 3 mapped
  • 5 to confirm
  • 5 archived
What the two products hold. The analysis confirms it field by field.

What moves

What moves from Trialworks to Server drives

Each row is a kind of record Trialworks holds, whether Server drives have 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 Server drives and are archived and five kinds are confirmed in the analysis.

Records in Trialworks and their place in Server drives
RecordIn TrialworksIn Server drivesWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldCases laid out in tabs, with case types, categories and status codes.No placeA matter becomes a folder; its details survive only in an index file.Kept as a readable archive
ContactsClients, other parties and referrersHeldContacts and related contacts, with an option to bring contacts in from Outlook.No placeCan be kept only as an exported spreadsheet.Kept as a readable archive
DocumentsFiles stored in or linked from the systemHeldFiles in the case folder on the server share, linked from the case.Has a placeFiles in folders, named and dated during the load.Carried across
EmailsEmails saved to matters or to the storeHeld in partOutlook integration, with a FileIT tool for filing to a case.Has a place in partAs .msg or .eml files in each matter’s correspondence folder.Carried with mapping
NotesFile notes, matter notes and contact notesHeldQuick Notes and a History tab.Has a place in partAs a text or PDF file per matter, not as separate records.Carried with mapping
CalendarAppointments, court dates and deadlinesHeldDocket entries, which can be sent to Outlook.No placeKept as a readable archive
TasksTo-dos and workflow steps assigned to peopleHeld in partDocket entries double as reminders.No placeKept as a readable archive
Time and expensesTime and expense entries, billed and unbilledTo be confirmedNo placeOnly as exported reports or spreadsheets.Confirmed in the analysis
BillingInvoices, payments and debtor balancesTo be confirmedHas a place in partInvoices as PDF files; no ledger.Confirmed in the analysis
Trust moneyTrust or client account ledgers and balancesTo be confirmedNo placeOnly as exported ledger reports kept as files.Confirmed in the analysis
Firm accountsGeneral ledger, office account and payablesTo be confirmedNo placeConfirmed in the analysis
Custom fieldsFields and record types the firm added itselfTo be confirmedNo placeConfirmed in the analysis
TemplatesPrecedents, document templates and automationHeldDocument templates generated through Word or WordPerfect.Has a place in partPrecedents as Word files; merge fields tied to the old system stop working.Carried with mapping
IntakeLeads, enquiries, intake forms and pipelinesHeldAn Intakes tab, and a web intake option.No placeKept as a readable archive

What the plans mean

Carried across
Server drives has a place for this kind of record. It is loaded there and checked against Trialworks.
Carried with mapping
Server drives 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
Server drives 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 Server drives 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 Server drives do 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.

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 Server drives has been checked.

Where the data is now

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.

  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. 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.

More about moving off Trialworks

Where it is going

Some firms leave a practice or document system and keep their documents on a server drive, either as the working store or as the archive of a system being switched off. The files will arrive without the database that described them. Everything the firm wants to keep knowing about a document has to be put into its path, its name or an index file.

  1. Agree the tree and the names

    A fixed pattern is chosen, for example client name and number, then matter number and short description, then a standard set of subfolders. Document titles from the old system become file names. Where two documents share a title, a date or sequence number is added so nothing is overwritten.

  2. Budget the path length

    Share name, client, matter, subfolder and file name all count towards the 260 character limit that many Windows programs still apply. The pattern is tested against the firm’s longest client names and document titles before the load. Descriptions are trimmed by rule, never by cutting off the file extension.

  3. Dates have to be set deliberately

    A file written to the server today is dated today unless its modified date is set from the old system’s record. Document dates are how lawyers find things in a folder. Which date each file is to carry is agreed in the analysis, and the trial load checks a sample.

  4. Emails become message files

    Emails filed to matters in the old system are written out as .msg or .eml files in a correspondence folder, named by date, sender and subject so they sort in order. Attachments stay inside the message. Subjects with characters Windows forbids are cleaned, and long ones cut.

  5. Keep an index beside the files

    A spreadsheet or small database listing every document with its matter, author, original date, document type and new path is the only place the old system’s profile data survives. It lets someone find a document by something other than its name. What the index records, and who keeps it, is decided in the analysis.

More about moving into Server drives

How NewLaw runs it

Four steps, in this order.

Nothing financial lands in Server drives on this route, which makes it repeatable: a load can be run again until it is right.

  1. Analysis

    We read what Trialworks holds and how it is organised, then agree with you where each kind of record will sit in Server drives. Anything with no place there stays behind or is archived, and you see which before the move.

  2. 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.

  3. Trial load

    A trial is loaded into Server drives 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.

  4. 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

Step 1 of 5: Start with the route

Moving fromTrialworks
Moving toServer drives

The route comes from this page. Four short steps follow. Nothing you send commits your firm to anything.

What happens after you send it

  1. A free first call

    We go through your answers with you and ask about anything they leave open.

  2. An analysis of what Trialworks holds

    What is in it, how its records link, and where each piece would sit in Server drives. Anything with no place there comes across as a note or stays behind, and you see which before the move.

  3. 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

Server drives are 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 server drive does only what the firm and its IT provider make it do. Setting one up as a document store means building the share, deciding who can open which folders, and arranging the protections a document system would have supplied: backups, earlier versions and a way to recover a deleted folder. The filing rule is written down and taught.

What is agreed and set up

  • Share and top-level folders for clients, precedents and administration
  • Security groups and folder permissions, with restricted matters separate
  • Drive letter mapped for every user at sign-in
  • Backup schedule and shadow copies for earlier versions
  • Written naming rule for client, matter and document names
  • Read-only area for closed matters and archived system exports

Questions

Trialworks to Server drives: 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 Server drives?

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 Server drives 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 Server drives have 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 Server drives?

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.

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.

How we do itDiscovery to rollout, step by step

Trialworks and Server drives are the names and marks of their owners, used here only to identify the two systems.

Moving from Trialworks to Server drives?

Tell us what you are moving. You get a plan and a fixed price after the analysis.

We reply within one business day.