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

Data migration route

Microsoft Graph data to Microsoft SQL Server

Microsoft Graph is a cloud specialist tool, and Microsoft SQL Server is a database on a server the firm runs. This is not a move to a new working system: the route writes out what Microsoft Graph holds and keeps it readable and open to queries.

FromMicrosoft GraphCloud
  1. Contacts: Exported in full
  2. Notes: Exported in full
  3. Calendar: Exported in full
  4. Tasks: Exported in full
  5. Documents: Exported with mapping
  6. Emails: Exported with mapping
  7. Custom fields: Exported with mapping
ToMicrosoft SQL ServerServer
  • 4 carried
  • 3 mapped
What the two products hold. The analysis confirms it field by field.

What moves

What moves from Microsoft Graph to Microsoft SQL Server

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

Records in Microsoft Graph and their place in Microsoft SQL Server
RecordIn Microsoft GraphIn Microsoft SQL ServerWhat is planned
ContactsClients, other parties and referrersHeldEach user’s Outlook contacts, and the firm’s directory of users.Has a placePeople and companies, with their roles on each matter.Exported in full
DocumentsFiles stored in or linked from the systemHeldFiles in each user’s OneDrive and in SharePoint document libraries.Has a place in partAs files in folders with an index table; storing files in the database is possible.Exported with mapping
EmailsEmails saved to matters or to the storeHeldMessages and attachments in every Exchange Online mailbox, by folder.Has a place in partAs message files with an index table, or as rows of header fields.Exported with mapping
NotesFile notes, matter notes and contact notesHeld in partOneNote notebooks, where staff keep notes there.Has a placeRows of text linked to matters and contacts.Exported in full
CalendarAppointments, court dates and deadlinesHeldEach user’s Outlook calendar and any shared calendars.Has a placeRows of appointments and key dates; nothing displays them as a calendar.Exported in full
TasksTo-dos and workflow steps assigned to peopleHeld in partPersonal tasks in To Do and team plans in Planner.Has a placeRows with assignee, due date and status.Exported in full
Custom fieldsFields and record types the firm added itselfHeld in partOutlook categories on items; columns on SharePoint libraries.Has a placeAs added columns, or a table of field names and values.Exported with mapping

What the plans mean

Exported in full
Microsoft SQL Server has a place for this kind of record. It is loaded there and checked against Microsoft Graph.
Exported with mapping
Microsoft SQL Server 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

Not a new system. A complete copy the firm can query.

Writing Microsoft Graph out to Microsoft SQL Server is not a migration into a new working system. Nobody will open a matter there on Monday morning. The aim is a complete, faithful copy that can be queried and reported on after the old system is gone. So the rules change. Nothing is cleaned or merged unless the firm asks, because an archive should show the records as they were. Every table and field is carried, including those a new system would have had no place for.

What makes an archive usable is the description that goes with it. The export is delivered with a plain account of each table: what it holds, how it joins to the others, what the codes mean. Record counts and financial totals are agreed to the reports in Microsoft Graph as at the export date, so the archive can stand as the record. Documents are exported beside the data with a table linking each file to its matter. Access is restricted, since the archive holds everything the live system did.

Microsoft Graph is hosted by its maker and Microsoft SQL Server sits on equipment the firm controls. The data leaves a service that was backed up for the firm and arrives somewhere the firm must back up itself, so backup and access are arranged before the export is copied in. What Microsoft Graph will release depends on its export tools, and that is confirmed in the analysis.

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

There are two ways to put a retired system into SQL Server, and they suit different firms. The old system’s own database can be restored as it is. Or the data can be loaded into a new set of tables designed to be read by people. The first is quicker and harder to use. Which suits is worked out in the analysis, and the choice is the firm’s.

  1. Restored copy or rebuilt schema

    Where the old practice system already kept its data in SQL Server, a backup can be restored onto a new server. The tables keep the vendor’s names and codes, which can be cryptic, and reading them takes someone who knows that product’s database. A rebuilt schema uses plain names such as Matter and TrustTransaction.

  2. No screens come with it

    A database has no matter screen. Someone has to ask it questions in SQL or through a reporting tool. Saved views can be set up for the things the firm will really look up: a matter with its parties, its ledger, its time entries and its list of documents. Which are worth having is agreed in the analysis.

  3. Documents sit beside the database

    Files are normally kept in folders on the same server, with a table recording each document’s matter, title, dates and path. Storing the files inside the database is possible but makes it far larger. On the Express edition, the cap on database size rules that out for most firms’ document stores.

  4. The edition follows the size

    A firm’s tables may fit within the Express limit once documents are kept outside the database. A long trust and time history at a larger firm may not. The size of the source data is measured in the analysis, and the edition is chosen from that figure with the firm’s IT provider.

  5. Backups and a test restore

    An archive that is never backed up is one disk failure from gone. Backups belong to the firm’s IT provider: a full one once the load is finished, and a schedule if anything is still being added. It is worth restoring one to a second machine as a test, because a backup that has never been restored is only a hope.

More about moving into Microsoft SQL Server

How NewLaw runs it

Four steps, in this order.

This route produces an archive, not a working system, so the steps are about completeness and proof.

  1. Analysis

    We read what Microsoft Graph holds, table by table, and agree with you what the copy in Microsoft SQL Server must be able to answer later. Everything Microsoft Graph holds is in scope unless you take it out.

  2. Clean-up, if you want it

    An archive should show the records as they were, so nothing is merged or corrected unless you ask. Where the copy is also meant for reporting, duplicate and inconsistent entries are tidied in a working copy and the original values are kept beside them.

  3. Trial export

    The data is written to Microsoft SQL Server as a trial and checked against Microsoft Graph: record counts, totals where Microsoft Graph holds money, the links between records, and a sample of documents opened from the export. Exceptions are listed for you to decide.

  4. Final export

    After the last day of work in Microsoft Graph, the export is run a final time and checked again. There is nothing to go live. Microsoft Graph is kept read only until you are satisfied the copy answers what you need, and it is handed over with a written description of its contents.

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 toMicrosoft SQL Server

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 Microsoft SQL Server. 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

Microsoft SQL Server is a place to keep data, not a system staff work in each day. What is agreed is how the data is laid out, who can reach it, and what is handed over with it.

Standing up SQL Server as an archive is IT work shared with the firm’s provider. A server or instance is chosen, logins are created for the few people who need to read the data, and nobody is given rights to change it. Views and a handful of reports are built for the common questions, and the IT provider owns the backup routine.

What is agreed and set up

  • Server, instance and edition agreed with the IT provider
  • Read-only logins and roles for named staff
  • Views for matter, ledger, time and document look-ups
  • Backup schedule and who tests a restore
  • Plain names and descriptions for tables and columns
  • Excel or Power BI connected for reporting

Questions

Microsoft Graph to Microsoft SQL Server: 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.

Does the copy in Microsoft SQL Server hold documents from Microsoft Graph?

In part. As files in folders with an index table; storing files in the database is possible. What Microsoft SQL Server can hold is written out once its mapping is agreed, and the rest is kept beside the data as files that open without Microsoft Graph.

Does everything in Microsoft Graph have a place in Microsoft SQL Server?

On paper, yes: each kind of record Microsoft Graph holds has a place in Microsoft SQL Server. 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 is written out to Microsoft SQL Server?

Documents, emails and custom fields are exported with mapping, so each mapping is agreed with you first. The firm also decides who may open the archive and how long it is kept.

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 Microsoft SQL Server are the names and marks of their owners, used here only to identify the two systems.

Moving from Microsoft Graph to Microsoft SQL Server?

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

We reply within one business day.