Data migration route
Document Locator to Litify migration
Document Locator is a server-based document management system, and Litify is a cloud case management system. The move is matching each file in Document Locator to its case in Litify.
Document LocatorServer- Documents: Carried across
- Tasks: Carried across
- Emails: Carried with mapping
- Custom fields: Carried with mapping
- Notes: Confirmed in the analysis
- Templates: Confirmed in the analysis
LitifyCloud- 2 carried
- 2 mapped
- 2 to confirm
What moves
What moves from Document Locator to Litify
Each row is a kind of record Document Locator holds, whether Litify has a place for it, and what is planned. On this route two kinds of record carry across, two kinds need mapping and two 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 placeLoaded to the document component and attached to matters. | 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 place in partShown on the activity timeline. How old email is loaded is confirmed in the analysis. | Carried with mapping |
| NotesFile notes, matter notes and contact notes | To be confirmed | To be confirmed | Confirmed in the analysis |
| TasksTo-dos and workflow steps assigned to people | Held in partWorkflow and approval steps routed to people. | Has a place | Carried across |
| Custom fieldsFields and record types the firm added itself | HeldMetadata is applied through profiles the administrator defines. | Has a placeCustom fields are created before loading. | Carried with mapping |
| TemplatesPrecedents, document templates and automation | To be confirmed | Has a place in partTemplates are rebuilt in Litify’s document generation. | Confirmed in the analysis |
What the plans mean
- Carried across
- Litify has a place for this kind of record. It is loaded there and checked against Document Locator.
- Carried with mapping
- Litify 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
Every document goes to the case it belongs to.
A case management system expects each document to sit on a case, usually in a category such as correspondence, medical records or court documents. Document Locator organises files its own way, by profile or by folder. So the move needs two rules: which case a file belongs to, and which category it goes in. The first comes from client and matter references or folder names. The second comes from a document type or a subfolder, and where neither exists the files arrive uncategorised and are marked as such.
Cases must exist in Litify before documents can be attached to them. If the system is already live, files are matched to its case list and the unmatched ones are reported. If it is new, the case list is created first. Dates, authors and file names are kept. Email comes across as message files. Where several versions of a document exist, the firm chooses between loading the latest and loading them all.
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. Litify 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 Litify
Loading a firm into Litify is done inside a Salesforce environment that has been configured for that firm, normally by Litify or one of its implementation partners. The data work fits around that project. Old records are mapped to parties, roles, intakes and matters and loaded into the Salesforce objects behind them, and documents are loaded separately and attached.
The design comes first
Case types, stages and page layouts are decided during discovery, before any load. A load into a half-configured environment has to be repeated when a field changes. The data mapping is written against the agreed design and updated whenever the design moves, so the two stay in step.
One party, many roles
Contacts from the old system become parties, and each appearance on a matter becomes a role. Duplicate contacts turn into duplicate parties with their roles divided between them. Duplicates are merged before the load where they can be identified, since separating them afterwards means pointing every role at the right party again.
Open enquiries load as intakes
Leads and enquiries that have not signed belong in intakes, not matters. They are loaded with their source and status so that conversion reports start from a true position. Old declined enquiries are loaded only if the firm wants them for conflict checking, and are marked so they do not count as live.
Documents load after records
Files are loaded into the document component once the matters exist, because each one is attached to a matter record. Folder structure is set per case type beforehand. Large injury files with medical records and video take time to transfer, and that time is planned into the cutover weekend.
Validation rules reject bad rows
A configured environment enforces required fields and validation rules, and old data seldom satisfies all of them. Rows that fail are reported by the load. They are fixed in the source and run again, or the rule is relaxed for migrated records, and the firm decides which for each rule.
How NewLaw runs it
Four steps, in this order.
Nothing financial lands in Litify on this route, which makes it repeatable: a load can be run again until it is right. The maker of Litify 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 Litify. 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 Litify 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 Litify. 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 Litify
Loaded data is not yet a working system. The maker of Litify runs or arranges the set-up of its product, so this is what has to be decided and put in place in Litify, whoever does the work, before people rely on it from the first day.
A Litify implementation is a configuration project on Salesforce, run by Litify or an implementation partner with the firm’s own project team. Discovery sessions with each department come first. The decisions that follow shape the system: what an intake asks, how a matter moves through its stages, who sees what, and which other systems are connected.
Set-up decisions in Litify
- Define intake questionnaires and the rules for conversion
- Set case types, matter stages and page layouts
- Build matter plans that create tasks at each stage
- Design document folders and generation templates per case type
- Configure user roles and sharing for restricted matters
- Decide on timekeeping, billing and accounting integrations
Questions
Document Locator to Litify: 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 Litify?
Litify stores documents. Loaded to the document component and attached to matters. 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 Litify?
Most of it does on paper. Notes 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 Litify 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 Litify?
Emails and custom fields are carried with mapping, so each mapping is agreed with you first. Notes 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 Litify
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 Litify are the names and marks of their owners, used here only to identify the two systems.
Moving from Document Locator to Litify?
Tell us what you are moving. You get a plan and a fixed price after the analysis.
We reply within one business day.