Data migration route
LegalServer to SmartAdvocate migration
LegalServer is a cloud case management system for legal aid work. SmartAdvocate is a case management system for personal injury work, run the same way. The records line up case for case, and the detail is in the fields and stages.
LegalServerCloud- Matters: Carried across
- Contacts: Carried across
- Documents: Carried across
- Emails: Carried across
- Notes: Carried across
- Calendar: Carried across
- Tasks: Carried across
- Time and expenses: Carried across
- Intake: Carried across
- 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
SmartAdvocateCloud- 9 carried
- 2 mapped
- 3 to confirm
What moves
What moves from LegalServer to SmartAdvocate
Each row is a kind of record LegalServer holds, whether SmartAdvocate has a place for it, and what is planned. On this route nine kinds of record carry across, two 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 placeCases by case type, with master and member relationships. | Carried across |
| ContactsClients, other parties and referrers | HeldClients and the other people connected with a case. | Has a place | 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 placeDocuments page, by category and subcategory. | Carried across |
| 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 placeEmails are attached to cases. | Carried across |
| NotesFile notes, matter notes and contact notes | HeldCase notes. | Has a place | Carried across |
| CalendarAppointments, court dates and deadlines | HeldAppointments, events, tasks and deadlines; entries can show in Outlook. | Has a placeAppointments and critical deadlines. | 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 placeTracked time entries. | Carried across |
| BillingInvoices, payments and debtor balances | To be confirmedBuilt for free legal services; client invoicing was not confirmed. | Has a place in partInvoices for hourly matters. Past invoices are scoped in the analysis. | Confirmed in the analysis |
| Trust moneyTrust or client account ledgers and balances | To be confirmed | To be confirmed | Confirmed in the analysis |
| Firm accountsGeneral ledger, office account and payables | To be confirmed | To be confirmed | 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 place in partConfirmed in the analysis for each field with no standard home. | Carried with mapping |
| TemplatesPrecedents, document templates and automation | HeldBuilt-in document templates; HotDocs, Docassemble and Gavel are integrations. | Has a place in partTemplates are rebuilt with SmartAdvocate merge codes. | Carried with mapping |
| IntakeLeads, enquiries, intake forms and pipelines | HeldConfigurable client intake, with a poverty level assessment and conflict check. | Has a placeIntake and lead records. | Carried across |
What the plans mean
- Carried across
- SmartAdvocate has a place for this kind of record. It is loaded there and checked against LegalServer.
- Carried with mapping
- SmartAdvocate 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
Case to case, field by field.
Two case management systems look alike from a distance and differ in almost every detail. Each has its own idea of a case type, a stage, a party role and a deadline. LegalServer and SmartAdvocate may both hold a limitation date, yet one calculates it and the other stores what was typed. The mapping goes field by field and status by status, and the trial load is checked by opening real cases in both systems side by side.
Custom fields hold most of what the firm has built up. Years of intake answers, injury details or visa histories sit in fields the firm added itself. Each is matched to a field in SmartAdvocate, and anything unmatched is kept as a note on the case so that it can still be searched. Workflows and document templates are rebuilt in the new system’s own tools. Open tasks come across with their owners and due dates.
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 SmartAdvocate 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 SmartAdvocate
SmartAdvocate keeps injury detail in structured fields and screens, so mapping counts for more than usual: the more precisely the old data is placed, the more of those screens are filled on the first day. Parties, incidents, insurers, providers and bills are loaded to their own screens, and the vendor’s implementation team runs conversions into it.
Map to fields, not notes
The case summary, dashboards and settlement screen read from structured fields. Injury details, insurance limits and provider bills dumped into a note leave those screens empty. The mapping takes each old field to its SmartAdvocate counterpart, and only what truly has no counterpart is loaded as a note.
Case types and statuses
Cases are loaded against case types and statuses that drive WorkPlans and reports. These are agreed with the firm before the trial load, and old statuses are translated to the new list. A status with no match is not guessed at. It is listed, and someone who knows the files decides.
Document categories
Documents are searched by category, subcategory, sender, recipient and date as well as by folder. The old system’s folders are translated into categories on the way in. Files that arrive uncategorised can still be found by description, but they fall outside the category views staff are trained to use.
Working with the vendor’s conversion
SmartAdvocate’s implementation team converts client data into the system and trains staff through its own classes. The firm’s side of that is supplying a clean source, checking the converted cases against the old system, and deciding what to do with the exceptions. Independent help is used on those tasks.
Choosing Server or Cloud
The firm decides before loading whether it will run the Server edition on its own Windows server or use the hosted Cloud edition. Either way the data load is the same. What differs is who looks after backups, updates and remote access afterwards, and that is settled with the firm’s IT provider.
How NewLaw runs it
Four steps, in this order.
Financial records move on this route, so the balances are rehearsed before the real cutover. The maker of SmartAdvocate says that it, or its partners, load firms into the product. Where the firm uses that service, NewLaw’s part is the work around it: the analysis, the clean-up in LegalServer and checking each trial against LegalServer.
Analysis
We read what LegalServer holds and how its records link, then agree with you, field by field, where each piece will sit in SmartAdvocate. 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 SmartAdvocate 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 SmartAdvocate 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 SmartAdvocate. 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 SmartAdvocate
Loaded data is not yet a working system. The maker of SmartAdvocate runs or arranges the set-up of its product, so this is what has to be decided and put in place in SmartAdvocate, whoever does the work, before people rely on it from the first day.
Setting up SmartAdvocate is a matter of deciding how much of its detail the firm will use from the start. Case types, statuses and WorkPlans come first because they drive everything else. Templates follow. The vendor trains staff through its own classes, and the decisions below are best made before the first of those.
Set-up decisions in SmartAdvocate
- Choose the Server or Cloud edition with IT
- Define case types, statuses and staff roles
- Build WorkPlans and Automated Procedures for each case type
- Convert letters and forms into templates with merge codes
- Install the Outlook plugin and agree email filing habits
- Set up intake screens, lead sources and dashboards
Questions
LegalServer to SmartAdvocate: 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 SmartAdvocate?
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 SmartAdvocate 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 SmartAdvocate?
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 SmartAdvocate is kept as a readable archive, and you see which before the move.
What has to be decided before LegalServer data is loaded into SmartAdvocate?
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 SmartAdvocate
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 SmartAdvocate are the names and marks of their owners, used here only to identify the two systems.
Moving from LegalServer to SmartAdvocate?
Tell us what you are moving. You get a plan and a fixed price after the analysis.
We reply within one business day.