Data migration route
LexWorkplace data to Microsoft SQL Server
LexWorkplace is a cloud document management system, 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.
LexWorkplaceCloud- Matters: Exported in full
- Notes: Exported in full
- Documents: Exported with mapping
- Emails: Exported with mapping
- Custom fields: Exported with mapping
- Templates: Exported with mapping
- Tasks: Confirmed in the analysis
Microsoft SQL ServerServer- 2 carried
- 4 mapped
- 1 to confirm
What moves
What moves from LexWorkplace to Microsoft SQL Server
Each row is a kind of record LexWorkplace holds, whether Microsoft SQL Server has a place for it, and what is planned. On this route two kinds of record carry across, four kinds need mapping and one kind is confirmed in the analysis.
| Record | What is planned | ||
|---|---|---|---|
| MattersMatters or cases, with their numbers, types, parties and status | Held in partName, custom matter ID, client, type, location, assigned staff, tags, open and close dates. | Has a placeA table of matters linked to clients, parties and fee earners. | Exported in full |
| DocumentsFiles stored in or linked from the system | HeldAny file type, in folders within a matter, with type, status, tags and versions. | 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 | HeldSaved to a matter from Outlook, with their own folders on the matter’s Email tab. | 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 | HeldRich-text Matter Notes, kept beside the matter’s documents and email. | Has a placeRows of text linked to matters and contacts. | Exported in full |
| TasksTo-dos and workflow steps assigned to people | To be confirmed | Has a placeRows with assignee, due date and status. | Confirmed in the analysis |
| Custom fieldsFields and record types the firm added itself | Held in partFirm-defined document types, statuses, tags and matter types. | Has a placeAs added columns, or a table of field names and values. | Exported with mapping |
| TemplatesPrecedents, document templates and automation | Held in partTemplates are stored as files in Firm Documents and copied into matters. | 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 LexWorkplace.
- 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 LexWorkplace 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 LexWorkplace 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.
LexWorkplace 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 LexWorkplace will release depends on its export tools, and that is confirmed in the analysis.
Where the data is now
Leaving LexWorkplace
A matter can be exported from LexWorkplace as a zip file, with its documents and emails in the folder structure the firm built. That export leaves out three things that usually matter: the matter notes, the matter’s own details, and earlier versions of documents. A full move collects those separately and joins them back to the right matter before anything is loaded elsewhere.
What the matter export omits
Export Matter gives a Documents folder and an Email folder. Matter Notes are not in it, nor are previous versions, nor the matter’s custom ID, client, type, staff and dates. Matter details can be exported to CSV from the matters list. The plan sets out how notes and versions are obtained, and whether older versions are needed at all.
Custom Matter ID is the key
LexWorkplace lets a firm give each matter a custom ID so that it matches the number in the practice management system. Where firms have used it consistently, documents line up with matters in the destination by that number. Where it is blank or free-typed, matters are matched by name and client, and the doubtful ones are listed.
Automatic versioning adds up
By default every save from Word makes a new numbered version, so a heavily edited contract can carry dozens. Firms on manual versioning have fewer, numbered 1.0, 1.1, 2.0. The analysis reports version counts so the firm can choose between bringing all of them, the latest only, or the latest plus the first.
Trash and archive states
Each matter, folder and item is active, archived or in the Trash Bin. Archived content stays in place but is not indexed or searched, and a matter export includes trashed items that have not been permanently deleted. Both need a decision before extraction, or deleted drafts reappear in the new system.
Firm Documents sit outside matters
Templates, policies and other internal files are kept in Firm Documents, which behaves like a matter but belongs to no client. It has no single export button: items are selected and downloaded. It is easy to leave off the list, and it is where the firm’s own templates are kept.
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 LexWorkplace holds, table by table, and agree with you what the copy in Microsoft SQL Server must be able to answer later. Everything LexWorkplace 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 LexWorkplace: record counts, totals where LexWorkplace 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 LexWorkplace, the export is run a final time and checked again. There is nothing to go live. LexWorkplace 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 LexWorkplace 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 LexWorkplace 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
LexWorkplace to Microsoft SQL Server: what firms ask
Does the matter export include our notes and old versions?
No. LexWorkplace’s own help says an exported matter contains documents and email, and does not include Matter Notes, matter details or previous versions of documents. Matter details can be exported to CSV separately. If notes and versions are needed in the next system, they are collected another way, and that is scoped in the analysis.
We use Clio Manage with LexWorkplace. What moves where?
Clio holds the clients, contacts, time, bills and trust records. LexWorkplace holds the documents, emails and notes, linked matter to matter. If both are being replaced, the two are extracted separately and joined on the matter. If only one is changing, the link to the other has to be rebuilt against the new matter numbers.
Does the copy in Microsoft SQL Server hold documents from LexWorkplace?
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 LexWorkplace.
Does everything in LexWorkplace have a place in Microsoft SQL Server?
Most of it does on paper. Tasks 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 LexWorkplace 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. Tasks are confirmed in the analysis. The firm also decides who may open the archive and how long it is kept.
Other routes
Other routes from LexWorkplace and into Microsoft SQL Server
Other destinations from LexWorkplace
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.
LexWorkplace and Microsoft SQL Server are the names and marks of their owners, used here only to identify the two systems.
Moving from LexWorkplace 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.