Data migration route
PracticeMaster to SmartAdvocate migration
PracticeMaster is a server-based case management system, and SmartAdvocate is a cloud case management system for personal injury work. The records line up case for case, and the detail is in the fields and stages.
PracticeMasterServer- Matters: Carried across
- Contacts: Carried across
- Documents: Carried across
- Emails: Carried across
- Notes: Carried across
- Calendar: Carried across
- Tasks: Carried across
- Time and expenses: Carried across
- Intake: Carried across
- Custom fields: Carried with mapping
- Templates: Carried with mapping
SmartAdvocateCloud- 9 carried
- 2 mapped
What moves
What moves from PracticeMaster to SmartAdvocate
Each row is a kind of record PracticeMaster holds, whether SmartAdvocate has a place for it, and what is planned. On this route nine kinds of record carry across and two kinds need mapping.
| Record | What is planned | ||
|---|---|---|---|
| MattersMatters or cases, with their numbers, types, parties and status | HeldClient file mirrored with Tabs3 Billing, one record per Client ID. | Has a placeCases by case type, with master and member relationships. | Carried across |
| ContactsClients, other parties and referrers | Held | Has a place | Carried across |
| DocumentsFiles stored in or linked from the system | HeldDocument Management records link files to a client or contact, with check-out and versions. | Has a placeDocuments page, by category and subcategory. | Carried across |
| EmailsEmails saved to matters or to the store | HeldEmail records in the Journal, created through the Outlook integration. | Has a placeEmails are attached to cases. | Carried across |
| NotesFile notes, matter notes and contact notes | HeldNote, phone call and research records in the Journal. | Has a place | Carried across |
| CalendarAppointments, court dates and deadlines | HeldFirm-wide calendar with Outlook integration and calendar plan templates. | Has a placeAppointments and critical deadlines. | Carried across |
| TasksTo-dos and workflow steps assigned to people | HeldTasks and reminders on the calendar. | Has a place | Carried across |
| Time and expensesTime and expense entries, billed and unbilled | Held in partTimer records and fees that pass to Tabs3 Billing. | Has a placeTracked time entries. | Carried across |
| Custom fieldsFields and record types the firm added itself | HeldAreas of Practice with the firm’s own files and fields. | Has a place in partConfirmed in the analysis for each field with no standard home. | Carried with mapping |
| TemplatesPrecedents, document templates and automation | HeldDocument assembly with Word or HotDocs, WorkFlows and calendar plan templates. | Has a place in partTemplates are rebuilt with SmartAdvocate merge codes. | Carried with mapping |
| IntakeLeads, enquiries, intake forms and pipelines | Held in partTabs3 CRM handles leads and intake and passes them to PracticeMaster. | Has a placeIntake and lead records. | Carried across |
What the plans mean
- Carried across
- SmartAdvocate has a place for this kind of record. It is loaded there and checked against PracticeMaster.
- Carried with mapping
- SmartAdvocate holds this differently, or in part. Each field or value is matched to its place before loading, and you see the mapping first.
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
Case to case, field by field.
Two case management systems look alike from a distance and differ in almost every detail. Each has its own idea of a case type, a stage, a party role and a deadline. PracticeMaster and SmartAdvocate may both hold a limitation date, yet one calculates it and the other stores what was typed. The mapping goes field by field and status by status, and the trial load is checked by opening real cases in both systems side by side.
Custom fields hold most of what the firm has built up. Years of intake answers, injury details or visa histories sit in fields the firm added itself. Each is matched to a field in SmartAdvocate, and anything unmatched is kept as a note on the case so that it can still be searched. Workflows and document templates are rebuilt in the new system’s own tools. Open tasks come across with their owners and due dates.
PracticeMaster runs on the firm’s own equipment, so the data is collected there: a copy of the database and the folders its documents sit in, taken with the firm’s IT provider or over a remote session. SmartAdvocate is hosted by its maker, so loading depends on the import tools and access it provides. The old machine is kept, read only, as the fall-back record.
Where the data is now
Leaving PracticeMaster
PracticeMaster is the part of Tabs3 that looks most like other practice systems, and the part firms have customised most. Contacts, calendar and journal records move in a familiar way. The detail is in the Areas of Practice the firm built, the documents it linked, and the WorkFlows it depends on, none of which have the same shape in another product.
Areas of Practice are tables
Each Area of Practice has its own files, and firms add files and fields through File Maintenance. A probate area might hold assets and heirs, a family area children and hearings. These can hold many rows for one matter. Every file is listed with its row counts, and each needs a home or a decision.
The Journal mixes record types
Timer records, phone calls, emails, research and notes are all stored in one Journal file, told apart by a record type. Destinations usually split those into time entries, emails and file notes. Journal records are sorted by type on the way out, so a timer record already billed is not loaded a second time as a note.
Documents are linked, with versions
The Document Management file links documents to a client or contact, with check-out, check-in and versions. Each record is only the link, and the document is a file on the firm’s storage. PracticeMaster has its own verify function for these links, and it is run before extraction so broken ones are known.
Template paths by practice area
Document assembly templates sit in a Template Path for each Area of Practice, by default a DOCS folder under that area, and may be Word or HotDocs templates. Their merge codes refer to PracticeMaster fields. Templates are rebuilt against the new system’s fields, starting with the ones produced most often.
WorkFlows and calendar plans
WorkFlows fire when records are added or changed, and calendar plan templates lay down a series of dated events. Events already created come across as calendar entries. The automation itself is described and rebuilt with the destination’s own tools, because rules do not transfer between products.
Where it is going
Arriving in SmartAdvocate
SmartAdvocate keeps injury detail in structured fields and screens, so mapping counts for more than usual: the more precisely the old data is placed, the more of those screens are filled on the first day. Parties, incidents, insurers, providers and bills are loaded to their own screens, and the vendor’s implementation team runs conversions into it.
Map to fields, not notes
The case summary, dashboards and settlement screen read from structured fields. Injury details, insurance limits and provider bills dumped into a note leave those screens empty. The mapping takes each old field to its SmartAdvocate counterpart, and only what truly has no counterpart is loaded as a note.
Case types and statuses
Cases are loaded against case types and statuses that drive WorkPlans and reports. These are agreed with the firm before the trial load, and old statuses are translated to the new list. A status with no match is not guessed at. It is listed, and someone who knows the files decides.
Document categories
Documents are searched by category, subcategory, sender, recipient and date as well as by folder. The old system’s folders are translated into categories on the way in. Files that arrive uncategorised can still be found by description, but they fall outside the category views staff are trained to use.
Working with the vendor’s conversion
SmartAdvocate’s implementation team converts client data into the system and trains staff through its own classes. The firm’s side of that is supplying a clean source, checking the converted cases against the old system, and deciding what to do with the exceptions. Independent help is used on those tasks.
Choosing Server or Cloud
The firm decides before loading whether it will run the Server edition on its own Windows server or use the hosted Cloud edition. Either way the data load is the same. What differs is who looks after backups, updates and remote access afterwards, and that is settled with the firm’s IT provider.
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 SmartAdvocate 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 PracticeMaster and checking each trial against PracticeMaster.
Analysis
We read what PracticeMaster holds and how its records link, then agree with you, field by field, where each piece will sit in SmartAdvocate. 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 PracticeMaster, before extraction. It is not always possible to find every one, so some may carry across.
Trial load
The data is loaded into SmartAdvocate as a trial and checked against PracticeMaster: record counts, financial totals, the links between records, document dates. Exceptions are listed for you to decide.
Cutover
Changes in PracticeMaster are frozen for an agreed window, the data is collected a final time and SmartAdvocate 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 PracticeMaster as at the cutover date. PracticeMaster 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 PracticeMaster 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 PracticeMaster holds
What is in it, how its records link, and where each piece would sit in SmartAdvocate. 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 SmartAdvocate
Loaded data is not yet a working system. The maker of SmartAdvocate runs or arranges the set-up of its product, so this is what has to be decided and put in place in SmartAdvocate, whoever does the work, before people rely on it from the first day.
Setting up SmartAdvocate is a matter of deciding how much of its detail the firm will use from the start. Case types, statuses and WorkPlans come first because they drive everything else. Templates follow. The vendor trains staff through its own classes, and the decisions below are best made before the first of those.
Set-up decisions in SmartAdvocate
- Choose the Server or Cloud edition with IT
- Define case types, statuses and staff roles
- Build WorkPlans and Automated Procedures for each case type
- Convert letters and forms into templates with merge codes
- Install the Outlook plugin and agree email filing habits
- Set up intake screens, lead sources and dashboards
Questions
PracticeMaster to SmartAdvocate: what firms ask
Do emails saved from Outlook come across?
Emails saved through the Outlook integration become journal records on the client. They are loaded to the matter as emails where the destination has an email record, otherwise as dated notes with the message saved as a file.
We want to keep PracticeMaster and replace billing. Is that possible?
The two are tied by mirrored client files and only integrate when installed together. Replacing Billing alone breaks the flow of fees from PracticeMaster. If the plan is to split them, the analysis sets out the manual steps that would stand in for the link, and what they cost in staff time.
What happens to conflict searching?
Conflict searching in PracticeMaster reads the fields the firm marked for it, across clients, contacts and linked documents. After the move, searches run in the new system over the migrated contacts and matters. Names that lived only in free text or old documents are worth a check, since they may not be indexed the same way.
Do documents from PracticeMaster keep their folders and dates in SmartAdvocate?
SmartAdvocate stores documents. Documents page, by category and subcategory. Each file is placed under the client and matter it came from, and created and modified dates are carried, so a document still shows when it was written. The trial load is checked by count and by opening a sample.
Does everything in PracticeMaster have a place in SmartAdvocate?
On paper, yes: each kind of record PracticeMaster holds has a place in SmartAdvocate. Whether every field fits is a separate question, and the analysis answers it field by field. Anything with no place comes across as a note or stays behind, and you see which before the move.
What has to be decided before PracticeMaster data is loaded into SmartAdvocate?
Custom fields and templates are carried with mapping, so each mapping is agreed with you first. The firm also sets the cutover date and how much financial history comes across as live records.
Other routes
Other routes from PracticeMaster and into SmartAdvocate
Other destinations from PracticeMaster
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.
PracticeMaster and SmartAdvocate are the names and marks of their owners, used here only to identify the two systems.
Moving from PracticeMaster to SmartAdvocate?
Tell us what you are moving. You get a plan and a fixed price after the analysis.
We reply within one business day.