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

Data migration route

Liberate to SharePoint migration

Liberate is a 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.

FromLiberatePractice management
  1. Documents: Carried across
  2. Matters: Carried with mapping
  3. Emails: Carried with mapping
  4. Tasks: Carried with mapping
  5. Templates: Carried with mapping
  6. Contacts: Confirmed in the analysis
  7. Notes: Confirmed in the analysis
  8. Calendar: Confirmed in the analysis
  9. Trust money: Confirmed in the analysis
  10. Custom fields: Confirmed in the analysis
  11. Intake: Confirmed in the analysis
ToSharePointCloud
  1. Time and expenses: Kept as a readable archive
  2. Billing: Kept as a readable archive
  3. Firm accounts: Kept as a readable archive
Readable archiveNo place in SharePoint
  • 1 carried
  • 4 mapped
  • 6 to confirm
  • 3 archived
What the two products hold. The analysis confirms it field by field.

What moves

What moves from Liberate to SharePoint

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

Records in Liberate and their place in SharePoint
RecordIn LiberateIn SharePointWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldElectronic matters holding data, documents and emails.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 referrersTo be confirmedHas a place in partOnly as rows in a list built for the purpose.Confirmed in the analysis
DocumentsFiles stored in or linked from the systemHeldTags and definable document categories, with version control.Has a placeFiles in libraries, with columns and versions.Carried across
EmailsEmails saved to matters or to the storeHeldEmails are held on the matter; time spent in Outlook can be recorded.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 deadlinesTo be confirmedHas a place in partPossible as a list; usually left in Outlook.Confirmed in the analysis
TasksTo-dos and workflow steps assigned to peopleHeld in partAuthorisation workflows and business process automation.Has a place in partPossible as a list; no legal workflow built in.Carried with mapping
Time and expensesTime and expense entries, billed and unbilledHeldIncludes automatic time recording.No placeKept as a readable archive
BillingInvoices, payments and debtor balancesHeldOne-click and scheduled billing, with credit control procedures.No placeKept as a readable archive
Trust moneyTrust or client account ledgers and balancesTo be confirmedNo placeConfirmed in the analysis
Firm accountsGeneral ledger, office account and payablesHeldPurchase ledger, supplier database and built-in financial reporting.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 automationHeldPrecedents and document templates filled with matter data.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 Liberate.
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 Liberate 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 Liberate 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 Liberate.

How Liberate is run at the firm is settled at the start of the analysis, because its maker’s own material does not settle it. The usual arrangement is assumed here. Liberate 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

Linetime sells Liberate to larger firms, which tend to have high matter volumes and an accounts department that runs credit control inside the system. Customisation by Linetime is part of the offer. A move therefore begins with an inventory of what was changed for this firm, and with the accounts team, whose billing schedules, credit control procedures and purchase ledger all have to be closed off or carried over.

  1. Customised for the firm

    Linetime offers customisation to meet a firm’s own needs, and long-standing clients may have screens, fields and processes built for them. Those additions are not in any manual. We ask the firm and the vendor for a list, then confirm it against the database, so a field built only for this firm is not missed.

  2. Categories and tags, not folders

    Documents are organised by tags and by categories the firm defines. A matter’s documents may never have been in a folder. For a destination that files by folder, the category becomes the folder name, tags are carried as metadata where the new system has it, and uncategorised documents are placed in a general folder for review.

  3. Documents under version control

    Liberate keeps documents under version control. A migration normally takes the latest version of each document. Where the firm needs earlier drafts, we establish how Liberate stores them and whether the destination has its own versioning to receive them, then test on a matter with a long drafting history.

  4. Credit control procedures

    Credit control is run inside Liberate, with procedures that can be set at client and matter level. An unpaid bill may be part-way through a chasing sequence at cutover. The debtor balances move as figures. Alongside them, the stage each debt has reached is exported as a list so the accounts team can pick up the chase.

  5. Scheduled bills in progress

    Billing can be scheduled, so some clients are billed automatically on set dates. Those schedules do not transfer. They are listed before cutover with their amounts and dates, the last scheduled run is completed in Liberate, and the equivalent arrangement is set up in the new system before the next one falls due.

More about moving off Liberate

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

Liberate to SharePoint: what firms ask

How do we find out what was customised for us?

Start with the people who asked for it: accounts, department heads, IT. Linetime’s records of development work for the firm help as well. We then compare the firm’s database with the list, looking for tables and fields that hold data but appear in nobody’s account, and ask what they were for.

Does our purchase ledger move?

Only if the new system, or an accounting package beside it, has a purchase ledger. Supplier records and unpaid supplier invoices are extracted and loaded there as opening items. Paid history stays in the archive. A firm moving to a product without office accounts decides on its accounting package during the analysis.

Can the move be staged by department?

Case data can sometimes be staged. Accounts cannot be split easily, because billing and the ledgers for the whole firm sit in one system. Running two systems also means two places to check conflicts. Most firms move everything in one cutover and stage the training instead.

Do trust balances in Liberate have a place in SharePoint?

That is confirmed in the analysis. We could not establish it from the two products’ own material, so it is checked against your data in Liberate before the plan is fixed. If SharePoint turns out to have no place for trust ledgers, they are kept as a readable archive and the firm decides where trust accounting runs.

What happens to records SharePoint has no place for?

On this route that is time entries, billing records and the firm’s accounts. They are exported from Liberate 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 Liberate data is loaded into SharePoint?

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

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

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