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

Data migration route

CasePeer to Filevine migration

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

FromCasePeerCloud
  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. Trust money: Carried with mapping
  10. Templates: Carried with mapping
  11. Intake: Carried with mapping
  12. Billing: Confirmed in the analysis
  13. Custom fields: Confirmed in the analysis
ToFilevineCloud
  • 7 carried
  • 4 mapped
  • 2 to confirm
What the two products hold. The analysis confirms it field by field.

What moves

What moves from CasePeer to Filevine

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

Records in CasePeer and their place in Filevine
RecordIn CasePeerIn FilevineWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldPersonal injury cases with statutes, status and links to connected cases.Has a placeLoaded as projects of a defined project type.Carried across
ContactsClients, other parties and referrersHeldClients, defendants, insurers, providers and referral sources.Has a placeContact cards, linked to projects.Carried across
DocumentsFiles stored in or linked from the systemHeldUnlimited storage, a mail centre for incoming post, and Dropbox or OneDrive links.Has a placeDocs section with folders. Templated project folders can be set per type.Carried across
EmailsEmails saved to matters or to the storeHeld in partText and email messages with clients are tied to the case.Has a placeHeld in the activity feed of the project.Carried across
NotesFile notes, matter notes and contact notesHeldCase notes, including notes written automatically by workflows.Has a placeHeld as notes in the activity feed.Carried across
CalendarAppointments, court dates and deadlinesHeldEvents, statutes and litigation event plans. Syncs to Outlook, Google or iCal.Has a placeDeadlines and calendar events.Carried across
TasksTo-dos and workflow steps assigned to peopleHeldTask manager with workflows triggered by case status, age or client details.Has a placeCarried across
Time and expensesTime and expense entries, billed and unbilledHeld in partTime logging is built in. The product is designed for contingency fee work.Has a place in partNeeds the Billing product enabled.Carried with mapping
BillingInvoices, payments and debtor balancesTo be confirmedClient payments are taken through LawPay. Invoicing was not confirmed.Has a place in partNeeds the Billing product enabled.Confirmed in the analysis
Trust moneyTrust or client account ledgers and balancesHeld in partClient trust tracking by case. Trust accounting itself runs in a linked package.Has a place in partTrust accounts sit in Payments by Filevine. Loading history is confirmed in the analysis.Carried with mapping
Custom fieldsFields and record types the firm added itselfTo be confirmedSold as pre-configured. How far fields can be added was not confirmed.Has a placeCustom sections and fields per project type.Confirmed in the analysis
TemplatesPrecedents, document templates and automationHeldDocument automation from case data.Has a place in partTemplates are rebuilt as Filevine document templates. They are not converted.Carried with mapping
IntakeLeads, enquiries, intake forms and pipelinesHeldIntake manager with forms, checklists and conversion reporting.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 CasePeer.
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. CasePeer 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 CasePeer 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 CasePeer is kept running until the checks on Filevine are finished.

Where the data is now

CasePeer holds an injury case in a fixed shape that suits the work: treatment, bills, liens, costs and settlement each have their own place. Leaving it means finding where each of those sits in the destination. A system built for injury work will have most of them. A general system needs fields or record types set up first.

  1. Treatment and medical bills

    Each provider on a case carries treatment, billed amounts and the status of the requests made for records and bills. This is the bulk of the structured data and the part clients ring about. It is mapped provider by provider, and billed totals per case are compared after the trial load, since they feed the demand.

  2. Liens and settlement distribution

    Liens are tracked against the case, and the settlement figures work out fees, costs, lien payments and the client’s net. For settled cases the final distribution is a record the firm must be able to produce later. It is carried as data where the destination can hold it, and otherwise as a saved statement on the case.

  3. Cost requests and accounting

    Staff raise cost requests in CasePeer and the payment itself is made in the accounting package. The cost history on a case therefore depends on that link having been used consistently. Case cost totals are reconciled to the accounting package before cutover, so the amount recovered at settlement is the amount actually spent.

  4. Client trust tracking

    The product tracks client trust money by case. Those balances are compared with the firm’s bank and accounting records before any figure is loaded into a new trust ledger. Because a trust cutover cannot be run again like a document load, it is rehearsed on a full trial load first.

  5. Mail centre and flagged documents

    Incoming post is sorted through a mail centre, and documents can be flagged for review. Items still waiting in that queue at cutover belong to no finished process in the new system. The queue is cleared or listed during the freeze window, so nothing sits unread in the old one.

More about moving off CasePeer

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.

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

  1. Analysis

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

  4. Cutover

    Changes in CasePeer are frozen for an agreed window, the data is collected a final time and Filevine 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. CasePeer 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 CasePeer 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 fromCasePeer
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 CasePeer 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

CasePeer to Filevine: what firms ask

Is CASEpeer the same product as 8am CasePeer?

Yes. The product was written CASEpeer for years, and its owner now brands it 8am CasePeer alongside 8am MyCase, LawPay and DocketWise. Nothing about what the system stores changed with the rename. A firm that knows it under any of these names is using the same personal injury system.

Can our treatment and lien data go into a general practice system?

It can, but someone has to build the place for it first. General systems hold parties and documents well and usually have nothing for provider visits, bills and lien balances. Custom fields or record types are set up at the analysis stage, and where the destination cannot hold a table of bills, a schedule is saved to the case.

What happens to leads that never became cases?

Leads in the intake manager are separate from cases. Declined and unconverted leads can move to the new system’s intake module if it has one, be loaded as contacts with a note, or be left in an export. Referral sources are kept in every option, because the marketing reports depend on them.

Do trust balances in CasePeer have a place in Filevine?

In part. Trust accounts sit in Payments by Filevine. Loading history is confirmed in the analysis. The analysis sets out which trust records have a place in Filevine 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 CasePeer have a place in Filevine?

Most of it does on paper. Billing records and custom fields 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 CasePeer data is loaded into Filevine?

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

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

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