Data migration route
Document Locator to LexWorkplace migration
Document Locator is a server-based document management system, and LexWorkplace is a cloud one. The test of this move is whether profiles, versions and access rules survive it.
Document LocatorServer- Documents: Carried across
- Emails: Carried across
- Custom fields: Carried with mapping
- Notes: Confirmed in the analysis
- Tasks: Confirmed in the analysis
- Templates: Confirmed in the analysis
LexWorkplaceCloud- 2 carried
- 1 mapped
- 3 to confirm
What moves
What moves from Document Locator to LexWorkplace
Each row is a kind of record Document Locator holds, whether LexWorkplace has a place for it, and what is planned. On this route two kinds of record carry across, one kind needs mapping and three kinds are confirmed in the analysis.
| Record | What is planned | ||
|---|---|---|---|
| DocumentsFiles stored in or linked from the system | HeldIn repository folders, with automatic versions, profiles and an audit log. | Has a placeFiled to a matter or to Firm Documents, in folders. | Carried across |
| EmailsEmails saved to matters or to the store | Held in partEmails and attachments can be captured and managed with the documents. | Has a placeOn the matter’s Email tab, in their own folders. | Carried across |
| NotesFile notes, matter notes and contact notes | To be confirmed | Has a placeAs Matter Notes on the matter’s Notes tab. | Confirmed in the analysis |
| TasksTo-dos and workflow steps assigned to people | Held in partWorkflow and approval steps routed to people. | To be confirmed | Confirmed in the analysis |
| Custom fieldsFields and record types the firm added itself | HeldMetadata is applied through profiles the administrator defines. | Has a place in partOld categories can become document types, statuses or tags. | Carried with mapping |
| TemplatesPrecedents, document templates and automation | To be confirmed | Has a place in partStored as files in Firm Documents. | Confirmed in the analysis |
What the plans mean
- Carried across
- LexWorkplace has a place for this kind of record. It is loaded there and checked against Document Locator.
- Carried with mapping
- LexWorkplace 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
Profiles, versions and security, kept intact.
Between two document management systems the files are the easy part. What a firm has built in Document Locator is everything around them: the profile on each document, its version history, who can open it, which workspace it sits in. LexWorkplace has its own model for each. Document types and custom profile fields are mapped one to one where they can be. Versions are loaded in order, so the latest in the old system is the latest in the new one.
Security is checked on its own. A restricted client or an information barrier must arrive restricted, so access groups are created in LexWorkplace before any document is loaded, and a sample of restricted workspaces is tested with a user who should not see them. Document numbers are worth keeping, since they appear in footers and old emails. Where the new system assigns its own, the old number is stored as a searchable field.
Document Locator runs on the firm’s own equipment, so the data is collected there: a copy of the database and the folders its documents sit in, taken with the firm’s IT provider or over a remote session. LexWorkplace is hosted by its maker, so loading depends on the import tools and access it provides. The old machine is kept, read only, as the fall-back record.
Where the data is now
Leaving Document Locator
Because Document Locator presents itself as folders in Windows, people assume the documents can be dragged out like files on a drive. They are in a SQL Server repository. A copy made that way should not be expected to bring versions, profile values or permissions with it. A planned extraction reads the repository for those, and for check-out state as well.
A repository, not a share
The folder tree users see is drawn from a Microsoft SQL Server repository. On-premises, that database is on the firm’s server and can be backed up and read. In the hosted service it is on Azure and access is arranged with ColumbiaSoft. Which of the two applies shapes how the work begins.
Folders stand in for matters
There is no client or matter record, so firms build the equivalent with a folder convention, sometimes created automatically by a project-folder rule. The convention is read off the tree and tested: how many top-level folders match a client in the practice management system, and how many are something else.
Version numbers and notes
Every check-in adds a version with an incrementing number, users can add a version note, and prior versions can be promoted. For controlled documents such as policies and precedents, that history is the point of the system. The firm decides folder by folder whether history comes across or only the current version.
Workflow and required reading
Approvals in progress, review reminders and acknowledgements that staff have read a policy are records of process. A legal document system will usually have nowhere to put them. Reports are run from Document Locator before cutover and saved as documents, so the evidence is kept even though the workflow is not.
Where it is going
Arriving in LexWorkplace
LexWorkplace expects every document and email to belong to a matter, so loading it starts with the matter list: name, custom ID, client, type and dates. Uptime Legal states that it runs migration and onboarding for its customers itself. The preparation is getting the old system’s content into a clean client and matter structure, with the exceptions resolved, ready for that load.
Matters carry little, by design
A matter record holds a name, a custom ID, a client, a type, a location, assigned staff, tags and open and close dates. Parties, court details and financial data have no fields. Those stay in the practice management system, and the two are tied together by using the same matter number as the custom ID.
Clients are only containers
LexWorkplace says plainly that its clients are for grouping matters, not for client management. A client has a name, a status, primary attorneys and tags. Addresses, phone numbers and contact history from the old system are not loaded here. They go to the practice management system or stay behind.
Three tabs per matter
Content arrives as documents, emails or notes, each on its own tab with its own folders. Emails held as message files in an old folder tree have to be recognised and loaded as emails, not as documents, or they will not appear where lawyers look for correspondence.
Closed matters and archive
A matter is closed by giving it a close date, and closed matters can be moved to archive storage, where they keep their place but are not searched or indexed until un-archived. Old matters can therefore be loaded and archived straight away. The firm sets the cut-off year.
Profiling is optional unless enforced
Document type, status and tags are not required by default, though a firm can switch on mandatory profiling for matters. If the old system had document types, they are mapped to LexWorkplace types during the load. If it had none, the firm chooses between loading unprofiled and assigning types by folder name.
How NewLaw runs it
Four steps, in this order.
Nothing financial lands in LexWorkplace on this route, which makes it repeatable: a load can be run again until it is right. The maker of LexWorkplace says that it, or its partners, load firms into the product. Where the firm uses that service, NewLaw’s part is the work around it: the analysis, the clean-up in Document Locator and checking each trial against Document Locator.
Analysis
We read what Document Locator holds and how it is organised, then agree with you where each kind of record will sit in LexWorkplace. Anything with no place there stays behind or is archived, and you see which before the move.
Clean-up
Duplicate clients, matters and folders are merged where they can be identified, and naming is put into one format, before anything is copied. It is not always possible to find every one, so some may carry across.
Trial load
A trial is loaded into LexWorkplace and checked against Document Locator: record and file counts, the links between records, document dates, and a sample opened by your own people. Exceptions are listed for you to decide.
Cutover
There is no financial cutover on this route. After a short freeze on changes in Document Locator, a final pass over a weekend picks up what changed since the trial. Document Locator is kept read only as the fall-back record.
Fixed price, agreed after the analysis. How NewLaw moves legal data
Start
Start this migration
Tell us what is in Document Locator 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 Document Locator holds
What is in it, how its records link, and where each piece would sit in LexWorkplace. 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
Setting up LexWorkplace
Loaded data is not yet a working system. The maker of LexWorkplace runs or arranges the set-up of its product, so this is what has to be decided and put in place in LexWorkplace, whoever does the work, before people rely on it from the first day.
Setting LexWorkplace up for a firm is a short list of decisions made in its settings, plus software on each computer. The decisions are what the firm calls its matter types, document types and statuses, who can open which matters by default, and whether versioning is automatic or manual. The Launcher and the Outlook add-in are then installed for every user.
Set-up decisions in LexWorkplace
- Matter types, document types, statuses and tag conventions
- Groups, rights and default permissions for new matters
- Automatic or manual versioning, and whether profiling is mandatory
- Linking matters to Clio Manage where the firm uses it
- Launcher, Office and Outlook add-ins on each Windows or Mac computer
- A Firm Documents structure for templates, policies and internal files
Questions
Document Locator to LexWorkplace: what firms ask
Can we simply copy the folders out through Windows?
It will produce files, and for a small set that may be all that is needed. It should not be relied on for a whole repository, because versions, profile metadata, permissions and audit history are in the database. The analysis establishes what the repository records about a document beyond the file itself.
How do documents get matched to matters when there is no matter record?
By the folder path or a profile field, whichever the firm used consistently. A matter list from the practice management system is matched against folder names, and the matches, near-matches and orphans are reported. Near-matches are confirmed by someone at the firm who knows the files.
Do documents from Document Locator keep their folders and dates in LexWorkplace?
LexWorkplace stores documents. Filed to a matter or to Firm Documents, in folders. Each file is placed under the client and matter it came from, and created and modified dates are carried, so a document still shows when it was written. The trial load is checked by count and by opening a sample.
Does everything in Document Locator have a place in LexWorkplace?
Most of it does on paper. Notes, tasks and templates 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 LexWorkplace is kept as a readable archive, and you see which before the move.
What has to be decided before Document Locator data is loaded into LexWorkplace?
Custom fields are carried with mapping, so each mapping is agreed with you first. Notes, tasks and templates are confirmed in the analysis. The firm also decides which closed matters and how many versions of a document are in scope.
Other routes
Other routes from Document Locator and into 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.
Document Locator and LexWorkplace are the names and marks of their owners, used here only to identify the two systems.
Moving from Document Locator to LexWorkplace?
Tell us what you are moving. You get a plan and a fixed price after the analysis.
We reply within one business day.