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

Data migration route

triConvey to SharePoint 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 SharePoint is cloud file storage. Documents move into a folder for each client and matter, and the data behind them is kept as an export.

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

What moves

What moves from triConvey to SharePoint

Each row is a kind of record triConvey holds, whether SharePoint has a place for it, and what is planned. On this route one kind of record carries across, five kinds need mapping, four kinds have no place in SharePoint and are archived and three kinds are confirmed in the analysis.

Records in triConvey and their place in SharePoint
RecordIn triConveyIn SharePointWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldProperty matters, with customisable tasks and workflows.Has a place in partAs a site, library, folder or list row the firm designs; no built-in matter record.Carried with mapping
ContactsClients, other parties and referrersHeldHas a place in partOnly as rows in a list built for the purpose.Carried with mapping
DocumentsFiles stored in or linked from the systemHeldCloud storage with local access for offline work.Has a placeFiles in libraries, with columns and versions.Carried across
EmailsEmails saved to matters or to the storeHeldThrough its Outlook integration.Has a place in partAs .msg or .eml files, with columns for sender and date if set up.Carried with mapping
NotesFile notes, matter notes and contact notesTo be confirmedHas a place in partAs documents, or as rows in a notes list if one is built.Confirmed in the analysis
CalendarAppointments, court dates and deadlinesTo be confirmedHas a place in partPossible as a list; usually left in Outlook.Confirmed in the analysis
TasksTo-dos and workflow steps assigned to peopleHeldHas a place in partPossible as a list; no legal workflow built in.Carried with mapping
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 placeColumns and content types on libraries and lists.Confirmed in the analysis
TemplatesPrecedents, document templates and automationHeldForms and precedents library maintained by triSearch’s content team.Has a place in partPrecedents as files; templates can be offered from a library.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
SharePoint has a place for this kind of record. It is loaded there and checked against triConvey.
Carried with mapping
SharePoint 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
SharePoint 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

Out of the system, into folders the firm can read.

File storage has folders and files and nothing else. Moving from triConvey into SharePoint means turning matters into a folder tree, usually client, then matter, then the folders used inside it. The naming rule is agreed first, because it is hard to change once thousands of folders exist: whether the matter number leads, how closed matters are separated, what happens to characters SharePoint does not allow in a name.

Everything that is not a document needs somewhere to go. Contacts, notes, time, invoices and trust ledgers have no place in a folder, so they are exported as spreadsheets and reports and stored alongside, often as a summary file in each matter folder and a full set in an archive area. Firms choose this route to keep a readable copy of a system they are retiring, or as a staging step. The export is checked either way: folders against matters, files against the document register in triConvey.

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

SharePoint will take a firm’s documents in almost any arrangement, which is the difficulty. The structure has to be chosen before the load: what a client is, what a matter is, and where security is applied. Changing it afterwards means moving every file again. Most of the effort goes into that design and into the columns that describe each document.

  1. Site, library or folder per matter

    A matter can be a site, a library within a client site, or a folder in one large library. Each choice has consequences for permissions, for search and for how a new matter is opened. The firm makes that decision, and the people who open matters every day should be part of it.

  2. Columns are built before content

    If documents are to carry matter number, client, document type or author as columns, those columns and any content types exist before loading, so each file can be tagged as it arrives. Tagging hundreds of thousands of documents afterwards is a second project that seldom gets finished.

  3. The 400 character path

    SharePoint limits the full decoded path, site and library and folders and file name, to 400 characters. A deep tree copied from a server drive under a long site name can cross it. Path lengths are calculated against the planned structure, not the old one, before any file moves.

  4. Large libraries and the view threshold

    A library can hold millions of files, but a view that tries to show more than 5,000 items at once runs into the list view threshold. One flat library with a folder per matter needs indexed columns and filtered views from the start, or views begin to fail as the library fills.

  5. Security by library, not by file

    Microsoft supports up to 50,000 unique permissions in a library and recommends staying under 5,000. Restricting matters one folder at a time reaches that sooner than firms expect. Restricted work is better grouped into its own site or library, so the permission is set once.

More about moving into SharePoint

How NewLaw runs it

Four steps, in this order.

Nothing financial lands in SharePoint 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 SharePoint. 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 SharePoint 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 toSharePoint

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

Structure, permissions and handover

SharePoint is storage, not an application, so there is no product to configure. What is agreed and set up is the folder structure, who can open what, and how the result is handed to the firm.

Making SharePoint work as a firm’s document store is a design and build job in its own right. The sites, libraries, columns and permission groups are created, a way of opening a new matter is put in place so the structure repeats itself, and the Outlook and Teams habits around it are agreed. Search is tested with real questions from fee earners.

What is agreed and set up

  • Site and library structure for clients and matters
  • Columns and content types for matter number and document type
  • Permission groups, with restricted matters in their own libraries
  • A repeatable way to create each new matter’s workspace
  • Version history limits and retention labels for closed matters
  • Views, indexed columns and search tested on loaded data

Questions

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

No. SharePoint 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 SharePoint has no place for?

On this route that is 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 SharePoint?

Matters, contacts, emails, tasks 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 SharePoint are the names and marks of their owners, used here only to identify the two systems.

Moving from triConvey to SharePoint?

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

We reply within one business day.