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

Data migration route

SmartAdvocate to Litify migration

SmartAdvocate is a cloud case management system for personal injury work. Litify is a case management system, run the same way. The records line up case for case, and the detail is in the fields and stages.

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

What moves

What moves from SmartAdvocate to Litify

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

Records in SmartAdvocate and their place in Litify
RecordIn SmartAdvocateIn LitifyWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldCases, with master and member cases for mass tort and class action work.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 systemHeldDocuments page with categories, subcategories and custom folder views.Has a placeLoaded to the document component and attached to matters.Carried across
EmailsEmails saved to matters or to the storeHeldThe Outlook plugin attaches emails and their attachments to cases.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 notesHeldCase notes.To be confirmedConfirmed in the analysis
CalendarAppointments, court dates and deadlinesHeldA Case Calendar and an Office Calendar. Critical deadlines sync to Outlook.Has a placeCalendar events on the matter.Carried across
TasksTo-dos and workflow steps assigned to peopleHeldTasks created by WorkPlans and Automated Procedures.Has a placeCarried across
Time and expensesTime and expense entries, billed and unbilledHeldTime tracking, including from the mobile apps.Has a placeTime entries on the matter.Carried across
BillingInvoices, payments and debtor balancesHeld in partBuilt-in invoicing for hourly matters, from expenses and time entries.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 balancesTo be confirmedTo be confirmedConfirmed in the analysis
Firm accountsGeneral ledger, office account and payablesTo be confirmedTo be confirmedConfirmed in the analysis
Custom fieldsFields and record types the firm added itselfHeldDescribed as fully customisable, with custom merge codes and plaintiff fact sheets.Has a placeCustom fields are created before loading.Carried with mapping
TemplatesPrecedents, document templates and automationHeldWord, Excel and PDF templates filled from thousands of merge codes.Has a place in partTemplates are rebuilt in Litify’s document generation.Carried with mapping
IntakeLeads, enquiries, intake forms and pipelinesHeldBuilt-in intake and lead management.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 SmartAdvocate.
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

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. SmartAdvocate and Litify 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 Litify, 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.

Both are hosted by their makers, so nothing is collected from the firm’s office. What can be taken out of SmartAdvocate 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 SmartAdvocate is kept running until the checks on Litify are finished.

Where the data is now

SmartAdvocate holds a great deal of structured detail on each case, and leaving it is mostly a question of what the destination can receive. The edition matters for the mechanics. A Server firm has the database and document store on its own equipment. A Cloud firm arranges a copy through its hosted service. The content is the same either way.

  1. Server or Cloud edition

    With the Server edition the firm owns the installation, so a backup of the database and of the document and image storage can be taken on site. On the Cloud edition the vendor hosts both. Which edition the firm has is the first thing established, since it decides how the copy for the trial load is obtained.

  2. Master and member cases

    Mass tort and class action work is held as a master case with member cases related to it, and plaintiff fact sheets record the criteria for each litigation. Member cases are loaded as individual matters. The relationship and the fact sheet answers need an agreed home, or the firm loses the ability to report across a litigation.

  3. WorkPlans in progress

    A WorkPlan is a checklist that also automates steps, and Automated Procedures send reminders, texts, emails and generated documents. On an open case some items are done and some are pending. Pending items are loaded as tasks with due dates. The automation is rebuilt in the destination’s workflow tool from the WorkPlan definitions.

  4. Merge codes in templates

    Templates are Word, Excel or PDF files containing merge codes, including table codes that pull in lists of providers, bills, liens and expenses. The codes mean nothing outside SmartAdvocate. Template wording is kept and coded again for the new system, and list-style merges are tested early because not every system can produce them.

  5. Emails filed through Outlook

    The Outlook plugin files emails to the case and saves attachments to the documents page. Email is therefore part of the case record, and usually a large part. It is extracted with sender, recipients and date, and attachments already saved as documents are not loaded a second time.

More about moving off SmartAdvocate

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

  1. Analysis

    We read what SmartAdvocate 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 SmartAdvocate, 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 SmartAdvocate: record counts, financial totals, the links between records, document dates. Exceptions are listed for you to decide.

  4. Cutover

    Changes in SmartAdvocate 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 SmartAdvocate as at the cutover date. SmartAdvocate 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 SmartAdvocate 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 fromSmartAdvocate
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 SmartAdvocate 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

SmartAdvocate to Litify: what firms ask

Is SmartAdvocate cloud or on-premise?

Both exist. The Cloud edition is hosted by the vendor, and the Server edition is installed on the firm’s own server and maintained by the firm’s IT. Either way staff use it in a browser, and there are phone and tablet apps. A firm can tell which it has by who takes the backups.

Can our WorkPlans be migrated?

Yes for the open items, which load as tasks. The WorkPlan itself is SmartAdvocate automation and has to be recreated in the destination’s own workflow tool. Its definitions are documented step by step for that purpose, and the firm is asked which plans are still followed, because some will not have been touched in years.

We are moving to SmartAdvocate. What should we clean first?

Contacts and statuses. Duplicate providers and insurers multiply once they are attached to cases, and vague statuses cannot be translated to case stages. Merging the obvious duplicates and closing cases that are really finished, in the old system before extraction, costs far less than correcting them after the load.

Do trust balances in SmartAdvocate 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 SmartAdvocate 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 SmartAdvocate have a place in Litify?

Most of it does on paper. Notes, trust ledgers and the firm’s accounts 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 SmartAdvocate data is loaded into Litify?

Emails, billing records, custom fields and templates are carried with mapping, so each mapping is agreed with you first. Notes, trust ledgers and the firm’s accounts 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

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

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