Data migration route
Juris to Centerbase migration
Juris is a server-based accounting and billing system, and Centerbase is a cloud practice management system. The financial records lead: balances and open items move, and the matters in Centerbase are built around them.
- Matters: Carried across
- Contacts: Carried across
- Notes: Carried across
- Calendar: Carried across
- Time and expenses: Carried across
- Billing: Carried across
- Trust money: Carried across
- Firm accounts: Carried across
- Documents: Confirmed in the analysis
- Emails: Confirmed in the analysis
- Tasks: Confirmed in the analysis
- Custom fields: Confirmed in the analysis
- Templates: Confirmed in the analysis
CenterbaseCloud- 8 carried
- 5 to confirm
What moves
What moves from Juris to Centerbase
Each row is a kind of record Juris holds, whether Centerbase has a place for it, and what is planned. On this route eight kinds of record carry across and five kinds are confirmed in the analysis.
| Record | In Juris | What is planned | |
|---|---|---|---|
| MattersMatters or cases, with their numbers, types, parties and status | HeldClients and matters as financial records, coded by lawyer, practice class and office. | Has a placeLoaded under their client, with practice-specific custom fields. | Carried across |
| ContactsClients, other parties and referrers | Held in partClients, vendors and names typed on note cards. | Has a placeClients, related parties and prospects. | Carried across |
| DocumentsFiles stored in or linked from the system | To be confirmed | Has a placeInto Document Storage, or left in a connected NetDocuments, iManage or SharePoint store. | Confirmed in the analysis |
| EmailsEmails saved to matters or to the store | To be confirmed | Has a place in partEmails saved to matters; mailboxes stay in Microsoft 365. | Confirmed in the analysis |
| NotesFile notes, matter notes and contact notes | Held in partNote cards at client or matter level. | Has a place | Carried across |
| CalendarAppointments, court dates and deadlines | Held in partThe vendor’s site lists a Juris Calendar beside the main product. | Has a place | Carried across |
| 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 | HeldEntered in Juris, Juris Suite or the Juris Go mobile app. | Has a place | Carried across |
| BillingInvoices, payments and debtor balances | HeldIncludes electronic billing. | 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 | Held | Has a placeMultiple trust and retainer accounts per matter or client. | Carried across |
| Firm accountsGeneral ledger, office account and payables | HeldGeneral ledger with multi-level sub-accounts, payables and cheque reconciliation. | 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 |
What the plans mean
- Carried across
- Centerbase has a place for this kind of record. It is loaded there and checked against Juris.
- 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
Time, bills and balances move. How much history is a decision.
Coming from an accounting or billing system, the records that count are balances: unbilled time, unpaid invoices, client funds, the ledger. A practice management system takes these as opening positions on a matter. So every client and job in Juris needs a matter to land on, and the first piece of work is building that matter list, often from client and project codes that were never meant to be matter numbers.
How much history to bring is the main choice. Paid invoices from years ago can be loaded as records, kept as PDF copies on the matter, or left in a read-only copy of Juris. Most firms bring open items and a period of history, and keep the rest as reports. Opening balances in Centerbase are agreed to the trial balance and aged debtors from Juris as at the cutover date, and that load is rehearsed before it is done for real.
Juris runs on the firm’s own equipment, so the data is collected there: a copy of the database and the folders its documents sit in, taken with the firm’s IT provider or over a remote session. Centerbase is hosted by its maker, so loading depends on the import tools and access it provides. The old machine is kept, read only, as the fall-back record.
Where the data is now
Leaving Juris
Juris holds the firm’s financial history and little else, so a move off it is mostly about money and the codes that classify it. Work in progress, receivables, trust, payables and the ledger are each agreed to a Juris report. Matter documents and calendars usually live in another product beside it, and that product is brought into the same plan.
Three kinds of charge
Juris separates fees, cash expenses and non-cash expenses, and supports accrual, billed and cash accounting methods. Many destinations know only time and disbursements. The mapping has to say where non-cash expenses go, or unbilled and billed cost totals will not agree after the load.
Codes carry the reporting
Billing lawyer, originating lawyer, working timekeeper, practice class, office and billing agreement are all coded on the matter. Partner reports are built on them. Each code table is extracted and mapped, and codes that have drifted into near-duplicates are tidied in Juris before extraction.
Note cards feed conflict searches
Clients and matters can have note cards with other names and special information, and the conflict search reads them. They are where related parties were typed when there was no better field. Note cards come across as notes, and names inside them are flagged in case the firm wants them as contacts.
Juris Suite is a second layer
Firms with Juris Suite enter time, run collections and keep budgets through it. Budgets and collection notes are extra records worth asking about. They are listed in the analysis so nobody finds after go-live that the collections history was never in scope.
Sub-accounts in the chart
The chart of accounts can be split into multi-level sub-accounts to match how the firm is organised. A destination with a flat chart needs those collapsed or turned into tracking categories. The firm’s accountant agrees the new chart first, and the closing trial balance is restated into it before loading.
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 Juris 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 Juris, 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 Juris: record counts, trust and debtor totals, the links between records, document dates. Exceptions are listed for you to decide.
Cutover
Changes in Juris 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. Juris 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 Juris 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 Juris 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
Juris to Centerbase: what firms ask
Can we keep our client and matter codes?
Juris codes are carried over wherever the destination allows a firm-set number, with the same padding and separators so old bills still match. If the new system numbers matters itself, the Juris code is stored as a reference and printed on invoices where clients expect to see it.
How much billing history should we bring?
Enough to answer a client’s question about a bill and to run aged debtors properly. Open invoices are loaded with their original dates. Paid invoices from earlier years can be loaded as summaries or left in Juris, kept read only. The destination’s limits usually decide it.
Our e-billing clients have strict formats. What happens?
The task codes, timekeeper classifications and client rates behind your e-bills are extracted and rebuilt in the new system. Past submissions stay where they are. Before go-live one real invoice for each e-billing client is produced from the trial load and checked against that client’s rules.
Do trust balances in Juris 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 Juris 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 Juris have a place in Centerbase?
Most of it does on paper. Documents, emails, tasks, custom fields and templates 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 Juris data is loaded into Centerbase?
Documents, emails, tasks, custom fields and templates 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 Juris and into Centerbase
Other destinations from Juris
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.
Juris and Centerbase are the names and marks of their owners, used here only to identify the two systems.
Moving from Juris 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.