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

Data migration route

Aderant Expert Sierra to Server drives migration

Aderant Expert Sierra is a cloud practice management system, and Server drives are plain files on equipment the firm controls. Documents move into a folder for each client and matter, and the data behind them is kept as an export.

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

What moves

What moves from Aderant Expert Sierra to Server drives

Each row is a kind of record Aderant Expert Sierra holds, whether Server drives have a place for it, and what is planned. On this route one kind of record carries across, one kind needs mapping, ten kinds have no place in Server drives and are archived and two kinds are confirmed in the analysis.

Records in Aderant Expert Sierra and their place in Server drives
RecordIn Aderant Expert SierraIn Server drivesWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldClient, matter and case management, with conflicts checks at file opening.No placeA matter becomes a folder; its details survive only in an index file.Kept as a readable archive
ContactsClients, other parties and referrersHeldClients and case contacts, as in on-premises Expert.No placeCan be kept only as an exported spreadsheet.Kept 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 placeFiles in folders, named and dated during the load.Carried across
EmailsEmails saved to matters or to the storeTo be confirmedHas a place in partAs .msg or .eml files in each matter’s correspondence folder.Confirmed in the analysis
NotesFile notes, matter notes and contact notesTo be confirmedHas a place in partAs a text or PDF file per matter, not as separate records.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 placeKept as a readable archive
Time and expensesTime and expense entries, billed and unbilledHeldTime and expense entry on any device, checked against client guidelines.No placeOnly as exported reports or spreadsheets.Kept as a readable archive
BillingInvoices, payments and debtor balancesHeldPaperless prebilling, bills, rates and alternative fee arrangements.Has a place in partInvoices as PDF files; no ledger.Kept as a readable archive
Trust moneyTrust or client account ledgers and balancesHeldTrust management sits with AP, AR and the general ledger.No placeOnly as exported ledger reports kept as files.Kept 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.No placeKept as a readable archive
TemplatesPrecedents, document templates and automationHeld in partBill formats and automated document creation.Has a place in partPrecedents as Word files; merge fields tied to the old system stop working.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
Server drives has a place for this kind of record. It is loaded there and checked against Aderant Expert Sierra.
Carried with mapping
Server drives 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
Server drives 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

Out of the system, into folders the firm can read.

File storage has folders and files and nothing else. Moving from Aderant Expert Sierra into Server drives means turning matters into a folder tree, usually client, then matter, then the folders used inside it. The naming rule is agreed first, because it is hard to change once thousands of folders exist: whether the matter number leads, how closed matters are separated, what happens to characters Server drives do not allow in a name.

Everything that is not a document needs somewhere to go. Contacts, notes, time, invoices and trust ledgers have no place in a folder, so they are exported as spreadsheets and reports and stored alongside, often as a summary file in each matter folder and a full set in an archive area. Firms choose this route to keep a readable copy of a system they are retiring, or as a staging step. The export is checked either way: folders against matters, files against the document register in Aderant Expert Sierra.

Aderant Expert Sierra is hosted by its maker and Server drives sit on equipment the firm controls. The data leaves a service that was backed up for the firm and arrives somewhere the firm must back up itself, so backup and access are arranged before the export is copied in. What Aderant Expert Sierra will release depends on its export tools, and that is confirmed in the analysis.

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

Some firms leave a practice or document system and keep their documents on a server drive, either as the working store or as the archive of a system being switched off. The files will arrive without the database that described them. Everything the firm wants to keep knowing about a document has to be put into its path, its name or an index file.

  1. Agree the tree and the names

    A fixed pattern is chosen, for example client name and number, then matter number and short description, then a standard set of subfolders. Document titles from the old system become file names. Where two documents share a title, a date or sequence number is added so nothing is overwritten.

  2. Budget the path length

    Share name, client, matter, subfolder and file name all count towards the 260 character limit that many Windows programs still apply. The pattern is tested against the firm’s longest client names and document titles before the load. Descriptions are trimmed by rule, never by cutting off the file extension.

  3. Dates have to be set deliberately

    A file written to the server today is dated today unless its modified date is set from the old system’s record. Document dates are how lawyers find things in a folder. Which date each file is to carry is agreed in the analysis, and the trial load checks a sample.

  4. Emails become message files

    Emails filed to matters in the old system are written out as .msg or .eml files in a correspondence folder, named by date, sender and subject so they sort in order. Attachments stay inside the message. Subjects with characters Windows forbids are cleaned, and long ones cut.

  5. Keep an index beside the files

    A spreadsheet or small database listing every document with its matter, author, original date, document type and new path is the only place the old system’s profile data survives. It lets someone find a document by something other than its name. What the index records, and who keeps it, is decided in the analysis.

More about moving into Server drives

How NewLaw runs it

Four steps, in this order.

Nothing financial lands in Server drives 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 Server drives. 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 Server drives 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 toServer drives

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 Server drives. 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

Structure, permissions and handover

Server drives are storage, not an application, so there is no product to configure. What is agreed and set up is the folder structure, who can open what, and how the result is handed to the firm.

A server drive does only what the firm and its IT provider make it do. Setting one up as a document store means building the share, deciding who can open which folders, and arranging the protections a document system would have supplied: backups, earlier versions and a way to recover a deleted folder. The filing rule is written down and taught.

What is agreed and set up

  • Share and top-level folders for clients, precedents and administration
  • Security groups and folder permissions, with restricted matters separate
  • Drive letter mapped for every user at sign-in
  • Backup schedule and shadow copies for earlier versions
  • Written naming rule for client, matter and document names
  • Read-only area for closed matters and archived system exports

Questions

Aderant Expert Sierra to Server drives: 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 Server drives?

No. Server drives do not keep trust ledgers. Only as exported ledger reports kept as files. 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 Server drives have no place for?

On this route that is matters, contacts, calendar entries, tasks, time entries, billing records, trust ledgers, the firm’s accounts, custom fields 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 Server drives?

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

Moving from Aderant Expert Sierra to Server drives?

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

We reply within one business day.