Data migration route
AbacusLaw to Server drives migration
AbacusLaw is a server-based 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.
AbacusLawServer- Documents: Carried across
- Emails: Carried with mapping
- Notes: Carried with mapping
- Templates: Carried with mapping
Server drivesFiles- Matters: Kept as a readable archive
- Contacts: Kept as a readable archive
- Calendar: Kept as a readable archive
- Tasks: Kept as a readable archive
- Time and expenses: Kept as a readable archive
- Billing: Kept as a readable archive
- Trust money: Kept as a readable archive
- Firm accounts: Kept as a readable archive
- Custom fields: Kept as a readable archive
- Intake: Kept as a readable archive
- 1 carried
- 3 mapped
- 10 archived
What moves
What moves from AbacusLaw to Server drives
Each row is a kind of record AbacusLaw holds, whether Server drives have a place for it, and what is planned. On this route one kind of record carries across, three kinds need mapping and ten kinds have no place in Server drives and are archived.
| 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. | No placeA matter becomes a folder; its details survive only in an index file. | Kept as a readable archive |
| ContactsClients, other parties and referrers | HeldCalled Names. | No placeCan be kept only as an exported spreadsheet. | Kept as a readable archive |
| 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 placeFiles in folders, named and dated during the load. | 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 place in partAs .msg or .eml files in each matter’s correspondence folder. | Carried with mapping |
| NotesFile notes, matter notes and contact notes | Held | Has a place in partAs a text or PDF file per matter, not as separate records. | Carried with mapping |
| CalendarAppointments, court dates and deadlines | HeldCalled Events; court rules can generate dates. | No place | Kept as a readable archive |
| TasksTo-dos and workflow steps assigned to people | Held | No place | Kept as a readable archive |
| Time and expensesTime and expense entries, billed and unbilled | HeldTime is billed through the Abacus Accounting module. | No placeOnly as exported reports or spreadsheets. | Kept as a readable archive |
| BillingInvoices, payments and debtor balances | Held in partInvoices and receivables are in Abacus Accounting, where the firm has it. | Has a place in partInvoices as PDF files; no ledger. | Kept as a readable archive |
| Trust moneyTrust or client account ledgers and balances | Held in partTrust accounting is part of Abacus Accounting. | No placeOnly as exported ledger reports kept as files. | Kept as a readable archive |
| Firm accountsGeneral ledger, office account and payables | Held in partGeneral ledger and vendor bills are part of Abacus Accounting. | No place | Kept as a readable archive |
| Custom fieldsFields and record types the firm added itself | HeldPractice area packs and the firm’s own changes add screens, fields and codes. | No place | Kept as a readable archive |
| TemplatesPrecedents, document templates and automation | HeldAbacus forms and court forms filled from name and matter data. | 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 pipelines | HeldIntake screens and lead management. | No place | Kept 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 AbacusLaw.
- 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.
- Kept as a readable archive
- Server drives has no place for it. It is exported in a format that opens without AbacusLaw 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 AbacusLaw 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 AbacusLaw.
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 AbacusLaw stays untouched until the copy in Server drives has been checked.
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 Server drives
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.
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.
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.
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.
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.
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.
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.
Analysis
We read what AbacusLaw 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.
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.
Trial load
A trial is loaded into Server drives and checked against AbacusLaw: 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.
Cutover
There is no financial cutover on this route. After a short freeze on changes in AbacusLaw, a final pass over a weekend picks up what changed since the trial. 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 Server drives. 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
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
AbacusLaw to Server drives: 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 Server drives?
No. Server drives do not keep trust ledgers. Only as exported ledger reports kept as files. Trust records from AbacusLaw 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 AbacusLaw 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 AbacusLaw data is loaded into Server drives?
Emails, notes and templates are carried with mapping, so each mapping is agreed with you first. The firm also decides which closed matters and how many versions of a document are in scope.
Other routes
Other routes from AbacusLaw and into Server drives
Other destinations from AbacusLaw
Other systems that move into Server drives
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 Server drives are the names and marks of their owners, used here only to identify the two systems.
Moving from AbacusLaw 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.