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

Data migration route

CasePeer to SharePoint migration

CasePeer is a cloud case management system for personal injury work, 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.

FromCasePeerCloud
  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. Templates: Carried with mapping
  9. Billing: Confirmed in the analysis
  10. Custom fields: Confirmed in the analysis
ToSharePointCloud
  1. Time and expenses: Kept as a readable archive
  2. Trust money: Kept as a readable archive
  3. Intake: Kept as a readable archive
Readable archiveNo place in SharePoint
  • 1 carried
  • 7 mapped
  • 2 to confirm
  • 3 archived
What the two products hold. The analysis confirms it field by field.

What moves

What moves from CasePeer to SharePoint

Each row is a kind of record CasePeer holds, whether SharePoint has a place for it, and what is planned. On this route one kind of record carries across, seven kinds need mapping, three kinds have no place in SharePoint and are archived and two kinds are confirmed in the analysis.

Records in CasePeer and their place in SharePoint
RecordIn CasePeerIn SharePointWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldPersonal injury cases with statutes, status and links to connected cases.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 referrersHeldClients, defendants, insurers, providers and referral sources.Has a place in partOnly as rows in a list built for the purpose.Carried with mapping
DocumentsFiles stored in or linked from the systemHeldUnlimited storage, a mail centre for incoming post, and Dropbox or OneDrive links.Has a placeFiles in libraries, with columns and versions.Carried across
EmailsEmails saved to matters or to the storeHeld in partText and email messages with clients are tied to the case.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 notesHeldCase notes, including notes written automatically by workflows.Has a place in partAs documents, or as rows in a notes list if one is built.Carried with mapping
CalendarAppointments, court dates and deadlinesHeldEvents, statutes and litigation event plans. Syncs to Outlook, Google or iCal.Has a place in partPossible as a list; usually left in Outlook.Carried with mapping
TasksTo-dos and workflow steps assigned to peopleHeldTask manager with workflows triggered by case status, age or client details.Has a place in partPossible as a list; no legal workflow built in.Carried with mapping
Time and expensesTime and expense entries, billed and unbilledHeld in partTime logging is built in. The product is designed for contingency fee work.No placeKept as a readable archive
BillingInvoices, payments and debtor balancesTo be confirmedClient payments are taken through LawPay. Invoicing was not confirmed.No placeConfirmed in the analysis
Trust moneyTrust or client account ledgers and balancesHeld in partClient trust tracking by case. Trust accounting itself runs in a linked package.No placeKept as a readable archive
Custom fieldsFields and record types the firm added itselfTo be confirmedSold as pre-configured. How far fields can be added was not confirmed.Has a placeColumns and content types on libraries and lists.Confirmed in the analysis
TemplatesPrecedents, document templates and automationHeldDocument automation from case data.Has a place in partPrecedents as files; templates can be offered from a library.Carried with mapping
IntakeLeads, enquiries, intake forms and pipelinesHeldIntake manager with forms, checklists and conversion reporting.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 CasePeer.
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.
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.
Kept as a readable archive
SharePoint has no place for it. It is exported in a format that opens without CasePeer 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 CasePeer 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 CasePeer.

Both are hosted by their makers, so nothing is collected from the firm’s office. What can be taken out of CasePeer 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 CasePeer is kept running until the checks on SharePoint are finished.

Where the data is now

CasePeer holds an injury case in a fixed shape that suits the work: treatment, bills, liens, costs and settlement each have their own place. Leaving it means finding where each of those sits in the destination. A system built for injury work will have most of them. A general system needs fields or record types set up first.

  1. Treatment and medical bills

    Each provider on a case carries treatment, billed amounts and the status of the requests made for records and bills. This is the bulk of the structured data and the part clients ring about. It is mapped provider by provider, and billed totals per case are compared after the trial load, since they feed the demand.

  2. Liens and settlement distribution

    Liens are tracked against the case, and the settlement figures work out fees, costs, lien payments and the client’s net. For settled cases the final distribution is a record the firm must be able to produce later. It is carried as data where the destination can hold it, and otherwise as a saved statement on the case.

  3. Cost requests and accounting

    Staff raise cost requests in CasePeer and the payment itself is made in the accounting package. The cost history on a case therefore depends on that link having been used consistently. Case cost totals are reconciled to the accounting package before cutover, so the amount recovered at settlement is the amount actually spent.

  4. Client trust tracking

    The product tracks client trust money by case. Those balances are compared with the firm’s bank and accounting records before any figure is loaded into a new trust ledger. Because a trust cutover cannot be run again like a document load, it is rehearsed on a full trial load first.

  5. Mail centre and flagged documents

    Incoming post is sorted through a mail centre, and documents can be flagged for review. Items still waiting in that queue at cutover belong to no finished process in the new system. The queue is cleared or listed during the freeze window, so nothing sits unread in the old one.

More about moving off CasePeer

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 CasePeer 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 CasePeer: 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 CasePeer, a final pass over a weekend picks up what changed since the trial. CasePeer 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 CasePeer 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 fromCasePeer
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 CasePeer 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

CasePeer to SharePoint: what firms ask

Is CASEpeer the same product as 8am CasePeer?

Yes. The product was written CASEpeer for years, and its owner now brands it 8am CasePeer alongside 8am MyCase, LawPay and DocketWise. Nothing about what the system stores changed with the rename. A firm that knows it under any of these names is using the same personal injury system.

Can our treatment and lien data go into a general practice system?

It can, but someone has to build the place for it first. General systems hold parties and documents well and usually have nothing for provider visits, bills and lien balances. Custom fields or record types are set up at the analysis stage, and where the destination cannot hold a table of bills, a schedule is saved to the case.

What happens to leads that never became cases?

Leads in the intake manager are separate from cases. Declined and unconverted leads can move to the new system’s intake module if it has one, be loaded as contacts with a note, or be left in an export. Referral sources are kept in every option, because the marketing reports depend on them.

Do trust balances in CasePeer have a place in SharePoint?

No. SharePoint does not keep trust ledgers. Trust records from CasePeer 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, trust ledgers and intake records. They are exported from CasePeer 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 CasePeer data is loaded into SharePoint?

Matters, contacts, emails, notes, calendar entries, tasks and templates are carried with mapping, so each mapping is agreed with you first. Billing records and custom fields are confirmed in the analysis. 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

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

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