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

Data migration route

Firm Central to SharePoint migration

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

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

What moves

What moves from Firm Central to SharePoint

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

Records in Firm Central and their place in SharePoint
RecordIn Firm CentralIn SharePointWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldOpen and closed matters with practice area, client group, permissions and primary attorney.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, contacts and client groups.Has a place in partOnly as rows in a list built for the purpose.Carried with mapping
DocumentsFiles stored in or linked from the systemHeldMatter folders that could be layered freely, plus a My Documents area for each user.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 notesHeldMatter notes.Has a place in partAs documents, or as rows in a notes list if one is built.Carried with mapping
CalendarAppointments, court dates and deadlinesHeldCalendar events, and Deadline Assistant events for firms that had that add-on.Has a place in partPossible as a list; usually left in Outlook.Carried with mapping
TasksTo-dos and workflow steps assigned to peopleHeldMatter tasks.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 partThrough the Time & Billing module, which was supplied by eBillity.No placeKept as a readable archive
BillingInvoices, payments and debtor balancesHeld in partPre-bills, invoices and payments in the Time & Billing module.No placeKept as a readable archive
Trust moneyTrust or client account ledgers and balancesHeld in partThe Time & Billing module had a Trusts & Retainers tab.No placeKept as a readable archive
Firm accountsGeneral ledger, office account and payablesHeld in partEditions sold with Accounting had a chart of accounts and accounts payable.No placeKept as a readable archive
Custom fieldsFields and record types the firm added itselfTo be confirmedHas a placeColumns and content types on libraries and lists.Confirmed in the analysis
TemplatesPrecedents, document templates and automationTo be confirmedHas a place in partPrecedents as files; templates can be offered from a library.Confirmed in the analysis
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 Firm Central.
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 Firm Central 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 Firm Central 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 Firm Central.

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

Where the data is now

Firm Central was discontinued in 2024, so a move from it today starts with whatever the firm saved before the shutdown. Thomson Reuters’ extraction guide had firms download their data as a set of CSV files and zipped document bundles. The job is to find those files, work out what each contains, and rebuild matters from the pieces in a system the firm now uses.

  1. The source is an export

    What survives is a collection of downloads: contact and matter lists, document bundles and calendar files, saved by whoever ran the export in 2024. They may sit on one person’s computer. The analysis begins with an inventory of those files, including their dates, since an export taken weeks before the shutdown misses later work.

  2. One file per kind of record

    Matter lists, matter notes, matter tasks, billing rates, permissions and primary attorneys were each exported as their own CSV, and separately for open and closed matters. Each file is a flat list. The pieces are joined back together on the matter and client they name, and rows that match nothing are listed for the firm.

  3. Documents came out as zips

    Bulk document extraction produced zipped bundles holding each matter’s folders, with files in the format they were uploaded in. Firm Central allowed folders to be layered freely, so structures vary from matter to matter. Each user’s My Documents came out as a separate set and has no matter attached until someone assigns one.

  4. Billing sat with eBillity

    Time entries, invoices, payments and trust records were in the Time & Billing module, which eBillity supplied. Thomson Reuters told firms they could carry on with those eBillity products under a new billing arrangement. A firm that did so has its billing history in eBillity, not in the Firm Central export.

  5. What the export left out

    The guide notes that client portal messages could not be exported, and that links to Westlaw research saved in matter folders do not include the documents themselves. Neither can be recovered from the files. If either mattered to a particular matter, the firm’s email and Westlaw folders are the places to look.

More about moving off Firm Central

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

Firm Central to SharePoint: what firms ask

Firm Central has shut down. Is it too late to move our data?

Not if the firm ran the exports. Thomson Reuters gave firms a way to download contacts, matters, notes, tasks, calendar events and documents before the product ended. Those files can be cleaned and loaded into a current system. If no export was taken, what remains is whatever was also saved elsewhere.

We exported everything in 2024 but never loaded it anywhere. What can be done with it?

Quite a lot. The CSV files are joined back into matters with their contacts, notes and tasks, and the document bundles are unzipped and filed against the right matter. Before anything is made final, the firm sees a trial load and a list of whatever could not be matched.

Where did our time and billing records go?

They were never in the main Firm Central database. Time & Billing was an eBillity product offered through Thomson Reuters. Firms that kept it moved to a direct arrangement with eBillity. Those that did not would have downloaded invoices and reports before the end, and those downloads are the record.

Do trust balances in Firm Central have a place in SharePoint?

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

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

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

Moving from Firm Central 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.