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

Data migration route

Litify to SharePoint migration

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

FromLitifyCloud
  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
  10. Trust money: Confirmed in the analysis
  11. Firm accounts: Confirmed in the analysis
ToSharePointCloud
  1. Time and expenses: Kept as a readable archive
  2. Billing: Kept as a readable archive
  3. Intake: Kept as a readable archive
Readable archiveNo place in SharePoint
  • 1 carried
  • 7 mapped
  • 3 to confirm
  • 3 archived
What the two products hold. The analysis confirms it field by field.

What moves

What moves from Litify to SharePoint

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

Records in Litify and their place in SharePoint
RecordIn LitifyIn SharePointWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldMatters, with parties, calendar events, tasks, time and costs attached.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 referrersHeldParties, connected to intakes and matters through roles.Has a place in partOnly as rows in a list built for the purpose.Carried with mapping
DocumentsFiles stored in or linked from the systemHeldHeld in Litify’s document component, with tags, versions and templates.Has a placeFiles in libraries, with columns and versions.Carried across
EmailsEmails saved to matters or to the storeHeld in partEmails appear on the case activity timeline. Mailboxes stay in the mail system.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 deadlinesHeldCalendar events on the matter and the activity timeline.Has a place in partPossible as a list; usually left in Outlook.Carried with mapping
TasksTo-dos and workflow steps assigned to peopleHeldTasks, including those generated by matter plans.Has a place in partPossible as a list; no legal workflow built in.Carried with mapping
Time and expensesTime and expense entries, billed and unbilledHeldTimekeeping, with time entries tied to the matter.No placeKept as a readable archive
BillingInvoices, payments and debtor balancesHeldBilling and eBilling, aimed chiefly at insurance defence work.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 payablesTo be confirmedNo placeConfirmed in the analysis
Custom fieldsFields and record types the firm added itselfHeldFields are added through Salesforce configuration.Has a placeColumns and content types on libraries and lists.Carried with mapping
TemplatesPrecedents, document templates and automationHeldDocument templates with conditional logic. Matter plans automate tasks.Has a place in partPrecedents as files; templates can be offered from a library.Carried with mapping
IntakeLeads, enquiries, intake forms and pipelinesHeldIntakes with questionnaires, lead scoring and marketing source tracking.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 Litify.
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 Litify 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 Litify 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 Litify.

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

Where the data is now

A firm leaving Litify is leaving a Salesforce environment that has usually been shaped by an implementation team and several years of administrators. Its data is all there and can be queried. The effort is in reading the configuration, separating Litify’s own objects from the firm’s additions, and collecting the documents, which are managed by a separate component.

  1. Parties and roles

    A person or company is a party, and a role ties that party to an intake or matter as client, defendant, insurer, provider or something the firm defined. One party can hold different roles on different matters. Roles are extracted with the party, so the destination gets one contact with its relationships and not a copy per matter.

  2. Intakes become matters

    An intake is its own record with a questionnaire and a status, converted to a matter when the client signs. Turned-down and referred-out intakes stay as intakes and can far outnumber matters in a high-volume practice. They are counted separately, and the firm decides how many go to the new system.

  3. Documents sit beside the records

    Files are managed by Docrio, Litify’s document component. How they are stored, and how a full copy is obtained, is established in the analysis. Records and files are generally extracted by different routes and joined on the matter. Counts are checked per matter after the join, including on closed matters.

  4. Injury detail in related records

    Plaintiff firms typically record damages, insurance, liens, negotiations and settlement figures in records related to the matter, and each firm names and extends them its own way. These lists are extracted as tables with the matter reference. Where the destination has no equivalent, each becomes a schedule saved to the matter.

  5. Automation stays behind

    Matter plans, flows and validation rules are Salesforce configuration. They explain why the data looks the way it does, for example why a field is always filled at a given stage, but they cannot be exported into another product. Each is documented and used as the specification for workflows in the destination.

More about moving off Litify

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

Litify to SharePoint: what firms ask

Do we need a Salesforce administrator to get our data out?

Someone with administrator access is needed, yes. The extraction reads the environment’s objects directly, and the administrator grants that access and explains what was customised. If the person who built it has left, the configuration is read from the system itself, which takes longer.

Are our documents included when Litify data is exported?

Do not assume so. Documents are managed by a separate component, and an export of matter records should not be expected to contain the files themselves. Both routes are covered in the plan and joined on the matter. A matter is only counted as moved when its files are attached to it.

We are moving to Litify. Who does the configuration?

Litify or one of its implementation partners normally configures the system. The migration fits into that project: the data mapping follows their design, and trial loads go into a test environment before production. It helps to agree early who owns the field list, because data and configuration change each other.

Do trust balances in Litify 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 Litify 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 intake records. They are exported from Litify 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 Litify 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, trust ledgers and the firm’s accounts 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

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

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