Data migration route
Lawcus to Centerbase migration
Lawcus 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.
LawcusCloud- Matters: Carried across
- Contacts: Carried across
- Documents: Carried across
- Notes: Carried across
- Calendar: Carried across
- Tasks: Carried across
- Time and expenses: Carried across
- Billing: Carried across
- Trust money: Carried across
- Intake: Carried across
- Emails: Carried with mapping
- Custom fields: Carried with mapping
- Templates: Carried with mapping
CenterbaseCloud- 10 carried
- 3 mapped
What moves
What moves from Lawcus to Centerbase
Each row is a kind of record Lawcus holds, whether Centerbase has a place for it, and what is planned. On this route ten kinds of record carry across and three kinds need mapping.
| Record | What is planned | ||
|---|---|---|---|
| MattersMatters or cases, with their numbers, types, parties and status | HeldShown as cards on boards with a stage, or as a list; numbers come from a saved scheme. | Has a placeLoaded under their client, with practice-specific custom fields. | Carried across |
| ContactsClients, other parties and referrers | HeldContacts with custom fields and field groups. | Has a placeClients, related parties and prospects. | Carried across |
| DocumentsFiles stored in or linked from the system | HeldFolders in Lawcus, with two-way sync to Google Drive and links to Dropbox, Box or OneDrive. | 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 | Held in partEmails and attachments logged to a matter through the Gmail or Outlook add-ins. | Has a place in partEmails saved to matters; mailboxes stay in Microsoft 365. | Carried with mapping |
| NotesFile notes, matter notes and contact notes | HeldNotes and interactions on a matter can be pinned or starred. | Has a place | Carried across |
| CalendarAppointments, court dates and deadlines | Held | Has a place | Carried across |
| TasksTo-dos and workflow steps assigned to people | HeldNo-code workflows can create tasks when a matter changes. | Has a place | Carried across |
| Time and expensesTime and expense entries, billed and unbilled | Held | Has a place | Carried across |
| BillingInvoices, payments and debtor balances | HeldHourly, flat fee and contingency; invoice templates per currency; credit notes. | 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 | HeldTrust balances and a minimum retainer threshold per matter. | Has a placeMultiple trust and retainer accounts per matter or client. | Carried across |
| Custom fieldsFields and record types the firm added itself | HeldCustom fields and field groups for contacts and matters. | Has a placeCreated and placed on page layouts before records are loaded. | Carried with mapping |
| TemplatesPrecedents, document templates and automation | HeldDocument automation and reusable invoice templates. | Has a place in partTemplates are rebuilt to merge Centerbase client and matter data. | Carried with mapping |
| IntakeLeads, enquiries, intake forms and pipelines | HeldLeads on a Kanban board, with client-facing and internal forms. | Has a placeEnquiries are held as Potential New Client records; loading open ones is confirmed in the analysis. | Carried across |
What the plans mean
- Carried across
- Centerbase has a place for this kind of record. It is loaded there and checked against Lawcus.
- 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.
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. Lawcus 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 Lawcus’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 Lawcus 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 Lawcus is kept running until the checks on Centerbase are finished.
Where the data is now
Leaving Lawcus
In Lawcus a matter’s position on a board says as much about it as any field. Stages, boards and the automations attached to them are how a firm on Lawcus knows where every file stands. A move off it has to turn that visual arrangement into something the destination can store, and it has to do so without losing the difference between a lead and a matter.
Stages are the status
Each board has its own stages, and a matter’s stage is what staff look at to see progress. A conveyancing board and a litigation board will not share stage names. Destinations tend to offer one status list, or a status per matter type. Every board’s stages are mapped separately, and the firm approves the mapping.
Leads sit on boards too
Prospects are tracked on a Kanban board of their own before they become clients. A lead and a matter can look alike in the interface. The extraction keeps them apart, and leads that were never converted are loaded as intake records or left as an exported list, depending on what the destination offers.
Automations are not data
No-code workflows send emails, create tasks and produce documents when a matter changes stage or a form comes in. None of that is a record that can be moved. The workflows are documented as rules during the analysis, and the firm chooses which ones to rebuild in the new system’s own automation.
QuickBooks was fed one way
Lawcus pushes invoices, payments and expenses to QuickBooks Online and takes nothing back. An edit made directly in QuickBooks is therefore unknown to Lawcus. The two can drift apart. Receivables are compared on both sides before cutover, and the firm decides which figure is right where they differ.
More than one currency
Invoice templates can be set up for clients billed in different currencies. A destination that works in one currency cannot hold those balances as they are. Foreign-currency clients are identified early, and the firm decides whether their history is converted at a stated rate or kept in the old system.
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 Lawcus 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 Lawcus, 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 Lawcus: record counts, trust and debtor totals, the links between records, document dates. Exceptions are listed for you to decide.
Cutover
Changes in Lawcus 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. Lawcus 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 Lawcus 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 Lawcus 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
Lawcus to Centerbase: what firms ask
Our documents sync between Lawcus and Google Drive. Which copy is moved?
The Google Drive copy is usually the easier source, because it is in the firm’s own account and the sync keeps the two alike. Lawcus supplies the link between each folder and its matter. A sample of matters is compared on both sides first to confirm nothing is missing from the Drive.
Can our matter numbers be kept?
Yes. Lawcus generates matter numbers from a numbering scheme the firm saved, so the numbers are consistent and can be carried as they are. If the destination produces numbers in another format, the Lawcus number is kept in a reference field and new matters follow the new format.
What happens to forms our clients filled in?
Answers that were saved to fields on a contact or matter are data and move with that record. Forms marked internal are treated the same way. The form designs are specific to Lawcus. If the new system has intake forms, they are rebuilt there from the same questions.
Do trust balances in Lawcus 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 Lawcus 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 Lawcus have a place in Centerbase?
On paper, yes: each kind of record Lawcus holds has a place in Centerbase. Whether every field fits is a separate question, and the analysis answers it field by field. Anything with no place comes across as a note or stays behind, and you see which before the move.
What has to be decided before Lawcus data is loaded into Centerbase?
Emails, custom fields and templates are carried with mapping, so each mapping is agreed with you first. The firm also sets the cutover date and how much financial history comes across as live records.
Other routes
Other routes from Lawcus and into Centerbase
Other destinations from Lawcus
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.
Lawcus and Centerbase are the names and marks of their owners, used here only to identify the two systems.
Moving from Lawcus 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.