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

Data migration route

Server drives data to Microsoft SQL Server

Server drives are plain files on equipment the firm controls, 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.

FromServer drivesFiles
  1. Notes: Exported in full
  2. Documents: Exported with mapping
  3. Emails: Exported with mapping
  4. Templates: Exported with mapping
  5. Billing: Confirmed in the analysis
ToMicrosoft SQL ServerServer
  • 1 carried
  • 3 mapped
  • 1 to confirm
What the two products hold. The analysis confirms it field by field.

What moves

What moves from Server drives to Microsoft SQL Server

Each row is a kind of record Server drives hold, whether Microsoft SQL Server has a place for it, and what is planned. On this route one kind of record carries across, three kinds need mapping and one kind is confirmed in the analysis.

Records in Server drives and their place in Microsoft SQL Server
RecordIn Server drivesIn Microsoft SQL ServerWhat is planned
DocumentsFiles stored in or linked from the systemHeldFiles in folders; path, name and dates are the only description.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 partMessages dragged from Outlook into matter folders as .msg 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 partFile notes kept as Word documents or text files in the matter folder.Has a placeRows of text linked to matters and contacts.Exported in full
BillingInvoices, payments and debtor balancesHeld in partCopies of invoices saved as PDFs; no ledger.Has a placeInvoices, lines and receipts as rows; invoice PDFs kept as files.Confirmed in the analysis
TemplatesPrecedents, document templates and automationHeld in partA precedents folder of Word templates, with or without macros.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 Server drives.
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.
Confirmed in the analysis
We could not confirm this from the two products’ own material, so it is checked against your data before the plan is fixed.

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 Server drives 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 Server drives know 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.

Both ends are on equipment the firm controls, so the work is done on the firm’s own network with its IT provider. Disk space for a second full copy is checked first. The original in Server drives stays untouched until the copy in Microsoft SQL Server has been checked.

Where the data is now

Moving off a server drive is a job of interpretation. The files copy easily. Working out which matter each folder belongs to does not, because the tree was built by many hands over many years and the naming changed with every new secretary. The analysis reads the tree, proposes rules for matching folders to matters, and shows the firm what the rules fail to place.

  1. The folder tree is the index

    Each matter folder is matched to a matter in the new system by the client name and matter number in its path. Some match exactly. Others say only Smith or Old files 2011. The unmatched folders are listed with their size and last-modified date, and the firm assigns them, archives them or leaves them.

  2. Paths past 260 characters

    Windows has long limited a full path to 260 characters, and deep matter trees routinely pass it. Such files exist but Explorer and Word may refuse to open or copy them. They are counted in the analysis and shortened to suit the destination’s own limit.

  3. Permissions do not travel with files

    Who may open the Partners folder or a restricted matter is set in Windows permissions on the server. A copy of the files should not be assumed to carry any of that. The permissions on each top-level and matter folder are reported before the move and rebuilt as groups or matter security in the new system.

  4. Folders another system owns

    The same drive often holds the document store of a practice management or accounting system, in folders with coded names. Those files are indexed in that system’s database and mean little without it. They are moved through the system that owns them, and kept out of the loose-file scan.

  5. What accumulates over twenty years

    Server drives collect shortcuts, temporary Word files, copies named Final v3 and whole duplicated matter folders. Exact duplicates are identified and reported. The firm sets the rule for near-duplicates, since only a person can say whether Final or Final v3 is the one that went to court.

More about moving off Server drives

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

Server drives to Microsoft SQL Server: what firms ask

Our folders are a mess. Do we have to tidy them before the move?

No, and it is better not to rename things by hand beforehand. The analysis works from the tree as it stands and proposes matching rules. Staff time is better spent on the short list of folders the rules cannot place, and on deciding what is old enough to archive without filing it to a matter.

Will the dates on our documents be kept?

The modified date on each file is read from the server and passed to the new system where it accepts a document date. Created dates on a server are less reliable, because copying files between drives in the past can have changed them. The trial load compares document dates on sample matters against the old folders.

Can staff keep using the S: drive after go-live?

For reading, yes: the drive is kept read only as the fall-back record. Not for filing. If people can still save to the old drive, some will, and within a month the firm has two places to look for every document. The drive is switched to read only at cutover.

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

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 Server drives.

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

Most of it does on paper. Billing records could not be confirmed from the two products’ own material, so those are checked in the analysis. Anything that turns out to have no place in Microsoft SQL Server is kept as a readable archive, and you see which before the move.

What has to be decided before Server drives are written out to Microsoft SQL Server?

Documents, emails and templates are exported with mapping, so each mapping is agreed with you first. Billing records are confirmed in the analysis. 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

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

Moving from Server drives 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.