Data migration route
Aderant Omega to Centerbase migration
Aderant Omega is a practice management system, and Centerbase is a cloud one. Both run a whole practice, so this is a full move, and the financial records set the timetable.
Aderant OmegaPractice management- Matters: Carried across
- Calendar: Carried across
- Time and expenses: Carried across
- Billing: Carried across
- Firm accounts: Carried across
- Intake: Carried across
- Contacts: Confirmed in the analysis
- Documents: Confirmed in the analysis
- Emails: Confirmed in the analysis
- Notes: Confirmed in the analysis
- Tasks: Confirmed in the analysis
- Trust money: Confirmed in the analysis
- Custom fields: Confirmed in the analysis
- Templates: Confirmed in the analysis
CenterbaseCloud- 6 carried
- 8 to confirm
What moves
What moves from Aderant Omega to Centerbase
Each row is a kind of record Aderant Omega holds, whether Centerbase has a place for it, and what is planned. On this route six kinds of record carry across and eight kinds are confirmed in the analysis.
| Record | What is planned | ||
|---|---|---|---|
| MattersMatters or cases, with their numbers, types, parties and status | HeldClients and matters, with case management. | 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 | 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 | To be confirmed | Has a place | Confirmed in the analysis |
| CalendarAppointments, court dates and deadlines | HeldCalendar and docket. | 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 | Held | Has a place | Carried across |
| BillingInvoices, payments and debtor balances | HeldBilling, electronic billing and collections. | 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 | To be confirmed | Has a placeMultiple trust and retainer accounts per matter or client. | Confirmed in the analysis |
| Firm accountsGeneral ledger, office account and payables | HeldAccounting and financial reporting. | 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 | Held in partMatter Intake collects new client and matter details on an electronic form. | 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 Aderant Omega.
- 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. Aderant Omega 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 Aderant Omega’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.
How Aderant Omega is run at the firm is settled at the start of the analysis, because its maker’s own material does not settle it. The usual arrangement is assumed here. Aderant Omega 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 Aderant Omega
Omega is a finance-led system, so the heart of a move off it is the firm’s books: work in progress, debtors, the ledgers and the billing history behind them. The analysis begins with the installation itself, establishing the version, the modules in use and where the database sits, before anything is promised about what will move.
A name shared with others
Several unrelated products are called Omega. This one is the law firm financial system from Omega Legal Systems, later sold as Omega Legal vx and now owned by Aderant. Confirming that from the login screen and the licence takes minutes and avoids planning a migration around the wrong product’s data structure.
Finance is the core
The system was described as integrated time, billing, accounting, e-billing and collections. That means unbilled time, draft bills, debtor balances and the general ledger are all in one place and agree with each other today. They are extracted together on one date so that they still agree when they are loaded.
E-billing set-ups per client
Electronic billing is part of the product, and corporate clients who are billed that way each expect their own format and codes. Those arrangements are configuration, not data. Every client billed electronically is listed with its format, so the same invoices can be produced from the new system in the first billing run.
Reports built in Visual Xpress
Management reporting was done through a dashboard tool called Visual Xpress. Dashboards do not migrate. Partners are asked which figures they look at each month, and those reports are reproduced from the new system and compared with the old ones for the same period before the old system is retired.
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.
Financial records move on this route, so the balances are rehearsed before the real cutover.
Analysis
We read what Aderant Omega 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 Aderant Omega, 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 Aderant Omega: record counts, financial totals, the links between records, document dates. Exceptions are listed for you to decide.
Cutover
Changes in Aderant Omega are frozen for an agreed window, the data is collected a final time and Centerbase goes live over a weekend. The financial cutover is rehearsed on a full trial load first, so that opening balances agree with the reports in Aderant Omega as at the cutover date. Aderant Omega 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 Aderant Omega 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 Aderant Omega 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
Aderant Omega to Centerbase: what firms ask
How much financial history should we bring?
Enough to answer a client’s question about an old bill and to satisfy the auditors. Many firms bring open matters in full, with several years of billing and payment history, and keep older ledgers in the read-only system. The destination’s limits on historical transactions are checked in the analysis before that line is drawn.
Can work in progress and unbilled costs move mid-month?
They can, but the cutover is planned for a period end where possible. Time and costs entered up to the freeze are extracted as unbilled items with their matter, timekeeper, date and rate. The total by matter is checked against the Omega work in progress report for the same day before anyone bills from the new system.
We are not sure which version we have. Does it matter?
It does, and it is easy to settle. The version, the database it runs on and the modules licensed all affect how the data is collected and what it contains. These are read from the installation at the start of the analysis, and the plan and the fixed price follow from them.
Do trust balances in Aderant Omega have a place in Centerbase?
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 Aderant Omega before the plan is fixed. If Centerbase 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 Aderant Omega have a place in Centerbase?
Most of it does on paper. Contacts, documents, emails, notes, tasks, trust ledgers, 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 Aderant Omega data is loaded into Centerbase?
Contacts, documents, emails, notes, tasks, trust ledgers, 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 Aderant Omega and into Centerbase
Other destinations from Aderant Omega
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.
Aderant Omega and Centerbase are the names and marks of their owners, used here only to identify the two systems.
Moving from Aderant Omega 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.