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

Data migration route

Microsoft Graph to Neos migration

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

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

What moves

What moves from Microsoft Graph to Neos

Each row is a kind of record Microsoft Graph holds, whether Neos has a place for it, and what is planned. On this route five kinds of record carry across and two kinds need mapping.

Records in Microsoft Graph and their place in Neos
RecordIn Microsoft GraphIn NeosWhat is planned
ContactsClients, other parties and referrersHeldEach user’s Outlook contacts, and the firm’s directory of users.Has a placeParties, providers and case contacts. Contacts can be imported from CSV.Carried across
DocumentsFiles stored in or linked from the systemHeldFiles in each user’s OneDrive and in SharePoint document libraries.Has a placeCase Docs tab, organised in sub-tabs.Carried across
EmailsEmails saved to matters or to the storeHeldMessages and attachments in every Exchange Online mailbox, by folder.Has a place in partEmails tagged to a case are held. Loading old mail is scoped in the analysis.Carried with mapping
NotesFile notes, matter notes and contact notesHeld in partOneNote notebooks, where staff keep notes there.Has a placeCarried across
CalendarAppointments, court dates and deadlinesHeldEach user’s Outlook calendar and any shared calendars.Has a placeCase calendar entries.Carried across
TasksTo-dos and workflow steps assigned to peopleHeld in partPersonal tasks in To Do and team plans in Planner.Has a placeLoaded as checklist items.Carried across
Custom fieldsFields and record types the firm added itselfHeld in partOutlook categories on items; columns on SharePoint libraries.Has a placeUser-defined fields are created on the relevant tab first.Carried with mapping

What the plans mean

Carried across
Neos has a place for this kind of record. It is loaded there and checked against Microsoft Graph.
Carried with mapping
Neos holds this differently, or in part. Each field or value is matched to its place before loading, and you see the mapping first.

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

Neos expects personal injury data in its own tab structure, so loading a firm means deciding which tab each old record belongs on. Parties, insurance and counsel map directly from most injury systems. Money maps to value items. Anything the standard tabs lack becomes a user-defined field, which has to be created before the load.

  1. Every figure needs a value code

    Costs, medical bills, fees and settlement amounts are loaded as value items, and each carries a value code. The code list is agreed with the firm’s accounts staff first. A figure loaded under the wrong code is reported in the wrong place, so the list is tested on real cases before the bulk load.

  2. Lists are set up first

    Cases are loaded against case types, statuses and staff assignments that already exist in Neos. Those lists are set up, and the old system’s values tidied to match, before the trial load. Misspelt attorney names and unused case types in the source are cleaned out at the same stage.

  3. Documents go to sub-tabs

    Files land on the Case Docs tab under sub-tabs, which staff can view as a list or as folders. The old system’s folders or categories are mapped to a fixed set of sub-tabs. Without that, every personal habit of naming folders is reproduced and the folder view becomes hard to read.

  4. Reminders split two ways

    Neos fills its dashboards from checklists and case calendars. Old diary entries and tasks are sorted between them: dated appointments and court events to the calendar, and to-dos to the checklist. An item assigned to several people in the old system may need one named owner, and the firm chooses who.

  5. Assembly runs its own conversions

    Assembly migrates firms into Neos with its own team and tooling, and offers routes from self-service templates to a full conversion. Where the firm uses that service, outside help goes on the work around it: cleaning the source, checking the converted cases against the old system, and listing exceptions.

More about moving into Neos

How NewLaw runs it

Four steps, in this order.

Nothing financial lands in Neos on this route, which makes it repeatable: a load can be run again until it is right. The maker of Neos 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 Neos. 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 Neos 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 toNeos

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 Neos. 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 Neos

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

Neos comes set up for injury work, so implementation is mostly choosing among its options and connecting the firm’s other tools. The lists that drive reporting are decided first, then checklists, then documents. Assembly provides its own implementation team, and the firm’s internal lead still has to make the decisions listed below.

Set-up decisions in Neos

  • Set case types, statuses and staff roles
  • Agree the value code list with accounts staff
  • Build checklists for each case type and stage
  • Create user-defined fields for data the tabs lack
  • Prepare document templates for the generation wizard
  • Connect Microsoft 365, QuickBooks and the phone system

Questions

Microsoft Graph to Neos: 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 Neos?

Neos stores documents. Case Docs tab, organised in sub-tabs. 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 Neos?

On paper, yes: each kind of record Microsoft Graph holds has a place in Neos. Whether every field fits is a separate question, and the analysis answers it field by field. Anything with no place comes across as a note or stays behind, and you see which before the move.

What has to be decided before Microsoft Graph data is loaded into Neos?

Emails and custom fields are carried with mapping, so each mapping is agreed with you first. 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 Neos are the names and marks of their owners, used here only to identify the two systems.

Moving from Microsoft Graph to Neos?

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

We reply within one business day.