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

Data migration route

Trialworks data to Microsoft SQL Server

Trialworks is a server-based case management system for personal injury work, and Microsoft SQL Server is a database on a server the firm runs. 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.

FromTrialworksServer
  1. Matters: Exported in full
  2. Contacts: Exported in full
  3. Notes: Exported in full
  4. Calendar: Exported in full
  5. Tasks: Exported in full
  6. Intake: Exported in full
  7. Documents: Exported with mapping
  8. Emails: Exported with mapping
  9. Templates: Exported with mapping
  10. Time and expenses: Confirmed in the analysis
  11. Billing: Confirmed in the analysis
  12. Trust money: Confirmed in the analysis
  13. Firm accounts: Confirmed in the analysis
  14. Custom fields: Confirmed in the analysis
ToMicrosoft SQL ServerServer
  • 6 carried
  • 3 mapped
  • 5 to confirm
What the two products hold. The analysis confirms it field by field.

What moves

What moves from Trialworks to Microsoft SQL Server

Each row is a kind of record Trialworks holds, whether Microsoft SQL Server has a place for it, and what is planned. On this route six kinds of record carry across, three kinds need mapping and five kinds are confirmed in the analysis.

Records in Trialworks and their place in Microsoft SQL Server
RecordIn TrialworksIn Microsoft SQL ServerWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldCases laid out in tabs, with case types, categories and status codes.Has a placeA table of matters linked to clients, parties and fee earners.Exported in full
ContactsClients, other parties and referrersHeldContacts and related contacts, with an option to bring contacts in from Outlook.Has a placePeople and companies, with their roles on each matter.Exported in full
DocumentsFiles stored in or linked from the systemHeldFiles in the case folder on the server share, linked from the case.Has a place in partAs files in folders with an index table; storing files in the database is possible.Exported with mapping
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 message files with an index table, or as rows of header fields.Exported with mapping
NotesFile notes, matter notes and contact notesHeldQuick Notes and a History tab.Has a placeRows of text linked to matters and contacts.Exported in full
CalendarAppointments, court dates and deadlinesHeldDocket entries, which can be sent to Outlook.Has a placeRows of appointments and key dates; nothing displays them as a calendar.Exported in full
TasksTo-dos and workflow steps assigned to peopleHeld in partDocket entries double as reminders.Has a placeRows with assignee, due date and status.Exported in full
Time and expensesTime and expense entries, billed and unbilledTo be confirmedHas a placeTime and expense rows with rates and billed status.Confirmed in the analysis
BillingInvoices, payments and debtor balancesTo be confirmedHas a placeInvoices, lines and receipts as rows; invoice PDFs kept as files.Confirmed in the analysis
Trust moneyTrust or client account ledgers and balancesTo be confirmedHas a placeTransactions and balances for look-up; it is not a trust accounting system.Confirmed in the analysis
Firm accountsGeneral ledger, office account and payablesTo be confirmedHas a placeGeneral ledger journals and balances, where the source held them.Confirmed in the analysis
Custom fieldsFields and record types the firm added itselfTo be confirmedHas a placeAs added columns, or a table of field names and values.Confirmed in the analysis
TemplatesPrecedents, document templates and automationHeldDocument templates generated through Word or WordPerfect.Has a place in partPrecedent files can be stored; automation does not run here.Exported with mapping
IntakeLeads, enquiries, intake forms and pipelinesHeldAn Intakes tab, and a web intake option.Has a placeEnquiry rows, where the source recorded them.Exported in full

What the plans mean

Exported in full
Microsoft SQL Server has a place for this kind of record. It is loaded there and checked against Trialworks.
Exported with mapping
Microsoft SQL Server 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.

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 Microsoft SQL Server 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 Microsoft SQL Server 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

There are two ways to put a retired system into SQL Server, and they suit different firms. The old system’s own database can be restored as it is. Or the data can be loaded into a new set of tables designed to be read by people. The first is quicker and harder to use. Which suits is worked out in the analysis, and the choice is the firm’s.

  1. Restored copy or rebuilt schema

    Where the old practice system already kept its data in SQL Server, a backup can be restored onto a new server. The tables keep the vendor’s names and codes, which can be cryptic, and reading them takes someone who knows that product’s database. A rebuilt schema uses plain names such as Matter and TrustTransaction.

  2. No screens come with it

    A database has no matter screen. Someone has to ask it questions in SQL or through a reporting tool. Saved views can be set up for the things the firm will really look up: a matter with its parties, its ledger, its time entries and its list of documents. Which are worth having is agreed in the analysis.

  3. Documents sit beside the database

    Files are normally kept in folders on the same server, with a table recording each document’s matter, title, dates and path. Storing the files inside the database is possible but makes it far larger. On the Express edition, the cap on database size rules that out for most firms’ document stores.

  4. The edition follows the size

    A firm’s tables may fit within the Express limit once documents are kept outside the database. A long trust and time history at a larger firm may not. The size of the source data is measured in the analysis, and the edition is chosen from that figure with the firm’s IT provider.

  5. Backups and a test restore

    An archive that is never backed up is one disk failure from gone. Backups belong to the firm’s IT provider: a full one once the load is finished, and a schedule if anything is still being added. It is worth restoring one to a second machine as a test, because a backup that has never been restored is only a hope.

More about moving into Microsoft SQL Server

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.

  1. Analysis

    We read what Trialworks holds, table by table, and agree with you what the copy in Microsoft SQL Server must be able to answer later. Everything Trialworks holds is in scope unless you take it out.

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

  3. Trial export

    The data is written to Microsoft SQL Server 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.

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

Step 1 of 5: Start with the route

Moving fromTrialworks
Moving toMicrosoft SQL Server

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 Microsoft SQL Server. 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

Microsoft SQL Server 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.

Standing up SQL Server as an archive is IT work shared with the firm’s provider. A server or instance is chosen, logins are created for the few people who need to read the data, and nobody is given rights to change it. Views and a handful of reports are built for the common questions, and the IT provider owns the backup routine.

What is agreed and set up

  • Server, instance and edition agreed with the IT provider
  • Read-only logins and roles for named staff
  • Views for matter, ledger, time and document look-ups
  • Backup schedule and who tests a restore
  • Plain names and descriptions for tables and columns
  • Excel or Power BI connected for reporting

Questions

Trialworks to Microsoft SQL Server: 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 Microsoft SQL Server 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.

Does everything in Trialworks have a place in Microsoft SQL Server?

Most of it does on paper. Time entries, billing records, trust ledgers, the firm’s accounts and custom fields could not be confirmed from the two products’ own material, so those are checked in the analysis. Anything that turns out to have no place in Microsoft SQL Server is kept as a readable archive, and you see which before the move.

What has to be decided before Trialworks is written out to Microsoft SQL Server?

Documents, emails and templates 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.

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 Microsoft SQL Server are the names and marks of their owners, used here only to identify the two systems.

Moving from Trialworks to Microsoft SQL Server?

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

We reply within one business day.