Data migration route
LawCloud to Lawmatics migration
LawCloud is a cloud practice management system, 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.
LawCloudCloud- Matters: Carried across
- Notes: Carried across
- Documents: Carried with mapping
- Emails: Carried with mapping
- Time and expenses: Carried with mapping
- Billing: Carried with mapping
- Trust money: Carried with mapping
- Contacts: Confirmed in the analysis
- Calendar: Confirmed in the analysis
- Tasks: Confirmed in the analysis
- Custom fields: Confirmed in the analysis
- Templates: Confirmed in the analysis
- Intake: Confirmed in the analysis
LawmaticsCloud- Firm accounts: Kept as a readable archive
- 2 carried
- 5 mapped
- 6 to confirm
- 1 archived
What moves
What moves from LawCloud to Lawmatics
Each row is a kind of record LawCloud holds, whether Lawmatics has a place for it, and what is planned. On this route two kinds of record carry across, five kinds need mapping, one kind has no place in Lawmatics and is archived and six kinds are confirmed in the analysis.
| Record | What is planned | ||
|---|---|---|---|
| MattersMatters or cases, with their numbers, types, parties and status | HeldOrganised as cases, with every activity logged to the case record. | Has a placeLoaded from CSV with a status of PNC, Hired or Lost and a pipeline stage. | Carried across |
| ContactsClients, other parties and referrers | To be confirmed | Has a placeContacts and companies load from CSV; relationships link further parties to a matter. | Confirmed in the analysis |
| DocumentsFiles stored in or linked from the system | HeldDocuments are stored and searched within 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 store | HeldEmails are logged to the case record. | 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 | Held in partPhone calls are logged against the case. | Has a placeNotes on matters, contacts and companies. | Carried across |
| CalendarAppointments, court dates and deadlines | To be confirmed | Has a placeAppointments, called events, with types and locations. | Confirmed in the analysis |
| TasksTo-dos and workflow steps assigned to people | To be confirmed | Has a place | Confirmed in the analysis |
| Time and expensesTime and expense entries, billed and unbilled | HeldBuilt-in time recording. | Has a place in partTime entries and expenses, where the Time & Billing module is enabled. | Carried with mapping |
| BillingInvoices, payments and debtor balances | Held | Has a place in partInvoices and payments; a past invoice is entered as sent, then marked paid. | Carried with mapping |
| Trust moneyTrust or client account ledgers and balances | HeldClient accounting under Law Society of Scotland and SRA accounts rules. | Has a place in partA trust account with a running balance; deposits are allocated to a contact and matter. | Carried with mapping |
| Firm accountsGeneral ledger, office account and payables | HeldSolicitors’ accounts software in the same system as case management. | No placeNo general ledger. | Kept as a readable archive |
| 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 | To be confirmed | Has a place in partDocument and email templates are rebuilt with Lawmatics merge fields. | Confirmed in the analysis |
| IntakeLeads, enquiries, intake forms and pipelines | To be confirmed | Has a placePipelines and stages, marketing sources and campaigns. | Confirmed in the analysis |
What the plans mean
- Carried across
- Lawmatics has a place for this kind of record. It is loaded there and checked against LawCloud.
- 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.
- Kept as a readable archive
- Lawmatics has no place for it. It is exported in a format that opens without LawCloud and handed to the firm as a read-only archive.
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 LawCloud 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 LawCloud 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 LawCloud 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 LawCloud is kept running until the checks on Lawmatics are finished.
Where the data is now
Leaving LawCloud
A LawCloud firm does not hold its own database: LawWare hosts it. Leaving starts with a request for a copy of the data and documents, and with working out which edition the firm is actually on. Because legal accounts sit in the same system as the cases, the client ledgers and the case files leave together and have to agree with each other on arrival.
Hosted LawWare, by another name
LawCloud is LawWare’s Enterprise edition run from LawWare’s hosting. Staff may call it LawWare, LawCloud or just the case management system. We confirm the edition and version with the vendor at the start, because LawWare describes New LawWare as a complete redesign of version 4, and the extraction has to match the version in use.
The case record logs everything
Every phone call, document, email and time entry is written to the case record as an activity. That log is the running history of the file. Systems that keep documents, notes and time in separate lists can hold each item, but the single history is rebuilt only if entries keep their dates and authors.
Scottish accounts rules
The accounts software is written for the Law Society of Scotland’s accounts rules, including real-time monitoring of surpluses, as well as the rules south of the border. A destination must cope with the rules the firm practises under. For Scottish firms that is the first thing to confirm with any replacement.
Outsourced cashiering
LawWare also runs an outsourced legal cashiering service, and some firms have their books kept that way. If so, the people who know the ledgers are outside the firm. They need to be part of the cutover plan: closing the period, producing the final reconciliation and confirming the balances that are loaded.
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.
Trust money moves on this route, so the trust cutover gets a rehearsal of its own.
Analysis
We read what LawCloud 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 LawCloud, 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 LawCloud: record counts, trust and debtor totals, the links between records, document dates. Exceptions are listed for you to decide.
Cutover
Changes in LawCloud are frozen for an agreed window, the data is collected a final time and Lawmatics goes live over a weekend. The trust and financial cutover is rehearsed on a full trial load first, because it cannot be re-run the way a document load can. LawCloud 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 LawCloud 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 LawCloud 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
LawCloud to Lawmatics: what firms ask
Who gives us our data if LawWare hosts it?
The firm asks LawWare for it. We set out what is needed: the database, the document store and the closing accounts reports, taken at the same moment. How the copy is supplied and how long it takes are confirmed with LawWare during the analysis, and the cutover date is set around that answer.
Is LawCloud the same thing as LawWare?
For migration purposes, yes. LawCloud was the name for LawWare’s hosted service, and the software behind it is LawWare. What matters is the version: the older version 4 or the redesigned New LawWare. The firm’s support contact can confirm that, and we plan the extraction around it.
Do trust balances in LawCloud have a place in Lawmatics?
In part. A trust account with a running balance; deposits are allocated to a contact and matter. The analysis sets out which trust records have a place in Lawmatics and which are kept as an archive, and the trust cutover is rehearsed on a full trial load before the real one.
What happens to records Lawmatics has no place for?
On this route that is the firm’s accounts. They are exported from LawCloud in formats that open without it, spreadsheets and PDFs, and handed to the firm as a read-only archive. You see the list before the move.
What has to be decided before LawCloud data is loaded into Lawmatics?
Documents, emails, time entries, billing records and trust ledgers are carried with mapping, so each mapping is agreed with you first. Contacts, calendar entries, tasks, custom fields, templates and intake records 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 LawCloud and into Lawmatics
Other destinations from LawCloud
Other systems that move 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.
LawCloud and Lawmatics are the names and marks of their owners, used here only to identify the two systems.
Moving from LawCloud 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.