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

Data migration route

Aderant Expert to SharePoint migration

Aderant Expert is a server-based practice management system, and SharePoint is cloud file storage. Documents move into a folder for each client and matter, and the data behind them is kept as an export.

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

What moves

What moves from Aderant Expert to SharePoint

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

Records in Aderant Expert and their place in SharePoint
RecordIn Aderant ExpertIn SharePointWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldClients and matters, with file opening and conflicts checking.Has a place in partAs a site, library, folder or list row the firm designs; no built-in matter record.Carried with mapping
ContactsClients, other parties and referrersHeldClients and the contacts attached to cases in Expert Case.Has a place in partOnly as rows in a list built for the purpose.Carried with mapping
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 placeFiles in libraries, with columns and versions.Carried across
EmailsEmails saved to matters or to the storeTo be confirmedHas a place in partAs .msg or .eml files, with columns for sender and date if set up.Confirmed in the analysis
NotesFile notes, matter notes and contact notesTo be confirmedHas a place in partAs documents, or as rows in a notes list if one is built.Confirmed in the analysis
CalendarAppointments, court dates and deadlinesHeld in partExpert Case tracks key dates and links to Outlook and Exchange calendars.Has a place in partPossible as a list; usually left in Outlook.Carried with mapping
TasksTo-dos and workflow steps assigned to peopleHeld in partTask management in Expert Case, plus firm-built workflows.Has a place in partPossible as a list; no legal workflow built in.Carried with mapping
Time and expensesTime and expense entries, billed and unbilledHeldExpert Time and Expert Expenses, with work in progress by matter.No placeKept as a readable archive
BillingInvoices, payments and debtor balancesHeldPrebills, bills, rates, collections and accounts receivable.No placeKept as a readable archive
Trust moneyTrust or client account ledgers and balancesHeldTrust management is listed among its accounting applications.No placeKept as a readable archive
Firm accountsGeneral ledger, office account and payablesHeldGeneral ledger, accounts payable, tax and disbursements.No placeKept as a readable archive
Custom fieldsFields and record types the firm added itselfHeldAderant describes firm-specific customisations held alongside the standard data.Has a placeColumns and content types on libraries and lists.Carried with mapping
TemplatesPrecedents, document templates and automationHeld in partDocument assembly in Expert Case; bill layouts in billing.Has a place in partPrecedents as files; templates can be offered from a library.Carried with mapping
IntakeLeads, enquiries, intake forms and pipelinesHeld in partClient and matter intake with conflicts checks, not a marketing pipeline.No placeKept as a readable archive

What the plans mean

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

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. SharePoint 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

SharePoint will take a firm’s documents in almost any arrangement, which is the difficulty. The structure has to be chosen before the load: what a client is, what a matter is, and where security is applied. Changing it afterwards means moving every file again. Most of the effort goes into that design and into the columns that describe each document.

  1. Site, library or folder per matter

    A matter can be a site, a library within a client site, or a folder in one large library. Each choice has consequences for permissions, for search and for how a new matter is opened. The firm makes that decision, and the people who open matters every day should be part of it.

  2. Columns are built before content

    If documents are to carry matter number, client, document type or author as columns, those columns and any content types exist before loading, so each file can be tagged as it arrives. Tagging hundreds of thousands of documents afterwards is a second project that seldom gets finished.

  3. The 400 character path

    SharePoint limits the full decoded path, site and library and folders and file name, to 400 characters. A deep tree copied from a server drive under a long site name can cross it. Path lengths are calculated against the planned structure, not the old one, before any file moves.

  4. Large libraries and the view threshold

    A library can hold millions of files, but a view that tries to show more than 5,000 items at once runs into the list view threshold. One flat library with a folder per matter needs indexed columns and filtered views from the start, or views begin to fail as the library fills.

  5. Security by library, not by file

    Microsoft supports up to 50,000 unique permissions in a library and recommends staying under 5,000. Restricting matters one folder at a time reaches that sooner than firms expect. Restricted work is better grouped into its own site or library, so the permission is set once.

More about moving into SharePoint

How NewLaw runs it

Four steps, in this order.

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

  1. Analysis

    We read what Aderant Expert holds and how it is organised, then agree with you where each kind of record will sit in SharePoint. 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 SharePoint and checked against Aderant Expert: 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, a final pass over a weekend picks up what changed since the trial. 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 toSharePoint

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 SharePoint. 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

SharePoint is 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.

Making SharePoint work as a firm’s document store is a design and build job in its own right. The sites, libraries, columns and permission groups are created, a way of opening a new matter is put in place so the structure repeats itself, and the Outlook and Teams habits around it are agreed. Search is tested with real questions from fee earners.

What is agreed and set up

  • Site and library structure for clients and matters
  • Columns and content types for matter number and document type
  • Permission groups, with restricted matters in their own libraries
  • A repeatable way to create each new matter’s workspace
  • Version history limits and retention labels for closed matters
  • Views, indexed columns and search tested on loaded data

Questions

Aderant Expert to SharePoint: 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 SharePoint?

No. SharePoint does not keep trust ledgers. Trust records from Aderant Expert 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 SharePoint has no place for?

On this route that is time entries, billing records, trust ledgers, the firm’s accounts and intake records. They are exported from Aderant Expert 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 data is loaded into SharePoint?

Matters, contacts, calendar entries, tasks, 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 and SharePoint are the names and marks of their owners, used here only to identify the two systems.

Moving from Aderant Expert to SharePoint?

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

We reply within one business day.