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

Data migration route

Client Profiles to SharePoint migration

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

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

What moves

What moves from Client Profiles to SharePoint

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

Records in Client Profiles and their place in SharePoint
RecordIn Client ProfilesIn SharePointWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldCalled cases; screens and numbering are set per law type.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 referrersHeldHeld in the Card File, with categories, custom tabs and pick lists.Has a place in partOnly as rows in a list built for the purpose.Carried with mapping
DocumentsFiles stored in or linked from the systemHeldCase documents are kept in a History directory on the server; scanned pages may sit elsewhere.Has a placeFiles in libraries, with columns and versions.Carried across
EmailsEmails saved to matters or to the storeTo be confirmedHas a place in partAs .msg or .eml files, with columns for sender and date if set up.Confirmed in the analysis
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 partReleases from 2014 integrate with Outlook Tasks and the CompuLaw court rules database.Has a place in partPossible as a list; usually left in Outlook.Carried with mapping
TasksTo-dos and workflow steps assigned to peopleHeldTo-do packages set up per law type.Has a place in partPossible as a list; no legal workflow built in.Carried with mapping
Time and expensesTime and expense entries, billed and unbilledHeldTime slips, which can be released to a billing system.No placeKept as a readable archive
BillingInvoices, payments and debtor balancesHeld in partThrough the suite’s financial system, Profiles Financial or Profiles Plaintiff.No placeKept as a readable archive
Trust moneyTrust or client account ledgers and balancesHeld in partTrust and escrow are in the suite’s financial system.No placeKept as a readable archive
Firm accountsGeneral ledger, office account and payablesHeld in partGeneral ledger and payables are in the suite’s financial system.No placeKept as a readable archive
Custom fieldsFields and record types the firm added itselfHeldCustom information screens and custom tabs.Has a placeColumns and content types on libraries and lists.Carried with mapping
TemplatesPrecedents, document templates and automationHeldMerge documents created from templates.Has a place in partPrecedents as files; templates can be offered from a library.Carried with mapping
IntakeLeads, enquiries, intake forms and pipelinesTo be confirmedNo placeConfirmed in the analysis

What the plans mean

Carried across
SharePoint has a place for this kind of record. It is loaded there and checked against Client Profiles.
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 Client Profiles 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 Client Profiles 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 Client Profiles.

Client Profiles 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

Plenty of firms still say Client Profiles when the screen in front of them says Total Office. It is the same system. A move off it means reading a SQL Server database, collecting case documents from a history folder on the server, and working out how each law type was set up, because every law type carries its own screens and fields.

  1. Law types shape everything

    Every case belongs to a law type, and the law type decides its summary screen, custom information screens, numbering and to-do packages. Field mapping is therefore done once per law type, not once for the firm. The rarely used law types need as much attention as the busy ones, since their fields are the least documented.

  2. Numbering follows a formula

    Case numbers can be typed by hand or built from a formula set per law type, such as a four-digit client number, a dash and a four-digit matter sequence. Old and new formats often sit side by side. The numbers are carried as they are, and the destination’s own numbering starts above the highest one in use.

  3. Parties are more than opponents

    A party here is anyone with a role in a case: doctors, judges and insurance companies as well as plaintiffs and defendants. Each comes from the Card File and has a category. Categories are mapped to contact roles in the new system, and people entered twice in the Card File are merged where they can be identified.

  4. Documents sit in History

    Case documents are stored in a History directory, normally under the shared CPWin folder, and scanned pages can be kept in a second location if space was short. Both are collected. The link from each file to its case is in the database, so the folders alone do not show what belongs where.

  5. Time may leave by export

    Time slips can be entered against a case and then released to a billing system, either the suite’s own financial side or a third-party product. Where the money sits depends on which the firm chose. That billing source is identified in the analysis and matched to cases on the case number.

More about moving off Client Profiles

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

Client Profiles to SharePoint: what firms ask

Is Client Profiles the same as Aderant Total Office?

Yes. Aderant’s own announcements describe Total Office as formerly Client Profiles, and the administrator’s manual for Total Office still refers to CP and the CPWin folder. Older releases show the Client Profiles name on screen. The work of moving is the same under either name, and the release number is noted at the start.

What happens to our custom information screens?

Each custom screen is a set of fields added for a law type. Where the destination has custom fields, the ones in real use are recreated and filled. Screens the firm stopped using are listed with a count of how many cases have anything in them, and the firm decides which are worth recreating.

Do medical record requests come across?

The records request screens track requests for medical records on a case. Few systems outside personal injury have a matching feature. If the destination is built for injury work, requests are mapped to its own tracker. Otherwise they come across as dated notes on the case so the history is not lost.

Do trust balances in Client Profiles have a place in SharePoint?

No. SharePoint does not keep trust ledgers. Trust records from Client Profiles 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 and the firm’s accounts. They are exported from Client Profiles 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 Client Profiles data is loaded into SharePoint?

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

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

Moving from Client Profiles 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.