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

Data migration route

TXdocs to Filevine migration

TXdocs is a cloud specialist tool, and Filevine is a cloud case management system. The records line up case for case, and the detail is in the fields and stages.

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. Intake: Carried with mapping
  10. Notes: Confirmed in the analysis
  11. Tasks: Confirmed in the analysis
  12. Trust money: Confirmed in the analysis
  13. Firm accounts: Confirmed in the analysis
  14. Custom fields: Confirmed in the analysis
ToFilevineCloud
  • 5 carried
  • 4 mapped
  • 5 to confirm
What the two products hold. The analysis confirms it field by field.

What moves

What moves from TXdocs to Filevine

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

Records in TXdocs and their place in Filevine
RecordIn TXdocsIn FilevineWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldCases, with the data entered for document assembly.Has a placeLoaded as projects of a defined project type.Carried across
ContactsClients, other parties and referrersHeld in partCase and contact management is part of TXdocsPlus.Has a placeContact cards, linked to projects.Carried across
DocumentsFiles stored in or linked from the systemHeldDocuments assembled from the forms library. Storage detail is confirmed in the analysis.Has a placeDocs section with folders. Templated project folders can be set per type.Carried across
EmailsEmails saved to matters or to the storeHeld in partEmail management is listed as a TXdocsPlus feature.Has a placeHeld in the activity feed of the project.Carried across
NotesFile notes, matter notes and contact notesTo be confirmedHas a placeHeld as notes in the activity feed.Confirmed in the analysis
CalendarAppointments, court dates and deadlinesHeld in partCalendaring and deadline tools are in TXdocsPlus.Has a placeDeadlines and calendar events.Carried across
TasksTo-dos and workflow steps assigned to peopleTo be confirmedHas a placeConfirmed in the analysis
Time and expensesTime and expense entries, billed and unbilledHeld in partTime slips, in TXdocsPlus.Has a place in partNeeds the Billing product enabled.Carried with mapping
BillingInvoices, payments and debtor balancesHeld in partIndividual and periodic bills, in TXdocsPlus.Has a place in partNeeds the Billing product enabled.Carried with mapping
Trust moneyTrust or client account ledgers and balancesTo be confirmedHas a place in partTrust accounts sit in Payments by Filevine. Loading history is confirmed in the analysis.Confirmed in the analysis
Firm accountsGeneral ledger, office account and payablesTo be confirmedFinancial reports are included. A general ledger is not confirmed.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 automationHeldAutomated Texas forms from TXdocs, plus the firm’s own customisations.Has a place in partTemplates are rebuilt as Filevine document templates. They are not converted.Carried with mapping
IntakeLeads, enquiries, intake forms and pipelinesHeldOnline intake questionnaires that clients complete.Has a place in partLeads belong in Lead Docket, which passes signed clients to Filevine.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 TXdocs.
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

Case to case, field by field.

Two case management systems look alike from a distance and differ in almost every detail. Each has its own idea of a case type, a stage, a party role and a deadline. TXdocs and Filevine may both hold a limitation date, yet one calculates it and the other stores what was typed. The mapping goes field by field and status by status, and the trial load is checked by opening real cases in both systems side by side.

Custom fields hold most of what the firm has built up. Years of intake answers, injury details or visa histories sit in fields the firm added itself. Each is matched to a field in Filevine, and anything unmatched is kept as a note on the case so that it can still be searched. Workflows and document templates are rebuilt in the new system’s own tools. Open tasks come across with their owners and due dates.

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

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.

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

TXdocs to Filevine: 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 Filevine?

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 Filevine turns out to have no place for trust ledgers, they are kept as a readable archive and the firm decides where trust accounting runs.

Does everything in TXdocs have a place in Filevine?

Most of it does on paper. Notes, tasks, trust ledgers, 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 TXdocs data is loaded into Filevine?

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

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