Data migration route
Gladiate to Lawmatics migration
Gladiate is a cloud 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.
GladiateCloud- Matters: Carried across
- Contacts: Carried across
- Calendar: Carried across
- Tasks: Carried across
- Intake: Carried across
- Documents: Carried with mapping
- Templates: Carried with mapping
- Emails: Confirmed in the analysis
- Notes: Confirmed in the analysis
- Time and expenses: Confirmed in the analysis
- Billing: Confirmed in the analysis
- Trust money: Confirmed in the analysis
- Firm accounts: Confirmed in the analysis
- Custom fields: Confirmed in the analysis
LawmaticsCloud- 5 carried
- 2 mapped
- 7 to confirm
What moves
What moves from Gladiate to Lawmatics
Each row is a kind of record Gladiate holds, whether Lawmatics has a place for it, and what is planned. On this route five kinds of record carry across, two kinds need mapping and seven kinds are confirmed in the analysis.
| Record | What is planned | ||
|---|---|---|---|
| MattersMatters or cases, with their numbers, types, parties and status | HeldPersonal injury cases with coverage, liability and medical data. | 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, leads and referral sources in a built-in CRM. | 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 | HeldFiles in a folder structure the firm defines. E-signature is built in. | 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 | To be confirmed | Has a place in partEmails reach a matter through mail sync from a connected mailbox. | Confirmed in the analysis |
| NotesFile notes, matter notes and contact notes | To be confirmed | Has a placeNotes on matters, contacts and companies. | Confirmed in the analysis |
| CalendarAppointments, court dates and deadlines | HeldTwo-way sync with Microsoft Outlook and Google Calendar. | Has a placeAppointments, called events, with types and locations. | Carried across |
| TasksTo-dos and workflow steps assigned to people | HeldTask lists and task plans. | Has a place | Carried across |
| Time and expensesTime and expense entries, billed and unbilled | To be confirmed | Has a place in partTime entries and expenses, where the Time & Billing module is enabled. | Confirmed in the analysis |
| BillingInvoices, payments and debtor balances | To be 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 | To be confirmed | Has a placeMatter, contact and company fields. A field must exist before data is imported into it. | Confirmed in the analysis |
| TemplatesPrecedents, document templates and automation | HeldThe firm’s own document templates, set up during onboarding. | Has a place in partDocument and email templates are rebuilt with Lawmatics merge fields. | Carried with mapping |
| IntakeLeads, enquiries, intake forms and pipelines | HeldClient sign-up, questionnaires and lead nurturing. | 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 Gladiate.
- 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 Gladiate 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 Gladiate 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 Gladiate 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 Gladiate is kept running until the checks on Lawmatics are finished.
Where the data is now
Leaving Gladiate
Gladiate keeps an injury firm’s cases, client communications and marketing contacts together, so a move off it touches more than the case list. The structured injury data needs a home in the destination. So do the things most case systems lack: survey responses, scheduled client updates and the state of each medical record request.
Medical record request status
Requests to providers for records and bills are generated and followed up inside the product. At any moment a firm has many in flight. The open requests are listed at cutover with provider, date sent and what is outstanding, and loaded as tasks or a tracking list so the chasing carries on.
Surveys and questionnaires
Clients answer questionnaires for the case and surveys about their medical providers and the firm’s service. The answers are client evidence and marketing data at once. Questionnaire answers go to the case as fields or a saved document. Survey results are exported for the firm, as few destinations have a place for them.
Referral sources and past clients
The CRM side holds referral sources, former clients and the marketing campaigns sent to them. If the destination has no marketing module, those contacts still come across with their type and source. Campaign history is exported as a report, and the firm decides whether a separate marketing tool takes over.
Scheduled client updates
Automatic case updates go to clients on a schedule. When the old system is frozen those messages stop, and clients notice. The schedule and wording are recorded before cutover, and either an equivalent is switched on in the new system at go-live or the firm tells clients to expect a gap.
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.
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.
Analysis
We read what Gladiate 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.
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.
Trial load
A trial is loaded into Lawmatics and checked against Gladiate: 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.
Cutover
After a short freeze on changes in Gladiate, 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. Gladiate 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 Gladiate 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 Gladiate 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
Gladiate to Lawmatics: what firms ask
Does Gladiate handle time recording or trust accounting?
The vendor’s public material describes case management, client communication and marketing for injury firms. It does not describe time billing or trust ledgers. A firm that depends on either asks the vendor directly, and the answer decides whether an accounting package runs alongside.
Can we bring our closed cases into Gladiate?
That is confirmed with the vendor during onboarding, because its public pages do not say how history is loaded. The firm decides how far back to go. Former clients are also a marketing list in Gladiate, which is a reason to bring at least the client and the outcome of each closed case.
What do we lose if we move from Gladiate to a general system?
Mostly the client-facing automation: scheduled updates, surveys and the record request process. The case data moves. Those features are rebuilt with the destination’s own tools, replaced by a separate product, or dropped. The firm sees that list before deciding, together with any fields that have no home.
Do trust balances in Gladiate 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 Gladiate 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 Gladiate have a place in Lawmatics?
Most of it does on paper. Emails, notes, 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 Gladiate data is loaded into Lawmatics?
Documents and templates are carried with mapping, so each mapping is agreed with you first. Emails, notes, 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.
Other routes
Other routes from Gladiate 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.
Gladiate and Lawmatics are the names and marks of their owners, used here only to identify the two systems.
Moving from Gladiate 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.