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

Data migration route

USB drives data to Microsoft SQL Server

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

FromUSB drivesFiles
  1. Documents: Exported with mapping
  2. Emails: Exported with mapping
ToMicrosoft SQL ServerServer
  • 2 mapped
What the two products hold. The analysis confirms it field by field.

What moves

What moves from USB drives to Microsoft SQL Server

Each row is a kind of record USB drives hold, whether Microsoft SQL Server has a place for it, and what is planned. On this route two kinds need mapping.

Records in USB drives and their place in Microsoft SQL Server
RecordIn USB drivesIn Microsoft SQL ServerWhat is planned
DocumentsFiles stored in or linked from the systemHeldLoose files and folders; no sharing, versions or access control on FAT formats.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 partSaved message files or copied Outlook data files, where someone put them there.Has a place in partAs message files with an index table, or as rows of header fields.Exported with mapping

What the plans mean

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 USB 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 USB 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 USB drives stays untouched until the copy in Microsoft SQL Server has been checked.

Where the data is now

Each USB drive is its own small puzzle, and the first task is to say what it is. A working copy of matter files is handled one way. The backup of an old practice system is a database to be restored, not a set of documents. Material received from a client belongs to one matter and may need to be kept exactly as it was received.

  1. Identify each drive first

    Every drive is labelled and listed, and its contents are classed as loose documents, a system backup, or third-party material for a known matter. A stick holding a .bak or other backup file goes to whoever is handling that old system, because the documents inside cannot be reached by copying.

  2. Copy once, then put it away

    Flash drives can fail without warning, and each reading is a small risk. It is safer to copy a drive once and do the sorting and matching on the copy than to keep going back to the stick. How the copy is made and checked is agreed with the firm’s IT provider, and the drive goes back in the safe.

  3. Times shift on FAT drives

    FAT file systems store times in local time and record the modified time only to the nearest two seconds. The same document on a stick and on the server can show dates an hour apart after a daylight saving change. Matching dates is therefore an unreliable way to find duplicates on these drives.

  4. Encrypted drives need their password

    A drive protected with BitLocker To Go or a hardware keypad opens only with its password or recovery key. Where the person who set it has left, the firm’s IT provider may hold a recovery key. If nobody does, the contents cannot be read, and that is recorded against the drive.

  5. Material from clients and other parties

    Drives received in a matter are evidence of what was handed over. The original folder structure and file dates are preserved in the copy, and the files are filed to the matter as a set under the date received. What happens to the physical drive, kept or returned, follows the firm’s own file rules.

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

USB drives to Microsoft SQL Server: what firms ask

We have a box of old USB drives and no idea what is on them. Is it worth including them?

Usually it is worth the listing, which is quick. Each drive is summarised: how many files, what kinds, what date range, which client names appear. The firm then chooses which drives are loaded, which are kept as they are, and which hold nothing but copies of files already on the server.

One drive has a backup from the system we used ten years ago. Can that be brought in?

Possibly. It depends on whether the backup can be restored, which needs a copy of the old software or a database engine that reads its format. That is tested on its own before any promise is made. If it restores, its matters and documents are treated like any other source system.

Is it safe to plug unknown drives into our network?

That is a question for the firm’s IT provider, and the cautious answer is no. A drive of unknown origin can carry malicious software as well as documents. How unknown drives are read, and on which machine, is agreed with the IT provider before any of them is opened.

Does the copy in Microsoft SQL Server hold documents from USB 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 USB drives.

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

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

Documents and emails 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

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

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