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

Data migration route

triConvey to Litify 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 Litify is a cloud case management system. Matter records move into cases, and the firm decides where its accounting runs from the cutover date.

FromtriConveyDesktop and cloud
  1. Matters: Carried across
  2. Contacts: Carried across
  3. Documents: Carried across
  4. Tasks: Carried across
  5. Time and expenses: Carried across
  6. Intake: Carried across
  7. Emails: Carried with mapping
  8. Billing: Carried with mapping
  9. Templates: Carried with mapping
  10. Notes: Confirmed in the analysis
  11. Calendar: Confirmed in the analysis
  12. Trust money: Confirmed in the analysis
  13. Custom fields: Confirmed in the analysis
ToLitifyCloud
  • 6 carried
  • 3 mapped
  • 4 to confirm
What the two products hold. The analysis confirms it field by field.

What moves

What moves from triConvey to Litify

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

Records in triConvey and their place in Litify
RecordIn triConveyIn LitifyWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldProperty matters, with customisable tasks and workflows.Has a placeMatters, by case type.Carried across
ContactsClients, other parties and referrersHeldHas a placeLoaded as parties and connected by roles.Carried across
DocumentsFiles stored in or linked from the systemHeldCloud storage with local access for offline work.Has a placeLoaded to the document component and attached to matters.Carried across
EmailsEmails saved to matters or to the storeHeldThrough its Outlook integration.Has a place in partShown on the activity timeline. How old email is loaded is confirmed in the analysis.Carried with mapping
NotesFile notes, matter notes and contact notesTo be confirmedTo be confirmedConfirmed in the analysis
CalendarAppointments, court dates and deadlinesTo be confirmedHas a placeCalendar events on the matter.Confirmed in the analysis
TasksTo-dos and workflow steps assigned to peopleHeldHas a placeCarried across
Time and expensesTime and expense entries, billed and unbilledHeldBuilt-in time tracking by staff member and matter.Has a placeTime entries on the matter.Carried across
BillingInvoices, payments and debtor balancesHeldInvoices and disbursements.Has a place in partBilling is part of the product. Loading past invoices is scoped in the analysis.Carried with mapping
Trust moneyTrust or client account ledgers and balancesHeldTrust account tool that can run more than one trust account.To be confirmedConfirmed in the analysis
Custom fieldsFields and record types the firm added itselfTo be confirmedHas a placeCustom fields are created before loading.Confirmed in the analysis
TemplatesPrecedents, document templates and automationHeldForms and precedents library maintained by triSearch’s content team.Has a place in partTemplates are rebuilt in Litify’s document generation.Carried with mapping
IntakeLeads, enquiries, intake forms and pipelinesHeld in partIntake forms are part of an add-on.Has a placeLoaded as intakes.Carried across

What the plans mean

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

Matters become cases. The ledgers need a home.

Going from a practice management system to a case management system is a move towards the file and away from the ledger. Matters, parties, documents, notes and deadlines have a natural place in Litify. Time, invoices, trust and the general ledger often do not, or only in part, and the table above shows which. Before the move is planned the firm settles where billing and trust accounting will run, because that decides what is loaded and what is archived.

Case systems are usually built around a practice area, with their own stages, roles and document sets. A general matter from triConvey has to be given a case type in Litify, and that choice drives which fields and workflows it gets. The mapping is agreed type by type. Financial history with no place in Litify is exported as reports and ledgers the firm can open without triConvey, and kept as the record of what was billed and held.

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

Loading a firm into Litify is done inside a Salesforce environment that has been configured for that firm, normally by Litify or one of its implementation partners. The data work fits around that project. Old records are mapped to parties, roles, intakes and matters and loaded into the Salesforce objects behind them, and documents are loaded separately and attached.

  1. The design comes first

    Case types, stages and page layouts are decided during discovery, before any load. A load into a half-configured environment has to be repeated when a field changes. The data mapping is written against the agreed design and updated whenever the design moves, so the two stay in step.

  2. One party, many roles

    Contacts from the old system become parties, and each appearance on a matter becomes a role. Duplicate contacts turn into duplicate parties with their roles divided between them. Duplicates are merged before the load where they can be identified, since separating them afterwards means pointing every role at the right party again.

  3. Open enquiries load as intakes

    Leads and enquiries that have not signed belong in intakes, not matters. They are loaded with their source and status so that conversion reports start from a true position. Old declined enquiries are loaded only if the firm wants them for conflict checking, and are marked so they do not count as live.

  4. Documents load after records

    Files are loaded into the document component once the matters exist, because each one is attached to a matter record. Folder structure is set per case type beforehand. Large injury files with medical records and video take time to transfer, and that time is planned into the cutover weekend.

  5. Validation rules reject bad rows

    A configured environment enforces required fields and validation rules, and old data seldom satisfies all of them. Rows that fail are reported by the load. They are fixed in the source and run again, or the rule is relaxed for migrated records, and the firm decides which for each rule.

More about moving into Litify

How NewLaw runs it

Four steps, in this order.

Financial records move on this route, so the balances are rehearsed before the real cutover. The maker of Litify says that it, or its partners, load firms into the product. Where the firm uses that service, NewLaw’s part is the work around it: the analysis, the clean-up in triConvey and checking each trial against triConvey.

  1. Analysis

    We read what triConvey holds and how its records link, then agree with you, field by field, where each piece will sit in Litify. 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 triConvey, before extraction. It is not always possible to find every one, so some may carry across.

  3. Trial load

    The data is loaded into Litify as a trial and checked against triConvey: record counts, financial totals, the links between records, document dates. Exceptions are listed for you to decide.

  4. Cutover

    Changes in triConvey are frozen for an agreed window, the data is collected a final time and Litify 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 triConvey as at the cutover date. 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 toLitify

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 Litify. 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 Litify

Loaded data is not yet a working system. The maker of Litify runs or arranges the set-up of its product, so this is what has to be decided and put in place in Litify, whoever does the work, before people rely on it from the first day.

A Litify implementation is a configuration project on Salesforce, run by Litify or an implementation partner with the firm’s own project team. Discovery sessions with each department come first. The decisions that follow shape the system: what an intake asks, how a matter moves through its stages, who sees what, and which other systems are connected.

Set-up decisions in Litify

  • Define intake questionnaires and the rules for conversion
  • Set case types, matter stages and page layouts
  • Build matter plans that create tasks at each stage
  • Design document folders and generation templates per case type
  • Configure user roles and sharing for restricted matters
  • Decide on timekeeping, billing and accounting integrations

Questions

triConvey to Litify: 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 Litify?

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 triConvey before the plan is fixed. If Litify 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 triConvey have a place in Litify?

Most of it does on paper. Notes, calendar entries, trust ledgers 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 Litify is kept as a readable archive, and you see which before the move.

What has to be decided before triConvey data is loaded into Litify?

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

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

Moving from triConvey to Litify?

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

We reply within one business day.