Data migration route
LegalServer to Lawmatics migration
LegalServer is a cloud case management system for legal aid 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.
LegalServerCloud- Matters: Carried across
- Contacts: Carried across
- Notes: Carried across
- Calendar: Carried across
- Tasks: Carried across
- Intake: Carried across
- Documents: Carried with mapping
- Emails: Carried with mapping
- Time and expenses: Carried with mapping
- Custom fields: Carried with mapping
- Templates: Carried with mapping
- Billing: Confirmed in the analysis
- Trust money: Confirmed in the analysis
- Firm accounts: Confirmed in the analysis
LawmaticsCloud- 6 carried
- 5 mapped
- 3 to confirm
What moves
What moves from LegalServer to Lawmatics
Each row is a kind of record LegalServer holds, whether Lawmatics has a place for it, and what is planned. On this route six kinds of record carry across, five kinds need mapping and three kinds are confirmed in the analysis.
| Record | What is planned | ||
|---|---|---|---|
| MattersMatters or cases, with their numbers, types, parties and status | HeldCases and matters, with case types configured for each site. | Has a placeLoaded from CSV with a status of PNC, Hired or Lost and a pipeline stage. | Carried across |
| ContactsClients, other parties and referrers | HeldClients and the other people connected with a case. | Has a placeContacts and companies load from CSV; relationships link further parties to a matter. | Carried across |
| DocumentsFiles stored in or linked from the system | HeldStored on the case, or linked from SharePoint, Google Shared Drives or Dropbox. | 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 store | Held in partBuilt-in email, and email sent to a case from Gmail through an integration. | Has a place in partEmails reach a matter through mail sync from a connected mailbox. | Carried with mapping |
| NotesFile notes, matter notes and contact notes | HeldCase notes. | Has a placeNotes on matters, contacts and companies. | Carried across |
| CalendarAppointments, court dates and deadlines | HeldAppointments, events, tasks and deadlines; entries can show in Outlook. | Has a placeAppointments, called events, with types and locations. | Carried across |
| TasksTo-dos and workflow steps assigned to people | Held | Has a place | Carried across |
| Time and expensesTime and expense entries, billed and unbilled | HeldTimekeeping, used for grant and funder reporting. | Has a place in partTime entries and expenses, where the Time & Billing module is enabled. | Carried with mapping |
| BillingInvoices, payments and debtor balances | To be confirmedBuilt for free legal services; client invoicing was not confirmed. | Has 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 balances | To be confirmed | Has 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 payables | To be confirmed | No placeNo general ledger. | Confirmed in the analysis |
| Custom fieldsFields and record types the firm added itself | HeldSites add their own fields, forms and processes without code. | Has a placeMatter, contact and company fields. A field must exist before data is imported into it. | Carried with mapping |
| TemplatesPrecedents, document templates and automation | HeldBuilt-in document templates; HotDocs, Docassemble and Gavel are integrations. | Has a place in partDocument and email templates are rebuilt with Lawmatics merge fields. | Carried with mapping |
| IntakeLeads, enquiries, intake forms and pipelines | HeldConfigurable client intake, with a poverty level assessment and conflict check. | 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 LegalServer.
- 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 LegalServer 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 LegalServer 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.
Both are hosted by their makers, so nothing is collected from the firm’s office. What can be taken out of LegalServer depends on its export tools and on what its maker provides on request, and that is confirmed during the analysis, before a date is set. The subscription to LegalServer is kept running until the checks on Lawmatics are finished.
Where the data is now
Leaving LegalServer
Each agency configures its own intake, case types and fields, so a move off LegalServer starts with that site’s configuration, not with a standard list of tables. The data most at risk is the data a commercial practice system never asks for: eligibility answers, funding codes, outcomes and the time recorded against each grant.
Each site has its own shape
Intake processes, case types and data fields are set up by the agency’s own administrators, often over many years. Two programs on the same product can hold quite different records. The analysis reads this site’s configuration first and lists every field that holds data, including ones no current staff member remembers adding.
Time belongs to funders
Timekeeping exists to show funders what their grant paid for, so entries are tied to grants and funding sources, not to a bill. A practice system records time against a matter for invoicing. The funding link has to be carried as its own field, or grant reports for the period before the move cannot be reproduced.
Documents may live elsewhere
LegalServer can store files itself, or link a case to folders in SharePoint, Google Shared Drives or Dropbox. On a site that uses those integrations the documents are not in the case management system at all. Where the files are is established before anything else, because it decides whether they are moved or simply linked again.
Eligibility and outcome data
Intake assesses a client against the poverty level and runs a conflict check, and outcomes are tracked across cases for reporting. These answers justify the service to an auditor. They are carried as fields where the destination allows, and otherwise as a dated intake summary filed on the case.
Feeds from courts and agencies
Some sites receive court data several times a day, create cases from a county system, or send counselling data to HUD. These connections are part of how the office works. Each is listed with what it sends or receives, and a decision is made on whether it is rebuilt, replaced by manual entry, or retired.
Where it is going
Arriving in Lawmatics
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.
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.
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.
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.
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.
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.
How NewLaw runs it
Four steps, in this order.
Financial records move on this route, so the balances are rehearsed before the real cutover.
Analysis
We read what LegalServer holds and how its records link, then agree with you, field by field, where each piece will sit in Lawmatics. Anything with no place there comes across as a note or stays behind, and you see which before the move.
Clean-up
Duplicate contacts and matters are merged where they can be identified, and inconsistent entries are put into one format, in LegalServer, before extraction. It is not always possible to find every one, so some may carry across.
Trial load
The data is loaded into Lawmatics as a trial and checked against LegalServer: record counts, financial totals, the links between records, document dates. Exceptions are listed for you to decide.
Cutover
Changes in LegalServer are frozen for an agreed window, the data is collected a final time and Lawmatics goes live over a weekend. The financial cutover is rehearsed on a full trial load first, so that opening balances agree with the reports in LegalServer as at the cutover date. LegalServer 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 LegalServer 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 LegalServer 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.
- 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
LegalServer to Lawmatics: what firms ask
Can a commercial practice system hold legal aid data?
It can hold the cases, people, notes, documents and time. It will not have funding codes, eligibility screening or funder reports unless they are built with custom fields and reports. The analysis sets out which of those can be rebuilt in the chosen system and which reporting would have to be done outside it.
What happens to cases closed years ago?
Closed cases matter in legal aid for conflict checks and for funder audits. Bringing every case means a returning client or an adverse party is still found. If older cases are left out, their names should still be loaded for conflict searching, and the full record stays in the read-only copy.
Our documents are in SharePoint, not in LegalServer. Must they move as well?
Not necessarily. If LegalServer only links to SharePoint, the files are already in the program’s own Microsoft 365. They can stay where they are and be linked from the new system, or be moved into it. The choice depends on how the destination stores documents and is made in the analysis.
Do trust balances in LegalServer 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 LegalServer 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 LegalServer have a place in Lawmatics?
Most of it does on paper. Billing records, trust ledgers and the firm’s accounts 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 LegalServer data is loaded into Lawmatics?
Documents, emails, time entries, custom fields and templates are carried with mapping, so each mapping is agreed with you first. Billing records, trust ledgers and the firm’s accounts are confirmed in the analysis. The firm also sets the cutover date and how much financial history comes across as live records.
Other routes
Other routes from LegalServer and into Lawmatics
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.
LegalServer and Lawmatics are the names and marks of their owners, used here only to identify the two systems.
Moving from LegalServer 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.