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

Data migration route

AbacusLaw to SharePoint migration

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

FromAbacusLawServer
  1. Documents: Carried across
  2. Matters: Carried with mapping
  3. Contacts: Carried with mapping
  4. Emails: Carried with mapping
  5. Notes: Carried with mapping
  6. Calendar: Carried with mapping
  7. Tasks: Carried with mapping
  8. Custom fields: Carried with mapping
  9. Templates: Carried with mapping
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
  • 8 mapped
  • 5 archived
What the two products hold. The analysis confirms it field by field.

What moves

What moves from AbacusLaw to SharePoint

Each row is a kind of record AbacusLaw holds, whether SharePoint has a place for it, and what is planned. On this route one kind of record carries across, eight kinds need mapping and five kinds have no place in SharePoint and are archived.

Records in AbacusLaw and their place in SharePoint
RecordIn AbacusLawIn SharePointWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldMatters are joined to Names by typed links such as BILLTO.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 referrersHeldCalled Names.Has a place in partOnly as rows in a list built for the purpose.Carried with mapping
DocumentsFiles stored in or linked from the systemHeldEach document record stores the path to a file on disk, with type codes, author, status and notes.Has a placeFiles in libraries, with columns and versions.Carried across
EmailsEmails saved to matters or to the storeHeld 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, with columns for sender and date if set up.Carried with mapping
NotesFile notes, matter notes and contact notesHeldHas a place in partAs documents, or as rows in a notes list if one is built.Carried with mapping
CalendarAppointments, court dates and deadlinesHeldCalled Events; court rules can generate dates.Has a place in partPossible as a list; usually left in Outlook.Carried with mapping
TasksTo-dos and workflow steps assigned to peopleHeldHas a place in partPossible as a list; no legal workflow built in.Carried with mapping
Time and expensesTime and expense entries, billed and unbilledHeldTime is billed through the Abacus Accounting module.No placeKept as a readable archive
BillingInvoices, payments and debtor balancesHeld in partInvoices and receivables are in Abacus Accounting, where the firm has it.No placeKept as a readable archive
Trust moneyTrust or client account ledgers and balancesHeld in partTrust accounting is part of Abacus Accounting.No placeKept as a readable archive
Firm accountsGeneral ledger, office account and payablesHeld in partGeneral ledger and vendor bills are part of Abacus Accounting.No placeKept as a readable archive
Custom fieldsFields and record types the firm added itselfHeldPractice area packs and the firm’s own changes add screens, fields and codes.Has a placeColumns and content types on libraries and lists.Carried with mapping
TemplatesPrecedents, document templates and automationHeldAbacus forms and court forms filled from name and matter data.Has a place in partPrecedents as files; templates can be offered from a library.Carried with mapping
IntakeLeads, enquiries, intake forms and pipelinesHeldIntake screens and lead management.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 AbacusLaw.
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.
Kept as a readable archive
SharePoint 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 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 AbacusLaw.

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

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

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

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

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

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

More about moving off AbacusLaw

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

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

Step 1 of 5: Start with the route

Moving fromAbacusLaw
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 AbacusLaw 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

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

No. SharePoint does not keep trust ledgers. 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 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 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 SharePoint?

Matters, contacts, emails, notes, calendar entries, tasks, custom fields 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.

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

AbacusLaw and SharePoint are the names and marks of their owners, used here only to identify the two systems.

Moving from AbacusLaw 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.