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

Moving into a system

Migrating to Microsoft SQL Server

Microsoft’s relational database server, used by firms as a queryable archive for the records of a practice system they are leaving. This page sets out what Microsoft SQL Server has a place for, what loading a firm’s records into it involves and what NewLaw sets up beyond the data.

What it accepts

What has a place in Microsoft SQL Server

Of the fourteen kinds of record that matter to a move, Microsoft SQL Server has a place for all fourteen, three in part. A record with no place there is kept as a readable archive.

  • MattersYesA table of matters linked to clients, parties and fee earners.
  • ContactsYesPeople and companies, with their roles on each matter.
  • DocumentsIn partAs files in folders with an index table; storing files in the database is possible.
  • EmailsIn partAs message files with an index table, or as rows of header fields.
  • NotesYesRows of text linked to matters and contacts.
  • CalendarYesRows of appointments and key dates; nothing displays them as a calendar.
  • TasksYesRows with assignee, due date and status.
  • Time and expensesYesTime and expense rows with rates and billed status.
  • BillingYesInvoices, lines and receipts as rows; invoice PDFs kept as files.
  • Trust moneyYesTransactions and balances for look-up; it is not a trust accounting system.
  • Firm accountsYesGeneral ledger journals and balances, where the source held them.
  • Custom fieldsYesAs added columns, or a table of field names and values.
  • TemplatesIn partPrecedent files can be stored; automation does not run here.
  • IntakeYesEnquiry rows, where the source recorded them.

Moving into it

Arriving in Microsoft SQL Server

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.

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

How NewLaw runs it

Four steps, in this order.

A route into a database or an export produces an archive, not a working system, so the steps are about completeness and proof.

  1. Analysis

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

Choose the system the firm is on now. 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

Type a few letters to find it. If it is not listed, type its name anyway.

Moving toMicrosoft SQL Server

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 your old system 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.

Where firms come from

Routes into Microsoft SQL Server

Each route has a page of its own: what moves, what has no place here and how the move is run.

The system

What Microsoft SQL Server is

SQL Server is Microsoft’s relational database engine. It is general-purpose software with no legal features of its own, and it is the database underneath a number of server-based practice systems, which is confirmed system by system. A firm chooses it as a destination when it wants the records of a retired system kept in a form that can be queried and reported on.

It installs on a Windows or Linux server, on the firm’s own hardware or a hosted machine, and comes in several editions. The free Express edition caps the size of each database: 50 GB in SQL Server 2025, and less in earlier versions. Data is held in tables with defined columns and relationships, read with SQL queries or through reporting tools, and protected by logins, roles and backups.

Kind
Database or export
Runs as
On the firm’s server or a hosted server
Made by
Microsoft
Mainly used in
Worldwide
Also known as
SQL Server, MS SQL, MSSQL, SQL Server Express, Azure SQL

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 SQL Server and the other product names and logos on this page belong to their owners and are used only to identify the systems.

Moving into 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.