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

Data migration route

Interbill data to Microsoft SQL Server

Interbill is a cloud accounting and billing system, and Microsoft SQL Server is a database on a server the firm runs. This is not a move to a new working system: the route writes out what Interbill holds and keeps it readable and open to queries.

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

What moves

What moves from Interbill to Microsoft SQL Server

Each row is a kind of record Interbill holds, whether Microsoft SQL Server has a place for it, and what is planned. On this route six kinds of record carry across, one kind needs mapping and seven kinds are confirmed in the analysis.

Records in Interbill and their place in Microsoft SQL Server
RecordIn InterbillIn Microsoft SQL ServerWhat 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 placeA table of matters linked to clients, parties and fee earners.Exported in full
ContactsClients, other parties and referrersHeld in partClients, as billing records.Has a placePeople and companies, with their roles on each matter.Exported in full
DocumentsFiles stored in or linked from the systemTo be confirmedHas a place in partAs files in folders with an index table; storing files in the database is possible.Confirmed in the analysis
EmailsEmails saved to matters or to the storeTo be confirmedHas a place in partAs message files with an index table, or as rows of header fields.Confirmed in the analysis
NotesFile notes, matter notes and contact notesTo be confirmedHas a placeRows of text linked to matters and contacts.Confirmed in the analysis
CalendarAppointments, court dates and deadlinesTo be confirmedHas a placeRows of appointments and key dates; nothing displays them as a calendar.Confirmed in the analysis
TasksTo-dos and workflow steps assigned to peopleTo be confirmedHas a placeRows with assignee, due date and status.Confirmed in the analysis
Time and expensesTime and expense entries, billed and unbilledHeldBilling entries, typed with optional description codes.Has a placeTime and expense rows with rates and billed status.Exported in full
BillingInvoices, payments and debtor balancesHeldMonthly, reminder and retainer statements, late charges, receivables reports.Has a placeInvoices, lines and receipts as rows; invoice PDFs kept as files.Exported in full
Trust moneyTrust or client account ledgers and balancesHeldTrust and retainer reports and ledgers.Has a placeTransactions and balances for look-up; it is not a trust accounting system.Exported in full
Firm accountsGeneral ledger, office account and payablesHeld in partAn optional general ledger designed for solo practitioners.Has a placeGeneral ledger journals and balances, where the source held them.Exported in full
Custom fieldsFields and record types the firm added itselfTo be confirmedHas a placeAs added columns, or a table of field names and values.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 partPrecedent files can be stored; automation does not run here.Exported with mapping
IntakeLeads, enquiries, intake forms and pipelinesTo be confirmedHas a placeEnquiry rows, where the source recorded them.Confirmed in the analysis

What the plans mean

Exported in full
Microsoft SQL Server has a place for this kind of record. It is loaded there and checked against Interbill.
Exported with mapping
Microsoft SQL Server 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

Not a new system. A complete copy the firm can query.

Writing Interbill out to Microsoft SQL Server is not a migration into a new working system. Nobody will open a matter there on Monday morning. The aim is a complete, faithful copy that can be queried and reported on after the old system is gone. So the rules change. Nothing is cleaned or merged unless the firm asks, because an archive should show the records as they were. Every table and field is carried, including those a new system would have had no place for.

What makes an archive usable is the description that goes with it. The export is delivered with a plain account of each table: what it holds, how it joins to the others, what the codes mean. Record counts and financial totals are agreed to the reports in Interbill as at the export date, so the archive can stand as the record. Documents are exported beside the data with a table linking each file to its matter. Access is restricted, since the archive holds everything the live system did.

Interbill is hosted by its maker and Microsoft SQL Server sits on equipment the firm controls. The data leaves a service that was backed up for the firm and arrives somewhere the firm must back up itself, so backup and access are arranged before the export is copied in. What Interbill will release depends on its export tools, and that is confirmed in the analysis.

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

There are two ways to put a retired system into SQL Server, and they suit different firms. The old system’s own database can be restored as it is. Or the data can be loaded into a new set of tables designed to be read by people. The first is quicker and harder to use. Which suits is worked out in the analysis, and the choice is the firm’s.

  1. Restored copy or rebuilt schema

    Where the old practice system already kept its data in SQL Server, a backup can be restored onto a new server. The tables keep the vendor’s names and codes, which can be cryptic, and reading them takes someone who knows that product’s database. A rebuilt schema uses plain names such as Matter and TrustTransaction.

  2. No screens come with it

    A database has no matter screen. Someone has to ask it questions in SQL or through a reporting tool. Saved views can be set up for the things the firm will really look up: a matter with its parties, its ledger, its time entries and its list of documents. Which are worth having is agreed in the analysis.

  3. Documents sit beside the database

    Files are normally kept in folders on the same server, with a table recording each document’s matter, title, dates and path. Storing the files inside the database is possible but makes it far larger. On the Express edition, the cap on database size rules that out for most firms’ document stores.

  4. The edition follows the size

    A firm’s tables may fit within the Express limit once documents are kept outside the database. A long trust and time history at a larger firm may not. The size of the source data is measured in the analysis, and the edition is chosen from that figure with the firm’s IT provider.

  5. Backups and a test restore

    An archive that is never backed up is one disk failure from gone. Backups belong to the firm’s IT provider: a full one once the load is finished, and a schedule if anything is still being added. It is worth restoring one to a second machine as a test, because a backup that has never been restored is only a hope.

More about moving into Microsoft SQL Server

How NewLaw runs it

Four steps, in this order.

This route produces an archive, not a working system, so the steps are about completeness and proof.

  1. Analysis

    We read what Interbill holds, table by table, and agree with you what the copy in Microsoft SQL Server must be able to answer later. Everything Interbill holds is in scope unless you take it out.

  2. Clean-up, if you want it

    An archive should show the records as they were, so nothing is merged or corrected unless you ask. Where the copy is also meant for reporting, duplicate and inconsistent entries are tidied in a working copy and the original values are kept beside them.

  3. Trial export

    The data is written to Microsoft SQL Server as a trial and checked against Interbill: record counts, totals where Interbill holds money, the links between records, and a sample of documents opened from the export. Exceptions are listed for you to decide.

  4. Final export

    After the last day of work in Interbill, the export is run a final time and checked again. There is nothing to go live. Interbill is kept read only until you are satisfied the copy answers what you need, and it is handed over with a written description of its contents.

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 toMicrosoft SQL Server

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 Microsoft SQL Server. 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

Structure, permissions and handover

Microsoft SQL Server is a place to keep data, not a system staff work in each day. What is agreed is how the data is laid out, who can reach it, and what is handed over with it.

Standing up SQL Server as an archive is IT work shared with the firm’s provider. A server or instance is chosen, logins are created for the few people who need to read the data, and nobody is given rights to change it. Views and a handful of reports are built for the common questions, and the IT provider owns the backup routine.

What is agreed and set up

  • Server, instance and edition agreed with the IT provider
  • Read-only logins and roles for named staff
  • Views for matter, ledger, time and document look-ups
  • Backup schedule and who tests a restore
  • Plain names and descriptions for tables and columns
  • Excel or Power BI connected for reporting

Questions

Interbill to Microsoft SQL Server: 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.

Does the copy in Microsoft SQL Server hold trust ledgers from Interbill?

Yes. Transactions and balances for look-up; it is not a trust accounting system. Trust ledgers are written out with the rest, and counts and totals are agreed to the reports in Interbill as at the export date.

Does everything in Interbill have a place in Microsoft SQL Server?

Most of it does on paper. Documents, emails, notes, calendar entries, tasks, 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 Microsoft SQL Server is kept as a readable archive, and you see which before the move.

What has to be decided before Interbill is written out to Microsoft SQL Server?

Templates are exported 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 who may open the archive and how long it is kept.

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

Moving from Interbill to Microsoft SQL Server?

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

We reply within one business day.