Data migration route
Worldox data to SQLite
Worldox 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.
WorldoxServer- Matters: Exported in full
- Notes: Exported in full
- Documents: Exported with mapping
- Emails: Exported with mapping
- Custom fields: Exported with mapping
- Tasks: Confirmed in the analysis
SQLiteFiles- Templates: Kept as a readable archive
- 2 carried
- 3 mapped
- 1 to confirm
- 1 archived
What moves
What moves from Worldox to SQLite
Each row is a kind of record Worldox holds, whether SQLite has a place for it, and what is planned. On this route two kinds of record carry across, three kinds need mapping, one kind has no place in SQLite and is archived and one kind is confirmed in the analysis.
| Record | What is planned | ||
|---|---|---|---|
| MattersMatters or cases, with their numbers, types, parties and status | Held in partClient and matter exist as coded profile fields with descriptions, not as matter records. | Has a placeA matters table keyed by matter number. | Exported in full |
| DocumentsFiles stored in or linked from the system | HeldOrdinary files on the network, named by an eight-digit Doc ID, each with a profile. | 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 | HeldOutlook messages and attachments are profiled and saved to cabinets like other documents. | Has a place in partAs message files in folders, indexed in a table. | Exported with mapping |
| NotesFile notes, matter notes and contact notes | Held in partEach profile has a comments field of up to 5,000 characters. | Has a placeA notes table linked to matters. | Exported in full |
| 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 | HeldEach cabinet has its own profile form and field tables, set up by the firm. | Has a placeColumns added to the table they belonged to. | Exported with mapping |
| TemplatesPrecedents, document templates and automation | Held in partPrecedents are kept as documents, often in a cabinet of their own. | No placePrecedent files are kept in folders, not in the database. | Kept as a readable archive |
What the plans mean
- Exported in full
- SQLite has a place for this kind of record. It is loaded there and checked against Worldox.
- 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.
- Kept as a readable archive
- SQLite has no place for it. It is exported in a format that opens without Worldox and handed to the firm as a read-only archive.
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 Worldox 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 Worldox 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 Worldox stays untouched until the copy in SQLite has been checked.
Where the data is now
Leaving Worldox
Worldox documents are real files in real folders on the firm’s network, which makes them easy to reach and easy to misread. The folder path encodes the client and matter codes, the file name is a number, and the description users see is kept by Worldox, not in the file name. A move reads all three together, so each file arrives with its title, matter and author.
File names are numbers
Worldox numbers documents consecutively and uses the eight-digit Doc ID plus the extension as the file name. Copy a matter folder to another drive and you get files called 00123456.docx with no titles. The description, up to 128 characters, comes from the profile, and the migration names each file from it.
The path is the profile
Each cabinet has a base path, and the client, matter and document type chosen on the profile form decide the folder beneath it. Reading a path back gives the codes. The field tables give what the codes mean. Both are needed, because a folder called 004417 says nothing until the table says which client that is.
Cabinets differ from one another
A site can have up to 150 cabinets and each has its own set of fields. One may file by client and matter, another by department and year, and a legacy cabinet may hold documents kept from an earlier system for reference only. Every cabinet gets its own mapping.
Versions, archive and legal hold
Earlier versions of a document are kept and listed with it, and cabinets can have Archive and Legal Hold areas for documents moved out of the active tree. Whether each of these comes across is a scope question. The file counts in the analysis are split into current, versions, archived and held.
Security lives in two places
Access is set by Worldox administrators in WDADMIN, by cabinet and by folder, which is how ethical walls are built. Individual files can also be given their own security when profiled. The Windows permissions on the share do not tell the whole story, so restrictions are read from Worldox itself.
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 Worldox holds, table by table, and agree with you what the copy in SQLite must be able to answer later. Everything Worldox 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 Worldox: record counts, totals where Worldox 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 Worldox, the export is run a final time and checked again. There is nothing to go live. Worldox 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 Worldox 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 Worldox 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
Worldox to SQLite: what firms ask
Can we just copy the Worldox folders to the new system?
The files will copy, but they will be named with eight-digit numbers and sit in folders named with codes. The descriptions, authors, document types and comments are in the profiles. A proper move pairs each file with its profile first, then names it and files it by matter in the destination.
Do our Doc IDs carry over?
The new system will give each document its own identifier. The Worldox Doc ID can be kept in a field or added to the document name, which is worth doing where the firm prints Doc IDs in document footers. Whether it is searchable afterwards depends on the destination and is confirmed in the analysis.
What about emails saved into Worldox?
They were saved with a profile in the same way as documents, so they move with the matter. In the destination they should arrive as emails, with sender and date readable, not as attachments nobody can sort. The trial load is where that is checked, on a sample of matters with heavy correspondence.
Does the copy in SQLite hold documents from Worldox?
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 Worldox.
What happens to records SQLite has no place for?
On this route that is templates. They are exported from Worldox in formats that open without it, spreadsheets and PDFs, and handed to the firm as a read-only archive. You see the list before the move.
What has to be decided before Worldox is written out to SQLite?
Documents, emails and custom fields 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 Worldox 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.
Worldox and SQLite are the names and marks of their owners, used here only to identify the two systems.
Moving from Worldox 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.