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

Data migration route

Trialworks to Lawmatics migration

Trialworks is a server-based case management system for personal injury work, and Lawmatics is a cloud CRM and intake system. This route carries people and their history into Lawmatics, and the table shows how much of the firm’s files and money has a place there.

FromTrialworksServer
  1. Matters: Carried across
  2. Contacts: Carried across
  3. Notes: Carried across
  4. Calendar: Carried across
  5. Tasks: Carried across
  6. Intake: Carried across
  7. Documents: Carried with mapping
  8. Emails: Carried with mapping
  9. Templates: Carried 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
ToLawmaticsCloud
  • 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 Lawmatics

Each row is a kind of record Trialworks holds, whether Lawmatics 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 Lawmatics
RecordIn TrialworksIn LawmaticsWhat 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 placeLoaded from CSV with a status of PNC, Hired or Lost and a pipeline stage.Carried across
ContactsClients, other parties and referrersHeldContacts and related contacts, with an option to bring contacts in from Outlook.Has a placeContacts and companies load from CSV; relationships link further parties to a matter.Carried across
DocumentsFiles stored in or linked from the systemHeldFiles in the case folder on the server share, linked from the case.Has a place in partFiles and folders on each matter, added by upload or API, not by the spreadsheet import.Carried 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 partEmails reach a matter through mail sync from a connected mailbox.Carried with mapping
NotesFile notes, matter notes and contact notesHeldQuick Notes and a History tab.Has a placeNotes on matters, contacts and companies.Carried across
CalendarAppointments, court dates and deadlinesHeldDocket entries, which can be sent to Outlook.Has a placeAppointments, called events, with types and locations.Carried across
TasksTo-dos and workflow steps assigned to peopleHeld in partDocket entries double as reminders.Has a placeCarried across
Time and expensesTime and expense entries, billed and unbilledTo be confirmedHas a place in partTime entries and expenses, where the Time & Billing module is enabled.Confirmed in the analysis
BillingInvoices, payments and debtor balancesTo be confirmedHas a place in partInvoices and payments; a past invoice is entered as sent, then marked paid.Confirmed in the analysis
Trust moneyTrust or client account ledgers and balancesTo be confirmedHas a place in partA trust account with a running balance; deposits are allocated to a contact and matter.Confirmed in the analysis
Firm accountsGeneral ledger, office account and payablesTo be confirmedNo placeNo general ledger.Confirmed in the analysis
Custom fieldsFields and record types the firm added itselfTo be confirmedHas a placeMatter, contact and company fields. A field must exist before data is imported into it.Confirmed in the analysis
TemplatesPrecedents, document templates and automationHeldDocument templates generated through Word or WordPerfect.Has a place in partDocument and email templates are rebuilt with Lawmatics merge fields.Carried with mapping
IntakeLeads, enquiries, intake forms and pipelinesHeldAn Intakes tab, and a web intake option.Has a placePipelines and stages, marketing sources and campaigns.Carried across

What the plans mean

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

People and history move. Files and accounts stay.

A CRM wants to know who the firm knows and what has passed between them. From Trialworks that means contacts, their roles, their matters as a history of work done, and the referrers who sent them. Loaded into Lawmatics, a past client becomes someone the firm can contact again with that history in view. That is usually the reason for this route: the firm is adding an intake and marketing system beside its matter system, or replacing the front end of it.

A CRM is not usually where documents, time, billing and trust are kept, and the table above shows what Lawmatics takes. What it does not take stays in Trialworks or its successor. So the plan has to say which system is the master for a contact once both are running, or the two lists drift apart. Contacts are de-duplicated before the load, and anyone who has asked not to be contacted is flagged in Lawmatics from the first day.

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

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

Lawmatics takes matters, contacts and companies from CSV files, and its API accepts notes, tasks, appointments, files, time entries and invoices. It is an intake and client relationship system, so a firm arriving from full practice management has to decide what it is for. People and matters load well. There is no general ledger, and years of billing history have no natural home.

  1. Contacts and matters load separately

    The import expects two spreadsheets: one for contacts or companies with no case, such as referrers and other lawyers, and one for matters. A matter import creates the matter and its primary contact together. Every matter has exactly one primary contact, so joint clients are loaded as one primary and one relationship.

  2. Set up before loading

    Owner, stage, practice area, source and campaign are matched by name. A value on the spreadsheet that does not match one in Lawmatics exactly creates a new one, which is how a firm ends up with two spellings of the same practice area. Users, pipelines, practice areas and marketing sources are set up first, and custom fields must exist before data is loaded into them.

  3. Statuses and matter numbers

    Each imported matter must be PNC (potential new client), Hired or Lost, with open and closed handled as sub-statuses the firm creates. The case number is a system field assigned by an auto-numbering pattern and cannot be edited by hand afterwards. Whether old matter numbers can be loaded into it, or belong in a custom field, is tested in the trial load.

  4. Duplicates are matched by email

    With Match Contacts by Email switched on, a contact whose email already exists is skipped or updated, never doubled. Names and phone numbers are not checked. Matters are not deduplicated at all, so two rows with one email create two matters on one contact. Clean-up therefore happens in the spreadsheet, and automations are switched off for every load.

  5. What has no place

    There is no general ledger. The Time & Billing module holds time entries, expenses, invoices and a trust account with a running balance per matter, and past invoices are entered as already sent and then marked paid. A firm that needs its full accounting history keeps the old system read only or carries the books in an accounting package.

More about moving into Lawmatics

How NewLaw runs it

Four steps, in this order.

No financial cutover is planned on this route, so a load can be run again until it is right. If the analysis finds financial records with a place in Lawmatics, they get a rehearsed cutover of their own.

  1. Analysis

    We read what Trialworks holds and how it is organised, then agree with you where each kind of record will sit in Lawmatics. 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 Lawmatics 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

    After a short freeze on changes in Trialworks, a final pass over a weekend picks up what changed since the trial. If the analysis found financial records to move, their cutover is rehearsed on a full trial load first. 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 toLawmatics

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

Setting up Lawmatics

Loaded data is not yet a working system. This is what NewLaw sets up in Lawmatics, beyond the migration, so that people can work in it from the first day.

In Lawmatics the design comes before the data. The pipeline stages, practice areas, custom fields and relationship types decide what the import can hold, and the forms and automations decide what the firm’s intake looks like from the first day. If a practice system sits behind it, the field mapping between the two is part of the same job.

Set-up decisions in Lawmatics

  • Pipelines and stages for intake and for open matters
  • Practice areas, sub-statuses, relationship types and the matter numbering pattern
  • Custom fields on matters, contacts and companies
  • Intake forms, booking links and e-signature document templates
  • Follow-up automations, with marketing sources and campaigns
  • Mail and calendar sync, user roles and practice system integration

Questions

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

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 Lawmatics turns out to have no place for trust ledgers, they are kept as a readable archive and the firm decides where trust accounting runs.

Does everything in Trialworks have a place in Lawmatics?

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 Lawmatics is kept as a readable archive, and you see which before the move.

What has to be decided before Trialworks data is loaded into Lawmatics?

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

Moving from Trialworks to Lawmatics?

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

We reply within one business day.