Skip to content
NEWLAW.COM
+61 1300 495 281
Let’s talk

Data migration route

Aderant Omega data to SQLite

Aderant Omega is a practice management system, and SQLite is a store of data kept as files the firm holds. This is not a move to a new working system: the route writes out what Aderant Omega holds and keeps it readable and open to queries.

FromAderant OmegaPractice management
  1. Matters: Exported in full
  2. Calendar: Exported in full
  3. Time and expenses: Exported in full
  4. Billing: Exported in full
  5. Firm accounts: Exported in full
  6. Intake: Exported in full
  7. Contacts: Confirmed in the analysis
  8. Documents: Confirmed in the analysis
  9. Emails: Confirmed in the analysis
  10. Notes: Confirmed in the analysis
  11. Tasks: Confirmed in the analysis
  12. Trust money: Confirmed in the analysis
  13. Custom fields: Confirmed in the analysis
  14. Templates: Confirmed in the analysis
ToSQLiteFiles
  • 6 carried
  • 8 to confirm
What the two products hold. The analysis confirms it field by field.

What moves

What moves from Aderant Omega to SQLite

Each row is a kind of record Aderant Omega holds, whether SQLite 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.

Records in Aderant Omega and their place in SQLite
RecordIn Aderant OmegaIn SQLiteWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldClients and matters, with case management.Has a placeA matters table keyed by matter number.Exported in full
ContactsClients, other parties and referrersTo be confirmedHas a placeContacts and their roles on matters as linked tables.Confirmed in the analysis
DocumentsFiles stored in or linked from the systemTo be confirmedHas a place in partListed in a table; the files themselves stay in folders beside the database.Confirmed in the analysis
EmailsEmails saved to matters or to the storeTo be confirmedHas a place in partAs message files in folders, indexed in a table.Confirmed in the analysis
NotesFile notes, matter notes and contact notesTo be confirmedHas a placeA notes table linked to matters.Confirmed in the analysis
CalendarAppointments, court dates and deadlinesHeldCalendar and docket.Has a placeA table of dated entries, with no calendar view.Exported in full
TasksTo-dos and workflow steps assigned to peopleTo be confirmedHas a placeA table of tasks and their status at the final date.Confirmed in the analysis
Time and expensesTime and expense entries, billed and unbilledHeldHas a placeA table of time and expense entries.Exported in full
BillingInvoices, payments and debtor balancesHeldBilling, electronic billing and collections.Has a placeInvoice and receipt tables; invoice PDFs kept as files.Exported in full
Trust moneyTrust or client account ledgers and balancesTo be confirmedHas a placeTrust transactions as rows, for look-up and not for accounting.Confirmed in the analysis
Firm accountsGeneral ledger, office account and payablesHeldAccounting and financial reporting.Has a placeLedger journals as rows, where the source held them.Exported in full
Custom fieldsFields and record types the firm added itselfTo be confirmedHas a placeColumns added to the table they belonged to.Confirmed in the analysis
TemplatesPrecedents, document templates and automationTo be confirmedNo placePrecedent files are kept in folders, not in the database.Confirmed in the analysis
IntakeLeads, enquiries, intake forms and pipelinesHeld in partMatter Intake collects new client and matter details on an electronic form.Has a placeAn enquiries table, where the source tracked them.Exported in full

What the plans mean

Exported in full
SQLite 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

Not a new system. A complete copy the firm can query.

Writing Aderant Omega out to SQLite is not a migration into a new working system. Nobody will open a matter there on Monday morning. The aim is a complete, faithful copy that can be queried and reported on after the old system is gone. So the rules change. Nothing is cleaned or merged unless the firm asks, because an archive should show the records as they were. Every table and field is carried, including those a new system would have had no place for.

What makes an archive usable is the description that goes with it. The export is delivered with a plain account of each table: what it holds, how it joins to the others, what the codes mean. Record counts and financial totals are agreed to the reports in Aderant Omega as at the export date, so the archive can stand as the record. Documents are exported beside the data with a table linking each file to its matter. Access is restricted, since the archive holds everything the live system did.

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. Both ends are on equipment the firm controls, so the work is done on the firm’s own network with its IT provider. Disk space for a second full copy is checked first. The original in Aderant Omega stays untouched until the copy in SQLite has been checked.

Where the data is now

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.

  1. 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.

  2. 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.

  3. 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.

  4. 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.

More about moving off Aderant Omega

Where it is going

A SQLite archive suits a firm that wants the old system’s records kept, seldom consulted, and free of any server or subscription. Everything structured goes into one file. That simplicity moves the responsibility elsewhere: the file has no security of its own and no administrator watching it, so where it is stored and who can reach it are the real decisions.

  1. One file, kept with the archive

    Matters, contacts, time, invoices and trust transactions become tables in a single file. It is stored with the firm’s closed-matter records and can be copied like any document. A checksum recorded when the file is finalised lets anyone confirm, years later, that the copy they hold has not been altered, and the firm decides whether to keep one.

  2. No logins inside the file

    SQLite has no users or passwords. Anyone who can open the file can read every client’s ledger. Protection comes from where it is kept, such as a restricted folder or an encrypted volume, and that choice is the firm’s. It can suit an archive consulted by two people, and it is said plainly so nobody assumes otherwise.

  3. Built for reading, not sharing

    Only one program can write to the file at a time, and SQLite’s authors point people to a client/server database where many users share data over a network. A finished archive never meets that limit. It is the reason SQLite is used here for records that are closed and not for anything staff still update.

  4. Documents stay outside it

    Documents remain ordinary files in matter folders, and a table in the database lists each one with its matter, title, dates and path. Keeping them as files means they open with a double-click and can be handed to a client. The table is how a file is found by matter number instead of by guessing its name.

  5. Someone has to open it

    SQLite publishes its own command-line program for opening a database file, and other tools read the format too. None of that helps if nobody remembers how. Saved queries for the usual look-ups and a short note on which tool to use can sit in the same folder as the file, and the firm decides what it needs.

More about moving into SQLite

How NewLaw runs it

Four steps, in this order.

This route produces an archive, not a working system, so the steps are about completeness and proof.

  1. Analysis

    We read what Aderant Omega holds, table by table, and agree with you what the copy in SQLite must be able to answer later. Everything Aderant Omega holds is in scope unless you take it out.

  2. Clean-up, if you want it

    An archive should show the records as they were, so nothing is merged or corrected unless you ask. Where the copy is also meant for reporting, duplicate and inconsistent entries are tidied in a working copy and the original values are kept beside them.

  3. Trial export

    The data is written to SQLite as a trial and checked against Aderant Omega: record counts, totals where Aderant Omega holds money, the links between records, and a sample of documents opened from the export. Exceptions are listed for you to decide.

  4. Final export

    After the last day of work in Aderant Omega, the export is run a final time and checked again. There is nothing to go live. Aderant Omega is kept read only until you are satisfied the copy answers what you need, and it is handed over with a written description of its contents.

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

Step 1 of 5: Start with the route

Moving fromAderant Omega
Moving toSQLite

The route comes from this page. Four short steps follow. Nothing you send commits your firm to anything.

What happens after you send it

  1. A free first call

    We go through your answers with you and ask about anything they leave open.

  2. An analysis of what Aderant Omega holds

    What is in it, how its records link, and where each piece would sit in SQLite. Anything with no place there comes across as a note or stays behind, and you see which before the move.

  3. 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

Structure, permissions and handover

SQLite is a place to keep data, not a system staff work in each day. What is agreed is how the data is laid out, who can reach it, and what is handed over with it.

There is nothing to install on a server and nothing to license. The work is in making the file usable and safe to keep: naming it, documenting its tables, storing it where the firm’s records policy says archives go, and checking that a member of staff can open it and find a matter. Whether a second copy is held somewhere separate is the firm’s call.

What is agreed and set up

  • File name, storage location and whether a second copy exists
  • Whether a checksum is recorded for later verification
  • Saved queries for matter, ledger and document look-ups
  • Which tool staff will use to open the file
  • Who may open the folder the file sits in
  • Retention period and destruction date noted beside the file

Questions

Aderant Omega to SQLite: 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.

Does the copy in SQLite hold trust ledgers from Aderant Omega?

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.

Does everything in Aderant Omega have a place in SQLite?

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 SQLite is kept as a readable archive, and you see which before the move.

What has to be decided before Aderant Omega is written out to SQLite?

Contacts, documents, emails, notes, tasks, trust ledgers, custom fields and templates are confirmed in the analysis. The firm also decides who may open the archive and how long it is kept.

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.

How we do itDiscovery to rollout, step by step

Aderant Omega and SQLite are the names and marks of their owners, used here only to identify the two systems.

Moving from Aderant Omega to SQLite?

Tell us what you are moving. You get a plan and a fixed price after the analysis.

We reply within one business day.