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

Data migration route

AdvoLogix to SmartAdvocate migration

AdvoLogix is a cloud practice management system, and SmartAdvocate is a cloud case management system for personal injury work. Matter records move into cases, and the firm decides where its accounting runs from the cutover date.

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

What moves

What moves from AdvoLogix to SmartAdvocate

Each row is a kind of record AdvoLogix holds, whether SmartAdvocate has a place for it, and what is planned. On this route nine kinds of record carry across, three kinds need mapping and one kind is confirmed in the analysis.

Records in AdvoLogix and their place in SmartAdvocate
RecordIn AdvoLogixIn SmartAdvocateWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldMatters are the central record, with stage, status and a closed flag.Has a placeCases by case type, with master and member relationships.Carried across
ContactsClients, other parties and referrersHeldSalesforce accounts and contacts, linked to matters as participants with roles.Has a placeCarried across
DocumentsFiles stored in or linked from the systemHeldSalesforce files on the matter, or a linked NetDocuments, iManage, SharePoint or Google Drive store.Has a placeDocuments page, by category and subcategory.Carried across
EmailsEmails saved to matters or to the storeHeld in partEmails sent from a matter are logged. Mailbox filing depends on an email integration.Has a placeEmails are attached to cases.Carried across
NotesFile notes, matter notes and contact notesHeldComments recorded against the matter.Has a placeCarried across
CalendarAppointments, court dates and deadlinesHeldA Matter Calendar, with date calculation rules.Has a placeAppointments and critical deadlines.Carried across
TasksTo-dos and workflow steps assigned to peopleHeldActivity plans and task checklists generate tasks on a matter.Has a placeCarried across
Time and expensesTime and expense entries, billed and unbilledHeldTime entries with timekeepers, rate groups and UTBMS codes. Expenses are tracked too.Has a placeTracked time entries.Carried across
BillingInvoices, payments and debtor balancesHeld in partTime, expenses and fees become billings, split between billing parties.Has a place in partInvoices for hourly matters. Past invoices are scoped in the analysis.Carried with mapping
Trust moneyTrust or client account ledgers and balancesTo be confirmedTo be confirmedConfirmed in the analysis
Custom fieldsFields and record types the firm added itselfHeldCustom fields are added to matters and participants through Salesforce set-up.Has a place in partConfirmed in the analysis for each field with no standard home.Carried with mapping
TemplatesPrecedents, document templates and automationHeldAdvoDoc document assembly templates. A HotDocs integration is also listed.Has a place in partTemplates are rebuilt with SmartAdvocate merge codes.Carried with mapping
IntakeLeads, enquiries, intake forms and pipelinesHeldIntake records and intake forms, converted to matters.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 AdvoLogix.
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.
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 SmartAdvocate. 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 AdvoLogix has to be given a case type in SmartAdvocate, and that choice drives which fields and workflows it gets. The mapping is agreed type by type. Financial history with no place in SmartAdvocate is exported as reports and ledgers the firm can open without AdvoLogix, 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 AdvoLogix 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 AdvoLogix is kept running until the checks on SmartAdvocate are finished.

Where the data is now

A move off AdvoLogix is a move out of a Salesforce org. The matter data is spread across the vendor’s packaged objects, standard Salesforce objects and whatever the firm’s administrator added over the years. An inventory of that org comes first: which objects hold live data, which fields are the firm’s own, and where the documents physically are.

  1. Participants carry the relationships

    A client, an opposing party or an expert is a Salesforce account or contact joined to the matter by a participant record with a role. Some participants are typed in as free text with no contact behind them. Both kinds are extracted, and the free-text ones are matched to real contacts or created as new ones before loading.

  2. Documents may sit elsewhere

    Files can be held as Salesforce files on the matter, or in NetDocuments, iManage, SharePoint or Google Drive through an integration. Many orgs have a mix, with older matters in one place and newer ones in another. Each matter is checked for where its files are before any document count is agreed.

  3. Billings are derived records

    Time and expense entries generate billing records, which can be split between billing parties and edited without changing the source entry. The two can therefore disagree by design. Which one is the record of truth for unbilled work is decided in the analysis, and totals are reconciled per matter against that choice.

  4. Every org is configured differently

    Matter stages, statuses, page layouts and automation are set by each firm’s Salesforce administrator. Two firms on the same product rarely share a field list. The mapping is written from the firm’s own org, including fields nobody remembers adding, and unused ones are listed for the firm to drop.

  5. Where the books are kept

    The help centre describes no ledger inside the matter application. An integration with Accounting Seed, a separate Salesforce application with its own objects, is offered for firms that keep their books on the platform. If the destination has built-in accounting, opening balances are taken from wherever the books were actually kept, not from the matter records.

More about moving off AdvoLogix

Where it is going

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.

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

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

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

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

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

More about moving into SmartAdvocate

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 AdvoLogix and checking each trial against AdvoLogix.

  1. Analysis

    We read what AdvoLogix 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.

  2. Clean-up

    Duplicate contacts and matters are merged where they can be identified, and inconsistent entries are put into one format, in AdvoLogix, before extraction. It is not always possible to find every one, so some may carry across.

  3. Trial load

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

  4. Cutover

    Changes in AdvoLogix 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 AdvoLogix as at the cutover date. AdvoLogix 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 AdvoLogix 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 fromAdvoLogix
Moving toSmartAdvocate

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

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

AdvoLogix to SmartAdvocate: what firms ask

Is AdvoLogix the same thing as Mitratech CaseCloud?

For practical purposes, yes. Mitratech introduced CaseCloud in November 2024 and describes it as built on Salesforce and AdvoLogix technologies. The help centre and many of the component names still say AdvoLogix. A firm that installed the product under the old name is holding the same kind of data in the same kind of org.

Do we lose our Salesforce history if we leave?

Salesforce keeps field history only where tracking was switched on, so what exists varies by org. Emails, tasks and events logged on a matter can be extracted with it. Field-level change history usually has no equivalent in a legal system, and it either comes across as a note or stays behind.

Can our time entries and rates come across?

Time entries, timekeepers and UTBMS codes are structured records with fields of their own. Rates are harder, because they are held in rate groups applied to matters and can be changed on a single matter. The analysis lists the rate that actually applied to each matter, so unbilled time is valued the same way after the move.

Do trust balances in AdvoLogix have a place in SmartAdvocate?

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

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

What has to be decided before AdvoLogix data is loaded into SmartAdvocate?

Billing records, custom fields and templates are carried with mapping, so each mapping is agreed with you first. Trust ledgers 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

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

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