Data migration route
The Tussman Program to Server drives migration
The Tussman Program is a desktop accounting and billing system, and Server drives are plain files on equipment the firm controls. What moves is the files, plus a readable export of everything else the old system holds.
The Tussman ProgramDesktop- Documents: Carried across
- Notes: Carried with mapping
- Templates: Carried with mapping
- Custom fields: Confirmed in the analysis
Server drivesFiles- Matters: Kept as a readable archive
- Contacts: Kept as a readable archive
- Calendar: Kept as a readable archive
- Tasks: Kept as a readable archive
- Time and expenses: Kept as a readable archive
- Billing: Kept as a readable archive
- Trust money: Kept as a readable archive
- Firm accounts: Kept as a readable archive
- 1 carried
- 2 mapped
- 1 to confirm
- 8 archived
What moves
What moves from The Tussman Program to Server drives
Each row is a kind of record The Tussman Program holds, whether Server drives have a place for it, and what is planned. On this route one kind of record carries across, two kinds need mapping, eight kinds have no place in Server drives and are 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. | No placeA matter becomes a folder; its details survive only in an index file. | Kept as a readable archive |
| ContactsClients, other parties and referrers | HeldClients, plus contacts and persons related to each matter. | No placeCan be kept only as an exported spreadsheet. | Kept as a readable archive |
| DocumentsFiles stored in or linked from the system | Held in partA list of documents for each client, each opened with a click. | Has a placeFiles in folders, named and dated during the load. | Carried across |
| NotesFile notes, matter notes and contact notes | HeldFree-form notes on each client and matter. | Has a place in partAs a text or PDF file per matter, not as separate records. | Carried with mapping |
| CalendarAppointments, court dates and deadlines | Held in partWith the Docket/Calendar module. | No place | Kept as a readable archive |
| TasksTo-dos and workflow steps assigned to people | Held in partTasks and reminders in the Docket/Calendar module. | No place | Kept as a readable archive |
| Time and expensesTime and expense entries, billed and unbilled | HeldTime and disbursements, billable and non-billable. | No placeOnly as exported reports or spreadsheets. | Kept as a readable archive |
| BillingInvoices, payments and debtor balances | HeldBills, payments, credits and a master ledger for each client and matter. | Has a place in partInvoices as PDF files; no ledger. | Kept as a readable archive |
| Trust moneyTrust or client account ledgers and balances | HeldRetainer and trust accounts for each matter. | No placeOnly as exported ledger reports kept as files. | Kept as a readable archive |
| Firm accountsGeneral ledger, office account and payables | Held in partWith the General Ledger, Accounts Payable and Checkwriting module. | No place | Kept as a readable archive |
| Custom fieldsFields and record types the firm added itself | To be confirmed | No place | Confirmed in the analysis |
| TemplatesPrecedents, document templates and automation | Held in partUp to ten bill formats. | Has a place in partPrecedents as Word files; merge fields tied to the old system stop working. | Carried with mapping |
What the plans mean
- Carried across
- Server drives has a place for this kind of record. It is loaded there and checked against The Tussman Program.
- Carried with mapping
- Server drives 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
- Server drives 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
An export the firm can open without the system.
Server drives hold files, and most of what The Tussman Program holds is records. This route is therefore an export job. Each kind of record is written out in a format that opens without the system it came from: lists as spreadsheets, statements and invoices as PDFs, attachments as the files they were. The export is laid out in folders that make sense to someone who never used The Tussman Program, by client or by year, with a short index file saying what is where.
Firms do this when a subscription is ending, when a system is being retired, or to meet a retention rule. The test of the result is whether a question can still be answered from it years later: what was this client invoiced, who signed this agreement and when. So the trial export is checked by asking those questions of it. Totals are agreed to the system’s own reports, and access to the folder in Server drives is limited before the export is copied in.
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 Server drives 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 Server drives
Some firms leave a practice or document system and keep their documents on a server drive, either as the working store or as the archive of a system being switched off. The files will arrive without the database that described them. Everything the firm wants to keep knowing about a document has to be put into its path, its name or an index file.
Agree the tree and the names
A fixed pattern is chosen, for example client name and number, then matter number and short description, then a standard set of subfolders. Document titles from the old system become file names. Where two documents share a title, a date or sequence number is added so nothing is overwritten.
Budget the path length
Share name, client, matter, subfolder and file name all count towards the 260 character limit that many Windows programs still apply. The pattern is tested against the firm’s longest client names and document titles before the load. Descriptions are trimmed by rule, never by cutting off the file extension.
Dates have to be set deliberately
A file written to the server today is dated today unless its modified date is set from the old system’s record. Document dates are how lawyers find things in a folder. Which date each file is to carry is agreed in the analysis, and the trial load checks a sample.
Emails become message files
Emails filed to matters in the old system are written out as .msg or .eml files in a correspondence folder, named by date, sender and subject so they sort in order. Attachments stay inside the message. Subjects with characters Windows forbids are cleaned, and long ones cut.
Keep an index beside the files
A spreadsheet or small database listing every document with its matter, author, original date, document type and new path is the only place the old system’s profile data survives. It lets someone find a document by something other than its name. What the index records, and who keeps it, is decided in the analysis.
How NewLaw runs it
Four steps, in this order.
Nothing financial lands in Server drives on this route, which makes it repeatable: a load can be run again until it is right.
Analysis
We read what The Tussman Program holds and how it is organised, then agree with you where each kind of record will sit in Server drives. 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 Server drives and checked against The Tussman Program: 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 The Tussman Program, a final pass over a weekend picks up what changed since the trial. The Tussman Program 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 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 Server drives. 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
Server drives are storage, not an application, so there is no product to configure. What is agreed and set up is the folder structure, who can open what, and how the result is handed to the firm.
A server drive does only what the firm and its IT provider make it do. Setting one up as a document store means building the share, deciding who can open which folders, and arranging the protections a document system would have supplied: backups, earlier versions and a way to recover a deleted folder. The filing rule is written down and taught.
What is agreed and set up
- Share and top-level folders for clients, precedents and administration
- Security groups and folder permissions, with restricted matters separate
- Drive letter mapped for every user at sign-in
- Backup schedule and shadow copies for earlier versions
- Written naming rule for client, matter and document names
- Read-only area for closed matters and archived system exports
Questions
The Tussman Program to Server drives: 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.
Do trust balances in The Tussman Program have a place in Server drives?
No. Server drives do not keep trust ledgers. Only as exported ledger reports kept as files. Trust records from The Tussman Program are exported as ledgers and statements that open without it, and the firm settles where its trust accounting runs from the cutover date before the move is planned.
What happens to records Server drives have no place for?
On this route that is matters, contacts, calendar entries, tasks, time entries, billing records, trust ledgers and the firm’s accounts. 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 data is loaded into Server drives?
Notes and templates are carried with mapping, so each mapping is agreed with you first. Custom fields 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 The Tussman Program and into Server drives
Other destinations from The Tussman Program
Other systems that move into Server drives
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 Server drives are the names and marks of their owners, used here only to identify the two systems.
Moving from The Tussman Program to Server drives?
Tell us what you are moving. You get a plan and a fixed price after the analysis.
We reply within one business day.