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

Data migration route

PracticePanther to SharePoint migration

PracticePanther is a cloud 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.

FromPracticePantherCloud
  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 PracticePanther to SharePoint

Each row is a kind of record PracticePanther 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 PracticePanther and their place in SharePoint
RecordIn PracticePantherIn SharePointWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldMatters belong to a contact and are Open, Pending or Closed. Numbering is one firm-wide sequence.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 referrersHeldA contact can be a company holding several people. Prospects are contacts with a tag.Has a place in partOnly as rows in a list built for the purpose.Carried with mapping
DocumentsFiles stored in or linked from the systemHeldStored in the account, or synced with Box, Dropbox, Google Drive or OneDrive.Has a placeFiles in libraries, with columns and versions.Carried across
EmailsEmails saved to matters or to the storeHeld in partEmails archived by the Gmail or Outlook add-in, or sent to a MailSync address.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 deadlinesHeldSyncs with Google and Outlook calendars; court rules through LawToolBox.Has a place in partPossible as a list; usually left in Outlook.Carried with mapping
TasksTo-dos and workflow steps assigned to peopleHeldWorkflow templates create tasks and events.Has a place in partPossible as a list; no legal workflow built in.Carried with mapping
Time and expensesTime and expense entries, billed and unbilledHeldNo placeKept as a readable archive
BillingInvoices, payments and debtor balancesHeldNo placeKept as a readable archive
Trust moneyTrust or client account ledgers and balancesHeldNo placeKept as a readable archive
Firm accountsGeneral ledger, office account and payablesHeld in partOperating accounts and a chart of accounts come with the PantherAccounting Plus plan.No placeKept as a readable archive
Custom fieldsFields and record types the firm added itselfHeldCustom fields on contacts and matters, which can be grouped.Has a placeColumns and content types on libraries and lists.Carried with mapping
TemplatesPrecedents, document templates and automationHeldUploaded Word templates filled from merge fields.Has a place in partPrecedents as files; templates can be offered from a library.Carried with mapping
IntakeLeads, enquiries, intake forms and pipelinesHeld in partIntake forms create or update contacts; prospects are tracked with tags.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 PracticePanther.
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 PracticePanther 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 PracticePanther 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 PracticePanther.

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

Where the data is now

PracticePanther is flexible about how a firm files things, and each firm has used that freedom differently. One uses tags for practice areas, another for referral sources, a third for both. Leaving it starts with reading how this particular account was set up: what the tags mean, what Pending was used for, and whether clients were entered as people or as companies.

  1. Contacts hold several people

    A contact can be one person, or a company with a primary contact and others added beneath it. Systems that keep organisations and individuals as separate cards need each company contact split apart, with the links kept. The person who receives the invoices is not always the primary contact, so billing addresses are checked as part of this.

  2. One number sequence

    Automatic matter numbers run in a single sequence across the firm and cannot restart for each client. Contacts can be numbered the same way. A destination that uses a client number followed by a matter number needs new numbers generated, and the PracticePanther number is kept on each record as a reference.

  3. What Pending means here

    Matters have three statuses: Open, Pending and Closed. Firms use Pending for different things. For some it is a prospect who has not signed, for others a file waiting on a court. The firm confirms its own meaning, and pending matters are mapped to leads, open matters or a custom status accordingly.

  4. Emails arrive by MailSync

    Every contact and every matter has its own MailSync address, and an email copied to that address is attached with its attachments. The Gmail and Outlook add-ins do the same from the inbox. Some emails are therefore attached to a contact and no matter. Those need a rule for where they go.

  5. Tags carry the meaning

    Tags mark contacts as clients, prospects or professional contacts, and firms add their own for lead source, practice group or anything else they report on. A destination may offer matter types, categories and custom fields in their place. Each tag in use is listed with a count, and the firm decides what it becomes.

More about moving off PracticePanther

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

PracticePanther to SharePoint: what firms ask

We use PantherAccounting Plus. What extra has to be planned?

It adds the operating side. With that plan the firm keeps a chart of accounts, journal entries and bank reconciliations in PracticePanther as well as trust. Those need a destination that does accounting, or a separate package. Without the plan, only trust and billing balances have to be carried.

Our documents sync to Box. Where are the real files?

In both places. The sync puts the files in the firm’s Box account as well as in PracticePanther. Whether the two agree is checked in the analysis. Often the Box account is the simplest source for the files, with PracticePanther telling us which matter each folder is for.

Will intake form submissions come across?

Where the answers a client gave on an intake form were written into contact fields and custom fields, they move with the contact. Form designs do not transfer. They are rebuilt in the new system’s own form tool, if it has one, using the same questions.

Do trust balances in PracticePanther have a place in SharePoint?

No. SharePoint does not keep trust ledgers. Trust records from PracticePanther 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 PracticePanther 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 PracticePanther 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

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

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