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

Data migration route

PracticeEvolve to SharePoint migration

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

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

What moves

What moves from PracticeEvolve to SharePoint

Each row is a kind of record PracticeEvolve 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, five kinds have no place in SharePoint and are archived and one kind is confirmed in the analysis.

Records in PracticeEvolve and their place in SharePoint
RecordIn PracticeEvolveIn SharePointWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldHas 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 referrersHeldIncludes a conflict search across the system.Has a place in partOnly as rows in a list built for the purpose.Carried with mapping
DocumentsFiles stored in or linked from the systemHeldIndexed for searching, including image-based PDFs.Has a placeFiles in libraries, with columns and versions.Carried across
EmailsEmails saved to matters or to the storeHeldMatter emails are filed and saved centrally.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 notesTo be confirmedHas a place in partAs documents, or as rows in a notes list if one is built.Confirmed in the analysis
CalendarAppointments, court dates and deadlinesHeld in partEvents are held on the matter.Has a place in partPossible as a list; usually left in Outlook.Carried with mapping
TasksTo-dos and workflow steps assigned to peopleHeldTo-do lists, recurring tasks and workflows.Has a place in partPossible as a list; no legal workflow built in.Carried with mapping
Time and expensesTime and expense entries, billed and unbilledHeldAutomatic activity tracking converts to time entries.No placeKept as a readable archive
BillingInvoices, payments and debtor balancesHeldFlexible billing with approval flows.No placeKept as a readable archive
Trust moneyTrust or client account ledgers and balancesHeldClient funds management within the legal accounts.No placeKept as a readable archive
Firm accountsGeneral ledger, office account and payablesHeldLegal accounts with balance sheet, debtors, cash flow and budget reporting.No placeKept as a readable archive
Custom fieldsFields and record types the firm added itselfHeld in partEvolvePlus is described as fully customisable; the extent is confirmed in the analysis.Has a placeColumns and content types on libraries and lists.Carried with mapping
TemplatesPrecedents, document templates and automationHeldA supplied library of automated forms and precedents, plus the firm’s own.Has a place in partPrecedents as files; templates can be offered from a library.Carried with mapping
IntakeLeads, enquiries, intake forms and pipelinesHeldLead tracking for prospective clients.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 PracticeEvolve.
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 PracticeEvolve 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 PracticeEvolve 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 PracticeEvolve.

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

Where the data is now

PracticeEvolve keeps a firm’s data in the vendor’s Azure hosting, so extraction is arranged with the vendor. Which product the firm is on comes first, EvolveGo or EvolvePlus, because the two differ in how much has been customised. The accounts are inside the system, so client funds and office ledgers form part of every move.

  1. EvolveGo or EvolvePlus

    The vendor sells two cloud products. EvolveGo is the one built for quick implementation. EvolvePlus allows full customisation and workflows built without code. An EvolvePlus firm is likely to have fields, screens and processes of its own, and the analysis has to find them. An EvolveGo firm is closer to the product as supplied.

  2. Supplied precedents versus yours

    PracticeEvolve provides a large library of automated forms and precedents and keeps it up to date. Those belong to the vendor’s library. Precedents the firm added or adapted are the firm’s. We separate the two lists early, because only the second is rebuilt in the new system, and it is usually much shorter than staff expect.

  3. Where the documents are held

    Documents and filed emails are saved centrally and indexed for search. We confirm whether they are held by PracticeEvolve itself or by a separate document management product connected to it, as that decides who supplies the files and how each one is tied back to its matter.

  4. Messages in Communicate

    The built-in Communicate platform carries secure messages and shared files between the firm and its clients. Those conversations are part of the file for some matters. We check whether they are exported with the matter. If not, the messages for open matters are saved to the file as documents before cutover.

  5. Accounts in the same system

    Legal accounts, billing and client funds run inside PracticeEvolve, with its own reports for debtors, cash flow and budgets, and the UK site lists Making Tax Digital among its features. Leaving means choosing where office accounting goes next, and closing a tax period in the old system before balances are taken.

More about moving off PracticeEvolve

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

PracticeEvolve to SharePoint: what firms ask

How do we get our data out of a hosted system?

Through the vendor, at the firm’s request. We specify what is needed: the database or a full export, every document with its matter reference, and closing accounts reports taken at the same time. How it is delivered is confirmed with PracticeEvolve during the analysis, and the first copy is tested before a cutover date is set.

Do the automated forms come with us?

The supplied forms stay with PracticeEvolve. Documents already produced from them are on the matters and move as files. The firm’s own precedents are exported and their merge fields replaced with the destination’s. If the new system has its own forms library, we compare it with the forms the firm uses most.

Is the Australian version different from the UK one?

The vendor publishes separate UK and Australian sites, and each edition follows its own country’s rules for client money and tax. Our method is the same for both. The checks on the financial cutover are written against the rules of the jurisdiction the firm practises in.

Do trust balances in PracticeEvolve have a place in SharePoint?

No. SharePoint does not keep trust ledgers. Trust records from PracticeEvolve 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 PracticeEvolve 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 PracticeEvolve data is loaded into SharePoint?

Matters, contacts, emails, calendar entries, tasks, custom fields and templates are carried with mapping, so each mapping is agreed with you first. Notes 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

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

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