Data migration route
Box data to Microsoft SQL Server
Box 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.
BoxCloud- Notes: Exported in full
- Tasks: Exported in full
- Documents: Exported with mapping
- Emails: Exported with mapping
- Custom fields: Exported with mapping
- Templates: Exported with mapping
Microsoft SQL ServerServer- 2 carried
- 4 mapped
What moves
What moves from Box to Microsoft SQL Server
Each row is a kind of record Box holds, whether Microsoft SQL Server has a place for it, and what is planned. On this route two kinds of record carry across and four kinds need mapping.
| Record | What is planned | ||
|---|---|---|---|
| DocumentsFiles stored in or linked from the system | HeldFiles in folders, with version history, comments and optional metadata. | 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 store | Held in partOnly as message files saved or emailed into a folder. | 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 notes | Held in partBox Notes are documents written inside Box, not notes recorded against a matter. | Has a placeRows of text linked to matters and contacts. | Exported in full |
| TasksTo-dos and workflow steps assigned to people | Held in partTasks can be assigned on a file; they are not matter tasks. | Has a placeRows with assignee, due date and status. | Exported in full |
| Custom fieldsFields and record types the firm added itself | Held in partMetadata templates add fields to files and folders. | Has a placeAs added columns, or a table of field names and values. | Exported with mapping |
| TemplatesPrecedents, document templates and automation | Held in partPrecedents are kept as ordinary files; Box Notes has its own note templates. | 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 Box.
- 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 Box 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 Box 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.
Box 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 Box will release depends on its export tools, and that is confirmed in the analysis.
Where the data is now
Leaving Box
Leaving Box is mostly a question of ownership and of what is attached to files but not inside them. Folders belong to whoever created them unless the firm set Box up with administrator-owned folders. Comments, tasks, metadata values and earlier versions live in Box beside each file. A plain download brings the current files and none of the rest.
Every top-level folder has an owner
Box lets either administrators or ordinary users own top-level folders, depending on how the account was set up. Where users own them, matter files are spread across personal accounts, including those of people who have left. The inventory is taken from the administrator’s side so that nobody’s folders are missed.
Each person sees a different tree
A collaborator invited part-way down sees that folder as their own top level. Two lawyers describing the same matter folder may give different paths to it. The structure that moves is the owner’s full tree, and staff are shown where their familiar folders sit within it before go-live.
Box Notes are not Word files
Notes written in Box Notes exist only inside Box. They are not files in the usual sense and do not open in Word. Firms that kept file notes or meeting minutes this way need them converted to a document format before the move, and the conversion is checked on a sample in the trial load.
Shared links point at Box
Clients and other parties may hold links to matter folders or single documents. Those links point at Box and cannot be relied on once the account is closed. A report of links and outside collaborators shows which matters have live external access, so the firm can tell those people where documents will be from cutover.
Versions depend on the plan
How many earlier versions of a file Box keeps is set by the plan and can be reduced by an administrator. What is not there cannot be moved. Where versions do exist, the destination may take them as true versions or only as separately named copies, which is settled in the analysis.
Where it is going
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.
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.
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.
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.
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.
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.
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.
Analysis
We read what Box holds, table by table, and agree with you what the copy in Microsoft SQL Server must be able to answer later. Everything Box holds is in scope unless you take it out.
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.
Trial export
The data is written to Microsoft SQL Server as a trial and checked against Box: record counts, totals where Box holds money, the links between records, and a sample of documents opened from the export. Exceptions are listed for you to decide.
Final export
After the last day of work in Box, the export is run a final time and checked again. There is nothing to go live. Box 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 Box 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 Box 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.
- 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
Box to Microsoft SQL Server: what firms ask
Do our document versions come across from Box?
Only versions Box still holds can be moved, and that number depends on the plan. How they arrive depends on the destination: a document management system usually has version slots, a plain drive does not. The trial load can show one sample matter both ways if the firm is undecided.
What happens to folders we shared with clients?
The collaborators and shared links belong to Box and do not transfer. Before cutover the firm gets a list of every folder with outside access. If the new system has a client portal or its own sharing, access is set up there, and clients are told where to find their documents from then on.
Can we move only open matters and leave the rest in Box?
Yes, if the folder names or metadata show which matters are open. Where they do not, the open matter list from the practice management system is matched to folders by client and matter number. Closed folders can stay in Box read only for as long as the firm keeps the subscription.
Does the copy in Microsoft SQL Server hold documents from Box?
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 Box.
Does everything in Box have a place in Microsoft SQL Server?
On paper, yes: each kind of record Box 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 Box 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.
Other routes
Other routes from Box and into Microsoft SQL Server
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.
Box and Microsoft SQL Server are the names and marks of their owners, used here only to identify the two systems.
Moving from Box 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.