Data migration route
The Tussman Program data to SQLite
The Tussman Program is a desktop accounting and billing 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 The Tussman Program holds and keeps it readable and open to queries.
The Tussman ProgramDesktop- 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
- Documents: Exported with mapping
- Custom fields: Confirmed in the analysis
SQLiteFiles- Templates: Kept as a readable archive
- 9 carried
- 1 mapped
- 1 to confirm
- 1 archived
What moves
What moves from The Tussman Program to SQLite
Each row is a kind of record The Tussman Program holds, whether SQLite has a place for it, and what is planned. On this route nine kinds of record carry across, one kind needs 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 | HeldClient and matter IDs, alpha or numeric, up to 16 characters each. | Has a placeA matters table keyed by matter number. | Exported in full |
| ContactsClients, other parties and referrers | HeldClients, plus contacts and persons related to each matter. | Has a placeContacts and their roles on matters as linked tables. | Exported in full |
| DocumentsFiles stored in or linked from the system | Held in partA list of documents for each client, each opened with a click. | Has a place in partListed in a table; the files themselves stay in folders beside the database. | Exported with mapping |
| NotesFile notes, matter notes and contact notes | HeldFree-form notes on each client and matter. | Has a placeA notes table linked to matters. | Exported in full |
| CalendarAppointments, court dates and deadlines | Held in partWith the Docket/Calendar module. | Has a placeA table of dated entries, with no calendar view. | Exported in full |
| TasksTo-dos and workflow steps assigned to people | Held in partTasks and reminders in the Docket/Calendar module. | 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 and disbursements, billable and non-billable. | Has a placeA table of time and expense entries. | Exported in full |
| BillingInvoices, payments and debtor balances | HeldBills, payments, credits and a master ledger for each client and matter. | Has a placeInvoice and receipt tables; invoice PDFs kept as files. | Exported in full |
| Trust moneyTrust or client account ledgers and balances | HeldRetainer and trust accounts for each matter. | Has a placeTrust transactions as rows, for look-up and not for accounting. | Exported in full |
| Firm accountsGeneral ledger, office account and payables | Held in partWith the General Ledger, Accounts Payable and Checkwriting module. | 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 | Held in partUp to ten bill formats. | 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 The Tussman Program.
- 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 The Tussman Program 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
Not a new system. A complete copy the firm can query.
Writing The Tussman Program 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 The Tussman Program 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 The Tussman Program stays untouched until the copy in SQLite has been checked.
Where the data is now
Leaving The Tussman Program
A Tussman firm’s records are compact: one folder holds the clients, matters, charges, payments and bills, sometimes going back decades. The move takes unbilled charges, account balances, retainer and trust balances and the client and matter list, and checks each against the program’s own reports. Whether billed charges were ever archived or purged is established first, since it changes what can be reconciled.
One folder holds it all
Program and data live in the same folder, by default c:\tp9, and network users run it from a shortcut to that folder. The vendor’s own way of moving it between computers is to copy the folder. A copy taken with everyone logged out is therefore a complete source, and the trial load is made from it.
IDs chosen by the firm
Client IDs can be numeric, alphabetic or mixed, and the manual suggests using the client’s name as the ID. So an ID may be SMITH, not a number. Those work as references but not as matter numbers in most systems. The firm chooses a numbering scheme for the destination, and the old IDs are kept beside it.
Billed charges stay unless purged
Once billed, charges move to a Billed Charges file and stay there, so old bills can be reprinted exactly. They can be archived to a separate BTRAN file or purged, though the manual advises against both. Whether that was ever done decides how far back the detail goes, and it is checked before history is promised.
Finalised and unfinalised bills
A bill is marked as billed by finalising it, and any finalised bill can be unfinalised, changed and regenerated. Before the last extraction every bill the firm means to send is finalised. A draft left unfinalised would arrive as unbilled work, and the client could be billed for it again.
Retainer and trust per matter
Each matter can carry a retainer account and a trust account, with retainers applied to bills automatically and a replenishment request when the balance runs low. The two are different kinds of money and are mapped separately. With the general ledger module, the trust cheque register is another figure the load must agree to.
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 The Tussman Program holds, table by table, and agree with you what the copy in SQLite must be able to answer later. Everything The Tussman Program 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 The Tussman Program: record counts, totals where The Tussman Program 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 The Tussman Program, the export is run a final time and checked again. There is nothing to go live. The Tussman Program 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 The Tussman Program 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 The Tussman Program 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
The Tussman Program to SQLite: what firms ask
Closed and deleted clients: what comes across?
Closed clients stay in the data and can be loaded as closed matters. A client marked deleted is still there until someone runs the purge, after which it is gone. The analysis counts open, inactive, closed and deleted files so the firm can see what exists before choosing what to bring.
We use the cloud-hosted version. Can the data still be reached?
The hosted version is the same program running on a remote server, with the firm’s copy moved there from its own computer. A backup can be made from inside the program in the usual way. How that backup gets from the hosted server to the firm is arranged at the start.
Can we move the general ledger too?
If the firm bought the general ledger module, it holds cheque registers for office and trust accounts, vendors and the financial statements. Balances move as an opening journal, into the destination or into a separate accounting package. Vendor 1099 totals for the current year are carried as figures.
Does the copy in SQLite hold trust ledgers from The Tussman Program?
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 The Tussman Program as at the export date.
What happens to records SQLite has no place for?
On this route that is templates. They are exported from The Tussman Program 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 The Tussman Program is written out to SQLite?
Documents are exported with mapping, so each mapping is agreed with you first. Custom fields 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 The Tussman Program and into SQLite
Other destinations from The Tussman Program
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.
The Tussman Program and SQLite are the names and marks of their owners, used here only to identify the two systems.
Moving from The Tussman Program 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.