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

Data migration route

SmartAdvocate to Filevine migration

SmartAdvocate is a cloud case management system for personal injury work. Filevine 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. Emails: Carried across
  5. Notes: Carried across
  6. Calendar: Carried across
  7. Tasks: Carried across
  8. Time and expenses: Carried with mapping
  9. Billing: Carried with mapping
  10. Custom fields: Carried with mapping
  11. Templates: Carried with mapping
  12. Intake: Carried with mapping
  13. Trust money: Confirmed in the analysis
  14. Firm accounts: Confirmed in the analysis
ToFilevineCloud
  • 7 carried
  • 5 mapped
  • 2 to confirm
What the two products hold. The analysis confirms it field by field.

What moves

What moves from SmartAdvocate to Filevine

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

Records in SmartAdvocate and their place in Filevine
RecordIn SmartAdvocateIn FilevineWhat 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 placeLoaded as projects of a defined project type.Carried across
ContactsClients, other parties and referrersHeldHas a placeContact cards, linked to projects.Carried across
DocumentsFiles stored in or linked from the systemHeldDocuments page with categories, subcategories and custom folder views.Has a placeDocs section with folders. Templated project folders can be set per type.Carried across
EmailsEmails saved to matters or to the storeHeldThe Outlook plugin attaches emails and their attachments to cases.Has a placeHeld in the activity feed of the project.Carried across
NotesFile notes, matter notes and contact notesHeldCase notes.Has a placeHeld as notes in the activity feed.Carried across
CalendarAppointments, court dates and deadlinesHeldA Case Calendar and an Office Calendar. Critical deadlines sync to Outlook.Has a placeDeadlines and calendar events.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 place in partNeeds the Billing product enabled.Carried with mapping
BillingInvoices, payments and debtor balancesHeld in partBuilt-in invoicing for hourly matters, from expenses and time entries.Has a place in partNeeds the Billing product enabled.Carried with mapping
Trust moneyTrust or client account ledgers and balancesTo be confirmedHas a place in partTrust accounts sit in Payments by Filevine. Loading history is confirmed in the analysis.Confirmed 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 sections and fields per project type.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 as Filevine document templates. They are not converted.Carried with mapping
IntakeLeads, enquiries, intake forms and pipelinesHeldBuilt-in intake and lead management.Has a place in partLeads belong in Lead Docket, which passes signed clients to Filevine.Carried with mapping

What the plans mean

Carried across
Filevine has a place for this kind of record. It is loaded there and checked against SmartAdvocate.
Carried with mapping
Filevine 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 Filevine 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 Filevine, 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 Filevine 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 Filevine depends on the project types being built first. Until the sections and fields exist there is nowhere for the data to go, so configuration and migration are planned together. The old system’s parties, insurers, providers and key dates are mapped to sections, and its notes and emails are loaded into each project’s activity feed.

  1. Project types before data

    Each area of practice needs a project type with its sections, fields and phases defined in the Customs Editor. Changes made there apply to every project of that type. The types are drafted from the old system’s data, tested with a few real cases, and only then is the bulk load run.

  2. One contact card per person

    Contacts are held as contact cards. A doctor or adjuster who appears on many projects is best loaded as one card, not one for each project. Duplicates in the old system are merged before loading where they can be identified. Loading them as they are produces several cards for the same person, and staff then pick the wrong one when adding a party.

  3. Lists become collection items

    Anything the old system held as a list against a matter, such as providers, liens, insurance policies or expenses, is loaded as items in a collection section. Each column needs a matching field. Totals per project are compared with the old system afterwards, since those figures feed the settlement and disbursal sheets.

  4. History goes into the feed

    File notes, emails and completed tasks from the old system are loaded into the activity feed with their original dates and authors. Authors must exist as users or be recorded in the text. The feed is long on an old case, so staff are shown how to filter it before go-live.

  5. Billing is a separate switch

    The Billing section only appears once Billing is enabled for the firm. Time entries, invoices and trust balances from the old system need that in place before they can be loaded. A firm that leaves it off can still record case costs in a collection section built for the purpose.

More about moving into Filevine

How NewLaw runs it

Four steps, in this order.

Financial records move on this route, so the balances are rehearsed before the real cutover.

  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 Filevine. 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 Filevine 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 Filevine 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 toFilevine

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

Loaded data is not yet a working system. This is what NewLaw sets up in Filevine, beyond the migration, so that people can work in it from the first day.

Filevine arrives as a platform to be configured, and most of the implementation is design. Someone has to decide what a project looks like for each kind of work the firm does, what moves it from one phase to the next, and who can see what. Those decisions are made with the people who run the files, then built and tested.

Set-up decisions in Filevine

  • Design project types, sections and fields for each practice area
  • Define phases and the tasks each phase should trigger
  • Build document templates that fill from project fields
  • Set teams, permissions and protected sections for restricted matters
  • Decide whether Billing and Payments are switched on
  • Connect Lead Docket so signed leads become projects

Questions

SmartAdvocate to Filevine: 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 Filevine?

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

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

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

Time entries, billing records, custom fields, templates and intake records are carried with mapping, so each mapping is agreed with you first. 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 Filevine are the names and marks of their owners, used here only to identify the two systems.

Moving from SmartAdvocate to Filevine?

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

We reply within one business day.