Data migration route
triConvey to SimpleLaw 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 SimpleLaw is a cloud practice management system. Both run a whole practice, so this is a full move, and the financial records set the timetable.
triConveyDesktop and cloud- Matters: Carried across
- Contacts: Carried across
- Documents: Carried across
- Tasks: Carried across
- Time and expenses: Carried across
- Intake: Carried across
- Billing: Carried with mapping
- Trust money: Carried with mapping
- Templates: Carried with mapping
- Emails: Confirmed in the analysis
- Notes: Confirmed in the analysis
- Calendar: Confirmed in the analysis
- Custom fields: Confirmed in the analysis
SimpleLawCloud- 6 carried
- 3 mapped
- 4 to confirm
What moves
What moves from triConvey to SimpleLaw
Each row is a kind of record triConvey holds, whether SimpleLaw 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.
| Record | What is planned | ||
|---|---|---|---|
| MattersMatters or cases, with their numbers, types, parties and status | HeldProperty matters, with customisable tasks and workflows. | Has a place | Carried across |
| ContactsClients, other parties and referrers | Held | Has a placeAs leads, clients or other contacts in the CRM. | Carried across |
| DocumentsFiles stored in or linked from the system | HeldCloud storage with local access for offline work. | Has a placeUploaded to SimpleLaw storage or held in a linked Dropbox, Google Drive or OneDrive. | Carried across |
| EmailsEmails saved to matters or to the store | HeldThrough its Outlook integration. | To be confirmed | Confirmed in the analysis |
| NotesFile notes, matter notes and contact notes | To be confirmed | Has a place | Confirmed in the analysis |
| CalendarAppointments, court dates and deadlines | To be confirmed | Has a place | Confirmed in the analysis |
| TasksTo-dos and workflow steps assigned to people | Held | Has a place | Carried across |
| Time and expensesTime and expense entries, billed and unbilled | HeldBuilt-in time tracking by staff member and matter. | Has a place | Carried across |
| BillingInvoices, payments and debtor balances | HeldInvoices and disbursements. | Has a place in partInvoices are created in the product; loading invoice history is confirmed in the analysis. | Carried with mapping |
| Trust moneyTrust or client account ledgers and balances | HeldTrust account tool that can run more than one trust account. | Has a place in partTrust balances are supported; history depth is confirmed in the analysis. | Carried with mapping |
| Custom fieldsFields and record types the firm added itself | To be confirmed | Has a place | Confirmed in the analysis |
| TemplatesPrecedents, document templates and automation | HeldForms and precedents library maintained by triSearch’s content team. | Has a place in partTemplates are rebuilt using SimpleLaw’s own automation. | Carried with mapping |
| IntakeLeads, enquiries, intake forms and pipelines | Held in partIntake forms are part of an add-on. | Has a placeLeads and intake forms. | Carried across |
What the plans mean
- Carried across
- SimpleLaw has a place for this kind of record. It is loaded there and checked against triConvey.
- Carried with mapping
- SimpleLaw 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
The whole practice moves, accounts included.
A move between two practice management systems is the widest kind there is. triConvey and SimpleLaw each keep matters, contacts, documents, time and money in one place, but no two systems link those records the same way. In one, a client is a contact with a role on the matter. In another, every matter carries its own client card. Most of the analysis goes into those links, because a matter that arrives without its client or its documents is the first thing staff find.
The financial side decides the dates. Unbilled time, debtor balances and trust ledgers have to agree with triConvey’s own reports as at one day, and a new system usually wants them as opening balances, not as years of transactions. So the firm decides early how much history comes across as live records and how much is kept as reports. Matter and document loads can be repeated until they are right. The money is loaded once.
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 SimpleLaw are finished.
Where the data is now
Leaving triConvey
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.
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.
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.
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.
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.
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.
Where it is going
Arriving in SimpleLaw
Loading a firm into SimpleLaw is mostly a job of sorting contacts and setting up each matter’s billing type. The CRM holds leads, clients and everyone else, so every incoming contact needs a status. Where documents will be stored is decided early as well, since that choice determines where the files are sent. Accounting history stays in QuickBooks or the old system.
Lead, client or contact
A person is tracked from first enquiry to client in one CRM, with tasks and appointments kept against the contact. Source systems that only ever held clients load simply. Systems with separate intake records need each enquiry classed as a live lead, a lost one or a duplicate of an existing client.
Billing type on each matter
Every matter is billed as hourly, flat fee, instalments, contingency, pro bono, trust or LEDES. The source may record this loosely or not at all. During the trial load a billing type is set on each matter and checked by the person who raises the bills, because it controls how the invoice is built.
Storage chosen before loading
If the firm stores documents with SimpleLaw, files are uploaded against each matter. Where it prefers Dropbox, Google Drive or OneDrive, the files go there, and what the connection does with folders already in place is checked first. Switching later means moving everything again, so the choice is made at the start with the firm’s IT support.
Custom fields named for templates
Custom fields supply intake forms and document automation as well as reports. A field brought across from the old system is only useful if templates can call on it. Fields are therefore named and typed with the firm’s main documents in mind, and one template is tested against loaded data.
Portal access client by client
The client portal is optional and the firm chooses who has access and what each client can see. Nothing is exposed by loading data. After go-live, access is switched on for chosen clients, starting with a few, once the firm has reviewed what their matters show.
How NewLaw runs it
Four steps, in this order.
Trust money moves on this route, so the trust cutover gets a rehearsal of its own.
Analysis
We read what triConvey holds and how its records link, then agree with you, field by field, where each piece will sit in SimpleLaw. Anything with no place there comes across as a note or stays behind, and you see which before the move.
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.
Trial load
The data is loaded into SimpleLaw as a trial and checked against triConvey: record counts, trust and debtor totals, the links between records, document dates. Exceptions are listed for you to decide.
Cutover
Changes in triConvey are frozen for an agreed window, the data is collected a final time and SimpleLaw goes live over a weekend. The trust and financial cutover is rehearsed on a full trial load first, because it cannot be re-run the way a document load can. 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
What happens after you send it
- A free first call
We go through your answers with you and ask about anything they leave open.
- An analysis of what triConvey holds
What is in it, how its records link, and where each piece would sit in SimpleLaw. Anything with no place there comes across as a note or stays behind, and you see which before the move.
- 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 SimpleLaw
Loaded data is not yet a working system. This is what NewLaw sets up in SimpleLaw, beyond the migration, so that people can work in it from the first day.
The set-up work is in making the product reflect the firm. Labels are adjusted to the firm’s terms. Intake forms and the custom fields behind them are built for each practice area, then document templates are made to draw on those fields. Workflows are written for the case types that follow a standard path, and the QuickBooks and payment connections are made last.
Set-up decisions in SimpleLaw
- Labels for documents, activities, expenses and contact IDs
- Custom fields and intake forms for each practice area
- Document templates and the attorney-client agreement
- Workflows for case types that follow a standard process
- User permission sets and client portal visibility
- QuickBooks connection and the online payment processor
Questions
triConvey to SimpleLaw: 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 SimpleLaw?
In part. Trust balances are supported; history depth is confirmed in the analysis. The analysis sets out which trust records have a place in SimpleLaw and which are kept as an archive, and the trust cutover is rehearsed on a full trial load before the real one.
Does everything in triConvey have a place in SimpleLaw?
Most of it does on paper. Emails, notes, calendar entries 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 SimpleLaw is kept as a readable archive, and you see which before the move.
What has to be decided before triConvey data is loaded into SimpleLaw?
Billing records, trust ledgers and templates are carried with mapping, so each mapping is agreed with you first. Emails, notes, calendar entries 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.
Other routes
Other routes from triConvey and into SimpleLaw
Other destinations from triConvey
Other systems that move into SimpleLaw
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.
Choose your systems
Technology stack selection
Decide which practice management system your firm runs, with the evidence and the cost beside it.
About four weeks for a firm of about 15 people. Fixed price, set after a free first call.
Move your data
Data migration
Your data is cleaned up before anything moves, then a trial load is checked against the old system.
Fixed price, agreed after the analysis.
Set up your new system
Implementation
Your new system set up around the way your firm works: configuration, document automation and training.
A small firm of 1 to 10 users typically takes 4 to 8 weeks. A mid-sized firm of 10 to 50 users takes 8 to 16 weeks.
Put AI to work
AI advisory and enablement
A small group of your people learn to use an approved AI tool on real work, under written rules.
Two to four weeks for a small first group. Fixed price, set after a free first call.
triConvey and SimpleLaw are the names and marks of their owners, used here only to identify the two systems.
Moving from triConvey to SimpleLaw?
Tell us what you are moving. You get a plan and a fixed price after the analysis.
We reply within one business day.