Data migration route
Aderant Expert data to Microsoft SQL Server
Aderant Expert is a server-based practice management system, and Microsoft SQL Server is a database on a server the firm runs. This is not a move to a new working system: the route writes out what Aderant Expert holds and keeps it readable and open to queries.
Aderant ExpertServer- Matters: Exported in full
- Contacts: Exported in full
- Calendar: Exported in full
- Tasks: Exported in full
- Time and expenses: Exported in full
- Billing: Exported in full
- Trust money: Exported in full
- Firm accounts: Exported in full
- Intake: Exported in full
- Documents: Exported with mapping
- Custom fields: Exported with mapping
- Templates: Exported with mapping
- Emails: Confirmed in the analysis
- Notes: Confirmed in the analysis
Microsoft SQL ServerServer- 9 carried
- 3 mapped
- 2 to confirm
What moves
What moves from Aderant Expert to Microsoft SQL Server
Each row is a kind of record Aderant Expert holds, whether Microsoft SQL Server has a place for it, and what is planned. On this route nine kinds of record carry across, three kinds need mapping and two kinds are confirmed in the analysis.
| Record | What is planned | ||
|---|---|---|---|
| MattersMatters or cases, with their numbers, types, parties and status | HeldClients and matters, with file opening and conflicts checking. | Has a placeA table of matters linked to clients, parties and fee earners. | Exported in full |
| ContactsClients, other parties and referrers | HeldClients and the contacts attached to cases in Expert Case. | Has a placePeople and companies, with their roles on each matter. | Exported in full |
| DocumentsFiles stored in or linked from the system | Held in partExpert Case assembles and tracks case documents; Aderant lists integration with a separate DMS. | Has a place in partAs files in folders with an index table; storing files in the database is possible. | Exported with mapping |
| EmailsEmails saved to matters or to the store | To be confirmed | Has a place in partAs message files with an index table, or as rows of header fields. | Confirmed in the analysis |
| NotesFile notes, matter notes and contact notes | To be confirmed | Has a placeRows of text linked to matters and contacts. | Confirmed in the analysis |
| CalendarAppointments, court dates and deadlines | Held in partExpert Case tracks key dates and links to Outlook and Exchange calendars. | Has a placeRows of appointments and key dates; nothing displays them as a calendar. | Exported in full |
| TasksTo-dos and workflow steps assigned to people | Held in partTask management in Expert Case, plus firm-built workflows. | Has a placeRows with assignee, due date and status. | Exported in full |
| Time and expensesTime and expense entries, billed and unbilled | HeldExpert Time and Expert Expenses, with work in progress by matter. | Has a placeTime and expense rows with rates and billed status. | Exported in full |
| BillingInvoices, payments and debtor balances | HeldPrebills, bills, rates, collections and accounts receivable. | Has a placeInvoices, lines and receipts as rows; invoice PDFs kept as files. | Exported in full |
| Trust moneyTrust or client account ledgers and balances | HeldTrust management is listed among its accounting applications. | Has a placeTransactions and balances for look-up; it is not a trust accounting system. | Exported in full |
| Firm accountsGeneral ledger, office account and payables | HeldGeneral ledger, accounts payable, tax and disbursements. | Has a placeGeneral ledger journals and balances, where the source held them. | Exported in full |
| Custom fieldsFields and record types the firm added itself | HeldAderant describes firm-specific customisations held alongside the standard data. | Has a placeAs added columns, or a table of field names and values. | Exported with mapping |
| TemplatesPrecedents, document templates and automation | Held in partDocument assembly in Expert Case; bill layouts in billing. | Has a place in partPrecedent files can be stored; automation does not run here. | Exported with mapping |
| IntakeLeads, enquiries, intake forms and pipelines | Held in partClient and matter intake with conflicts checks, not a marketing pipeline. | Has a placeEnquiry rows, where the source recorded them. | Exported in full |
What the plans mean
- Exported in full
- Microsoft SQL Server has a place for this kind of record. It is loaded there and checked against Aderant Expert.
- Exported with mapping
- Microsoft SQL Server 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
Not a new system. A complete copy the firm can query.
Writing Aderant Expert out to Microsoft SQL Server is not a migration into a new working system. Nobody will open a matter there on Monday morning. The aim is a complete, faithful copy that can be queried and reported on after the old system is gone. So the rules change. Nothing is cleaned or merged unless the firm asks, because an archive should show the records as they were. Every table and field is carried, including those a new system would have had no place for.
What makes an archive usable is the description that goes with it. The export is delivered with a plain account of each table: what it holds, how it joins to the others, what the codes mean. Record counts and financial totals are agreed to the reports in Aderant Expert as at the export date, so the archive can stand as the record. Documents are exported beside the data with a table linking each file to its matter. Access is restricted, since the archive holds everything the live system did.
Both ends are on equipment the firm controls, so the work is done on the firm’s own network with its IT provider. Disk space for a second full copy is checked first. The original in Aderant Expert stays untouched until the copy in Microsoft SQL Server has been checked.
Where the data is now
Leaving Aderant Expert
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.
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.
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.
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.
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.
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.
Where it is going
Arriving in Microsoft SQL Server
There are two ways to put a retired system into SQL Server, and they suit different firms. The old system’s own database can be restored as it is. Or the data can be loaded into a new set of tables designed to be read by people. The first is quicker and harder to use. Which suits is worked out in the analysis, and the choice is the firm’s.
Restored copy or rebuilt schema
Where the old practice system already kept its data in SQL Server, a backup can be restored onto a new server. The tables keep the vendor’s names and codes, which can be cryptic, and reading them takes someone who knows that product’s database. A rebuilt schema uses plain names such as Matter and TrustTransaction.
No screens come with it
A database has no matter screen. Someone has to ask it questions in SQL or through a reporting tool. Saved views can be set up for the things the firm will really look up: a matter with its parties, its ledger, its time entries and its list of documents. Which are worth having is agreed in the analysis.
Documents sit beside the database
Files are normally kept in folders on the same server, with a table recording each document’s matter, title, dates and path. Storing the files inside the database is possible but makes it far larger. On the Express edition, the cap on database size rules that out for most firms’ document stores.
The edition follows the size
A firm’s tables may fit within the Express limit once documents are kept outside the database. A long trust and time history at a larger firm may not. The size of the source data is measured in the analysis, and the edition is chosen from that figure with the firm’s IT provider.
Backups and a test restore
An archive that is never backed up is one disk failure from gone. Backups belong to the firm’s IT provider: a full one once the load is finished, and a schedule if anything is still being added. It is worth restoring one to a second machine as a test, because a backup that has never been restored is only a hope.
How NewLaw runs it
Four steps, in this order.
This route produces an archive, not a working system, so the steps are about completeness and proof.
Analysis
We read what Aderant Expert holds, table by table, and agree with you what the copy in Microsoft SQL Server must be able to answer later. Everything Aderant Expert holds is in scope unless you take it out.
Clean-up, if you want it
An archive should show the records as they were, so nothing is merged or corrected unless you ask. Where the copy is also meant for reporting, duplicate and inconsistent entries are tidied in a working copy and the original values are kept beside them.
Trial export
The data is written to Microsoft SQL Server as a trial and checked against Aderant Expert: record counts, totals where Aderant Expert holds money, the links between records, and a sample of documents opened from the export. Exceptions are listed for you to decide.
Final export
After the last day of work in Aderant Expert, the export is run a final time and checked again. There is nothing to go live. Aderant Expert is kept read only until you are satisfied the copy answers what you need, and it is handed over with a written description of its contents.
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
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 holds
What is in it, how its records link, and where each piece would sit in Microsoft SQL Server. 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
Structure, permissions and handover
Microsoft SQL Server is a place to keep data, not a system staff work in each day. What is agreed is how the data is laid out, who can reach it, and what is handed over with it.
Standing up SQL Server as an archive is IT work shared with the firm’s provider. A server or instance is chosen, logins are created for the few people who need to read the data, and nobody is given rights to change it. Views and a handful of reports are built for the common questions, and the IT provider owns the backup routine.
What is agreed and set up
- Server, instance and edition agreed with the IT provider
- Read-only logins and roles for named staff
- Views for matter, ledger, time and document look-ups
- Backup schedule and who tests a restore
- Plain names and descriptions for tables and columns
- Excel or Power BI connected for reporting
Questions
Aderant Expert to Microsoft SQL Server: 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.
Does the copy in Microsoft SQL Server hold trust ledgers from Aderant Expert?
Yes. Transactions and balances for look-up; it is not a trust accounting system. Trust ledgers are written out with the rest, and counts and totals are agreed to the reports in Aderant Expert as at the export date.
Does everything in Aderant Expert have a place in Microsoft SQL Server?
Most of it does on paper. Emails and notes 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 Microsoft SQL Server is kept as a readable archive, and you see which before the move.
What has to be decided before Aderant Expert is written out to Microsoft SQL Server?
Documents, custom fields and templates are exported with mapping, so each mapping is agreed with you first. Emails and notes are confirmed in the analysis. The firm also decides who may open the archive and how long it is kept.
Other routes
Other routes from Aderant Expert and into Microsoft SQL Server
Other destinations from Aderant Expert
Other systems that move into Microsoft SQL Server
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 and Microsoft SQL Server are the names and marks of their owners, used here only to identify the two systems.
Moving from Aderant Expert to Microsoft SQL Server?
Tell us what you are moving. You get a plan and a fixed price after the analysis.
We reply within one business day.