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

Data migration route

Interbill to Filevine migration

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

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

What moves

What moves from Interbill to Filevine

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

Records in Interbill and their place in Filevine
RecordIn InterbillIn FilevineWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeld in partBilling is kept by client and matter; it is a billing record, not a case file.Has a placeLoaded as projects of a defined project type.Carried across
ContactsClients, other parties and referrersHeld in partClients, as billing records.Has a placeContact cards, linked to projects.Carried across
DocumentsFiles stored in or linked from the systemTo be confirmedHas a placeDocs section with folders. Templated project folders can be set per type.Confirmed in the analysis
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 deadlinesTo be confirmedHas a placeDeadlines and calendar events.Confirmed in the analysis
TasksTo-dos and workflow steps assigned to peopleTo be confirmedHas a placeConfirmed in the analysis
Time and expensesTime and expense entries, billed and unbilledHeldBilling entries, typed with optional description codes.Has a place in partNeeds the Billing product enabled.Carried with mapping
BillingInvoices, payments and debtor balancesHeldMonthly, reminder and retainer statements, late charges, receivables reports.Has a place in partNeeds the Billing product enabled.Carried with mapping
Trust moneyTrust or client account ledgers and balancesHeldTrust and retainer reports and ledgers.Has a place in partTrust accounts sit in Payments by Filevine. Loading history is confirmed in the analysis.Carried with mapping
Firm accountsGeneral ledger, office account and payablesHeld in partAn optional general ledger designed for solo practitioners.To be confirmedConfirmed in the analysis
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 automationHeld in partBilling statements can be customised and carry the firm’s logo.Has a place in partTemplates are rebuilt as Filevine document templates. They are not converted.Carried with mapping
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 Interbill.
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. Interbill 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 Interbill as reports and ledgers that open without it, and the firm decides where its accounts run from then on. If Interbill 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 Interbill 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 Interbill is kept running until the checks on Filevine are finished.

Where the data is now

An Interbill firm has its whole billing history in one place: entries, statements, payments, retainers and trust ledgers, often going back many years. It is a billing record, not a case file. The work is in turning statement-based billing into the invoices and ledgers of a practice system, and in carrying each client’s balance across to the cent.

  1. Statements, not single invoices

    Billing is built on monthly statements that show history, payments and a running balance, with reminder statements for overdue accounts. A practice system usually thinks in separate invoices. Each client’s balance is broken into the bills that make it up, or loaded as one opening balance where the detail is not needed.

  2. Evergreen and instalment arrangements

    Interbill supports evergreen retainer billing, instalment billing and client payment plans. These are ongoing arrangements with their own schedule and wording on the statement. Each active one is listed with its terms so it can be set up again in the destination before the next payment falls due.

  3. Trust and retainer ledgers

    Trust and retainer reports and ledgers are part of the billing reports. Every client ledger is printed as at the cutover date and agreed to the trust bank statement. Retainers that are the firm’s money once billed and those that are client money are separated, because they open in different ledgers.

  4. Description codes and late charges

    Entries can be typed with description codes that stand for standard wording, and late payment charges can be switched on by client. The codes are matched to activity codes in the new system. Late charges already billed stay on the balance. Whether they continue is a setting the firm chooses again.

  5. Your own backup copy

    Interbill says a firm can download a backup of all its online data to its own computer. That download is the natural starting point for analysis and for the fall-back record, since it can be taken on the cutover day itself and kept by the firm without depending on a login.

More about moving off Interbill

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

  4. Cutover

    Changes in Interbill 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. Interbill 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 Interbill 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 fromInterbill
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 Interbill 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

Interbill to Filevine: what firms ask

Can ten years of billing history come with us?

It can be read. Whether it should all be loaded is another matter. Open clients come across with enough history to explain their balance. For closed matters the Interbill backup can serve as the record, with only what the new system needs for conflict searches loaded.

How are client balances checked?

Each client’s receivable, retainer and trust balance in the new system is compared with the Interbill reports run on the cutover date. The totals have to agree, and so does every individual client. Differences are listed for the firm to decide before the new system is used for billing.

We use the Interbill general ledger. Does that move?

The ledger is a separate question from billing. If the new practice system has no general ledger, the firm needs an accounting package, and the closing balances from Interbill become its opening balances. The income tax figures the ledger reports are kept for the year in progress.

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

Most of it does on paper. Documents, emails, notes, calendar entries, tasks, the firm’s accounts, custom fields 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 Interbill data is loaded into Filevine?

Time entries, billing records, trust ledgers and templates are carried with mapping, so each mapping is agreed with you first. Documents, emails, notes, calendar entries, tasks, the firm’s accounts, custom fields 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

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

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