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

Data migration route

Microsoft Graph to Litify migration

Microsoft Graph is a cloud specialist tool, and Litify is a cloud case management system. This is a narrow move: the records Microsoft Graph holds are matched to the people and matters in Litify.

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

What moves

What moves from Microsoft Graph to Litify

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

Records in Microsoft Graph and their place in Litify
RecordIn Microsoft GraphIn LitifyWhat is planned
ContactsClients, other parties and referrersHeldEach user’s Outlook contacts, and the firm’s directory of users.Has a placeLoaded as parties and connected by roles.Carried across
DocumentsFiles stored in or linked from the systemHeldFiles in each user’s OneDrive and in SharePoint document libraries.Has a placeLoaded to the document component and attached to matters.Carried across
EmailsEmails saved to matters or to the storeHeldMessages and attachments in every Exchange Online mailbox, by folder.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, where staff keep notes there.To be confirmedConfirmed in the analysis
CalendarAppointments, court dates and deadlinesHeldEach user’s Outlook calendar and any shared calendars.Has a placeCalendar events on the matter.Carried across
TasksTo-dos and workflow steps assigned to peopleHeld in partPersonal tasks in To Do and team plans in Planner.Has a placeCarried across
Custom fieldsFields and record types the firm added itselfHeld in partOutlook categories on items; columns on SharePoint libraries.Has a placeCustom fields are created before loading.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 Microsoft Graph.
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

A narrow move, checked like a large one.

A source like Microsoft Graph holds one kind of record well: an address book, a calendar, a set of signed documents. None of it is organised by matter. The work is matching each contact to a contact in Litify, and each appointment or signed document to the matter it belongs to. Where a match cannot be made from a name, an email address or a reference, the record is listed for the firm to place by hand or leave behind.

The volume is small and the load is quick, which makes it tempting to skip the checks. They still apply. Contacts are compared with what Litify already holds, so the move does not create a second copy of every client. Dates are checked for time zones, a common fault in calendar data. Signed documents arrive with their completion date and, where the service provides one, the audit record as a separate file.

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

Where the data is now

Firms seldom leave Microsoft 365. They keep it for mail and move the matter-related part of what is in it into a practice or document system. So the work is selection: which mailboxes, which folders, which libraries, from what date. Access through Microsoft’s interface is granted by the firm’s administrator, who decides what can be read.

  1. Consent sets the reach

    An administrator approves the access. Application permissions are powerful: one granted for mail can read every mailbox in the firm. How far that reach is narrowed to the mailboxes and sites in scope, and when the access is removed, are the firm’s decisions, made with its administrator before anything is read.

  2. Mailboxes are not matter files

    Each mailbox mixes client work with staff matters, newsletters and private messages. The firm chooses between filing whole folders the owner already organised by matter, filing by correspondent and reference, or filing only from a date forward. Partners’ mailboxes usually get their own conversation before anything is read.

  3. Shared mailboxes and leavers

    Much matter correspondence sits outside personal mailboxes: in accounts@ and reception@ shared mailboxes, and in the mailboxes of former staff that were converted or kept on a licence. These are listed from the tenant, so the scope is drawn from what exists and not from the current staff list.

  4. Files in two kinds of place

    Documents are in personal OneDrives and in SharePoint libraries, including the ones behind Teams. Both are reached the same way, but they are scoped differently: OneDrives person by person, libraries site by site. A file shared from one person’s OneDrive is collected once, from its owner.

  5. Microsoft sets the pace

    Microsoft throttles heavy use of the interface and tells the calling software to wait. A large mailbox estate cannot be read in an afternoon however fast the connection. The trial load measures the real rate for this tenant, and the cutover window is planned from that figure.

More about moving off Microsoft Graph

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 Microsoft Graph and checking each trial against Microsoft Graph.

  1. Analysis

    We read what Microsoft Graph 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 Microsoft Graph: 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 Microsoft Graph, a final pass over a weekend picks up what changed since the trial. Microsoft Graph 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 Microsoft Graph 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 fromMicrosoft Graph
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 Microsoft Graph 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

Microsoft Graph to Litify: what firms ask

Does this mean you can read all our email?

Only what the firm’s administrator consents to, for as long as that consent stands. Which permission is granted, which mailboxes are in scope and when the access ends are the firm’s decisions, settled before any mailbox is read. The consent stays visible in the Microsoft 365 admin tools, where the administrator can revoke it.

Will email be removed from our mailboxes when it is filed to matters?

Not as part of the move. Filing to a matter copies the message, and the original stays in the mailbox, in the folder it was in. Whether staff later tidy their mailboxes, and how the new system files incoming mail from then on, is a separate set-up decision.

We are staying on Microsoft 365. Do calendars and contacts need to move?

Usually the calendars stay where they are and the new system connects to them. Contacts are different. Clients held in people’s personal Outlook contact lists are worth gathering into the practice system once, merged against the client records already there, so the firm ends up with a single entry for each client.

Do documents from Microsoft Graph 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 Microsoft Graph 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 Microsoft Graph data is loaded into Litify?

Emails and custom fields 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

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

Moving from Microsoft Graph 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.