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

Data migration route

triConvey to iManage Cloud migration

triConvey is a practice management system for conveyancing work that runs on the desktop and keeps its data in its maker’s cloud, 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.

FromtriConveyDesktop and cloud
  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. Calendar: Confirmed in the analysis
  7. Custom fields: Confirmed in the analysis
ToiManage CloudCloud
  1. Contacts: Kept as a readable archive
  2. Tasks: Kept as a readable archive
  3. Time and expenses: Kept as a readable archive
  4. Billing: Kept as a readable archive
  5. Trust money: Kept as a readable archive
  6. Intake: Kept as a readable archive
Readable archiveNo place in iManage Cloud
  • 2 carried
  • 2 mapped
  • 3 to confirm
  • 6 archived
What the two products hold. The analysis confirms it field by field.

What moves

What moves from triConvey to iManage Cloud

Each row is a kind of record triConvey 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, six kinds have no place in iManage Cloud and are archived and three kinds are confirmed in the analysis.

Records in triConvey and their place in iManage Cloud
RecordIn triConveyIn iManage CloudWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldProperty matters, with customisable tasks and workflows.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 referrersHeldNo placeKept as a readable archive
DocumentsFiles stored in or linked from the systemHeldCloud storage with local access for offline work.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 storeHeldThrough its Outlook integration.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 deadlinesTo be confirmedNo placeConfirmed in the analysis
TasksTo-dos and workflow steps assigned to peopleHeldNo placeiManage Tracker is a separate product with its own set-up.Kept as a readable archive
Time and expensesTime and expense entries, billed and unbilledHeldBuilt-in time tracking by staff member and matter.No placeKept as a readable archive
BillingInvoices, payments and debtor balancesHeldInvoices and disbursements.No placeKept as a readable archive
Trust moneyTrust or client account ledgers and balancesHeldTrust account tool that can run more than one trust account.No placeKept as a readable archive
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 automationHeldForms and precedents library maintained by triSearch’s content team.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 pipelinesHeld in partIntake forms are part of an add-on.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 triConvey.
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 triConvey 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 triConvey 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 triConvey 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 triConvey 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 triConvey is kept running until the checks on iManage Cloud are finished.

Where the data is now

A triConvey firm’s records are conveyancing files: the parties, the property, the contract, the searches, the settlement figures and the trust ledger. Because the software is powered by Smokeball, its records can be expected to follow Smokeball’s structure, which the analysis confirms. The first question is where the firm is going, since a move to Smokeball itself is a different exercise from a move to an unrelated system.

  1. It runs on Smokeball

    triSearch describes triConvey as powered by Smokeball, with data held on Smokeball’s servers. For a firm moving to Smokeball, we first establish with both vendors whether the account can be transferred as it stands. For any other destination, the work is planned like a move from Smokeball, with the property fields mapped one by one.

  2. Searches return to the matter

    Orders placed through triSearch are filled from matter data, and the fulfilled orders are captured back into the matter. Those results are documents and move with the file. The ordering link does not. In the new system, searches are ordered through whichever provider it connects to, and open orders are finished before cutover.

  3. Settlement adjustments

    triConvey has a calculator for settlement adjustments, which works from figures held in the matter. A general practice system may have no settlement calculator at all. For open matters approaching settlement, the current adjustment sheet is saved as a document, and the firm decides where the figures will be worked from afterwards.

  4. Trust accounts in several states

    The trust tool can run more than one trust account, which practices working across states rely on. Money is recorded against matters within each account. At cutover every account is reconciled and loaded separately, and the destination has to be set up with the same accounts under each state’s rules before any balance goes in.

  5. Journals to Xero or MYOB

    When an invoice is paid, triConvey’s billing puts journal entries into the firm’s Xero or MYOB file. The books are not inside triConvey, so they do not move. From an agreed date the new system takes over the posting, and its account mapping is tested first so the office account still reconciles.

More about moving off triConvey

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 triConvey 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 triConvey: 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 triConvey, a final pass over a weekend picks up what changed since the trial. triConvey 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 triConvey 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 fromtriConvey
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 triConvey 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

triConvey to iManage Cloud: what firms ask

Is moving from triConvey to Smokeball a migration at all?

It may not need to be a full one, since triConvey is powered by Smokeball. That is a question for the two vendors, and we ask it at the start. If a transfer is not available, the move is planned in the usual way: analysis, clean-up, trial load and a rehearsed trust cutover.

What happens to searches we ordered through triSearch?

Completed search results are saved in the matter, so they come across with the file. Orders still outstanding at cutover are the risk. We list them during the freeze window so they can be completed or re-ordered, and nothing is left arriving into a system the practice has stopped using.

Do contracts and precedents come across?

Contracts already prepared are documents and move with their matters. The forms and precedents library is maintained by triSearch’s content team, so it stays with triConvey. Any precedents the practice wrote itself are exported as Word files and rebuilt with the new system’s merge fields.

Do trust balances in triConvey have a place in iManage Cloud?

No. iManage Cloud does not keep trust ledgers. Trust records from triConvey are exported as ledgers and statements that open without it, and the firm settles where its trust accounting runs from the cutover date before the move is planned.

What happens to records iManage Cloud has no place for?

On this route that is contacts, tasks, time entries, billing records, trust ledgers and intake records. They are exported from triConvey 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 triConvey data is loaded into iManage Cloud?

Matters and templates are carried with mapping, so each mapping is agreed with you first. Notes, calendar entries 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

triConvey and iManage Cloud are the names and marks of their owners, used here only to identify the two systems.

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