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

Data migration route

The Tussman Program to Clio Manage migration

The Tussman Program is a desktop accounting and billing system, and Clio Manage is a cloud practice management system. The financial records lead: balances and open items move, and the matters in Clio Manage are built around them.

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. Custom fields: Confirmed in the analysis
ToClio ManageCloud
  1. Firm accounts: Kept as a readable archive
Readable archiveNo place in Clio Manage
  • 6 carried
  • 4 mapped
  • 1 to confirm
  • 1 archived
What the two products hold. The analysis confirms it field by field.

What moves

What moves from The Tussman Program to Clio Manage

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

Records in The Tussman Program and their place in Clio Manage
RecordIn The Tussman ProgramIn Clio ManageWhat 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 placeImported from a matters template, after contacts.Carried across
ContactsClients, other parties and referrersHeldClients, plus contacts and persons related to each matter.Has a placePeople and companies, with related contacts linked to matters by a separate template.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 placeFiled under the matter; Clio scopes document migration separately from data.Carried across
NotesFile notes, matter notes and contact notesHeldFree-form notes on each client and matter.Has a placeMatter notes and contact notes each have a template.Carried across
CalendarAppointments, court dates and deadlinesHeld in partWith the Docket/Calendar module.Has a placeCalendar events have a migration template.Carried across
TasksTo-dos and workflow steps assigned to peopleHeld in partTasks and reminders in the Docket/Calendar module.Has a placeTasks have a migration template.Carried across
Time and expensesTime and expense entries, billed and unbilledHeldTime and disbursements, billable and non-billable.Has a place in partUnbilled time entries load; billed time entries do not, by Clio’s migration guide.Carried with mapping
BillingInvoices, payments and debtor balancesHeldBills, payments, credits and a master ledger for each client and matter.Has a place in partAn outstanding balance loads as one line per matter; past invoices do not.Carried with mapping
Trust moneyTrust or client account ledgers and balancesHeldRetainer and trust accounts for each matter.Has a place in partA trust balance loads as one line per matter or contact; past transactions do not.Carried with mapping
Firm accountsGeneral ledger, office account and payablesHeld in partWith the General Ledger, Accounts Payable and Checkwriting module.No placeNot in Clio Manage. Books sit in a linked accounting package, or in Clio Accounting where Clio offers it.Kept as a readable archive
Custom fieldsFields and record types the firm added itselfTo be confirmedHas a placeCreated first, then filled from the custom field templates.Confirmed in the analysis
TemplatesPrecedents, document templates and automationHeld in partUp to ten bill formats.Has a placeRebuilt as Clio document templates with its merge fields.Carried with mapping

What the plans mean

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

Time, bills and balances move. How much history is a decision.

Coming from an accounting or billing system, the records that count are balances: unbilled time, unpaid invoices, client funds, the ledger. A practice management system takes these as opening positions on a matter. So every client and job in The Tussman Program needs a matter to land on, and the first piece of work is building that matter list, often from client and project codes that were never meant to be matter numbers.

How much history to bring is the main choice. Paid invoices from years ago can be loaded as records, kept as PDF copies on the matter, or left in a read-only copy of The Tussman Program. Most firms bring open items and a period of history, and keep the rest as reports. Opening balances in Clio Manage are agreed to the trial balance and aged debtors from The Tussman Program as at the cutover date, and that load is rehearsed before it is done for real.

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. Clio Manage 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

Clio Manage is loaded through its migration templates, one spreadsheet per kind of record, imported in a fixed order with contacts first. Clio’s own migration guide is plain about the limit: balances come across, financial history does not. So a load into Clio is planned as records plus opening positions, with the old system kept for the history behind them.

  1. Matters link by client name

    The matters template ties each matter to its client by an exact match on first name, last name or company name. A client spelt two ways in the old system becomes two contacts, or a matter assigned to an unknown client. This is why contact clean-up is finished before the first trial load, not after it.

  2. Decide the numbering scheme first

    Clio numbers imported matters itself unless the account is set to manual numbering, in which case the old number is supplied in the template. That setting and the firm’s preferred scheme are decided before any matter is loaded. The Client Reference field is available for an old file number the firm still wants to see.

  3. Balances, one line each

    Under Clio’s standard migration, an outstanding balance arrives as one line per matter and a trust balance as one line per matter or contact. Past invoices, billed time, payments and trust transactions are listed as data that cannot be migrated. The trust total is reconciled against the old system’s closing report on the trial load.

  4. Custom fields must exist

    Matter and contact custom fields are created in Clio before their values are imported, each with a field type. Accounts set up for a particular practice area come with preconfigured fields and matter templates, which affects the mapping. We compare those with the old system’s fields and add only what is missing.

  5. Rates and permissions by hand

    Billable rates for users, clients and matters are not part of an import. Neither are user permissions or settings. They are entered in Clio during set-up from a schedule the firm confirms, and a sample of imported unbilled time is checked against that schedule before the trial load is signed off.

More about moving into Clio Manage

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 Clio Manage. 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 Clio Manage 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 Clio Manage 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 toClio Manage

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 Clio Manage. 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 Clio Manage

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

Much of a Clio Manage set-up is firm-wide settings. The numbering scheme, practice areas, matter stages, billing preferences and trust accounts apply to everyone, so they are agreed once and early. Trust and accounting features are not the same in every country Clio sells in, so the firm’s own region is checked first. Document templates and custom fields follow. Email and document integrations are then installed for each user and tested on a real matter.

Set-up decisions in Clio Manage

  • Matter numbering scheme, practice areas and matter stages
  • Custom fields for matters and contacts, by practice area
  • Document templates with merge fields, uploaded from Word or PDF
  • Billing settings, user and client rates, and trust accounts
  • Roles and permissions for each user
  • Outlook add-in, Clio Drive and the accounting connection

Questions

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

In part. A trust balance loads as one line per matter or contact; past transactions do not. The analysis sets out which trust records have a place in Clio Manage and which are kept as an archive, and the trust cutover is rehearsed on a full trial load before the real one.

What happens to records Clio Manage has no place for?

On this route that is 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 Clio Manage?

Time entries, billing records, trust ledgers and templates are carried with mapping, so each mapping is agreed with you first. 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 Clio Manage are the names and marks of their owners, used here only to identify the two systems.

Moving from The Tussman Program to Clio Manage?

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

We reply within one business day.