Data migration route
LSSe64 data to SQLite
LSSe64 is a server-based practice management system, and SQLite is a store of data kept as files the firm holds. This is not a move to a new working system: the route writes out what LSSe64 holds and keeps it readable and open to queries.
LSSe64Server- Matters: Exported in full
- Contacts: Exported in full
- Notes: Exported in full
- Calendar: Exported in full
- Tasks: Exported in full
- Time and expenses: Exported in full
- Billing: Exported in full
- Trust money: Exported in full
- Firm accounts: Exported in full
- Intake: Exported in full
- Documents: Exported with mapping
- Emails: Exported with mapping
- Custom fields: Confirmed in the analysis
- Templates: Confirmed in the analysis
SQLiteFiles- 10 carried
- 2 mapped
- 2 to confirm
What moves
What moves from LSSe64 to SQLite
Each row is a kind of record LSSe64 holds, whether SQLite has a place for it, and what is planned. On this route ten kinds of record carry across, two kinds need mapping and two kinds are confirmed in the analysis.
| Record | What is planned | ||
|---|---|---|---|
| MattersMatters or cases, with their numbers, types, parties and status | HeldClient and matter numbers, with related parties and conflict records. | Has a placeA matters table keyed by matter number. | Exported in full |
| ContactsClients, other parties and referrers | HeldContact Management and mailing lists. | Has a placeContacts and their roles on matters as linked tables. | Exported in full |
| DocumentsFiles stored in or linked from the system | HeldFiles kept in native format; profiles held in a separate indexed 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 | HeldSaved from Outlook with a client and matter profile; attachments are text-indexed. | Has a place in partAs message files in folders, indexed in a table. | Exported with mapping |
| NotesFile notes, matter notes and contact notes | HeldCase Notes component. | Has a placeA notes table linked to matters. | Exported in full |
| CalendarAppointments, court dates and deadlines | HeldRules-based calendar. | Has a placeA table of dated entries, with no calendar view. | Exported in full |
| TasksTo-dos and workflow steps assigned to people | Held in partWorkflow Management routes intake forms and change requests. | Has a placeA table of tasks and their status at the final date. | Exported in full |
| Time and expensesTime and expense entries, billed and unbilled | HeldTime, cost and expense entry, with a timer and batch entry. | Has a placeA table of time and expense entries. | Exported in full |
| BillingInvoices, payments and debtor balances | HeldPaper and electronic billing from one billing dashboard. | Has a placeInvoice and receipt tables; invoice PDFs kept as files. | Exported in full |
| Trust moneyTrust or client account ledgers and balances | HeldMultiple trust accounts, with detail kept at client and matter level. | Has a placeTrust transactions as rows, for look-up and not for accounting. | Exported in full |
| Firm accountsGeneral ledger, office account and payables | HeldGeneral Ledger, Accounts Payable and bank reconciliation. | Has a placeLedger journals as rows, where the source held them. | Exported in full |
| Custom fieldsFields and record types the firm added itself | To be confirmed | Has a placeColumns added to the table they belonged to. | Confirmed in the analysis |
| TemplatesPrecedents, document templates and automation | To be confirmed | No placePrecedent files are kept in folders, not in the database. | Confirmed in the analysis |
| IntakeLeads, enquiries, intake forms and pipelines | HeldElectronic client and matter intake forms, and potential client records. | Has a placeAn enquiries table, where the source tracked them. | Exported in full |
What the plans mean
- Exported in full
- SQLite has a place for this kind of record. It is loaded there and checked against LSSe64.
- 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
Not a new system. A complete copy the firm can query.
Writing LSSe64 out to SQLite is not a migration into a new working system. Nobody will open a matter there on Monday morning. The aim is a complete, faithful copy that can be queried and reported on after the old system is gone. So the rules change. Nothing is cleaned or merged unless the firm asks, because an archive should show the records as they were. Every table and field is carried, including those a new system would have had no place for.
What makes an archive usable is the description that goes with it. The export is delivered with a plain account of each table: what it holds, how it joins to the others, what the codes mean. Record counts and financial totals are agreed to the reports in LSSe64 as at the export date, so the archive can stand as the record. Documents are exported beside the data with a table linking each file to its matter. Access is restricted, since the archive holds everything the live system did.
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 LSSe64 stays untouched until the copy in SQLite has been checked.
Where the data is now
Leaving LSSe64
LSSe64 keeps the firm’s whole operation in one SQL Server database: time, billing, trust, the general ledger, payables, documents and calendar. So a move off it is a finance migration as much as a matter migration. The first things to establish are which components the firm licensed, whether it is on LSSe64 or the older legacy system, and whether LSS hosts it.
Legacy LSS or LSSe64
LSS has had four generations of software. The third, a 32-bit Windows system, is now called legacy LSS and the vendor describes it as obsolete. LSSe64 was a complete redesign. A firm that says it is on LSS could be on either, and the two are structured differently, so the version is confirmed before any estimate is made.
Licensed by component
The system can be bought whole or as single components, and Document Management can run as a stand-alone application. One firm may have accounting only, another everything. Where a component was never licensed, that kind of record is somewhere else: in folders, in Outlook or in another product. The analysis covers those places too.
Payables feed client bills
A client expense entered in Accounts Payable appears on the client’s account and bill, and a scanned invoice attached to it can be printed with the billing statement. Trust disbursements are also entered through payables. Unbilled expenses therefore have a supplier invoice and sometimes an image behind them, and both are carried with the entry.
Documents by profile
Each saved file has a profile: client and matter number, document type, author, typist and optional fields. The file is stored in its native format and the profile in an indexed database. Loading into a folder-based system means turning profiles into folders, and the firm agrees that layout on sample matters before the full run.
Minimum trust balances
A matter can be given a minimum required trust balance, and the billing statement then asks the client for the amount needed to restore it. Trust deposits can also carry a clear date before which funds are not disbursed. Both settings are per matter and are recorded so they can be set again after the move.
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 LSSe64 holds, table by table, and agree with you what the copy in SQLite must be able to answer later. Everything LSSe64 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 LSSe64: record counts, totals where LSSe64 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 LSSe64, the export is run a final time and checked again. There is nothing to go live. LSSe64 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 LSSe64 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 LSSe64 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
LSSe64 to SQLite: what firms ask
LSS hosts our system. Can the data still be collected?
It is the same data in a different place. Hosted firms use the same software on remote desktops run by LSS, so the database is on LSS’s servers instead of the firm’s. Access is arranged with LSS on the firm’s authority. The collection is done once for the trial load and again after the freeze at cutover.
Can our general ledger history move, or only balances?
That depends on what the destination accepts. Some systems accept years of ledger transactions, others take opening balances and expect history to remain in the old books. Trust is settled separately: each matter’s balance is loaded and checked, and whether the transactions behind it follow depends on the destination. The analysis states which approach applies, and the old system is kept read only for the rest.
We only use LSS for accounting. What about our matters?
Then the client and matter list, time, billing and ledgers come from LSS, and everything else comes from wherever it is kept now. Documents on a server drive and calendars in Outlook are brought in alongside, matched to the same matter numbers. The matter number ties the sources together, so gaps in it are fixed first.
Does the copy in SQLite hold trust ledgers from LSSe64?
Yes. Trust transactions as rows, for look-up and not for accounting. Trust ledgers are written out with the rest, and counts and totals are agreed to the reports in LSSe64 as at the export date.
Does everything in LSSe64 have a place in SQLite?
Most of it does on paper. Custom fields 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 LSSe64 is written out to SQLite?
Documents and emails are exported with mapping, so each mapping is agreed with you first. Custom fields 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 LSSe64 and into SQLite
Other destinations from LSSe64
Other systems that move 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.
LSSe64 and SQLite are the names and marks of their owners, used here only to identify the two systems.
Moving from LSSe64 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.