Data migration route
eDOCS data to SQLite
eDOCS is a server-based document management system, and SQLite is a store of data kept as files the firm holds. What lands in SQLite is the register: every file’s name, place, dates and details, with the files themselves stored beside it.
eDOCSServer- Matters: Exported in full
- Documents: Exported with mapping
- Emails: Exported with mapping
- Custom fields: Exported with mapping
- Notes: Confirmed in the analysis
- Tasks: Confirmed in the analysis
- Templates: Confirmed in the analysis
SQLiteFiles- 1 carried
- 3 mapped
- 3 to confirm
What moves
What moves from eDOCS to SQLite
Each row is a kind of record eDOCS holds, whether SQLite has a place for it, and what is planned. On this route one kind of record carries across, three kinds need mapping and three kinds are confirmed in the analysis.
| Record | What is planned | ||
|---|---|---|---|
| MattersMatters or cases, with their numbers, types, parties and status | Held in partClient and matter are fields on the document profile, set up per library. | Has a placeA matters table keyed by matter number. | Exported in full |
| DocumentsFiles stored in or linked from the system | HeldFiles on document servers, each with a profile in the library’s SQL database. | Has a place in partListed in a table; the files themselves stay in folders beside the database. | Exported with mapping |
| EmailsEmails saved to matters or to the store | HeldFiled from Outlook through the email filing module. | Has a place in partAs message files in folders, indexed in a table. | Exported with mapping |
| NotesFile notes, matter notes and contact notes | To be confirmed | Has a placeA notes table linked to matters. | Confirmed in the analysis |
| TasksTo-dos and workflow steps assigned to people | To be confirmed | Has a placeA table of tasks and their status at the final date. | Confirmed in the analysis |
| Custom fieldsFields and record types the firm added itself | HeldProfile forms and the fields on them are designed for each library. | Has a placeColumns added to the table they belonged to. | Exported with mapping |
| TemplatesPrecedents, document templates and automation | To be confirmed | No placePrecedent files are kept in folders, not in the database. | Confirmed in the analysis |
What the plans mean
- Exported in full
- SQLite has a place for this kind of record. It is loaded there and checked against eDOCS.
- Exported with mapping
- SQLite 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 eDOCS are exported to storage the firm controls, and SQLite 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 eDOCS 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 SQLite, 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 eDOCS stays untouched until the copy in SQLite has been checked.
Where the data is now
Leaving eDOCS
An eDOCS library is usually long-lived. Many have come through several upgrades and more than one owner of the product. Moving off one means reading the SQL database and the document servers together, and it means dealing with what a long life leaves behind: retired users, superseded profile forms, and documents converted from the systems that came before it.
Three parts, read together
The library’s metadata is in a SQL database, the files are on one or more document servers, and the full-text index is separate. The database says which stored file belongs to which document and version. The database and the file stores are taken at the same point in time, and the trial load checks each profile against its file.
Profile forms changed over time
The profile form a document was saved with decides which fields it has. Firms redesign forms, add document types and retire others over the years. A document from 2006 may have fields that are no longer on the form. The analysis reads the fields present across the whole library, not only today’s form.
The records management module
Where the records module is in use, the library also holds information about retention and sometimes about paper files. Those are not documents, and a document system chosen for matter files may have no place for them. They are identified early so the firm can decide where its retention rules will be kept after the move.
Names the product has had
Staff may call the system Hummingbird, DM, OpenText or eDOCS depending on when they joined. It is the same product line. Old document references, macros and footers can use any of those names, which matters when searching the firm’s precedents for hard-coded links back to the library.
Where it is going
Arriving in SQLite
A SQLite archive suits a firm that wants the old system’s records kept, seldom consulted, and free of any server or subscription. Everything structured goes into one file. That simplicity moves the responsibility elsewhere: the file has no security of its own and no administrator watching it, so where it is stored and who can reach it are the real decisions.
One file, kept with the archive
Matters, contacts, time, invoices and trust transactions become tables in a single file. It is stored with the firm’s closed-matter records and can be copied like any document. A checksum recorded when the file is finalised lets anyone confirm, years later, that the copy they hold has not been altered, and the firm decides whether to keep one.
No logins inside the file
SQLite has no users or passwords. Anyone who can open the file can read every client’s ledger. Protection comes from where it is kept, such as a restricted folder or an encrypted volume, and that choice is the firm’s. It can suit an archive consulted by two people, and it is said plainly so nobody assumes otherwise.
Built for reading, not sharing
Only one program can write to the file at a time, and SQLite’s authors point people to a client/server database where many users share data over a network. A finished archive never meets that limit. It is the reason SQLite is used here for records that are closed and not for anything staff still update.
Documents stay outside it
Documents remain ordinary files in matter folders, and a table in the database lists each one with its matter, title, dates and path. Keeping them as files means they open with a double-click and can be handed to a client. The table is how a file is found by matter number instead of by guessing its name.
Someone has to open it
SQLite publishes its own command-line program for opening a database file, and other tools read the format too. None of that helps if nobody remembers how. Saved queries for the usual look-ups and a short note on which tool to use can sit in the same folder as the file, and the firm decides what it needs.
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 eDOCS holds, table by table, and agree with you what the copy in SQLite must be able to answer later. Everything eDOCS 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 SQLite as a trial and checked against eDOCS: record counts, totals where eDOCS 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 eDOCS, the export is run a final time and checked again. There is nothing to go live. eDOCS 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 eDOCS 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 eDOCS holds
What is in it, how its records link, and where each piece would sit in SQLite. 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
SQLite 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.
There is nothing to install on a server and nothing to license. The work is in making the file usable and safe to keep: naming it, documenting its tables, storing it where the firm’s records policy says archives go, and checking that a member of staff can open it and find a matter. Whether a second copy is held somewhere separate is the firm’s call.
What is agreed and set up
- File name, storage location and whether a second copy exists
- Whether a checksum is recorded for later verification
- Saved queries for matter, ledger and document look-ups
- Which tool staff will use to open the file
- Who may open the folder the file sits in
- Retention period and destruction date noted beside the file
Questions
eDOCS to SQLite: what firms ask
NetDocuments now owns eDOCS. Do we have to move?
NetDocuments has stated that there is no planned end of life for eDOCS and that it will keep supporting the on-premises platform. So the timing is the firm’s own decision. A firm that does move chooses its destination for its own reasons, and the migration is planned the same way whichever system that is.
How do document numbers and versions come across?
Each eDOCS document has a number and one or more versions, all recorded in the library database, and versions can be extracted one by one. A new system issues its own identifiers. The old document number is kept as a reference field or in the name where the firm still quotes it.
Does the copy in SQLite hold documents from eDOCS?
In part. Listed in a table; the files themselves stay in folders beside the database. What SQLite can hold is written out once its mapping is agreed, and the rest is kept beside the data as files that open without eDOCS.
Does everything in eDOCS have a place in SQLite?
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 SQLite is kept as a readable archive, and you see which before the move.
What has to be decided before eDOCS is written out to SQLite?
Documents, emails and custom fields are exported with mapping, so each mapping is agreed with you first. Notes, tasks and templates 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 eDOCS and into SQLite
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.
eDOCS and SQLite are the names and marks of their owners, used here only to identify the two systems.
Moving from eDOCS to SQLite?
Tell us what you are moving. You get a plan and a fixed price after the analysis.
We reply within one business day.