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

Data migration route

TXdocs to Clio Manage migration

TXdocs is a cloud specialist tool, and Clio Manage is a cloud practice management system. Case records move into matters, and time, billing and trust are set up in Clio Manage, often from a separate accounts package.

FromTXdocsCloud
  1. Matters: Carried across
  2. Contacts: Carried across
  3. Documents: Carried across
  4. Emails: Carried across
  5. Calendar: Carried across
  6. Time and expenses: Carried with mapping
  7. Billing: Carried with mapping
  8. Templates: Carried with mapping
  9. Notes: Confirmed in the analysis
  10. Tasks: Confirmed in the analysis
  11. Trust money: Confirmed in the analysis
  12. Firm accounts: Confirmed in the analysis
  13. Custom fields: Confirmed in the analysis
ToClio ManageCloud
  1. Intake: Kept as a readable archive
Readable archiveNo place in Clio Manage
  • 5 carried
  • 3 mapped
  • 5 to confirm
  • 1 archived
What the two products hold. The analysis confirms it field by field.

What moves

What moves from TXdocs to Clio Manage

Each row is a kind of record TXdocs holds, whether Clio Manage has a place for it, and what is planned. On this route five kinds of record carry across, three kinds need mapping, one kind has no place in Clio Manage and is archived and five kinds are confirmed in the analysis.

Records in TXdocs and their place in Clio Manage
RecordIn TXdocsIn Clio ManageWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldCases, with the data entered for document assembly.Has a placeImported from a matters template, after contacts.Carried across
ContactsClients, other parties and referrersHeld in partCase and contact management is part of TXdocsPlus.Has a placePeople and companies, with related contacts linked to matters by a separate template.Carried across
DocumentsFiles stored in or linked from the systemHeldDocuments assembled from the forms library. Storage detail is confirmed in the analysis.Has a placeFiled under the matter; Clio scopes document migration separately from data.Carried across
EmailsEmails saved to matters or to the storeHeld in partEmail management is listed as a TXdocsPlus feature.Has a placeHeld as communications on the matter, with phone logs.Carried across
NotesFile notes, matter notes and contact notesTo be confirmedHas a placeMatter notes and contact notes each have a template.Confirmed in the analysis
CalendarAppointments, court dates and deadlinesHeld in partCalendaring and deadline tools are in TXdocsPlus.Has a placeCalendar events have a migration template.Carried across
TasksTo-dos and workflow steps assigned to peopleTo be confirmedHas a placeTasks have a migration template.Confirmed in the analysis
Time and expensesTime and expense entries, billed and unbilledHeld in partTime slips, in TXdocsPlus.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 balancesHeld in partIndividual and periodic bills, in TXdocsPlus.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 balancesTo be confirmedHas a place in partA trust balance loads as one line per matter or contact; past transactions do not.Confirmed in the analysis
Firm accountsGeneral ledger, office account and payablesTo be confirmedFinancial reports are included. A general ledger is not confirmed.No placeNot in Clio Manage. Books sit in a linked accounting package, or in Clio Accounting where Clio offers it.Confirmed in the analysis
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 automationHeldAutomated Texas forms from TXdocs, plus the firm’s own customisations.Has a placeRebuilt as Clio document templates with its merge fields.Carried with mapping
IntakeLeads, enquiries, intake forms and pipelinesHeldOnline intake questionnaires that clients complete.No placeLeads and intake forms belong in Clio Grow.Kept as a readable archive

What the plans mean

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

Cases come across. The accounts are set up new.

A case management system holds the working file: parties, notes, deadlines, documents and the fields a practice area needs. It is not usually the firm’s ledger, so time, invoices and trust often sit in an accounting package beside it. Moving to Clio Manage brings those two sources together. The case records come from TXdocs. Opening balances for debtors and trust, where they move at all, come from the accounts package and are agreed to its reports.

Case systems are heavy with custom fields, and that is where the mapping work is. A personal injury or immigration file can carry dozens of fields that a general practice system has no standard place for. Each one is matched to a field in Clio Manage, created there as a custom field, or written into a note on the matter. The firm sees which before the load. Workflows and task templates are rebuilt, not copied.

Both are hosted by their makers, so nothing is collected from the firm’s office. What can be taken out of TXdocs depends on its export tools and on what its maker provides on request, and that is confirmed during the analysis, before a date is set. The subscription to TXdocs is kept running until the checks on Clio Manage are finished.

Where the data is now

What a firm has in TXdocs is mainly case data and the documents assembled from it, and for TXdocsPlus subscribers also time, bills, contacts and a calendar. The forms library belongs to TXdocs and stays with the subscription. A move takes the firm’s own records and finished documents, and plans how drafting will be done afterwards, since drafting is the reason the firm bought the product.

  1. The forms stay behind

    The automated Texas forms are TXdocs’ content, supplied by subscription, and are not carried into another system. What moves is each completed document and the case data behind it. Firms decide before cutover whether to keep a TXdocs subscription for drafting beside the new system, or rebuild their most-used documents as templates in the destination.

  2. Standard or Plus

    A TXdocs Standard firm has cases, intake answers and documents. A TXdocsPlus firm also has time slips, bills, a calendar, contacts and conflict data in the same account. Which plan the firm is on sets the scope. Billing history in particular needs a decision: balances only, or every bill and payment.

  3. Case data shaped for forms

    Information is entered once and reused across documents, so a divorce case may hold inventories and financial statements as structured answers. A general practice system has fields for only some of that. The rest is preserved as a generated summary document on the matter, so the answers are not lost.

  4. Data is held by TXdocs

    The software runs in a browser, and each firm’s data sits in a separate database on TXdocs’ servers. There is no local database for the firm’s IT provider to copy. How the firm’s records and documents are exported is confirmed with TXdocs at the start of the analysis, before a timetable is set.

  5. Filed versions and drafts

    Documents filed with Texas courts through the integrated eFiling should be kept apart from their drafts. Whether filing details can be exported as data is confirmed in the analysis. Either way, the filed version of each document is identified, so that it is the one a lawyer finds first on the matter.

More about moving off TXdocs

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.

Financial records move on this route, so the balances are rehearsed before the real cutover.

  1. Analysis

    We read what TXdocs 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 TXdocs, 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 TXdocs: record counts, financial totals, the links between records, document dates. Exceptions are listed for you to decide.

  4. Cutover

    Changes in TXdocs are frozen for an agreed window, the data is collected a final time and Clio Manage goes live over a weekend. The financial cutover is rehearsed on a full trial load first, so that opening balances agree with the reports in TXdocs as at the cutover date. TXdocs 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 TXdocs 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 fromTXdocs
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 TXdocs 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

TXdocs to Clio Manage: what firms ask

Can our TXdocs forms be moved into the new system?

No. The forms library is TXdocs’ own content and is tied to the subscription. Your finished documents move, and so does your case data. Drafting afterwards is done either by keeping TXdocs for assembly, or by building templates in the new system for the documents you produce most. That choice is made early.

We use TXdocsPlus for billing. What happens to our time and bills?

Unbilled time, open bills and client balances are the minimum that moves, so billing can continue without a gap. Whether older bills and payments come across as history depends on what the destination accepts and what TXdocs can export. The totals are checked against TXdocs reports on the trial load.

Do trust balances in TXdocs have a place in Clio Manage?

That is confirmed in the analysis. We could not establish it from the two products’ own material, so it is checked against your data in TXdocs before the plan is fixed. If Clio Manage turns out to have no place for trust ledgers, they are kept as a readable archive and the firm decides where trust accounting runs.

What happens to records Clio Manage has no place for?

On this route that is intake records. They are exported from TXdocs 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 TXdocs data is loaded into Clio Manage?

Time entries, billing records and templates are carried with mapping, so each mapping is agreed with you first. Notes, tasks, trust ledgers, 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

TXdocs and Clio Manage are the names and marks of their owners, used here only to identify the two systems.

Moving from TXdocs 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.