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

Data migration route

Aderant Expert to Litify migration

Aderant Expert is a server-based practice management system, and Litify is a cloud case management system. Matter records move into cases, and the firm decides where its accounting runs from the cutover date.

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

What moves

What moves from Aderant Expert to Litify

Each row is a kind of record Aderant Expert holds, whether Litify has a place for it, and what is planned. On this route seven kinds of record carry across, three kinds need mapping and four kinds are confirmed in the analysis.

Records in Aderant Expert and their place in Litify
RecordIn Aderant ExpertIn LitifyWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldClients and matters, with file opening and conflicts checking.Has a placeMatters, by case type.Carried across
ContactsClients, other parties and referrersHeldClients and the contacts attached to cases in Expert Case.Has a placeLoaded as parties and connected by roles.Carried across
DocumentsFiles stored in or linked from the systemHeld in partExpert Case assembles and tracks case documents; Aderant lists integration with a separate DMS.Has a placeLoaded to the document component and attached to matters.Carried across
EmailsEmails saved to matters or to the storeTo be confirmedHas a place in partShown on the activity timeline. How old email is loaded is confirmed in the analysis.Confirmed in the analysis
NotesFile notes, matter notes and contact notesTo be confirmedTo be confirmedConfirmed in the analysis
CalendarAppointments, court dates and deadlinesHeld in partExpert Case tracks key dates and links to Outlook and Exchange calendars.Has a placeCalendar events on the matter.Carried across
TasksTo-dos and workflow steps assigned to peopleHeld in partTask management in Expert Case, plus firm-built workflows.Has a placeCarried across
Time and expensesTime and expense entries, billed and unbilledHeldExpert Time and Expert Expenses, with work in progress by matter.Has a placeTime entries on the matter.Carried across
BillingInvoices, payments and debtor balancesHeldPrebills, bills, rates, collections and accounts receivable.Has a place in partBilling is part of the product. Loading past invoices is scoped in the analysis.Carried with mapping
Trust moneyTrust or client account ledgers and balancesHeldTrust management is listed among its accounting applications.To be confirmedConfirmed in the analysis
Firm accountsGeneral ledger, office account and payablesHeldGeneral ledger, accounts payable, tax and disbursements.To be confirmedConfirmed in the analysis
Custom fieldsFields and record types the firm added itselfHeldAderant describes firm-specific customisations held alongside the standard data.Has a placeCustom fields are created before loading.Carried with mapping
TemplatesPrecedents, document templates and automationHeld in partDocument assembly in Expert Case; bill layouts in billing.Has a place in partTemplates are rebuilt in Litify’s document generation.Carried with mapping
IntakeLeads, enquiries, intake forms and pipelinesHeld in partClient and matter intake with conflicts checks, not a marketing pipeline.Has a placeLoaded as intakes.Carried across

What the plans mean

Carried across
Litify has a place for this kind of record. It is loaded there and checked against Aderant Expert.
Carried with mapping
Litify 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 Litify. 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 Expert has to be given a case type in Litify, and that choice drives which fields and workflows it gets. The mapping is agreed type by type. Financial history with no place in Litify is exported as reports and ledgers the firm can open without Aderant Expert, and kept as the record of what was billed and held.

Aderant Expert 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. Litify 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

A firm leaving Expert is usually leaving its finance system, not only a matter list. Years of time entries, bills, receipts, trust movements and ledger postings sit in a SQL Server database the firm controls, often with customisations written for that firm alone. The work is deciding how much of that financial history the new system should carry as live records and how much stays in the old database as the record of the past.

  1. A database on your own servers

    On-premises Expert keeps its data in Microsoft SQL Server on infrastructure the firm manages, so a full copy of the database can be taken for analysis. That makes it possible to count every matter, time entry and ledger posting at the source before anything is mapped to the new system.

  2. Work in progress and receivables

    Unbilled time and disbursements, draft bills at the prebill stage and unpaid invoices are all open at once on any given day. Each needs a decision: bill it out of Expert before cutover, or carry it across as an opening balance or as live entries. For the largest matters that choice is made one by one.

  3. Rates, timekeepers and billing rules

    Expert Rates governs which rate applies to a timekeeper on a given client or matter, and billing carries client-specific rules and bill layouts. A smaller practice system usually has one rate table and a handful of invoice templates. Rate history is mapped where it has a home and listed where it does not, so nobody finds out from a wrong invoice.

  4. Customisations written for the firm

    Many Expert firms have custom fields, workflows, inquiries and reports built up over the years, and integrations feeding a document management system or CRM. Aderant itself talks about firms keeping their customisations when they change hosting. None of that carries into a different product by default, so each one is listed and the firm decides which are rebuilt.

  5. Trust and the general ledger

    Trust, accounts payable, tax and the general ledger run inside Expert. If the destination has trust accounting, balances are loaded per matter and agreed to the bank reconciliation. If it has no general ledger, the firm needs an accounting package beside it, and the closing trial balance goes there.

More about moving off Aderant Expert

Where it is going

Loading a firm into Litify is done inside a Salesforce environment that has been configured for that firm, normally by Litify or one of its implementation partners. The data work fits around that project. Old records are mapped to parties, roles, intakes and matters and loaded into the Salesforce objects behind them, and documents are loaded separately and attached.

  1. The design comes first

    Case types, stages and page layouts are decided during discovery, before any load. A load into a half-configured environment has to be repeated when a field changes. The data mapping is written against the agreed design and updated whenever the design moves, so the two stay in step.

  2. One party, many roles

    Contacts from the old system become parties, and each appearance on a matter becomes a role. Duplicate contacts turn into duplicate parties with their roles divided between them. Duplicates are merged before the load where they can be identified, since separating them afterwards means pointing every role at the right party again.

  3. Open enquiries load as intakes

    Leads and enquiries that have not signed belong in intakes, not matters. They are loaded with their source and status so that conversion reports start from a true position. Old declined enquiries are loaded only if the firm wants them for conflict checking, and are marked so they do not count as live.

  4. Documents load after records

    Files are loaded into the document component once the matters exist, because each one is attached to a matter record. Folder structure is set per case type beforehand. Large injury files with medical records and video take time to transfer, and that time is planned into the cutover weekend.

  5. Validation rules reject bad rows

    A configured environment enforces required fields and validation rules, and old data seldom satisfies all of them. Rows that fail are reported by the load. They are fixed in the source and run again, or the rule is relaxed for migrated records, and the firm decides which for each rule.

More about moving into Litify

How NewLaw runs it

Four steps, in this order.

Financial records move on this route, so the balances are rehearsed before the real cutover. The maker of Litify says that it, or its partners, load firms into the product. Where the firm uses that service, NewLaw’s part is the work around it: the analysis, the clean-up in Aderant Expert and checking each trial against Aderant Expert.

  1. Analysis

    We read what Aderant Expert holds and how its records link, then agree with you, field by field, where each piece will sit in Litify. 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 Expert, before extraction. It is not always possible to find every one, so some may carry across.

  3. Trial load

    The data is loaded into Litify as a trial and checked against Aderant Expert: record counts, financial totals, the links between records, document dates. Exceptions are listed for you to decide.

  4. Cutover

    Changes in Aderant Expert are frozen for an agreed window, the data is collected a final time and Litify 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 Expert as at the cutover date. Aderant Expert 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 Expert 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 Expert
Moving toLitify

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 Expert holds

    What is in it, how its records link, and where each piece would sit in Litify. 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 Litify

Loaded data is not yet a working system. The maker of Litify runs or arranges the set-up of its product, so this is what has to be decided and put in place in Litify, whoever does the work, before people rely on it from the first day.

A Litify implementation is a configuration project on Salesforce, run by Litify or an implementation partner with the firm’s own project team. Discovery sessions with each department come first. The decisions that follow shape the system: what an intake asks, how a matter moves through its stages, who sees what, and which other systems are connected.

Set-up decisions in Litify

  • Define intake questionnaires and the rules for conversion
  • Set case types, matter stages and page layouts
  • Build matter plans that create tasks at each stage
  • Design document folders and generation templates per case type
  • Configure user roles and sharing for restricted matters
  • Decide on timekeeping, billing and accounting integrations

Questions

Aderant Expert to Litify: what firms ask

Can we keep our client and matter numbers?

Usually, yes. Expert client and matter numbers are read from the database as they are, and most destinations let a matter number be set on import. Where the new system insists on its own numbering, the Expert number is kept in a reference field so old bills and correspondence can still be traced.

How much billing history should we bring across?

That depends on what the destination can hold and what your accounts team needs to look up. Open matters with their unbilled time and unpaid invoices come first. Paid bills from closed matters are often better left in the Expert database, kept read only, with summary balances carried forward.

We use a separate document management system with Expert. Does that move too?

It is a separate piece of work. Expert holds the financial and matter record, and the documents live in whatever store the firm pairs with it. The matter numbers are the link between the two, so they are checked together even when the document store moves on its own timetable.

Do trust balances in Aderant Expert have a place in Litify?

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 Expert before the plan is fixed. If Litify 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 Expert have a place in Litify?

Most of it does on paper. Emails, notes, trust ledgers and the firm’s accounts 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 Litify is kept as a readable archive, and you see which before the move.

What has to be decided before Aderant Expert data is loaded into Litify?

Billing records, custom fields and templates are carried with mapping, so each mapping is agreed with you first. Emails, notes, trust ledgers and the firm’s accounts 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 Expert and Litify are the names and marks of their owners, used here only to identify the two systems.

Moving from Aderant Expert to Litify?

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

We reply within one business day.