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

Data migration route

Interbill to Neos migration

Interbill is a cloud accounting and billing system, and Neos is a cloud case management system for personal injury work. 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. Templates: Carried with mapping
  6. Documents: Confirmed in the analysis
  7. Emails: Confirmed in the analysis
  8. Notes: Confirmed in the analysis
  9. Calendar: Confirmed in the analysis
  10. Tasks: Confirmed in the analysis
  11. Trust money: Confirmed in the analysis
  12. Custom fields: Confirmed in the analysis
  13. Intake: Confirmed in the analysis
ToNeosCloud
  1. Firm accounts: Kept as a readable archive
Readable archiveNo place in Neos
  • 2 carried
  • 3 mapped
  • 8 to confirm
  • 1 archived
What the two products hold. The analysis confirms it field by field.

What moves

What moves from Interbill to Neos

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

Records in Interbill and their place in Neos
RecordIn InterbillIn NeosWhat 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 placeCases by case type.Carried across
ContactsClients, other parties and referrersHeld in partClients, as billing records.Has a placeParties, providers and case contacts. Contacts can be imported from CSV.Carried across
DocumentsFiles stored in or linked from the systemTo be confirmedHas a placeCase Docs tab, organised in sub-tabs.Confirmed in the analysis
EmailsEmails saved to matters or to the storeTo be confirmedHas a place in partEmails tagged to a case are held. Loading old mail is scoped in the analysis.Confirmed in the analysis
NotesFile notes, matter notes and contact notesTo be confirmedHas a placeConfirmed in the analysis
CalendarAppointments, court dates and deadlinesTo be confirmedHas a placeCase calendar entries.Confirmed in the analysis
TasksTo-dos and workflow steps assigned to peopleTo be confirmedHas a placeLoaded as checklist items.Confirmed in the analysis
Time and expensesTime and expense entries, billed and unbilledHeldBilling entries, typed with optional description codes.Has a place in partTime can be held as value items. The treatment of old entries is confirmed in the analysis.Carried with mapping
BillingInvoices, payments and debtor balancesHeldMonthly, reminder and retainer statements, late charges, receivables reports.Has a place in partInvoices exist in Neos. Loading past invoices is confirmed in the analysis.Carried with mapping
Trust moneyTrust or client account ledgers and balancesHeldTrust and retainer reports and ledgers.To be confirmedConfirmed in the analysis
Firm accountsGeneral ledger, office account and payablesHeld in partAn optional general ledger designed for solo practitioners.No placeThe general ledger stays in QuickBooks.Kept as a readable archive
Custom fieldsFields and record types the firm added itselfTo be confirmedHas a placeUser-defined fields are created on the relevant tab first.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 for Neos document generation.Carried with mapping
IntakeLeads, enquiries, intake forms and pipelinesTo be confirmedHas a placeIntakes tab. Simple intake imports from CSV are supported.Confirmed in the analysis

What the plans mean

Carried across
Neos has a place for this kind of record. It is loaded there and checked against Interbill.
Carried with mapping
Neos 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.
Kept as a readable archive
Neos has no place for it. It is exported in a format that opens without Interbill and handed to the firm as a read-only archive.

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

Neos expects personal injury data in its own tab structure, so loading a firm means deciding which tab each old record belongs on. Parties, insurance and counsel map directly from most injury systems. Money maps to value items. Anything the standard tabs lack becomes a user-defined field, which has to be created before the load.

  1. Every figure needs a value code

    Costs, medical bills, fees and settlement amounts are loaded as value items, and each carries a value code. The code list is agreed with the firm’s accounts staff first. A figure loaded under the wrong code is reported in the wrong place, so the list is tested on real cases before the bulk load.

  2. Lists are set up first

    Cases are loaded against case types, statuses and staff assignments that already exist in Neos. Those lists are set up, and the old system’s values tidied to match, before the trial load. Misspelt attorney names and unused case types in the source are cleaned out at the same stage.

  3. Documents go to sub-tabs

    Files land on the Case Docs tab under sub-tabs, which staff can view as a list or as folders. The old system’s folders or categories are mapped to a fixed set of sub-tabs. Without that, every personal habit of naming folders is reproduced and the folder view becomes hard to read.

  4. Reminders split two ways

    Neos fills its dashboards from checklists and case calendars. Old diary entries and tasks are sorted between them: dated appointments and court events to the calendar, and to-dos to the checklist. An item assigned to several people in the old system may need one named owner, and the firm chooses who.

  5. Assembly runs its own conversions

    Assembly migrates firms into Neos with its own team and tooling, and offers routes from self-service templates to a full conversion. Where the firm uses that service, outside help goes on the work around it: cleaning the source, checking the converted cases against the old system, and listing exceptions.

More about moving into Neos

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

  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 Neos. 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 Neos as a trial and checked against Interbill: record counts, financial 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 Neos 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 Interbill as at the cutover date. 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 toNeos

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

Loaded data is not yet a working system. The maker of Neos runs or arranges the set-up of its product, so this is what has to be decided and put in place in Neos, whoever does the work, before people rely on it from the first day.

Neos comes set up for injury work, so implementation is mostly choosing among its options and connecting the firm’s other tools. The lists that drive reporting are decided first, then checklists, then documents. Assembly provides its own implementation team, and the firm’s internal lead still has to make the decisions listed below.

Set-up decisions in Neos

  • Set case types, statuses and staff roles
  • Agree the value code list with accounts staff
  • Build checklists for each case type and stage
  • Create user-defined fields for data the tabs lack
  • Prepare document templates for the generation wizard
  • Connect Microsoft 365, QuickBooks and the phone system

Questions

Interbill to Neos: 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 Neos?

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 Interbill before the plan is fixed. If Neos turns out to have no place for trust ledgers, they are kept as a readable archive and the firm decides where trust accounting runs.

What happens to records Neos has no place for?

On this route that is the firm’s accounts. They are exported from Interbill in formats that open without it, spreadsheets and PDFs, and handed to the firm as a read-only archive. You see the list before the move.

What has to be decided before Interbill data is loaded into Neos?

Time entries, billing records and templates are carried with mapping, so each mapping is agreed with you first. Documents, emails, notes, calendar entries, tasks, trust ledgers, 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 Neos are the names and marks of their owners, used here only to identify the two systems.

Moving from Interbill to Neos?

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

We reply within one business day.