Data migration route
Microsoft Graph to Sync.com migration
Microsoft Graph is a cloud specialist tool, and Sync.com is cloud file storage. What moves is the files, plus a readable export of everything else the old system holds.
Microsoft GraphCloud- Documents: Carried across
- Emails: Carried with mapping
- Notes: Carried with mapping
Sync.comCloud- Contacts: Kept as a readable archive
- Calendar: Kept as a readable archive
- Tasks: Kept as a readable archive
- Custom fields: Kept as a readable archive
- 1 carried
- 2 mapped
- 4 archived
What moves
What moves from Microsoft Graph to Sync.com
Each row is a kind of record Microsoft Graph holds, whether Sync.com has a place for it, and what is planned. On this route one kind of record carries across, two kinds need mapping and four kinds have no place in Sync.com and are archived.
| Record | What is planned | ||
|---|---|---|---|
| ContactsClients, other parties and referrers | HeldEach user’s Outlook contacts, and the firm’s directory of users. | No place | Kept as a readable archive |
| DocumentsFiles stored in or linked from the system | HeldFiles in each user’s OneDrive and in SharePoint document libraries. | Has a placeFiles and folders within the path limit; some file types are skipped by the apps. | Carried across |
| EmailsEmails saved to matters or to the store | HeldMessages and attachments in every Exchange Online mailbox, by folder. | Has a place in partMessage files such as .msg or .eml, filed in the matter’s folder. | Carried with mapping |
| NotesFile notes, matter notes and contact notes | Held in partOneNote notebooks, where staff keep notes there. | Has a place in partOnly as a document written out to the matter’s folder. | Carried with mapping |
| CalendarAppointments, court dates and deadlines | HeldEach user’s Outlook calendar and any shared calendars. | No place | Kept as a readable archive |
| TasksTo-dos and workflow steps assigned to people | Held in partPersonal tasks in To Do and team plans in Planner. | No place | Kept as a readable archive |
| Custom fieldsFields and record types the firm added itself | Held in partOutlook categories on items; columns on SharePoint libraries. | No place | Kept as a readable archive |
What the plans mean
- Carried across
- Sync.com has a place for this kind of record. It is loaded there and checked against Microsoft Graph.
- Carried with mapping
- Sync.com holds this differently, or in part. Each field or value is matched to its place before loading, and you see the mapping first.
- Kept as a readable archive
- Sync.com has no place for it. It is exported in a format that opens without Microsoft Graph 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
An export the firm can open without the system.
Sync.com holds files, and most of what Microsoft Graph holds is records. This route is therefore an export job. Each kind of record is written out in a format that opens without the system it came from: lists as spreadsheets, statements and invoices as PDFs, attachments as the files they were. The export is laid out in folders that make sense to someone who never used Microsoft Graph, by client or by year, with a short index file saying what is where.
Firms do this when a subscription is ending, when a system is being retired, or to meet a retention rule. The test of the result is whether a question can still be answered from it years later: what was this client invoiced, who signed this agreement and when. So the trial export is checked by asking those questions of it. Totals are agreed to the system’s own reports, and access to the folder in Sync.com is limited before the export is copied in.
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 Sync.com are finished.
Where the data is now
Leaving Microsoft Graph
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.
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.
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.
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.
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.
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.
Where it is going
Arriving in Sync.com
A firm that moves its files to Sync is usually doing so for confidentiality, and the load has to respect how the service is built to deliver it. Files are encrypted before they leave the computer. Nobody at Sync can look inside the account to confirm what arrived, so the checking is done from the firm’s side, against the list of what was sent.
Files or Vault
Open matters belong in Files, where they sync to the people working on them. Closed matters can go to Vault, which holds them in the cloud without putting a copy on every laptop. The firm supplies its open and closed matter lists so each folder is sent to the right side.
A 248 character path limit
Sync sets a maximum path length of 248 characters to stay compatible between Windows and Mac, and its apps skip anything longer. That is tighter than most systems a firm will be coming from. Folder names are shortened in the plan, and Sync’s own guidance favours a tree only a few levels deep.
What the apps leave out
The desktop apps do not upload shortcut files, temporary Office files or names containing a slash, and they warn against several other characters on Windows. A copy to Vault produces a transfer report listing what was skipped. That report is reconciled against the source file list after every load.
Permissions come from the top folder
Sharing is set on a folder and flows down to all of its contents. A matter that needs different access from the rest of a client’s work cannot simply sit one level down with tighter settings. It becomes its own shared folder, and those exceptions are identified before the tree is built.
Shared folders count against storage
A shared folder is added to each member’s account and normally counts towards their quota, and it syncs to their computer as a real folder. Sharing the whole client tree with every person can fill both. Shares are sized to teams, and the allowance needed per user is worked out from the document volumes.
How NewLaw runs it
Four steps, in this order.
Nothing financial lands in Sync.com on this route, which makes it repeatable: a load can be run again until it is right.
Analysis
We read what Microsoft Graph holds and how it is organised, then agree with you where each kind of record will sit in Sync.com. Anything with no place there stays behind or is archived, and you see which before the move.
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.
Trial load
A trial is loaded into Sync.com 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.
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
What happens after you send it
- A free first call
We go through your answers with you and ask about anything they leave open.
- An analysis of what Microsoft Graph holds
What is in it, how its records link, and where each piece would sit in Sync.com. Anything with no place there comes across as a note or stays behind, and you see which before the move.
- 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
Sync.com 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.
A Sync set-up comes down to accounts and shares. A team plan gives an administrator control over users, two-factor authentication and password resets, which matters more than usual in a service the provider says it cannot see into. The shared folders are then created to match the firm’s teams and its restricted matters.
What is agreed and set up
- Administrator account and a user for each staff member
- Two-factor authentication enforced across the firm
- Team shared folders with view or edit permission per person
- Which matters live in Files and which in Vault
- Rules for client links: passwords, expiry dates, upload rights
- Desktop app installed, with a filing guide for new matters
Questions
Microsoft Graph to Sync.com: 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 Sync.com?
Sync.com stores documents. Files and folders within the path limit; some file types are skipped by the apps. 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.
What happens to records Sync.com has no place for?
On this route that is contacts, calendar entries, tasks and custom fields. They are exported from Microsoft Graph 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 Microsoft Graph data is loaded into Sync.com?
Emails and notes 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.
Other routes
Other routes from Microsoft Graph and into Sync.com
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.
Choose your systems
Technology stack selection
Decide which practice management system your firm runs, with the evidence and the cost beside it.
About four weeks for a firm of about 15 people. Fixed price, set after a free first call.
Move your data
Data migration
Your data is cleaned up before anything moves, then a trial load is checked against the old system.
Fixed price, agreed after the analysis.
Set up your new system
Implementation
Your new system set up around the way your firm works: configuration, document automation and training.
A small firm of 1 to 10 users typically takes 4 to 8 weeks. A mid-sized firm of 10 to 50 users takes 8 to 16 weeks.
Put AI to work
AI advisory and enablement
A small group of your people learn to use an approved AI tool on real work, under written rules.
Two to four weeks for a small first group. Fixed price, set after a free first call.
Microsoft Graph and Sync.com are the names and marks of their owners, used here only to identify the two systems.
Moving from Microsoft Graph to Sync.com?
Tell us what you are moving. You get a plan and a fixed price after the analysis.
We reply within one business day.