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

Data migration route

TXdocs to iManage Cloud migration

TXdocs is a cloud specialist tool, and iManage Cloud is a cloud document management system. Documents and email move, filed under the matters they came from. Time, billing and trust have no place in a document system.

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

What moves

What moves from TXdocs to iManage Cloud

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

Records in TXdocs and their place in iManage Cloud
RecordIn TXdocsIn iManage CloudWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldCases, with the data entered for document assembly.Has a place in partAs a workspace with client and matter metadata. Parties and status stay in practice management.Carried with mapping
ContactsClients, other parties and referrersHeld in partCase and contact management is part of TXdocsPlus.No placeKept as a readable archive
DocumentsFiles stored in or linked from the systemHeldDocuments assembled from the forms library. Storage detail is confirmed in the analysis.Has a placeEach needs a workspace and valid client and matter values; its class sets default security.Carried across
EmailsEmails saved to matters or to the storeHeld in partEmail management is listed as a TXdocsPlus feature.Has a placeLoaded as email documents into the workspace’s email folders.Carried across
NotesFile notes, matter notes and contact notesTo be confirmedNo placeFile notes can be loaded as documents on the matter.Confirmed in the analysis
CalendarAppointments, court dates and deadlinesHeld in partCalendaring and deadline tools are in TXdocsPlus.No placeKept as a readable archive
TasksTo-dos and workflow steps assigned to peopleTo be confirmedNo placeiManage Tracker is a separate product with its own set-up.Confirmed in the analysis
Time and expensesTime and expense entries, billed and unbilledHeld in partTime slips, in TXdocsPlus.No placeKept as a readable archive
BillingInvoices, payments and debtor balancesHeld in partIndividual and periodic bills, in TXdocsPlus.No placeKept as a readable archive
Trust moneyTrust or client account ledgers and balancesTo be confirmedNo placeConfirmed in the analysis
Firm accountsGeneral ledger, office account and payablesTo be confirmedFinancial reports are included. A general ledger is not confirmed.No placeConfirmed in the analysis
Custom fieldsFields and record types the firm added itselfTo be confirmedHas a place in partA fixed number of custom profile fields, each a validated list.Confirmed in the analysis
TemplatesPrecedents, document templates and automationHeldAutomated Texas forms from TXdocs, plus the firm’s own customisations.Has a place in partPrecedents load as documents. Automation is rebuilt in the firm’s drafting tools.Carried with mapping
IntakeLeads, enquiries, intake forms and pipelinesHeldOnline intake questionnaires that clients complete.No placeKept as a readable archive

What the plans mean

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

The documents move. The accounts do not.

Moving from a matter system into a document management system is a documents job. iManage Cloud has no place for time, invoices or trust, so there is no financial cutover on this route. What it does want is structure. Every document from TXdocs is filed into a workspace or folder for its client and matter, with a profile that says what it is. The client and matter list becomes that structure, which is why it is cleaned before any file is copied.

A document’s own details count for more here than anywhere. Created and modified dates, author, document type and version become searchable profile fields, and a wrong date on a few thousand files is hard to undo. Email filed to matters is carried as messages. Document copies can be run again, so the trial is repeated until counts and dates agree. Matter data that iManage Cloud cannot hold goes to whatever replaces TXdocs for matters and billing, or into an archive.

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 iManage Cloud 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

Administrators of an iManage Cloud library have API access only, so nothing is loaded by writing to a database. For cloudimanage.com, the newer of its two cloud platforms, iManage lists a supervised import API, sync APIs and a metadata loader. Nothing can be filed loose: every document goes into a workspace, with valid client and matter values. So the client and matter lists, the workspace template and the security groups are built first.

  1. Client and matter lists first

    Custom1 and custom2 are validated lists, with each matter a child of its client. A value that is not already in the list cannot be assigned to a document. The lists are loaded from the practice management system or the old document store before any content, closed matters with documents included.

  2. One workspace per matter

    Each matter gets a workspace generated from a template, so the template is designed before migration: its tabs, its folders, which are created up front and which on demand. Old folder trees rarely match it. The mapping says where each old folder lands and what happens to folders with no equivalent.

  3. Authors must be known users

    Author and operator are profile fields tied to users of the library. Documents written by people who left years ago need a decision: recreate those people as inactive users, or assign a placeholder author. That choice affects searching by author for as long as the firm uses the system.

  4. Hybrid security

    iManage calls its security model hybrid: where a user’s groups disagree, the most permissive access applies unless one of them is denied. On cloudimanage.com that model cannot be changed. Default security is normally set on the workspace and inherited below it. Restricted matters from the old system are loaded with their access list already in place.

  5. New numbers, original dates

    Documents are numbered by iManage as they are loaded, so old numbers do not carry over as numbers. On cloudimanage.com the file date setting is fixed to the file’s own date, and on imanage.work it can be set either way. Which dates display is checked on the trial load. The old reference can be carried in a custom field or the description where the firm wants to search by it.

More about moving into iManage Cloud

How NewLaw runs it

Four steps, in this order.

Nothing financial lands in iManage Cloud on this route, which makes it repeatable: a load can be run again until it is right.

  1. Analysis

    We read what TXdocs holds and how it is organised, then agree with you where each kind of record will sit in iManage Cloud. Anything with no place there stays behind or is archived, and you see which before the move.

  2. Clean-up

    Duplicate clients, matters and folders are merged where they can be identified, and naming is put into one format, before anything is copied. It is not always possible to find every one, so some may carry across.

  3. Trial load

    A trial is loaded into iManage Cloud and checked against TXdocs: record and file counts, the links between records, document dates, and a sample opened by your own people. Exceptions are listed for you to decide.

  4. Cutover

    There is no financial cutover on this route. After a short freeze on changes in TXdocs, a final pass over a weekend picks up what changed since the trial. 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 toiManage Cloud

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 iManage Cloud. 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 iManage Cloud

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

Setting up iManage Cloud is mostly design work done before any user logs in: how many libraries, what a workspace looks like, which profile fields are captioned for what, and who can see which matters. Then come the links that keep it running day to day, such as creating a workspace when a matter is opened in the practice management system, and the add-ins on each desk.

Set-up decisions in iManage Cloud

  • Library structure and captions for client, matter and other fields
  • Workspace templates, folder names and Flexible Folders rules by practice area
  • Document classes, subclasses and the profile fields each one requires
  • Roles, groups, default security and walls for restricted matters
  • Workspace creation fed from the practice management system’s matter list
  • Work Desktop, Outlook email filing and Mobility on each device, with training

Questions

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

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 iManage Cloud 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 iManage Cloud has no place for?

On this route that is contacts, calendar entries, time entries, billing records and 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 iManage Cloud?

Matters 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 decides which closed matters and how many versions of a document are in scope.

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

Moving from TXdocs to iManage Cloud?

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

We reply within one business day.