Skip to content
NEWLAW.COM
+61 1300 495 281
Let’s talk

Data migration route

The Tussman Program data to Microsoft SQL Server

The Tussman Program is a desktop accounting and billing system, and Microsoft SQL Server is a database on a server the firm runs. 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.

FromThe Tussman ProgramDesktop
  1. Matters: Exported in full
  2. Contacts: Exported in full
  3. Notes: Exported in full
  4. Calendar: Exported in full
  5. Tasks: Exported in full
  6. Time and expenses: Exported in full
  7. Billing: Exported in full
  8. Trust money: Exported in full
  9. Firm accounts: Exported in full
  10. Documents: Exported with mapping
  11. Templates: Exported with mapping
  12. Custom fields: Confirmed in the analysis
ToMicrosoft SQL ServerServer
  • 9 carried
  • 2 mapped
  • 1 to confirm
What the two products hold. The analysis confirms it field by field.

What moves

What moves from The Tussman Program to Microsoft SQL Server

Each row is a kind of record The Tussman Program holds, whether Microsoft SQL Server has a place for it, and what is planned. On this route nine kinds of record carry across, two kinds need mapping and one kind is confirmed in the analysis.

Records in The Tussman Program and their place in Microsoft SQL Server
RecordIn The Tussman ProgramIn Microsoft SQL ServerWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldClient and matter IDs, alpha or numeric, up to 16 characters each.Has a placeA table of matters linked to clients, parties and fee earners.Exported in full
ContactsClients, other parties and referrersHeldClients, plus contacts and persons related to each matter.Has a placePeople and companies, with their roles on each matter.Exported in full
DocumentsFiles stored in or linked from the systemHeld in partA list of documents for each client, each opened with a click.Has a place in partAs files in folders with an index table; storing files in the database is possible.Exported with mapping
NotesFile notes, matter notes and contact notesHeldFree-form notes on each client and matter.Has a placeRows of text linked to matters and contacts.Exported in full
CalendarAppointments, court dates and deadlinesHeld in partWith the Docket/Calendar module.Has a placeRows of appointments and key dates; nothing displays them as a calendar.Exported in full
TasksTo-dos and workflow steps assigned to peopleHeld in partTasks and reminders in the Docket/Calendar module.Has a placeRows with assignee, due date and status.Exported in full
Time and expensesTime and expense entries, billed and unbilledHeldTime and disbursements, billable and non-billable.Has a placeTime and expense rows with rates and billed status.Exported in full
BillingInvoices, payments and debtor balancesHeldBills, payments, credits and a master ledger for each client and matter.Has a placeInvoices, lines and receipts as rows; invoice PDFs kept as files.Exported in full
Trust moneyTrust or client account ledgers and balancesHeldRetainer and trust accounts for each matter.Has a placeTransactions and balances for look-up; it is not a trust accounting system.Exported in full
Firm accountsGeneral ledger, office account and payablesHeld in partWith the General Ledger, Accounts Payable and Checkwriting module.Has a placeGeneral ledger journals and balances, where the source held them.Exported in full
Custom fieldsFields and record types the firm added itselfTo be confirmedHas a placeAs added columns, or a table of field names and values.Confirmed in the analysis
TemplatesPrecedents, document templates and automationHeld in partUp to ten bill formats.Has a place in partPrecedent files can be stored; automation does not run here.Exported with mapping

What the plans mean

Exported in full
Microsoft SQL Server has a place for this kind of record. It is loaded there and checked against The Tussman Program.
Exported with mapping
Microsoft SQL Server 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 The Tussman Program out to Microsoft SQL Server 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 Microsoft SQL Server has been checked.

Where the data is now

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.

  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. 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.

More about moving off The Tussman Program

Where it is going

There are two ways to put a retired system into SQL Server, and they suit different firms. The old system’s own database can be restored as it is. Or the data can be loaded into a new set of tables designed to be read by people. The first is quicker and harder to use. Which suits is worked out in the analysis, and the choice is the firm’s.

  1. Restored copy or rebuilt schema

    Where the old practice system already kept its data in SQL Server, a backup can be restored onto a new server. The tables keep the vendor’s names and codes, which can be cryptic, and reading them takes someone who knows that product’s database. A rebuilt schema uses plain names such as Matter and TrustTransaction.

  2. No screens come with it

    A database has no matter screen. Someone has to ask it questions in SQL or through a reporting tool. Saved views can be set up for the things the firm will really look up: a matter with its parties, its ledger, its time entries and its list of documents. Which are worth having is agreed in the analysis.

  3. Documents sit beside the database

    Files are normally kept in folders on the same server, with a table recording each document’s matter, title, dates and path. Storing the files inside the database is possible but makes it far larger. On the Express edition, the cap on database size rules that out for most firms’ document stores.

  4. The edition follows the size

    A firm’s tables may fit within the Express limit once documents are kept outside the database. A long trust and time history at a larger firm may not. The size of the source data is measured in the analysis, and the edition is chosen from that figure with the firm’s IT provider.

  5. Backups and a test restore

    An archive that is never backed up is one disk failure from gone. Backups belong to the firm’s IT provider: a full one once the load is finished, and a schedule if anything is still being added. It is worth restoring one to a second machine as a test, because a backup that has never been restored is only a hope.

More about moving into Microsoft SQL Server

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.

  1. Analysis

    We read what The Tussman Program holds, table by table, and agree with you what the copy in Microsoft SQL Server must be able to answer later. Everything The Tussman Program holds is in scope unless you take it out.

  2. 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.

  3. Trial export

    The data is written to Microsoft SQL Server 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.

  4. 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

Step 1 of 5: Start with the route

Moving fromThe Tussman Program
Moving toMicrosoft SQL Server

The route comes from this page. Four short steps follow. Nothing you send commits your firm to anything.

What happens after you send it

  1. A free first call

    We go through your answers with you and ask about anything they leave open.

  2. An analysis of what The Tussman Program holds

    What is in it, how its records link, and where each piece would sit in Microsoft SQL Server. Anything with no place there comes across as a note or stays behind, and you see which before the move.

  3. 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

Microsoft SQL Server 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.

Standing up SQL Server as an archive is IT work shared with the firm’s provider. A server or instance is chosen, logins are created for the few people who need to read the data, and nobody is given rights to change it. Views and a handful of reports are built for the common questions, and the IT provider owns the backup routine.

What is agreed and set up

  • Server, instance and edition agreed with the IT provider
  • Read-only logins and roles for named staff
  • Views for matter, ledger, time and document look-ups
  • Backup schedule and who tests a restore
  • Plain names and descriptions for tables and columns
  • Excel or Power BI connected for reporting

Questions

The Tussman Program to Microsoft SQL Server: 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 Microsoft SQL Server hold trust ledgers from The Tussman Program?

Yes. Transactions and balances for look-up; it is not a trust accounting system. 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.

Does everything in The Tussman Program have a place in Microsoft SQL Server?

Most of it does on paper. Custom fields 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 Microsoft SQL Server is kept as a readable archive, and you see which before the move.

What has to be decided before The Tussman Program is written out to Microsoft SQL Server?

Documents and templates 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.

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.

How we do itDiscovery to rollout, step by step

The Tussman Program and Microsoft SQL Server are the names and marks of their owners, used here only to identify the two systems.

Moving from The Tussman Program to Microsoft SQL Server?

Tell us what you are moving. You get a plan and a fixed price after the analysis.

We reply within one business day.