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

Data migration route

Interbill to iManage Cloud migration

Interbill is a cloud accounting and billing system, and iManage Cloud is a cloud document management system. Only files and their details have a place there, so this route carries the documents and archives the rest.

FromInterbillCloud
  1. Matters: Carried with mapping
  2. Templates: Carried with mapping
  3. Documents: Confirmed in the analysis
  4. Emails: Confirmed in the analysis
  5. Notes: Confirmed in the analysis
  6. Calendar: Confirmed in the analysis
  7. Tasks: Confirmed in the analysis
  8. Custom fields: Confirmed in the analysis
  9. Intake: Confirmed in the analysis
ToiManage CloudCloud
  1. Contacts: Kept as a readable archive
  2. Time and expenses: Kept as a readable archive
  3. Billing: Kept as a readable archive
  4. Trust money: Kept as a readable archive
  5. Firm accounts: Kept as a readable archive
Readable archiveNo place in iManage Cloud
  • 2 mapped
  • 7 to confirm
  • 5 archived
What the two products hold. The analysis confirms it field by field.

What moves

What moves from Interbill to iManage Cloud

Each row is a kind of record Interbill holds, whether iManage Cloud has a place for it, and what is planned. On this route two kinds need mapping, five kinds have no place in iManage Cloud and are archived and seven kinds are confirmed in the analysis.

Records in Interbill and their place in iManage Cloud
RecordIn InterbillIn iManage CloudWhat 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 place in partAs a workspace with client and matter metadata. Parties and status stay in practice management.Carried with mapping
ContactsClients, other parties and referrersHeld in partClients, as billing records.No placeKept as a readable archive
DocumentsFiles stored in or linked from the systemTo be confirmedHas a placeEach needs a workspace and valid client and matter values; its class sets default security.Confirmed in the analysis
EmailsEmails saved to matters or to the storeTo be confirmedHas a placeLoaded as email documents into the workspace’s email folders.Confirmed in the analysis
NotesFile notes, matter notes and contact notesTo be confirmedNo placeFile notes can be loaded as documents on the matter.Confirmed in the analysis
CalendarAppointments, court dates and deadlinesTo be confirmedNo placeConfirmed in the analysis
TasksTo-dos and workflow steps assigned to peopleTo be confirmedNo placeiManage Tracker is a separate product with its own set-up.Confirmed in the analysis
Time and expensesTime and expense entries, billed and unbilledHeldBilling entries, typed with optional description codes.No placeKept as a readable archive
BillingInvoices, payments and debtor balancesHeldMonthly, reminder and retainer statements, late charges, receivables reports.No placeKept as a readable archive
Trust moneyTrust or client account ledgers and balancesHeldTrust and retainer reports and ledgers.No placeKept as a readable archive
Firm accountsGeneral ledger, office account and payablesHeld in partAn optional general ledger designed for solo practitioners.No placeKept as a readable archive
Custom fieldsFields and record types the firm added itselfTo be confirmedHas a place in partA fixed number of custom profile fields, each a validated list.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 partPrecedents load as documents. Automation is rebuilt in the firm’s drafting tools.Carried with mapping
IntakeLeads, enquiries, intake forms and pipelinesTo be confirmedNo placeConfirmed in the analysis

What the plans mean

Carried with mapping
iManage Cloud 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
iManage Cloud 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

Only the documents have a place here.

iManage Cloud is a document management system: it takes files and the details that describe them. Most of what Interbill holds is not files. Entries, balances, settings and lists have no place in a document store, and the table above is short for that reason. What can move is any document Interbill produced or stored: invoices as PDFs, signed agreements, attachments, exported reports. Each is filed under the client or matter it relates to.

The useful version of this job is often an archive. A firm retiring a system wants its records readable later without keeping the subscription or the old PC. The data is exported in open formats, spreadsheets and PDFs, and filed in iManage Cloud in a workspace set aside for it, with access limited to the people who need it. That gives the firm one place to look, under the same retention rules as the rest of its documents.

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 iManage Cloud 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

Administrators of an iManage Cloud library have API access only, so nothing is loaded by writing to a database. For cloudimanage.com, the newer of its two cloud platforms, iManage lists a supervised import API, sync APIs and a metadata loader. Nothing can be filed loose: every document goes into a workspace, with valid client and matter values. So the client and matter lists, the workspace template and the security groups are built first.

  1. Client and matter lists first

    Custom1 and custom2 are validated lists, with each matter a child of its client. A value that is not already in the list cannot be assigned to a document. The lists are loaded from the practice management system or the old document store before any content, closed matters with documents included.

  2. One workspace per matter

    Each matter gets a workspace generated from a template, so the template is designed before migration: its tabs, its folders, which are created up front and which on demand. Old folder trees rarely match it. The mapping says where each old folder lands and what happens to folders with no equivalent.

  3. Authors must be known users

    Author and operator are profile fields tied to users of the library. Documents written by people who left years ago need a decision: recreate those people as inactive users, or assign a placeholder author. That choice affects searching by author for as long as the firm uses the system.

  4. Hybrid security

    iManage calls its security model hybrid: where a user’s groups disagree, the most permissive access applies unless one of them is denied. On cloudimanage.com that model cannot be changed. Default security is normally set on the workspace and inherited below it. Restricted matters from the old system are loaded with their access list already in place.

  5. New numbers, original dates

    Documents are numbered by iManage as they are loaded, so old numbers do not carry over as numbers. On cloudimanage.com the file date setting is fixed to the file’s own date, and on imanage.work it can be set either way. Which dates display is checked on the trial load. The old reference can be carried in a custom field or the description where the firm wants to search by it.

More about moving into iManage Cloud

How NewLaw runs it

Four steps, in this order.

Nothing financial lands in iManage Cloud on this route, which makes it repeatable: a load can be run again until it is right.

  1. Analysis

    We read what Interbill holds and how it is organised, then agree with you where each kind of record will sit in iManage Cloud. Anything with no place there stays behind or is archived, and you see which before the move.

  2. Clean-up

    Duplicate clients, matters and folders are merged where they can be identified, and naming is put into one format, before anything is copied. It is not always possible to find every one, so some may carry across.

  3. Trial load

    A trial is loaded into iManage Cloud and checked against Interbill: record and file counts, the links between records, document dates, and a sample opened by your own people. Exceptions are listed for you to decide.

  4. Cutover

    There is no financial cutover on this route. After a short freeze on changes in Interbill, a final pass over a weekend picks up what changed since the trial. 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 toiManage Cloud

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 iManage Cloud. 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 iManage Cloud

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

Setting up iManage Cloud is mostly design work done before any user logs in: how many libraries, what a workspace looks like, which profile fields are captioned for what, and who can see which matters. Then come the links that keep it running day to day, such as creating a workspace when a matter is opened in the practice management system, and the add-ins on each desk.

Set-up decisions in iManage Cloud

  • Library structure and captions for client, matter and other fields
  • Workspace templates, folder names and Flexible Folders rules by practice area
  • Document classes, subclasses and the profile fields each one requires
  • Roles, groups, default security and walls for restricted matters
  • Workspace creation fed from the practice management system’s matter list
  • Work Desktop, Outlook email filing and Mobility on each device, with training

Questions

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

No. iManage Cloud does not keep trust ledgers. Trust records from Interbill are exported as ledgers and statements that open without it, and the firm settles where its trust accounting runs from the cutover date before the move is planned.

What happens to records iManage Cloud has no place for?

On this route that is contacts, time entries, billing records, trust ledgers and 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 iManage Cloud?

Matters and templates are carried with mapping, so each mapping is agreed with you first. Documents, emails, notes, calendar entries, tasks, custom fields and intake records are confirmed in the analysis. The firm also decides which closed matters and how many versions of a document are in scope.

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 iManage Cloud are the names and marks of their owners, used here only to identify the two systems.

Moving from Interbill to iManage Cloud?

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

We reply within one business day.