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

Data migration route

Aderant Expert Sierra to Clio Manage migration

Aderant Expert Sierra and Clio Manage are each a cloud practice management system. Both run a whole practice, so this is a full move, and the financial records set the timetable.

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 with mapping
  7. Billing: Carried with mapping
  8. Trust money: 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
ToClio ManageCloud
  1. Firm accounts: Kept as a readable archive
  2. Intake: Kept as a readable archive
Readable archiveNo place in Clio Manage
  • 5 carried
  • 5 mapped
  • 2 to confirm
  • 2 archived
What the two products hold. The analysis confirms it field by field.

What moves

What moves from Aderant Expert Sierra to Clio Manage

Each row is a kind of record Aderant Expert Sierra holds, whether Clio Manage has a place for it, and what is planned. On this route five kinds of record carry across, five kinds need mapping, two kinds have no place in Clio Manage and are archived and two kinds are confirmed in the analysis.

Records in Aderant Expert Sierra and their place in Clio Manage
RecordIn Aderant Expert SierraIn Clio ManageWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldClient, matter and case management, with conflicts checks at file opening.Has a placeImported from a matters template, after contacts.Carried across
ContactsClients, other parties and referrersHeldClients and case contacts, as in on-premises Expert.Has a placePeople and companies, with related contacts linked to matters by a separate template.Carried across
DocumentsFiles stored in or linked from the systemHeld in partDocument creation is automated; storage is usually an integrated DMS.Has a placeFiled under the matter; Clio scopes document migration separately from data.Carried across
EmailsEmails saved to matters or to the storeTo be confirmedHas a placeHeld as communications on the matter, with phone logs.Confirmed in the analysis
NotesFile notes, matter notes and contact notesTo be confirmedHas a placeMatter notes and contact notes each have a template.Confirmed in the analysis
CalendarAppointments, court dates and deadlinesHeld in partKey dates through the case management application.Has a placeCalendar events have a migration template.Carried across
TasksTo-dos and workflow steps assigned to peopleHeld in partWorkflows built and deployed by the firm route work for review.Has a placeTasks have a migration template.Carried across
Time and expensesTime and expense entries, billed and unbilledHeldTime and expense entry on any device, checked against client guidelines.Has a place in partUnbilled time entries load; billed time entries do not, by Clio’s migration guide.Carried with mapping
BillingInvoices, payments and debtor balancesHeldPaperless prebilling, bills, rates and alternative fee arrangements.Has a place in partAn outstanding balance loads as one line per matter; past invoices do not.Carried with mapping
Trust moneyTrust or client account ledgers and balancesHeldTrust management sits with AP, AR and the general ledger.Has a place in partA trust balance loads as one line per matter or contact; past transactions do not.Carried with mapping
Firm accountsGeneral ledger, office account and payablesHeldGeneral ledger, payables and receivables, including Sierra-only applications.No placeNot in Clio Manage. Books sit in a linked accounting package, or in Clio Accounting where Clio offers it.Kept as a readable archive
Custom fieldsFields and record types the firm added itselfHeldAderant says firm customisations carry over from on-premises Expert.Has a placeCreated first, then filled from the custom field templates.Carried with mapping
TemplatesPrecedents, document templates and automationHeld in partBill formats and automated document creation.Has a placeRebuilt as Clio document templates with its merge fields.Carried with mapping
IntakeLeads, enquiries, intake forms and pipelinesHeld in partAutomated client intake and conflicts checks.No placeLeads and intake forms belong in Clio Grow.Kept as a readable archive

What the plans mean

Carried across
Clio Manage has a place for this kind of record. It is loaded there and checked against Aderant Expert Sierra.
Carried with mapping
Clio Manage 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
Clio Manage has no place for it. It is exported in a format that opens without Aderant Expert Sierra 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 Expert Sierra and Clio Manage 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 Expert Sierra’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.

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 Clio Manage 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

Clio Manage is loaded through its migration templates, one spreadsheet per kind of record, imported in a fixed order with contacts first. Clio’s own migration guide is plain about the limit: balances come across, financial history does not. So a load into Clio is planned as records plus opening positions, with the old system kept for the history behind them.

  1. Matters link by client name

    The matters template ties each matter to its client by an exact match on first name, last name or company name. A client spelt two ways in the old system becomes two contacts, or a matter assigned to an unknown client. This is why contact clean-up is finished before the first trial load, not after it.

  2. Decide the numbering scheme first

    Clio numbers imported matters itself unless the account is set to manual numbering, in which case the old number is supplied in the template. That setting and the firm’s preferred scheme are decided before any matter is loaded. The Client Reference field is available for an old file number the firm still wants to see.

  3. Balances, one line each

    Under Clio’s standard migration, an outstanding balance arrives as one line per matter and a trust balance as one line per matter or contact. Past invoices, billed time, payments and trust transactions are listed as data that cannot be migrated. The trust total is reconciled against the old system’s closing report on the trial load.

  4. Custom fields must exist

    Matter and contact custom fields are created in Clio before their values are imported, each with a field type. Accounts set up for a particular practice area come with preconfigured fields and matter templates, which affects the mapping. We compare those with the old system’s fields and add only what is missing.

  5. Rates and permissions by hand

    Billable rates for users, clients and matters are not part of an import. Neither are user permissions or settings. They are entered in Clio during set-up from a schedule the firm confirms, and a sample of imported unbilled time is checked against that schedule before the trial load is signed off.

More about moving into Clio Manage

How NewLaw runs it

Four steps, in this order.

Trust money moves on this route, so the trust cutover gets a rehearsal of its own.

  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 Clio Manage. 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 Clio Manage as a trial and checked against Aderant Expert Sierra: record counts, trust and debtor 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 Clio Manage goes live over a weekend. The trust and financial cutover is rehearsed on a full trial load first, because it cannot be re-run the way a document load can. 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 toClio Manage

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 Clio Manage. 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 Clio Manage

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

Much of a Clio Manage set-up is firm-wide settings. The numbering scheme, practice areas, matter stages, billing preferences and trust accounts apply to everyone, so they are agreed once and early. Trust and accounting features are not the same in every country Clio sells in, so the firm’s own region is checked first. Document templates and custom fields follow. Email and document integrations are then installed for each user and tested on a real matter.

Set-up decisions in Clio Manage

  • Matter numbering scheme, practice areas and matter stages
  • Custom fields for matters and contacts, by practice area
  • Document templates with merge fields, uploaded from Word or PDF
  • Billing settings, user and client rates, and trust accounts
  • Roles and permissions for each user
  • Outlook add-in, Clio Drive and the accounting connection

Questions

Aderant Expert Sierra to Clio Manage: 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 Clio Manage?

In part. A trust balance loads as one line per matter or contact; past transactions do not. The analysis sets out which trust records have a place in Clio Manage and which are kept as an archive, and the trust cutover is rehearsed on a full trial load before the real one.

What happens to records Clio Manage has no place for?

On this route that is the firm’s accounts and intake records. They are exported from Aderant Expert Sierra 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 Expert Sierra data is loaded into Clio Manage?

Time entries, billing records, trust ledgers, custom fields and templates are carried with mapping, so each mapping is agreed with you first. Emails and notes 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 Clio Manage are the names and marks of their owners, used here only to identify the two systems.

Moving from Aderant Expert Sierra to Clio Manage?

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

We reply within one business day.