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

Data migration route

eBillity to Filevine migration

eBillity is a cloud accounting and billing system, and Filevine is a cloud case management system. Only part of what eBillity holds has a place in a case file: clients and jobs move, and the table shows how much of the billing side does.

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

What moves

What moves from eBillity to Filevine

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

Records in eBillity and their place in Filevine
RecordIn eBillityIn FilevineWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldLawBillity tracks time and expenses against clients and matters.Has a placeLoaded as projects of a defined project type.Carried across
ContactsClients, other parties and referrersHeld in partClients and their billing details.Has a placeContact cards, linked to projects.Carried across
DocumentsFiles stored in or linked from the systemHeld in partReceipt images attached to expense entries and invoices.Has a placeDocs section with folders. Templated project folders can be set per type.Carried across
EmailsEmails saved to matters or to the storeTo be confirmedHas a placeHeld in the activity feed of the project.Confirmed in the analysis
NotesFile notes, matter notes and contact notesTo be confirmedHas a placeHeld as notes in the activity feed.Confirmed in the analysis
CalendarAppointments, court dates and deadlinesHeld in partCalendar entries can be converted into time entries.Has a placeDeadlines and calendar events.Carried across
TasksTo-dos and workflow steps assigned to peopleTo be confirmedHas a placeConfirmed in the analysis
Time and expensesTime and expense entries, billed and unbilledHeldTimers, weekly timesheets and expenses, approved before billing.Has a place in partNeeds the Billing product enabled.Carried with mapping
BillingInvoices, payments and debtor balancesHeldInvoices, LEDES billing and online payments through LawPay or Stripe.Has a place in partNeeds the Billing product enabled.Carried with mapping
Trust moneyTrust or client account ledgers and balancesHeld in partIn LawBillity only: client trust funds managed beside billing.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 confirmedHas a placeCustom sections and fields per project type.Confirmed in the analysis
TemplatesPrecedents, document templates and automationTo be confirmedHas a place in partTemplates are rebuilt as Filevine document templates. They are not converted.Confirmed in the analysis
IntakeLeads, enquiries, intake forms and pipelinesTo be confirmedHas a place in partLeads belong in Lead Docket, which passes signed clients to Filevine.Confirmed in the analysis

What the plans mean

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

Clients and jobs move. The books stay books.

An accounting or billing system and a case management system overlap less than firms expect. eBillity knows clients, jobs, time and invoices. Filevine knows cases, parties, documents and deadlines. The client list moves well, and jobs can seed the case list. Time and invoice history has a place only where the case system has a billing side, and the table above shows whether this one does. A general ledger does not belong in a case system.

So the plan has two halves. Records with a place in Filevine are loaded and checked there. The rest is exported from eBillity as reports and ledgers that open without it, and the firm decides where its accounts run from then on. If eBillity is staying as the accounting system, nothing financial needs to move at all, and the job is to line up client and case numbers so the two can be reconciled.

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

Where the data is now

A LawBillity account holds the firm’s time, expenses, invoices and, where it was used, trust balances, under a list of clients and matters. It does not hold the firm’s books, which are in QuickBooks or another package beside it. A move is mostly about carrying unbilled time and unpaid invoices across correctly and keeping the link to the accounting package intact.

  1. Which eBillity product

    The company sells general Time Tracker plans as well as LawBillity, and a firm may be on either. Those general plans track time for payroll, projects and client invoicing. Only LawBillity is described as having matters, UTBMS codes and trust, so the plan decides what records exist to move.

  2. Billing lives apart from books

    Invoices and payments are raised in LawBillity and synchronised to QuickBooks. Two systems therefore hold a version of each invoice. Before cutover the two are agreed to each other, so the receivables loaded into the new system match what the accounting package already says the firm is owed.

  3. Receipts on expense entries

    Staff can photograph a receipt and attach it to an expense entry, and the image can be attached to the invoice. These are easy to overlook because the product is not thought of as holding documents. They are collected with their expense entries so the evidence for a disbursement is not lost.

  4. Trust in LawBillity

    LawBillity manages client trust funds alongside billing. Each client’s trust balance is listed with its history and agreed to the trust bank statement at the cutover date. If the firm also tracked trust in QuickBooks, the two records are compared first and any difference is explained before either is loaded.

More about moving off eBillity

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

  4. Cutover

    Changes in eBillity 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. eBillity 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 eBillity 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 fromeBillity
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 eBillity 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

eBillity to Filevine: what firms ask

Does our unbilled time come across?

Time and expense entries that have not been invoiced are read with their date, person, matter, service item, description and rate. They are loaded as unbilled entries where the new system accepts them. A final billing round in LawBillity before cutover means less work in progress has to be carried.

We also use QuickBooks with it. Does that change?

QuickBooks stays where it is unless the firm is replacing it too. What changes is the connection: the new practice system has to post invoices and payments to the same QuickBooks company in place of LawBillity. The switch is timed so no invoice is posted twice or missed.

Can we keep our invoice numbers?

Invoice numbers belong to the invoice record, and where the LawBillity data supplies them they are kept on each historical invoice brought across. The new system’s next number is then set above the highest LawBillity number so the sequence continues, provided the destination allows the starting number to be set. That is checked in the analysis.

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

Most of it does on paper. Emails, notes, tasks, custom fields, templates and intake records 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 eBillity data is loaded into Filevine?

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

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

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