Data migration route
Aderant Expert Sierra to Filevine migration
Aderant Expert Sierra is a cloud practice management system, and Filevine is a cloud case management system. Matter records move into cases, and the firm decides where its accounting runs from the cutover date.
Aderant Expert SierraCloud- Matters: Carried across
- Contacts: Carried across
- Documents: Carried across
- Calendar: Carried across
- Tasks: Carried across
- Time and expenses: Carried with mapping
- Billing: Carried with mapping
- Trust money: Carried with mapping
- Custom fields: Carried with mapping
- Templates: Carried with mapping
- Intake: Carried with mapping
- Emails: Confirmed in the analysis
- Notes: Confirmed in the analysis
- Firm accounts: Confirmed in the analysis
FilevineCloud- 5 carried
- 6 mapped
- 3 to confirm
What moves
What moves from Aderant Expert Sierra to Filevine
Each row is a kind of record Aderant Expert Sierra holds, whether Filevine has a place for it, and what is planned. On this route five kinds of record carry across, six kinds need mapping and three kinds are confirmed in the analysis.
| Record | What is planned | ||
|---|---|---|---|
| MattersMatters or cases, with their numbers, types, parties and status | HeldClient, matter and case management, with conflicts checks at file opening. | Has a placeLoaded as projects of a defined project type. | Carried across |
| ContactsClients, other parties and referrers | HeldClients and case contacts, as in on-premises Expert. | Has a placeContact cards, linked to projects. | Carried across |
| DocumentsFiles stored in or linked from the system | Held in partDocument creation is automated; storage is usually an integrated DMS. | Has a placeDocs section with folders. Templated project folders can be set per type. | Carried across |
| EmailsEmails saved to matters or to the store | To be confirmed | Has a placeHeld in the activity feed of the project. | Confirmed in the analysis |
| NotesFile notes, matter notes and contact notes | To be confirmed | Has a placeHeld as notes in the activity feed. | Confirmed in the analysis |
| CalendarAppointments, court dates and deadlines | Held in partKey dates through the case management application. | Has a placeDeadlines and calendar events. | Carried across |
| TasksTo-dos and workflow steps assigned to people | Held in partWorkflows built and deployed by the firm route work for review. | Has a place | Carried across |
| Time and expensesTime and expense entries, billed and unbilled | HeldTime and expense entry on any device, checked against client guidelines. | Has a place in partNeeds the Billing product enabled. | Carried with mapping |
| BillingInvoices, payments and debtor balances | HeldPaperless prebilling, bills, rates and alternative fee arrangements. | Has a place in partNeeds the Billing product enabled. | Carried with mapping |
| Trust moneyTrust or client account ledgers and balances | HeldTrust management sits with AP, AR and the general ledger. | Has a place in partTrust accounts sit in Payments by Filevine. Loading history is confirmed in the analysis. | Carried with mapping |
| Firm accountsGeneral ledger, office account and payables | HeldGeneral ledger, payables and receivables, including Sierra-only applications. | To be confirmed | Confirmed in the analysis |
| Custom fieldsFields and record types the firm added itself | HeldAderant says firm customisations carry over from on-premises Expert. | Has a placeCustom sections and fields per project type. | Carried with mapping |
| TemplatesPrecedents, document templates and automation | Held in partBill formats and automated document creation. | Has a place in partTemplates are rebuilt as Filevine document templates. They are not converted. | Carried with mapping |
| IntakeLeads, enquiries, intake forms and pipelines | Held in partAutomated client intake and conflicts checks. | Has a place in partLeads belong in Lead Docket, which passes signed clients to Filevine. | Carried with mapping |
What the plans mean
- Carried across
- Filevine has a place for this kind of record. It is loaded there and checked against Aderant Expert Sierra.
- Carried with mapping
- Filevine 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 Filevine. 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 Filevine, and that choice drives which fields and workflows it gets. The mapping is agreed type by type. Financial history with no place in Filevine 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 Filevine are finished.
Where the data is now
Leaving Aderant Expert Sierra
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.
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.
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.
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.
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.
Where it is going
Arriving in Filevine
Loading a firm into Filevine depends on the project types being built first. Until the sections and fields exist there is nowhere for the data to go, so configuration and migration are planned together. The old system’s parties, insurers, providers and key dates are mapped to sections, and its notes and emails are loaded into each project’s activity feed.
Project types before data
Each area of practice needs a project type with its sections, fields and phases defined in the Customs Editor. Changes made there apply to every project of that type. The types are drafted from the old system’s data, tested with a few real cases, and only then is the bulk load run.
One contact card per person
Contacts are held as contact cards. A doctor or adjuster who appears on many projects is best loaded as one card, not one for each project. Duplicates in the old system are merged before loading where they can be identified. Loading them as they are produces several cards for the same person, and staff then pick the wrong one when adding a party.
Lists become collection items
Anything the old system held as a list against a matter, such as providers, liens, insurance policies or expenses, is loaded as items in a collection section. Each column needs a matching field. Totals per project are compared with the old system afterwards, since those figures feed the settlement and disbursal sheets.
History goes into the feed
File notes, emails and completed tasks from the old system are loaded into the activity feed with their original dates and authors. Authors must exist as users or be recorded in the text. The feed is long on an old case, so staff are shown how to filter it before go-live.
Billing is a separate switch
The Billing section only appears once Billing is enabled for the firm. Time entries, invoices and trust balances from the old system need that in place before they can be loaded. A firm that leaves it off can still record case costs in a collection section built for the purpose.
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.
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 Filevine. Anything with no place there comes across as a note or stays behind, and you see which before the move.
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.
Trial load
The data is loaded into Filevine 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.
Cutover
Changes in Aderant Expert Sierra are frozen for an agreed window, the data is collected a final time and Filevine 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
What happens after you send it
- A free first call
We go through your answers with you and ask about anything they leave open.
- An analysis of what Aderant Expert Sierra holds
What is in it, how its records link, and where each piece would sit in Filevine. Anything with no place there comes across as a note or stays behind, and you see which before the move.
- 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 Filevine
Loaded data is not yet a working system. This is what NewLaw sets up in Filevine, beyond the migration, so that people can work in it from the first day.
Filevine arrives as a platform to be configured, and most of the implementation is design. Someone has to decide what a project looks like for each kind of work the firm does, what moves it from one phase to the next, and who can see what. Those decisions are made with the people who run the files, then built and tested.
Set-up decisions in Filevine
- Design project types, sections and fields for each practice area
- Define phases and the tasks each phase should trigger
- Build document templates that fill from project fields
- Set teams, permissions and protected sections for restricted matters
- Decide whether Billing and Payments are switched on
- Connect Lead Docket so signed leads become projects
Questions
Aderant Expert Sierra to Filevine: 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 Filevine?
In part. Trust accounts sit in Payments by Filevine. Loading history is confirmed in the analysis. The analysis sets out which trust records have a place in Filevine and which are kept as an archive, and the trust cutover is rehearsed on a full trial load before the real one.
Does everything in Aderant Expert Sierra have a place in Filevine?
Most of it does on paper. Emails, notes 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 Filevine 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 Filevine?
Time entries, billing records, trust ledgers, custom fields, templates and intake records are carried with mapping, so each mapping is agreed with you first. Emails, notes 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.
Other routes
Other routes from Aderant Expert Sierra and into Filevine
Other destinations from Aderant Expert Sierra
Other systems that move into Filevine
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.
Choose your systems
Technology stack selection
Decide which practice management system your firm runs, with the evidence and the cost beside it.
About four weeks for a firm of about 15 people. Fixed price, set after a free first call.
Move your data
Data migration
Your data is cleaned up before anything moves, then a trial load is checked against the old system.
Fixed price, agreed after the analysis.
Set up your new system
Implementation
Your new system set up around the way your firm works: configuration, document automation and training.
A small firm of 1 to 10 users typically takes 4 to 8 weeks. A mid-sized firm of 10 to 50 users takes 8 to 16 weeks.
Put AI to work
AI advisory and enablement
A small group of your people learn to use an approved AI tool on real work, under written rules.
Two to four weeks for a small first group. Fixed price, set after a free first call.
Aderant Expert Sierra and Filevine are the names and marks of their owners, used here only to identify the two systems.
Moving from Aderant Expert Sierra to Filevine?
Tell us what you are moving. You get a plan and a fixed price after the analysis.
We reply within one business day.