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

Data migration route

SharePoint to Litify migration

SharePoint is cloud file storage, and Litify is a cloud case management system. The move is matching each file in SharePoint to its case in Litify.

FromSharePointCloud
  1. Matters: Carried across
  2. Contacts: Carried across
  3. Documents: Carried across
  4. Calendar: Carried across
  5. Tasks: Carried across
  6. Emails: Carried with mapping
  7. Custom fields: Carried with mapping
  8. Templates: Carried with mapping
  9. Notes: Confirmed in the analysis
ToLitifyCloud
  • 5 carried
  • 3 mapped
  • 1 to confirm
What the two products hold. The analysis confirms it field by field.

What moves

What moves from SharePoint to Litify

Each row is a kind of record SharePoint holds, whether Litify has a place for it, and what is planned. On this route five kinds of record carry across, three kinds need mapping and one kind is confirmed in the analysis.

Records in SharePoint and their place in Litify
RecordIn SharePointIn LitifyWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeld in partNo matter record as such; firms model matters as sites, libraries, folders or list rows.Has a placeMatters, by case type.Carried across
ContactsClients, other parties and referrersHeld in partOnly if the firm keeps a contacts list in a SharePoint list.Has a placeLoaded as parties and connected by roles.Carried across
DocumentsFiles stored in or linked from the systemHeldFiles in document libraries, with versions, columns and check-out.Has a placeLoaded to the document component and attached to matters.Carried across
EmailsEmails saved to matters or to the storeHeld in partOnly messages saved into a library as .msg or .eml files.Has a place in partShown on the activity timeline. How old email is loaded is confirmed in the analysis.Carried with mapping
NotesFile notes, matter notes and contact notesHeld in partOneNote notebooks and site pages, where the firm used them.To be confirmedConfirmed in the analysis
CalendarAppointments, court dates and deadlinesHeld in partCalendar lists exist; most firms keep calendars in Outlook instead.Has a placeCalendar events on the matter.Carried across
TasksTo-dos and workflow steps assigned to peopleHeld in partTask lists exist where a firm built them.Has a placeCarried across
Custom fieldsFields and record types the firm added itselfHeldColumns and content types defined by the firm on libraries and lists.Has a placeCustom fields are created before loading.Carried with mapping
TemplatesPrecedents, document templates and automationHeld in partPrecedents as files; a library can offer document templates through content types.Has a place in partTemplates are rebuilt in Litify’s document generation.Carried with mapping

What the plans mean

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

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

Every document goes to the case it belongs to.

A case management system expects each document to sit on a case, usually in a category such as correspondence, medical records or court documents. SharePoint organises files its own way, by profile or by folder. So the move needs two rules: which case a file belongs to, and which category it goes in. The first comes from client and matter references or folder names. The second comes from a document type or a subfolder, and where neither exists the files arrive uncategorised and are marked as such.

Cases must exist in Litify before documents can be attached to them. If the system is already live, files are matched to its case list and the unmatched ones are reported. If it is new, the case list is created first. Dates, authors and file names are kept. Email comes across as message files. Where several versions of a document exist, the firm chooses between loading the latest and loading them all.

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

Where the data is now

No two firms’ SharePoint looks alike, because the firm or its IT provider designed it. One has a site per client, another a single library with a folder per matter, a third filed everything by column and has no folders at all. The move starts by reading that design, since the matter a document belongs to may be recorded in any of several places.

  1. Find every site that holds files

    Matter documents can be in the main document site, in the Files tab of a Teams channel, and in the separate sites that private channels create. An administrator’s site list is the starting point. Each library is then classed as matter files, firm administration or abandoned, and only the first two are scoped.

  2. Columns hold what folders do not

    Where a library uses columns for matter number, client or document type, that information is not in the file or its path. A copy taken through the sync app cannot be relied on to carry it. The column values are exported with each document so the destination can file by them, or they are written into the folder path.

  3. Unique permissions need a report

    Permissions can be broken at site, library, folder and file level, and after a few years they usually have been. Nobody can state from memory who may see what. A permissions report across the libraries shows which matters are restricted, and that list is carried into the security design of the new system.

  4. Lists are data, not documents

    A matter register, a deeds register or a conflict list kept as a SharePoint list is a table. It moves as records, by export to a spreadsheet and a mapping of its columns to fields, on a separate track from the files. Firms often forget these lists exist until the analysis turns them up.

  5. Versions and checked-out files

    Libraries keep major versions, and some keep minor drafts as well. The firm chooses how many come across. Files that someone checked out and never checked back in are a known trap: other people may see only an older copy, so these are found and checked in before the final collection.

More about moving off SharePoint

Where it is going

Loading a firm into Litify is done inside a Salesforce environment that has been configured for that firm, normally by Litify or one of its implementation partners. The data work fits around that project. Old records are mapped to parties, roles, intakes and matters and loaded into the Salesforce objects behind them, and documents are loaded separately and attached.

  1. The design comes first

    Case types, stages and page layouts are decided during discovery, before any load. A load into a half-configured environment has to be repeated when a field changes. The data mapping is written against the agreed design and updated whenever the design moves, so the two stay in step.

  2. One party, many roles

    Contacts from the old system become parties, and each appearance on a matter becomes a role. Duplicate contacts turn into duplicate parties with their roles divided between them. Duplicates are merged before the load where they can be identified, since separating them afterwards means pointing every role at the right party again.

  3. Open enquiries load as intakes

    Leads and enquiries that have not signed belong in intakes, not matters. They are loaded with their source and status so that conversion reports start from a true position. Old declined enquiries are loaded only if the firm wants them for conflict checking, and are marked so they do not count as live.

  4. Documents load after records

    Files are loaded into the document component once the matters exist, because each one is attached to a matter record. Folder structure is set per case type beforehand. Large injury files with medical records and video take time to transfer, and that time is planned into the cutover weekend.

  5. Validation rules reject bad rows

    A configured environment enforces required fields and validation rules, and old data seldom satisfies all of them. Rows that fail are reported by the load. They are fixed in the source and run again, or the rule is relaxed for migrated records, and the firm decides which for each rule.

More about moving into Litify

How NewLaw runs it

Four steps, in this order.

Nothing financial lands in Litify on this route, which makes it repeatable: a load can be run again until it is right. The maker of Litify says that it, or its partners, load firms into the product. Where the firm uses that service, NewLaw’s part is the work around it: the analysis, the clean-up in SharePoint and checking each trial against SharePoint.

  1. Analysis

    We read what SharePoint holds and how it is organised, then agree with you where each kind of record will sit in Litify. 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 Litify and checked against SharePoint: 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 SharePoint, a final pass over a weekend picks up what changed since the trial. SharePoint 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 SharePoint 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 fromSharePoint
Moving toLitify

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 SharePoint holds

    What is in it, how its records link, and where each piece would sit in Litify. 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

Setting up Litify

Loaded data is not yet a working system. The maker of Litify runs or arranges the set-up of its product, so this is what has to be decided and put in place in Litify, whoever does the work, before people rely on it from the first day.

A Litify implementation is a configuration project on Salesforce, run by Litify or an implementation partner with the firm’s own project team. Discovery sessions with each department come first. The decisions that follow shape the system: what an intake asks, how a matter moves through its stages, who sees what, and which other systems are connected.

Set-up decisions in Litify

  • Define intake questionnaires and the rules for conversion
  • Set case types, matter stages and page layouts
  • Build matter plans that create tasks at each stage
  • Design document folders and generation templates per case type
  • Configure user roles and sharing for restricted matters
  • Decide on timekeeping, billing and accounting integrations

Questions

SharePoint to Litify: what firms ask

We only use Teams. Do we have anything in SharePoint to move?

Yes. The Files tab in every Teams channel is a folder in a SharePoint site, and each private or shared channel has a site of its own. If matter documents were dropped into channels, they are in SharePoint. Chat messages are stored differently and are a separate question from the files.

Can the new system keep our SharePoint columns?

It depends whether the destination has matching fields. Matter number and client usually map to the matter itself. Document type and author often have a home on the document profile. A column with nowhere to go is either written into the document’s name or description, or left behind, and the firm sees which before the move.

Should we move to SharePoint or to a legal document management system?

That is a decision about how the firm works, and it is the firm’s to make. What can be said plainly is that SharePoint arrives empty of legal structure: matters, filing rules and email filing are all designed and built. The analysis sets out what that build involves for the firm’s matter volume.

Do documents from SharePoint keep their folders and dates in Litify?

Litify stores documents. Loaded to the document component and attached to matters. Each file is placed under the client and matter it came from, and created and modified dates are carried, so a document still shows when it was written. The trial load is checked by count and by opening a sample.

Does everything in SharePoint have a place in Litify?

Most of it does on paper. Notes could not be confirmed from the two products’ own material, so those are checked in the analysis. Anything that turns out to have no place in Litify is kept as a readable archive, and you see which before the move.

What has to be decided before SharePoint data is loaded into Litify?

Emails, 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

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

Moving from SharePoint to Litify?

Tell us what you are moving. You get a plan and a fixed price after the analysis.

We reply within one business day.