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

Data migration route

Aderant Omega to SimpleLaw migration

Aderant Omega is a practice management system, and SimpleLaw is a cloud one. Both run a whole practice, so this is a full move, and the financial records set the timetable.

FromAderant OmegaPractice management
  1. Matters: Carried across
  2. Calendar: Carried across
  3. Time and expenses: Carried across
  4. Intake: Carried across
  5. Billing: Carried with mapping
  6. Contacts: Confirmed in the analysis
  7. Documents: Confirmed in the analysis
  8. Emails: Confirmed in the analysis
  9. Notes: Confirmed in the analysis
  10. Tasks: Confirmed in the analysis
  11. Trust money: Confirmed in the analysis
  12. Custom fields: Confirmed in the analysis
  13. Templates: Confirmed in the analysis
ToSimpleLawCloud
  1. Firm accounts: Kept as a readable archive
Readable archiveNo place in SimpleLaw
  • 4 carried
  • 1 mapped
  • 8 to confirm
  • 1 archived
What the two products hold. The analysis confirms it field by field.

What moves

What moves from Aderant Omega to SimpleLaw

Each row is a kind of record Aderant Omega holds, whether SimpleLaw has a place for it, and what is planned. On this route four kinds of record carry across, one kind needs mapping, one kind has no place in SimpleLaw and is archived and eight kinds are confirmed in the analysis.

Records in Aderant Omega and their place in SimpleLaw
RecordIn Aderant OmegaIn SimpleLawWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldClients and matters, with case management.Has a placeCarried across
ContactsClients, other parties and referrersTo be confirmedHas a placeAs leads, clients or other contacts in the CRM.Confirmed in the analysis
DocumentsFiles stored in or linked from the systemTo be confirmedHas a placeUploaded to SimpleLaw storage or held in a linked Dropbox, Google Drive or OneDrive.Confirmed in the analysis
EmailsEmails saved to matters or to the storeTo be confirmedTo be confirmedConfirmed in the analysis
NotesFile notes, matter notes and contact notesTo be confirmedHas a placeConfirmed in the analysis
CalendarAppointments, court dates and deadlinesHeldCalendar and docket.Has a placeCarried across
TasksTo-dos and workflow steps assigned to peopleTo be confirmedHas a placeConfirmed in the analysis
Time and expensesTime and expense entries, billed and unbilledHeldHas a placeCarried across
BillingInvoices, payments and debtor balancesHeldBilling, electronic billing and collections.Has a place in partInvoices are created in the product; loading invoice history is confirmed in the analysis.Carried with mapping
Trust moneyTrust or client account ledgers and balancesTo be confirmedHas a place in partTrust balances are supported; history depth is confirmed in the analysis.Confirmed in the analysis
Firm accountsGeneral ledger, office account and payablesHeldAccounting and financial reporting.No placeGeneral ledger stays in QuickBooks or another accounting package.Kept as a readable archive
Custom fieldsFields and record types the firm added itselfTo be confirmedHas a placeConfirmed in the analysis
TemplatesPrecedents, document templates and automationTo be confirmedHas a place in partTemplates are rebuilt using SimpleLaw’s own automation.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 placeLeads and intake forms.Carried across

What the plans mean

Carried across
SimpleLaw has a place for this kind of record. It is loaded there and checked against Aderant Omega.
Carried with mapping
SimpleLaw 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.
Kept as a readable archive
SimpleLaw has no place for it. It is exported in a format that opens without Aderant Omega and handed to the firm as a read-only archive.

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

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

Loading a firm into SimpleLaw is mostly a job of sorting contacts and setting up each matter’s billing type. The CRM holds leads, clients and everyone else, so every incoming contact needs a status. Where documents will be stored is decided early as well, since that choice determines where the files are sent. Accounting history stays in QuickBooks or the old system.

  1. Lead, client or contact

    A person is tracked from first enquiry to client in one CRM, with tasks and appointments kept against the contact. Source systems that only ever held clients load simply. Systems with separate intake records need each enquiry classed as a live lead, a lost one or a duplicate of an existing client.

  2. Billing type on each matter

    Every matter is billed as hourly, flat fee, instalments, contingency, pro bono, trust or LEDES. The source may record this loosely or not at all. During the trial load a billing type is set on each matter and checked by the person who raises the bills, because it controls how the invoice is built.

  3. Storage chosen before loading

    If the firm stores documents with SimpleLaw, files are uploaded against each matter. Where it prefers Dropbox, Google Drive or OneDrive, the files go there, and what the connection does with folders already in place is checked first. Switching later means moving everything again, so the choice is made at the start with the firm’s IT support.

  4. Custom fields named for templates

    Custom fields supply intake forms and document automation as well as reports. A field brought across from the old system is only useful if templates can call on it. Fields are therefore named and typed with the firm’s main documents in mind, and one template is tested against loaded data.

  5. Portal access client by client

    The client portal is optional and the firm chooses who has access and what each client can see. Nothing is exposed by loading data. After go-live, access is switched on for chosen clients, starting with a few, once the firm has reviewed what their matters show.

More about moving into SimpleLaw

How NewLaw runs it

Four steps, in this order.

Financial records move on this route, so the balances are rehearsed before the real cutover.

  1. 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 SimpleLaw. Anything with no place there comes across as a note or stays behind, and you see which before the move.

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

  3. Trial load

    The data is loaded into SimpleLaw 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.

  4. Cutover

    Changes in Aderant Omega are frozen for an agreed window, the data is collected a final time and SimpleLaw 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

Step 1 of 5: Start with the route

Moving fromAderant Omega
Moving toSimpleLaw

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

Setting up SimpleLaw

Loaded data is not yet a working system. This is what NewLaw sets up in SimpleLaw, beyond the migration, so that people can work in it from the first day.

The set-up work is in making the product reflect the firm. Labels are adjusted to the firm’s terms. Intake forms and the custom fields behind them are built for each practice area, then document templates are made to draw on those fields. Workflows are written for the case types that follow a standard path, and the QuickBooks and payment connections are made last.

Set-up decisions in SimpleLaw

  • Labels for documents, activities, expenses and contact IDs
  • Custom fields and intake forms for each practice area
  • Document templates and the attorney-client agreement
  • Workflows for case types that follow a standard process
  • User permission sets and client portal visibility
  • QuickBooks connection and the online payment processor

Questions

Aderant Omega to SimpleLaw: 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 SimpleLaw?

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 SimpleLaw turns out to have no place for trust ledgers, they are kept as a readable archive and the firm decides where trust accounting runs.

What happens to records SimpleLaw has no place for?

On this route that is the firm’s accounts. They are exported from Aderant Omega in formats that open without it, spreadsheets and PDFs, and handed to the firm as a read-only archive. You see the list before the move.

What has to be decided before Aderant Omega data is loaded into SimpleLaw?

Billing records are carried with mapping, so each mapping is agreed with you first. 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.

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 SimpleLaw are the names and marks of their owners, used here only to identify the two systems.

Moving from Aderant Omega to SimpleLaw?

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

We reply within one business day.