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

Data migration route

The Tussman Program to Filevine migration

The Tussman Program is a desktop accounting and billing system, and Filevine is a cloud case management system. Only part of what The Tussman Program holds has a place in a case file: clients and jobs move, and the table shows how much of the billing side does.

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

What moves

What moves from The Tussman Program to Filevine

Each row is a kind of record The Tussman Program holds, whether Filevine has a place for it, and what is planned. On this route six kinds of record carry across, four kinds need mapping and two kinds are confirmed in the analysis.

Records in The Tussman Program and their place in Filevine
RecordIn The Tussman ProgramIn FilevineWhat 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 placeLoaded as projects of a defined project type.Carried across
ContactsClients, other parties and referrersHeldClients, plus contacts and persons related to each matter.Has a placeContact cards, linked to projects.Carried across
DocumentsFiles stored in or linked from the systemHeld in partA list of documents for each client, each opened with a click.Has a placeDocs section with folders. Templated project folders can be set per type.Carried across
NotesFile notes, matter notes and contact notesHeldFree-form notes on each client and matter.Has a placeHeld as notes in the activity feed.Carried across
CalendarAppointments, court dates and deadlinesHeld in partWith the Docket/Calendar module.Has a placeDeadlines and calendar events.Carried across
TasksTo-dos and workflow steps assigned to peopleHeld in partTasks and reminders in the Docket/Calendar module.Has a placeCarried across
Time and expensesTime and expense entries, billed and unbilledHeldTime and disbursements, billable and non-billable.Has a place in partNeeds the Billing product enabled.Carried with mapping
BillingInvoices, payments and debtor balancesHeldBills, payments, credits and a master ledger for each client and matter.Has a place in partNeeds the Billing product enabled.Carried with mapping
Trust moneyTrust or client account ledgers and balancesHeldRetainer and trust accounts for each matter.Has a place in partTrust accounts sit in Payments by Filevine. Loading history is confirmed in the analysis.Carried with mapping
Firm accountsGeneral ledger, office account and payablesHeld in partWith the General Ledger, Accounts Payable and Checkwriting module.To be confirmedConfirmed in the analysis
Custom fieldsFields and record types the firm added itselfTo be confirmedHas a placeCustom sections and fields per project type.Confirmed in the analysis
TemplatesPrecedents, document templates and automationHeld in partUp to ten bill formats.Has a place in partTemplates are rebuilt as Filevine document templates. They are not converted.Carried with mapping

What the plans mean

Carried across
Filevine has a place for this kind of record. It is loaded there and checked against The Tussman Program.
Carried with mapping
Filevine 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

Clients and jobs move. The books stay books.

An accounting or billing system and a case management system overlap less than firms expect. The Tussman Program knows clients, jobs, time and invoices. Filevine knows cases, parties, documents and deadlines. The client list moves well, and jobs can seed the case list. Time and invoice history has a place only where the case system has a billing side, and the table above shows whether this one does. A general ledger does not belong in a case system.

So the plan has two halves. Records with a place in Filevine are loaded and checked there. The rest is exported from The Tussman Program as reports and ledgers that open without it, and the firm decides where its accounts run from then on. If The Tussman Program is staying as the accounting system, nothing financial needs to move at all, and the job is to line up client and case numbers so the two can be reconciled.

The Tussman Program runs on the firm’s own equipment, so the data is collected there: a copy of the database and the folders its documents sit in, taken with the firm’s IT provider or over a remote session. Filevine is hosted by its maker, so loading depends on the import tools and access it provides. The old machine is kept, read only, as the fall-back record.

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

Loading a firm into Filevine depends on the project types being built first. Until the sections and fields exist there is nowhere for the data to go, so configuration and migration are planned together. The old system’s parties, insurers, providers and key dates are mapped to sections, and its notes and emails are loaded into each project’s activity feed.

  1. Project types before data

    Each area of practice needs a project type with its sections, fields and phases defined in the Customs Editor. Changes made there apply to every project of that type. The types are drafted from the old system’s data, tested with a few real cases, and only then is the bulk load run.

  2. One contact card per person

    Contacts are held as contact cards. A doctor or adjuster who appears on many projects is best loaded as one card, not one for each project. Duplicates in the old system are merged before loading where they can be identified. Loading them as they are produces several cards for the same person, and staff then pick the wrong one when adding a party.

  3. Lists become collection items

    Anything the old system held as a list against a matter, such as providers, liens, insurance policies or expenses, is loaded as items in a collection section. Each column needs a matching field. Totals per project are compared with the old system afterwards, since those figures feed the settlement and disbursal sheets.

  4. History goes into the feed

    File notes, emails and completed tasks from the old system are loaded into the activity feed with their original dates and authors. Authors must exist as users or be recorded in the text. The feed is long on an old case, so staff are shown how to filter it before go-live.

  5. Billing is a separate switch

    The Billing section only appears once Billing is enabled for the firm. Time entries, invoices and trust balances from the old system need that in place before they can be loaded. A firm that leaves it off can still record case costs in a collection section built for the purpose.

More about moving into Filevine

How NewLaw runs it

Four steps, in this order.

Trust money moves on this route, so the trust cutover gets a rehearsal of its own.

  1. Analysis

    We read what The Tussman Program holds and how its records link, then agree with you, field by field, where each piece will sit in Filevine. Anything with no place there comes across as a note or stays behind, and you see which before the move.

  2. Clean-up

    Duplicate contacts and matters are merged where they can be identified, and inconsistent entries are put into one format, in The Tussman Program, before extraction. It is not always possible to find every one, so some may carry across.

  3. Trial load

    The data is loaded into Filevine as a trial and checked against The Tussman Program: record counts, trust and debtor totals, the links between records, document dates. Exceptions are listed for you to decide.

  4. Cutover

    Changes in The Tussman Program are frozen for an agreed window, the data is collected a final time and Filevine goes live over a weekend. The trust and financial cutover is rehearsed on a full trial load first, because it cannot be re-run the way a document load can. 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

Step 1 of 5: Start with the route

Moving fromThe Tussman Program
Moving toFilevine

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

Setting up Filevine

Loaded data is not yet a working system. This is what NewLaw sets up in Filevine, beyond the migration, so that people can work in it from the first day.

Filevine arrives as a platform to be configured, and most of the implementation is design. Someone has to decide what a project looks like for each kind of work the firm does, what moves it from one phase to the next, and who can see what. Those decisions are made with the people who run the files, then built and tested.

Set-up decisions in Filevine

  • Design project types, sections and fields for each practice area
  • Define phases and the tasks each phase should trigger
  • Build document templates that fill from project fields
  • Set teams, permissions and protected sections for restricted matters
  • Decide whether Billing and Payments are switched on
  • Connect Lead Docket so signed leads become projects

Questions

The Tussman Program to Filevine: 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 Filevine?

In part. Trust accounts sit in Payments by Filevine. Loading history is confirmed in the analysis. The analysis sets out which trust records have a place in Filevine and which are kept as an archive, and the trust cutover is rehearsed on a full trial load before the real one.

Does everything in The Tussman Program have a place in Filevine?

Most of it does on paper. The firm’s accounts and 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 Filevine is kept as a readable archive, and you see which before the move.

What has to be decided before The Tussman Program data is loaded into Filevine?

Time entries, billing records, trust ledgers and templates are carried with mapping, so each mapping is agreed with you first. The firm’s accounts and custom fields are confirmed in the analysis. The firm also sets the cutover date and how much financial history comes across as live records.

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 Filevine are the names and marks of their owners, used here only to identify the two systems.

Moving from The Tussman Program to Filevine?

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

We reply within one business day.