Data migration route
LawCloud to Centerbase migration
LawCloud and Centerbase are each a cloud practice management system. Both run a whole practice, so this is a full move, and the financial records set the timetable.
LawCloudCloud- Matters: Carried across
- Documents: Carried across
- Notes: Carried across
- Time and expenses: Carried across
- Billing: Carried across
- Trust money: Carried across
- Firm accounts: Carried across
- Emails: 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
CenterbaseCloud- 7 carried
- 1 mapped
- 6 to confirm
What moves
What moves from LawCloud to Centerbase
Each row is a kind of record LawCloud holds, whether Centerbase has a place for it, and what is planned. On this route seven kinds of record carry across, one kind needs mapping 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 under their client, with practice-specific custom fields. | Carried across |
| ContactsClients, other parties and referrers | To be confirmed | Has a placeClients, related parties and prospects. | Confirmed in the analysis |
| DocumentsFiles stored in or linked from the system | HeldDocuments are stored and searched within the case. | Has a placeInto Document Storage, or left in a connected NetDocuments, iManage or SharePoint store. | Carried across |
| EmailsEmails saved to matters or to the store | HeldEmails are logged to the case record. | Has a place in partEmails saved to matters; mailboxes stay in Microsoft 365. | Carried with mapping |
| NotesFile notes, matter notes and contact notes | Held in partPhone calls are logged against the case. | Has a place | Carried across |
| CalendarAppointments, court dates and deadlines | To be confirmed | Has a place | 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 | Carried across |
| BillingInvoices, payments and debtor balances | Held | Has a placeThe vendor says billing history can be migrated; the depth is set in the analysis. | Carried across |
| Trust moneyTrust or client account ledgers and balances | HeldClient accounting under Law Society of Scotland and SRA accounts rules. | Has a placeMultiple trust and retainer accounts per matter or client. | Carried across |
| Firm accountsGeneral ledger, office account and payables | HeldSolicitors’ accounts software in the same system as case management. | Has a placeGeneral ledger with chart of accounts; opening trial balance agreed with the accountant. | Carried across |
| Custom fieldsFields and record types the firm added itself | To be confirmed | Has a placeCreated and placed on page layouts before records are loaded. | Confirmed in the analysis |
| TemplatesPrecedents, document templates and automation | To be confirmed | Has a place in partTemplates are rebuilt to merge Centerbase client and matter data. | Confirmed in the analysis |
| IntakeLeads, enquiries, intake forms and pipelines | To be confirmed | Has a placeEnquiries are held as Potential New Client records; loading open ones is confirmed in the analysis. | Confirmed in the analysis |
What the plans mean
- Carried across
- Centerbase has a place for this kind of record. It is loaded there and checked against LawCloud.
- Carried with mapping
- Centerbase 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
The whole practice moves, accounts included.
A move between two practice management systems is the widest kind there is. LawCloud and Centerbase each keep matters, contacts, documents, time and money in one place, but no two systems link those records the same way. In one, a client is a contact with a role on the matter. In another, every matter carries its own client card. Most of the analysis goes into those links, because a matter that arrives without its client or its documents is the first thing staff find.
The financial side decides the dates. Unbilled time, debtor balances and trust ledgers have to agree with LawCloud’s own reports as at one day, and a new system usually wants them as opening balances, not as years of transactions. So the firm decides early how much history comes across as live records and how much is kept as reports. Matter and document loads can be repeated until they are right. The money is loaded once.
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 Centerbase 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 Centerbase
Centerbase takes practice, billing, trust and accounting data together, so loading a firm into it is a finance project as much as a matter load. Clients come first because matters inherit from them. The chart of accounts, bank accounts and accounting basis are fixed before balances go in. Because the product is configured per firm, the fields and layouts are designed before the trial load, not after.
Clients carry the billing rules
Billing arrangements, rates and accounting preferences are held on the client and passed to its matters. Source systems that create a fresh client for every matter leave duplicates behind. Those are merged during clean-up, so that each real client exists once and its terms are set in one place.
The ledger comes too
Centerbase has a full general ledger and runs on a cash or accrual basis. A firm arriving from a billing system with QuickBooks beside it is consolidating two sets of records. The accountant decides the basis and the opening date, and the trial balance loaded is agreed to the old books.
Trust and retainers are separate
A matter can hold multiple trust and retainer accounts. Source systems often blur the two, recording an advance on fees as trust or the reverse. Each balance is classified before loading, and client-level funds that were never tied to a matter are assigned to one or held at client level.
Decide the document home
Documents can go into built-in Document Storage, or stay in NetDocuments, iManage or SharePoint and be connected. Centerbase can create a standard folder structure when a matter is opened. That structure is agreed first, so migrated documents are filed into the same folders that new matters will get.
Fields are designed, not assumed
With unlimited custom fields, nearly every source field can have a home. That is a reason for restraint. Each one must be created and placed on a layout, and a page crowded with unused fields slows people down. The firm chooses which fields earn a place and which become a note.
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 Centerbase. 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 Centerbase 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 Centerbase 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 Centerbase. 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 Centerbase
Loaded data is not yet a working system. This is what NewLaw sets up in Centerbase, beyond the migration, so that people can work in it from the first day.
Setting up Centerbase is largely configuration. Bill templates, rate tables and the pre-bill approval chain have to match how the firm bills today, or the first billing cycle exposes the gaps. The chart of accounts and bank accounts are built with the finance team. Workflows that open matters, create folders and assign first tasks are written last, once the fields they depend on are settled.
Set-up decisions in Centerbase
- Bill templates and billing arrangements for each client type
- Rate tables, timekeepers and the pre-bill approval chain
- Chart of accounts, bank accounts and cash or accrual basis
- Custom fields, page layouts and automated workflows by practice
- Document storage choice and the standard matter folder structure
- Outlook and Microsoft 365 connection for email and calendar
Questions
LawCloud to Centerbase: 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 Centerbase?
Yes. Centerbase keeps trust ledgers. Multiple trust and retainer accounts per matter or client. Balances are loaded by matter and agreed to the trust report from LawCloud as at the cutover date. That load cannot be re-run the way a document load can, so it is rehearsed on a full trial load first.
Does everything in LawCloud have a place in Centerbase?
Most of it does on paper. Contacts, calendar entries, tasks, custom fields, templates and intake records 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 Centerbase is kept as a readable archive, and you see which before the move.
What has to be decided before LawCloud data is loaded into Centerbase?
Emails 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 Centerbase
Other destinations from LawCloud
Other systems that move into Centerbase
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 Centerbase are the names and marks of their owners, used here only to identify the two systems.
Moving from LawCloud to Centerbase?
Tell us what you are moving. You get a plan and a fixed price after the analysis.
We reply within one business day.