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

Data migration route

SharePoint data to Microsoft SQL Server

SharePoint is cloud file storage, and Microsoft SQL Server is a database on a server the firm runs. What lands in Microsoft SQL Server is the register: every file’s name, place, dates and details, with the files themselves stored beside it.

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

What moves

What moves from SharePoint to Microsoft SQL Server

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

Records in SharePoint and their place in Microsoft SQL Server
RecordIn SharePointIn Microsoft SQL ServerWhat 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 placeA table of matters linked to clients, parties and fee earners.Exported in full
ContactsClients, other parties and referrersHeld in partOnly if the firm keeps a contacts list in a SharePoint list.Has a placePeople and companies, with their roles on each matter.Exported in full
DocumentsFiles stored in or linked from the systemHeldFiles in document libraries, with versions, columns and check-out.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 storeHeld in partOnly messages saved into a library as .msg or .eml files.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 and site pages, where the firm used them.Has a placeRows of text linked to matters and contacts.Exported in full
CalendarAppointments, court dates and deadlinesHeld in partCalendar lists exist; most firms keep calendars in Outlook instead.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 partTask lists exist where a firm built them.Has a placeRows with assignee, due date and status.Exported in full
Custom fieldsFields and record types the firm added itselfHeldColumns and content types defined by the firm on libraries and lists.Has a placeAs added columns, or a table of field names and values.Exported with mapping
TemplatesPrecedents, document templates and automationHeld in partPrecedents as files; a library can offer document templates through content types.Has a place in partPrecedent files can be stored; automation does not run here.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 SharePoint.
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

The files, and a register of what each one is.

A database is a poor place to keep documents and a good place to keep facts about them. On this route the files from SharePoint are exported to storage the firm controls, and Microsoft SQL Server receives the register: one row per file, with its path, size, dates, author and whatever profile or folder details existed. That register is what makes a large export searchable. It also proves completeness, since the row count and total size can be agreed to the source.

How useful the register is depends on how much SharePoint knows about each file. A document management system has a profile to carry. A plain folder has only a path and dates, and the client or matter has to be read out of folder names. Where versions or an audit history exist, each becomes a table of its own. The export is checked by picking documents at random in the source, finding them through Microsoft SQL Server, and opening the file to confirm it is the same one.

SharePoint 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 SharePoint will release depends on its export tools, and that is confirmed in the analysis.

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

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 SharePoint holds, table by table, and agree with you what the copy in Microsoft SQL Server must be able to answer later. Everything SharePoint 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 SharePoint: record counts, totals where SharePoint 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 SharePoint, the export is run a final time and checked again. There is nothing to go live. SharePoint 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 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 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 SharePoint 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

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

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

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

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

On paper, yes: each kind of record SharePoint 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 SharePoint is written out to Microsoft SQL Server?

Documents, emails, custom fields and templates 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

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

Moving from SharePoint 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.