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

Data migration route

Aderant Expert Sierra to Litify migration

Aderant Expert Sierra is a cloud 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 Expert SierraCloud
  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 Sierra to Litify

Each row is a kind of record Aderant Expert Sierra 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 Sierra and their place in Litify
RecordIn Aderant Expert SierraIn LitifyWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldClient, matter and case management, with conflicts checks at file opening.Has a placeMatters, by case type.Carried across
ContactsClients, other parties and referrersHeldClients and case contacts, as in on-premises Expert.Has a placeLoaded as parties and connected by roles.Carried across
DocumentsFiles stored in or linked from the systemHeld in partDocument creation is automated; storage is usually an integrated 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 partKey dates through the case management application.Has a placeCalendar events on the matter.Carried across
TasksTo-dos and workflow steps assigned to peopleHeld in partWorkflows built and deployed by the firm route work for review.Has a placeCarried across
Time and expensesTime and expense entries, billed and unbilledHeldTime and expense entry on any device, checked against client guidelines.Has a placeTime entries on the matter.Carried across
BillingInvoices, payments and debtor balancesHeldPaperless prebilling, bills, rates and alternative fee arrangements.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 sits with AP, AR and the general ledger.To be confirmedConfirmed in the analysis
Firm accountsGeneral ledger, office account and payablesHeldGeneral ledger, payables and receivables, including Sierra-only applications.To be confirmedConfirmed in the analysis
Custom fieldsFields and record types the firm added itselfHeldAderant says firm customisations carry over from on-premises Expert.Has a placeCustom fields are created before loading.Carried with mapping
TemplatesPrecedents, document templates and automationHeld in partBill formats and automated document creation.Has a place in partTemplates are rebuilt in Litify’s document generation.Carried with mapping
IntakeLeads, enquiries, intake forms and pipelinesHeld in partAutomated client intake and conflicts checks.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 Sierra.
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 Sierra 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 Sierra, and kept as the record of what was billed and held.

Both are hosted by their makers, so nothing is collected from the firm’s office. What can be taken out of Aderant Expert Sierra depends on its export tools and on what its maker provides on request, and that is confirmed during the analysis, before a date is set. The subscription to Aderant Expert Sierra is kept running until the checks on Litify are finished.

Where the data is now

Moving off Sierra is a finance system move, the same in substance as leaving Expert, with one practical difference. The database is in Aderant’s hosting, not in the firm’s server room, so the first step is agreeing with Aderant what copy or extract of the firm’s data will be supplied and in what form. Everything after that depends on what arrives.

  1. The data is hosted

    Because Aderant operates the environment, the firm’s access to the underlying database is whatever the service provides. What can be obtained, whether a database copy, an export or report output, is settled early and written into the analysis before any field mapping starts.

  2. Sierra-only finance applications

    Firms using Aderant General Ledger, Accounts Receivable or Analytics have records in applications that on-premises Expert firms do not run. Cash application history and ledger detail held there are identified separately, so receivables and the trial balance are taken from the right place.

  3. Proformas in mid-cycle

    Billing runs through paperless prebills that sit with partners for review. At cutover some will be half edited. A cut-off date is agreed with the billing team so each proforma is either posted as a bill in Sierra or returned to unbilled time and carried across in that state.

  4. Integrations around it

    Sierra is rarely alone. Time capture tools, e-billing delivery, a document management system and a CRM are commonly wired to it through workflows and integrations. Each feed is listed with what it sends and receives, because the new system has to take over those connections or the firm has to drop them.

More about moving off Aderant Expert Sierra

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 Sierra and checking each trial against Aderant Expert Sierra.

  1. Analysis

    We read what Aderant Expert Sierra 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 Sierra, 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 Sierra: record counts, financial totals, the links between records, document dates. Exceptions are listed for you to decide.

  4. Cutover

    Changes in Aderant Expert Sierra 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 Sierra as at the cutover date. Aderant Expert Sierra 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 Sierra 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 Sierra
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 Sierra 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 Sierra to Litify: what firms ask

Is leaving Sierra different from leaving on-premises Expert?

The records are the same kind: matters, time, bills, trust and ledgers in the Expert structure. Access is the difference. On your own server the database can be copied directly. In Sierra the data is in Aderant’s hosting, so the form of the extract is agreed with Aderant first.

What happens to trust balances at cutover?

Trust is loaded as a balance per matter, with enough transaction history to explain it, and then agreed to the Sierra trust ledger and the bank reconciliation as at the cutover date. That step is rehearsed on a full trial load beforehand, because it cannot simply be run again after go-live.

Can the old system stay available afterwards?

A read only fall-back is part of the method, but a hosted system only stays available while the service does. How the firm’s Sierra data is kept after the move, as continued access for a period or as a copy of the data, is confirmed with Aderant during the analysis.

Do trust balances in Aderant Expert Sierra 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 Sierra 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 Sierra 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 Sierra 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 Sierra and Litify are the names and marks of their owners, used here only to identify the two systems.

Moving from Aderant Expert Sierra 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.