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

Data migration route

Aderant Expert Sierra to iManage Cloud migration

Aderant Expert Sierra is a cloud practice management system, and iManage Cloud is a cloud document management system. Documents and email move, filed under the matters they came from. Time, billing and trust have no place in a document system.

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

What moves

What moves from Aderant Expert Sierra to iManage Cloud

Each row is a kind of record Aderant Expert Sierra holds, whether iManage Cloud has a place for it, and what is planned. On this route one kind of record carries across, three kinds need mapping, eight kinds have no place in iManage Cloud and are archived and two kinds are confirmed in the analysis.

Records in Aderant Expert Sierra and their place in iManage Cloud
RecordIn Aderant Expert SierraIn iManage CloudWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldClient, matter and case management, with conflicts checks at file opening.Has a place in partAs a workspace with client and matter metadata. Parties and status stay in practice management.Carried with mapping
ContactsClients, other parties and referrersHeldClients and case contacts, as in on-premises Expert.No placeKept as a readable archive
DocumentsFiles stored in or linked from the systemHeld in partDocument creation is automated; storage is usually an integrated DMS.Has a placeEach needs a workspace and valid client and matter values; its class sets default security.Carried across
EmailsEmails saved to matters or to the storeTo be confirmedHas a placeLoaded as email documents into the workspace’s email folders.Confirmed in the analysis
NotesFile notes, matter notes and contact notesTo be confirmedNo placeFile notes can be loaded as documents on the matter.Confirmed in the analysis
CalendarAppointments, court dates and deadlinesHeld in partKey dates through the case management application.No placeKept as a readable archive
TasksTo-dos and workflow steps assigned to peopleHeld in partWorkflows built and deployed by the firm route work for review.No placeiManage Tracker is a separate product with its own set-up.Kept as a readable archive
Time and expensesTime and expense entries, billed and unbilledHeldTime and expense entry on any device, checked against client guidelines.No placeKept as a readable archive
BillingInvoices, payments and debtor balancesHeldPaperless prebilling, bills, rates and alternative fee arrangements.No placeKept as a readable archive
Trust moneyTrust or client account ledgers and balancesHeldTrust management sits with AP, AR and the general ledger.No placeKept as a readable archive
Firm accountsGeneral ledger, office account and payablesHeldGeneral ledger, payables and receivables, including Sierra-only applications.No placeKept as a readable archive
Custom fieldsFields and record types the firm added itselfHeldAderant says firm customisations carry over from on-premises Expert.Has a place in partA fixed number of custom profile fields, each a validated list.Carried with mapping
TemplatesPrecedents, document templates and automationHeld in partBill formats and automated document creation.Has a place in partPrecedents load as documents. Automation is rebuilt in the firm’s drafting tools.Carried with mapping
IntakeLeads, enquiries, intake forms and pipelinesHeld in partAutomated client intake and conflicts checks.No placeKept as a readable archive

What the plans mean

Carried across
iManage Cloud has a place for this kind of record. It is loaded there and checked against Aderant Expert Sierra.
Carried with mapping
iManage Cloud 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
iManage Cloud 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 documents move. The accounts do not.

Moving from a matter system into a document management system is a documents job. iManage Cloud has no place for time, invoices or trust, so there is no financial cutover on this route. What it does want is structure. Every document from Aderant Expert Sierra is filed into a workspace or folder for its client and matter, with a profile that says what it is. The client and matter list becomes that structure, which is why it is cleaned before any file is copied.

A document’s own details count for more here than anywhere. Created and modified dates, author, document type and version become searchable profile fields, and a wrong date on a few thousand files is hard to undo. Email filed to matters is carried as messages. Document copies can be run again, so the trial is repeated until counts and dates agree. Matter data that iManage Cloud cannot hold goes to whatever replaces Aderant Expert Sierra for matters and billing, or into an archive.

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 iManage Cloud 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

Administrators of an iManage Cloud library have API access only, so nothing is loaded by writing to a database. For cloudimanage.com, the newer of its two cloud platforms, iManage lists a supervised import API, sync APIs and a metadata loader. Nothing can be filed loose: every document goes into a workspace, with valid client and matter values. So the client and matter lists, the workspace template and the security groups are built first.

  1. Client and matter lists first

    Custom1 and custom2 are validated lists, with each matter a child of its client. A value that is not already in the list cannot be assigned to a document. The lists are loaded from the practice management system or the old document store before any content, closed matters with documents included.

  2. One workspace per matter

    Each matter gets a workspace generated from a template, so the template is designed before migration: its tabs, its folders, which are created up front and which on demand. Old folder trees rarely match it. The mapping says where each old folder lands and what happens to folders with no equivalent.

  3. Authors must be known users

    Author and operator are profile fields tied to users of the library. Documents written by people who left years ago need a decision: recreate those people as inactive users, or assign a placeholder author. That choice affects searching by author for as long as the firm uses the system.

  4. Hybrid security

    iManage calls its security model hybrid: where a user’s groups disagree, the most permissive access applies unless one of them is denied. On cloudimanage.com that model cannot be changed. Default security is normally set on the workspace and inherited below it. Restricted matters from the old system are loaded with their access list already in place.

  5. New numbers, original dates

    Documents are numbered by iManage as they are loaded, so old numbers do not carry over as numbers. On cloudimanage.com the file date setting is fixed to the file’s own date, and on imanage.work it can be set either way. Which dates display is checked on the trial load. The old reference can be carried in a custom field or the description where the firm wants to search by it.

More about moving into iManage Cloud

How NewLaw runs it

Four steps, in this order.

Nothing financial lands in iManage Cloud on this route, which makes it repeatable: a load can be run again until it is right.

  1. Analysis

    We read what Aderant Expert Sierra holds and how it is organised, then agree with you where each kind of record will sit in iManage Cloud. Anything with no place there stays behind or is archived, and you see which before the move.

  2. Clean-up

    Duplicate clients, matters and folders are merged where they can be identified, and naming is put into one format, before anything is copied. It is not always possible to find every one, so some may carry across.

  3. Trial load

    A trial is loaded into iManage Cloud and checked against Aderant Expert Sierra: record and file counts, the links between records, document dates, and a sample opened by your own people. Exceptions are listed for you to decide.

  4. Cutover

    There is no financial cutover on this route. After a short freeze on changes in Aderant Expert Sierra, a final pass over a weekend picks up what changed since the trial. 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 toiManage Cloud

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 iManage Cloud. 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 iManage Cloud

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

Setting up iManage Cloud is mostly design work done before any user logs in: how many libraries, what a workspace looks like, which profile fields are captioned for what, and who can see which matters. Then come the links that keep it running day to day, such as creating a workspace when a matter is opened in the practice management system, and the add-ins on each desk.

Set-up decisions in iManage Cloud

  • Library structure and captions for client, matter and other fields
  • Workspace templates, folder names and Flexible Folders rules by practice area
  • Document classes, subclasses and the profile fields each one requires
  • Roles, groups, default security and walls for restricted matters
  • Workspace creation fed from the practice management system’s matter list
  • Work Desktop, Outlook email filing and Mobility on each device, with training

Questions

Aderant Expert Sierra to iManage Cloud: 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 iManage Cloud?

No. iManage Cloud does not keep trust ledgers. Trust records from Aderant Expert Sierra are exported as ledgers and statements that open without it, and the firm settles where its trust accounting runs from the cutover date before the move is planned.

What happens to records iManage Cloud has no place for?

On this route that is contacts, calendar entries, tasks, time entries, billing records, trust ledgers, 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 iManage Cloud?

Matters, 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 decides which closed matters and how many versions of a document are in scope.

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

Moving from Aderant Expert Sierra to iManage Cloud?

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

We reply within one business day.