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

Data migration route

Filevine to SimpleLaw migration

Filevine is a cloud case management system, and SimpleLaw is a cloud practice management system. Case records move into matters, and time, billing and trust are set up in SimpleLaw, often from a separate accounts package.

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

What moves

What moves from Filevine to SimpleLaw

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

Records in Filevine and their place in SimpleLaw
RecordIn FilevineIn SimpleLawWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldCalled projects. Each has a project type, a phase and sections.Has a placeCarried across
ContactsClients, other parties and referrersHeldContact cards, collected on each project’s Contacts section.Has a placeAs leads, clients or other contacts in the CRM.Carried across
DocumentsFiles stored in or linked from the systemHeldDocs section per project, with folders, named versions and searchable text.Has a placeUploaded to SimpleLaw storage or held in a linked Dropbox, Google Drive or OneDrive.Carried across
EmailsEmails saved to matters or to the storeHeldProject emails are stored in the activity feed.To be confirmedConfirmed in the analysis
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 placeCarried 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 placeCarried across
BillingInvoices, payments and debtor balancesHeld in partInvoices and payments through the Billing and Payments products.Has a place in partInvoices are created in the product; loading invoice history is confirmed 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.Has a place in partTrust balances are supported; history depth is confirmed in the analysis.Carried with mapping
Firm accountsGeneral ledger, office account and payablesTo be confirmedNo placeGeneral ledger stays in QuickBooks or another accounting package.Confirmed in the analysis
Custom fieldsFields and record types the firm added itselfHeldCustom sections and fields are built in the Customs Editor.Has a placeCarried with mapping
TemplatesPrecedents, document templates and automationHeldDocument generation templates that fill from project data.Has a place in partTemplates are rebuilt using SimpleLaw’s own automation.Carried with mapping
IntakeLeads, enquiries, intake forms and pipelinesHeld in partLeads and intake are handled by Lead Docket, a separate Filevine product.Has a placeLeads and intake forms.Carried across

What the plans mean

Carried across
SimpleLaw has a place for this kind of record. It is loaded there and checked against Filevine.
Carried with mapping
SimpleLaw 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

Cases come across. The accounts are set up new.

A case management system holds the working file: parties, notes, deadlines, documents and the fields a practice area needs. It is not usually the firm’s ledger, so time, invoices and trust often sit in an accounting package beside it. Moving to SimpleLaw brings those two sources together. The case records come from Filevine. Opening balances for debtors and trust, where they move at all, come from the accounts package and are agreed to its reports.

Case systems are heavy with custom fields, and that is where the mapping work is. A personal injury or immigration file can carry dozens of fields that a general practice system has no standard place for. Each one is matched to a field in SimpleLaw, created there as a custom field, or written into a note on the matter. The firm sees which before the load. Workflows and task templates are rebuilt, not copied.

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

Loading a firm into SimpleLaw is mostly a job of sorting contacts and setting up each matter’s billing type. The CRM holds leads, clients and everyone else, so every incoming contact needs a status. Where documents will be stored is decided early as well, since that choice determines where the files are sent. Accounting history stays in QuickBooks or the old system.

  1. Lead, client or contact

    A person is tracked from first enquiry to client in one CRM, with tasks and appointments kept against the contact. Source systems that only ever held clients load simply. Systems with separate intake records need each enquiry classed as a live lead, a lost one or a duplicate of an existing client.

  2. Billing type on each matter

    Every matter is billed as hourly, flat fee, instalments, contingency, pro bono, trust or LEDES. The source may record this loosely or not at all. During the trial load a billing type is set on each matter and checked by the person who raises the bills, because it controls how the invoice is built.

  3. Storage chosen before loading

    If the firm stores documents with SimpleLaw, files are uploaded against each matter. Where it prefers Dropbox, Google Drive or OneDrive, the files go there, and what the connection does with folders already in place is checked first. Switching later means moving everything again, so the choice is made at the start with the firm’s IT support.

  4. Custom fields named for templates

    Custom fields supply intake forms and document automation as well as reports. A field brought across from the old system is only useful if templates can call on it. Fields are therefore named and typed with the firm’s main documents in mind, and one template is tested against loaded data.

  5. Portal access client by client

    The client portal is optional and the firm chooses who has access and what each client can see. Nothing is exposed by loading data. After go-live, access is switched on for chosen clients, starting with a few, once the firm has reviewed what their matters show.

More about moving into SimpleLaw

How NewLaw runs it

Four steps, in this order.

Trust money moves on this route, so the trust cutover gets a rehearsal of its own.

  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 SimpleLaw. 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 SimpleLaw as a trial and checked against Filevine: record counts, trust and debtor 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 SimpleLaw goes live over a weekend. The trust and financial cutover is rehearsed on a full trial load first, because it cannot be re-run the way a document load can. 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 toSimpleLaw

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

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

The set-up work is in making the product reflect the firm. Labels are adjusted to the firm’s terms. Intake forms and the custom fields behind them are built for each practice area, then document templates are made to draw on those fields. Workflows are written for the case types that follow a standard path, and the QuickBooks and payment connections are made last.

Set-up decisions in SimpleLaw

  • Labels for documents, activities, expenses and contact IDs
  • Custom fields and intake forms for each practice area
  • Document templates and the attorney-client agreement
  • Workflows for case types that follow a standard process
  • User permission sets and client portal visibility
  • QuickBooks connection and the online payment processor

Questions

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

In part. Trust balances are supported; history depth is confirmed in the analysis. The analysis sets out which trust records have a place in SimpleLaw and which are kept as an archive, and the trust cutover is rehearsed on a full trial load before the real one.

Does everything in Filevine have a place in SimpleLaw?

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

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

Billing records, trust ledgers, custom fields and templates are carried with mapping, so each mapping is agreed with you first. Emails 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 SimpleLaw are the names and marks of their owners, used here only to identify the two systems.

Moving from Filevine to SimpleLaw?

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

We reply within one business day.