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

Data migration route

Filevine to SmartAdvocate migration

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

FromFilevineCloud
  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
  14. Firm accounts: Confirmed in the analysis
ToSmartAdvocateCloud
  • 9 carried
  • 3 mapped
  • 2 to confirm
What the two products hold. The analysis confirms it field by field.

What moves

What moves from Filevine to SmartAdvocate

Each row is a kind of record Filevine 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 two kinds are confirmed in the analysis.

Records in Filevine and their place in SmartAdvocate
RecordIn FilevineIn SmartAdvocateWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldCalled projects. Each has a project type, a phase and sections.Has a placeCases by case type, with master and member relationships.Carried across
ContactsClients, other parties and referrersHeldContact cards, collected on each project’s Contacts section.Has a placeCarried across
DocumentsFiles stored in or linked from the systemHeldDocs section per project, with folders, named versions and searchable text.Has a placeDocuments page, by category and subcategory.Carried across
EmailsEmails saved to matters or to the storeHeldProject emails are stored in the activity feed.Has a placeEmails are attached to cases.Carried across
NotesFile notes, matter notes and contact notesHeldNotes are posted to the activity feed.Has a placeCarried across
CalendarAppointments, court dates and deadlinesHeldDeadlines, deadline chains and project calendars.Has a placeAppointments and critical deadlines.Carried across
TasksTo-dos and workflow steps assigned to peopleHeldTasks in the activity feed. Phases can create auto-tasks.Has a placeCarried across
Time and expensesTime and expense entries, billed and unbilledHeld in partTimekeeping is part of Billing, which must be enabled for the firm.Has a placeTracked time entries.Carried across
BillingInvoices, payments and debtor balancesHeld in partInvoices and payments through the Billing and Payments products.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 balancesHeld in partPayments by Filevine includes trust accounts and a trust reconciliation report.To 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 itselfHeldCustom sections and fields are built in the Customs Editor.Has a place in partConfirmed in the analysis for each field with no standard home.Carried with mapping
TemplatesPrecedents, document templates and automationHeldDocument generation templates that fill from project data.Has a place in partTemplates are rebuilt with SmartAdvocate merge codes.Carried with mapping
IntakeLeads, enquiries, intake forms and pipelinesHeld in partLeads and intake are handled by Lead Docket, a separate Filevine product.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 Filevine.
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

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

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

Where the data is now

No two Filevine set-ups are alike, because each firm designs its own project types and sections. A move off it starts by reading that design: every section, every field, and how many projects actually use them. Much of the firm’s history is in the activity feed as a single stream, and the plan has to say what happens to that.

  1. Sections are the data model

    Static sections hold one set of fields per project. Collection sections hold many items, each with its own fields, such as a row per medical provider. They extract as separate tables. Each one is mapped to a destination record, a set of custom fields or a document, and the firm sees which before the trial load.

  2. The activity feed

    Notes, emails, texts, faxes, reminders and tasks all live in one feed per project, and firms tag them with hashtags. Most systems keep those things in different places. Items are split by type on the way out, so emails become emails and tasks become tasks, with the original date and author kept on each.

  3. Phases and auto-tasks

    A project’s phase can trigger automatic tasks through taskflows. The phase itself maps to a status or stage. Automation does not move, and open auto-tasks are loaded as plain tasks so work in progress still shows on someone’s list. Workflows are then rebuilt in the destination from the firm’s own list of what each phase should trigger.

  4. Archived projects still exist

    Projects cannot be deleted, only moved to the Archived phase, where they drop out of searches and reports unless specifically included. An extract that follows the default view will miss them. Archived projects are counted on their own, and the firm decides how many years of them the new system should hold.

  5. Hashtags instead of folders

    Many firms organise documents and notes with hashtags as much as with folders. A destination built on folders or categories has nowhere obvious for a tag. The most used tags are listed with counts, and each becomes a folder, a document category or text in the name, so a search for it still finds the item.

More about moving off Filevine

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

  1. Analysis

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

  4. Cutover

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

Filevine to SmartAdvocate: what firms ask

Can we take our custom sections with us when we leave?

The data in them, yes. Every static and collection section extracts as fields and rows. The section design itself belongs to Filevine and has to be recreated in whatever the destination offers. Sections that hold only a handful of records are usually better turned into notes than rebuilt.

What happens to everything in the activity feed?

It is separated by type. Notes become file notes, emails become emails where the destination stores them, texts become notes or a transcript, and tasks become tasks. Dates and authors are kept, and hashtags are carried in the text. The count of feed items per project is checked against the load, and any shortfall is listed.

We are moving to Filevine. Do matter numbers carry over?

The old matter number can be kept on the project, in the project name, a number field or both, so that paper files and old correspondence still match. Filevine also gives each project its own ID. Staff are told which number to quote, and searches are tested for the old one.

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

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 SmartAdvocate is kept as a readable archive, and you see which before the move.

What has to be decided before Filevine 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 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

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

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