Data migration route
Aderant Omega to Filevine migration
Aderant Omega is a practice management system, and Filevine is a cloud case management system. Matter records move into cases, and the firm decides where its accounting runs from the cutover date.
Aderant OmegaPractice management- Matters: Carried across
- Calendar: Carried across
- Time and expenses: Carried with mapping
- Billing: Carried with mapping
- Intake: Carried with mapping
- 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
- Firm accounts: Confirmed in the analysis
- Custom fields: Confirmed in the analysis
- Templates: Confirmed in the analysis
FilevineCloud- 2 carried
- 3 mapped
- 9 to confirm
What moves
What moves from Aderant Omega to Filevine
Each row is a kind of record Aderant Omega holds, whether Filevine has a place for it, and what is planned. On this route two kinds of record carry across, three kinds need mapping and nine 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 as projects of a defined project type. | Carried across |
| ContactsClients, other parties and referrers | To be confirmed | Has a placeContact cards, linked to projects. | Confirmed in the analysis |
| DocumentsFiles stored in or linked from the system | To be confirmed | Has a placeDocs section with folders. Templated project folders can be set per type. | Confirmed in the analysis |
| EmailsEmails saved to matters or to the store | To be confirmed | Has a placeHeld in the activity feed of the project. | Confirmed in the analysis |
| NotesFile notes, matter notes and contact notes | To be confirmed | Has a placeHeld as notes in the activity feed. | Confirmed in the analysis |
| CalendarAppointments, court dates and deadlines | HeldCalendar and docket. | Has a placeDeadlines and calendar events. | 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 in partNeeds the Billing product enabled. | Carried with mapping |
| BillingInvoices, payments and debtor balances | HeldBilling, electronic billing and collections. | Has a place in partNeeds the Billing product enabled. | Carried with mapping |
| Trust moneyTrust or client account ledgers and balances | To be confirmed | Has a place in partTrust accounts sit in Payments by Filevine. Loading history is confirmed in the analysis. | Confirmed in the analysis |
| Firm accountsGeneral ledger, office account and payables | HeldAccounting and financial reporting. | To be confirmed | Confirmed in the analysis |
| Custom fieldsFields and record types the firm added itself | To be confirmed | Has a placeCustom sections and fields per project type. | Confirmed in the analysis |
| TemplatesPrecedents, document templates and automation | To be confirmed | Has a place in partTemplates are rebuilt as Filevine document templates. They are not converted. | 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 place in partLeads belong in Lead Docket, which passes signed clients to Filevine. | Carried with mapping |
What the plans mean
- Carried across
- Filevine has a place for this kind of record. It is loaded there and checked against Aderant Omega.
- Carried with mapping
- Filevine 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
Matters become cases. The ledgers need a home.
Going from a practice management system to a case management system is a move towards the file and away from the ledger. Matters, parties, documents, notes and deadlines have a natural place in Filevine. Time, invoices, trust and the general ledger often do not, or only in part, and the table above shows which. Before the move is planned the firm settles where billing and trust accounting will run, because that decides what is loaded and what is archived.
Case systems are usually built around a practice area, with their own stages, roles and document sets. A general matter from Aderant Omega has to be given a case type in Filevine, and that choice drives which fields and workflows it gets. The mapping is agreed type by type. Financial history with no place in Filevine is exported as reports and ledgers the firm can open without Aderant Omega, and kept as the record of what was billed and held.
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. Filevine 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 Filevine
Loading a firm into Filevine depends on the project types being built first. Until the sections and fields exist there is nowhere for the data to go, so configuration and migration are planned together. The old system’s parties, insurers, providers and key dates are mapped to sections, and its notes and emails are loaded into each project’s activity feed.
Project types before data
Each area of practice needs a project type with its sections, fields and phases defined in the Customs Editor. Changes made there apply to every project of that type. The types are drafted from the old system’s data, tested with a few real cases, and only then is the bulk load run.
One contact card per person
Contacts are held as contact cards. A doctor or adjuster who appears on many projects is best loaded as one card, not one for each project. Duplicates in the old system are merged before loading where they can be identified. Loading them as they are produces several cards for the same person, and staff then pick the wrong one when adding a party.
Lists become collection items
Anything the old system held as a list against a matter, such as providers, liens, insurance policies or expenses, is loaded as items in a collection section. Each column needs a matching field. Totals per project are compared with the old system afterwards, since those figures feed the settlement and disbursal sheets.
History goes into the feed
File notes, emails and completed tasks from the old system are loaded into the activity feed with their original dates and authors. Authors must exist as users or be recorded in the text. The feed is long on an old case, so staff are shown how to filter it before go-live.
Billing is a separate switch
The Billing section only appears once Billing is enabled for the firm. Time entries, invoices and trust balances from the old system need that in place before they can be loaded. A firm that leaves it off can still record case costs in a collection section built for the purpose.
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 Filevine. 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 Filevine 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 Filevine 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 Filevine. 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 Filevine
Loaded data is not yet a working system. This is what NewLaw sets up in Filevine, beyond the migration, so that people can work in it from the first day.
Filevine arrives as a platform to be configured, and most of the implementation is design. Someone has to decide what a project looks like for each kind of work the firm does, what moves it from one phase to the next, and who can see what. Those decisions are made with the people who run the files, then built and tested.
Set-up decisions in Filevine
- Design project types, sections and fields for each practice area
- Define phases and the tasks each phase should trigger
- Build document templates that fill from project fields
- Set teams, permissions and protected sections for restricted matters
- Decide whether Billing and Payments are switched on
- Connect Lead Docket so signed leads become projects
Questions
Aderant Omega to Filevine: 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 Filevine?
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 Filevine 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 Filevine?
Most of it does on paper. Contacts, documents, emails, notes, tasks, trust ledgers, the firm’s accounts, 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 Filevine 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 Filevine?
Time entries, billing records and intake records are carried with mapping, so each mapping is agreed with you first. Contacts, documents, emails, notes, tasks, trust ledgers, the firm’s accounts, 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 Filevine
Other destinations from Aderant Omega
Other systems that move into Filevine
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 Filevine are the names and marks of their owners, used here only to identify the two systems.
Moving from Aderant Omega to Filevine?
Tell us what you are moving. You get a plan and a fixed price after the analysis.
We reply within one business day.