Data migration route
AbacusLaw to SmartAdvocate migration
AbacusLaw is a server-based practice management system, and SmartAdvocate is a cloud case management system for personal injury work. Matter records move into cases, and the firm decides where its accounting runs from the cutover date.
AbacusLawServer- Matters: Carried across
- Contacts: Carried across
- Documents: Carried across
- Emails: Carried across
- Notes: Carried across
- Calendar: Carried across
- Tasks: Carried across
- Time and expenses: Carried across
- Intake: Carried across
- Billing: Carried with mapping
- Custom fields: Carried with mapping
- Templates: Carried with mapping
- Trust money: Confirmed in the analysis
- Firm accounts: Confirmed in the analysis
SmartAdvocateCloud- 9 carried
- 3 mapped
- 2 to confirm
What moves
What moves from AbacusLaw to SmartAdvocate
Each row is a kind of record AbacusLaw holds, whether SmartAdvocate 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 | HeldMatters are joined to Names by typed links such as BILLTO. | Has a placeCases by case type, with master and member relationships. | Carried across |
| ContactsClients, other parties and referrers | HeldCalled Names. | Has a place | Carried across |
| DocumentsFiles stored in or linked from the system | HeldEach document record stores the path to a file on disk, with type codes, author, status and notes. | Has a placeDocuments page, by category and subcategory. | Carried across |
| EmailsEmails saved to matters or to the store | Held in partEmails linked from Outlook through the add-in are copied to an Email folder on the server. | Has a placeEmails are attached to cases. | Carried across |
| NotesFile notes, matter notes and contact notes | Held | Has a place | Carried across |
| CalendarAppointments, court dates and deadlines | HeldCalled Events; court rules can generate dates. | Has a placeAppointments and critical deadlines. | Carried across |
| TasksTo-dos and workflow steps assigned to people | Held | Has a place | Carried across |
| Time and expensesTime and expense entries, billed and unbilled | HeldTime is billed through the Abacus Accounting module. | Has a placeTracked time entries. | Carried across |
| BillingInvoices, payments and debtor balances | Held in partInvoices and receivables are in Abacus Accounting, where the firm has it. | Has a place in partInvoices for hourly matters. Past invoices are scoped in the analysis. | Carried with mapping |
| Trust moneyTrust or client account ledgers and balances | Held in partTrust accounting is part of Abacus Accounting. | To be confirmed | Confirmed in the analysis |
| Firm accountsGeneral ledger, office account and payables | Held in partGeneral ledger and vendor bills are part of Abacus Accounting. | To be confirmed | Confirmed in the analysis |
| Custom fieldsFields and record types the firm added itself | HeldPractice area packs and the firm’s own changes add screens, fields and codes. | Has a place in partConfirmed in the analysis for each field with no standard home. | Carried with mapping |
| TemplatesPrecedents, document templates and automation | HeldAbacus forms and court forms filled from name and matter data. | Has a place in partTemplates are rebuilt with SmartAdvocate merge codes. | Carried with mapping |
| IntakeLeads, enquiries, intake forms and pipelines | HeldIntake screens and lead management. | Has a placeIntake and lead records. | Carried across |
What the plans mean
- Carried across
- SmartAdvocate has a place for this kind of record. It is loaded there and checked against AbacusLaw.
- Carried with mapping
- SmartAdvocate 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 SmartAdvocate. 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 AbacusLaw has to be given a case type in SmartAdvocate, and that choice drives which fields and workflows it gets. The mapping is agreed type by type. Financial history with no place in SmartAdvocate is exported as reports and ledgers the firm can open without AbacusLaw, and kept as the record of what was billed and held.
AbacusLaw 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. SmartAdvocate 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
Leaving AbacusLaw
A move off AbacusLaw starts with which database version the firm runs and which folders its files sit in. The case data lives in tables on the server, while documents, linked emails and forms are ordinary files in folders beside them. Names and Matters are joined by typed links, and those links decide who the client is on each matter in the new system.
Check the database version
Many installs run on Advantage Database Server, which the vendor calls the ADS version, with tables in a data folder usually named data01. Releases up to v23.16 also kept DBF files there. Which version and release a firm has decides how the data is read out, so it is the first thing checked.
Names are linked, not typed
A person is entered once as a Name and then linked to matters with a link type. One Name can be the client on one matter and a witness on another. The link types a firm has used are mapped one by one to contact roles in the destination, because that is where the client relationship is recorded.
Documents are paths on disk
Each document record stores the full path to a file, plus type codes, author, status, a box number and notes. Files commonly sit in an Abacus\Docs folder and linked Outlook emails in an Email folder. If a file was moved or renamed outside the program, the record still points at the old place, so paths are tested before the trial load.
Accounting is a separate module
Billing, trust and the ledgers belong to Abacus Accounting, which keeps its tables in an accounting subfolder. A matter only appears there after a Name is linked to it as BILLTO. Firms that never bought the module have their time and costs in some other program, and that program joins the scope.
Practice packs change the fields
Practice Area Essentials add input screens, codes, rules and forms for a practice area. Two firms on the same version can hold quite different fields on a matter. The field list is read from the firm’s own database, not from a standard layout.
Where it is going
Arriving in SmartAdvocate
SmartAdvocate keeps injury detail in structured fields and screens, so mapping counts for more than usual: the more precisely the old data is placed, the more of those screens are filled on the first day. Parties, incidents, insurers, providers and bills are loaded to their own screens, and the vendor’s implementation team runs conversions into it.
Map to fields, not notes
The case summary, dashboards and settlement screen read from structured fields. Injury details, insurance limits and provider bills dumped into a note leave those screens empty. The mapping takes each old field to its SmartAdvocate counterpart, and only what truly has no counterpart is loaded as a note.
Case types and statuses
Cases are loaded against case types and statuses that drive WorkPlans and reports. These are agreed with the firm before the trial load, and old statuses are translated to the new list. A status with no match is not guessed at. It is listed, and someone who knows the files decides.
Document categories
Documents are searched by category, subcategory, sender, recipient and date as well as by folder. The old system’s folders are translated into categories on the way in. Files that arrive uncategorised can still be found by description, but they fall outside the category views staff are trained to use.
Working with the vendor’s conversion
SmartAdvocate’s implementation team converts client data into the system and trains staff through its own classes. The firm’s side of that is supplying a clean source, checking the converted cases against the old system, and deciding what to do with the exceptions. Independent help is used on those tasks.
Choosing Server or Cloud
The firm decides before loading whether it will run the Server edition on its own Windows server or use the hosted Cloud edition. Either way the data load is the same. What differs is who looks after backups, updates and remote access afterwards, and that is settled with the firm’s IT provider.
How NewLaw runs it
Four steps, in this order.
Financial records move on this route, so the balances are rehearsed before the real cutover. The maker of SmartAdvocate says that it, or its partners, load firms into the product. Where the firm uses that service, NewLaw’s part is the work around it: the analysis, the clean-up in AbacusLaw and checking each trial against AbacusLaw.
Analysis
We read what AbacusLaw holds and how its records link, then agree with you, field by field, where each piece will sit in SmartAdvocate. 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 AbacusLaw, before extraction. It is not always possible to find every one, so some may carry across.
Trial load
The data is loaded into SmartAdvocate as a trial and checked against AbacusLaw: record counts, financial totals, the links between records, document dates. Exceptions are listed for you to decide.
Cutover
Changes in AbacusLaw are frozen for an agreed window, the data is collected a final time and SmartAdvocate goes live over a weekend. The financial cutover is rehearsed on a full trial load first, so that opening balances agree with the reports in AbacusLaw as at the cutover date. AbacusLaw 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 AbacusLaw 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 AbacusLaw holds
What is in it, how its records link, and where each piece would sit in SmartAdvocate. 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 SmartAdvocate
Loaded data is not yet a working system. The maker of SmartAdvocate runs or arranges the set-up of its product, so this is what has to be decided and put in place in SmartAdvocate, whoever does the work, before people rely on it from the first day.
Setting up SmartAdvocate is a matter of deciding how much of its detail the firm will use from the start. Case types, statuses and WorkPlans come first because they drive everything else. Templates follow. The vendor trains staff through its own classes, and the decisions below are best made before the first of those.
Set-up decisions in SmartAdvocate
- Choose the Server or Cloud edition with IT
- Define case types, statuses and staff roles
- Build WorkPlans and Automated Procedures for each case type
- Convert letters and forms into templates with merge codes
- Install the Outlook plugin and agree email filing habits
- Set up intake screens, lead sources and dashboards
Questions
AbacusLaw to SmartAdvocate: what firms ask
Can we keep our AbacusLaw matter numbers?
Usually, if the destination lets you set the matter number yourself or has a reference field for it. The file number and the matter name are both carried so staff can search by either. If the new system insists on its own numbering, the old number comes across as a searchable reference.
What happens to our court forms and templates?
Forms built in Abacus are tied to its own field names, so they do not run anywhere else. The analysis lists the forms the firm really uses and each one is rebuilt as a template in the new system. Standard court forms supplied by the vendor are replaced with the destination’s own library where it has one.
Do emails linked from Outlook come across?
Emails linked through the Outlook add-in are copied to a folder on the server, with a record against the name or matter. Those copies can be filed to the same matter in the new system. Mail that was never linked stays in the mailbox and is not part of the move.
Do trust balances in AbacusLaw have a place in SmartAdvocate?
That is confirmed in the analysis. We could not establish it from the two products’ own material, so it is checked against your data in AbacusLaw before the plan is fixed. If SmartAdvocate turns out to have no place for trust ledgers, they are kept as a readable archive and the firm decides where trust accounting runs.
Does everything in AbacusLaw have a place in SmartAdvocate?
Most of it does on paper. Trust ledgers 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 SmartAdvocate is kept as a readable archive, and you see which before the move.
What has to be decided before AbacusLaw data is loaded into SmartAdvocate?
Billing records, custom fields and templates are carried with mapping, so each mapping is agreed with you first. Trust ledgers 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 AbacusLaw and into SmartAdvocate
Other destinations from AbacusLaw
Other systems that move into SmartAdvocate
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.
AbacusLaw and SmartAdvocate are the names and marks of their owners, used here only to identify the two systems.
Moving from AbacusLaw to SmartAdvocate?
Tell us what you are moving. You get a plan and a fixed price after the analysis.
We reply within one business day.