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

Data migration route

eBillity to NetDocuments migration

eBillity is a cloud accounting and billing system, and NetDocuments 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.

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

What moves

What moves from eBillity to NetDocuments

Each row is a kind of record eBillity holds, whether NetDocuments has a place for it, and what is planned. On this route one kind of record carries across, one kind needs mapping, five kinds have no place in NetDocuments and are archived and six kinds are confirmed in the analysis.

Records in eBillity and their place in NetDocuments
RecordIn eBillityIn NetDocumentsWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldLawBillity tracks time and expenses against clients and matters.Has a place in partAs a client and matter value with its workspace. Other matter details stay in practice management.Carried with mapping
ContactsClients, other parties and referrersHeld in partClients and their billing details.No placeKept as a readable archive
DocumentsFiles stored in or linked from the systemHeld in partReceipt images attached to expense entries and invoices.Has a placeImported with profile values, folder, dates and access set per document.Carried across
EmailsEmails saved to matters or to the storeTo be confirmedHas a placeLoaded as email items profiled to the matter.Confirmed in the analysis
NotesFile notes, matter notes and contact notesTo be confirmedNo placeFile notes are loaded as documents in the matter workspace.Confirmed in the analysis
CalendarAppointments, court dates and deadlinesHeld in partCalendar entries can be converted into time entries.No placeKept as a readable archive
TasksTo-dos and workflow steps assigned to peopleTo be confirmedTo be confirmedConfirmed in the analysis
Time and expensesTime and expense entries, billed and unbilledHeldTimers, weekly timesheets and expenses, approved before billing.No placeKept as a readable archive
BillingInvoices, payments and debtor balancesHeldInvoices, LEDES billing and online payments through LawPay or Stripe.No placeKept as a readable archive
Trust moneyTrust or client account ledgers and balancesHeld in partIn LawBillity only: client trust funds managed beside billing.No placeKept as a readable archive
Custom fieldsFields and record types the firm added itselfTo be confirmedHas a placeAs custom profile attributes, created in the repository before the load.Confirmed in the analysis
TemplatesPrecedents, document templates and automationTo be confirmedHas a place in partLoaded as documents in a precedents cabinet or workspace. Automation is set up afresh.Confirmed in the analysis
IntakeLeads, enquiries, intake forms and pipelinesTo be confirmedNo placeConfirmed in the analysis

What the plans mean

Carried across
NetDocuments has a place for this kind of record. It is loaded there and checked against eBillity.
Carried with mapping
NetDocuments 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
NetDocuments has no place for it. It is exported in a format that opens without eBillity 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.

NetDocuments is a document management system: it takes files and the details that describe them. Most of what eBillity 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 eBillity 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 NetDocuments 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 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 NetDocuments 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 into NetDocuments means every document arrives with a profile. The cabinet, its profile attributes and the client and matter lookup tables are built first. Documents are then imported with an instruction file that says, line by line, which file gets which client, matter, author, document type, folder and access. Preparing that file from the old system’s data is most of the work.

  1. Lookup tables before documents

    Client and matter are validated attributes, with matter the child of client. A value missing from the lookup table cannot be used to profile a document. The tables are loaded from the practice management system first, closed matters included, and each matter is flagged open or closed so old ones stay out of pick lists.

  2. Workspaces come from the profile

    A workspace shows whatever is profiled to its matter. So the question is not where to put a folder tree but how to profile each file. Old folder names are often turned into a document type attribute, or kept as a workspace folder, and the mapping decides which for each one.

  3. Import files are unforgiving

    The import file is comma-separated text, and NetDocuments itself warns that opening one in Excel can strip leading zeros from numbers and alter dates. A matter number of 00123 that becomes 123 will not match its lookup value. The files are kept as plain text from start to finish and are not opened in a spreadsheet.

  4. Folder limits and depth

    A folder can hold any number of documents but no more than 500 subfolders. Deep trees copied from a file server also work against the way the system is searched. Where a matter arrives with hundreds of nested folders, the plan flattens them and keeps the lost path in the document name or an attribute.

  5. Security at the right level

    Access can be set on the cabinet, by profile value, on a workspace or on a single document. Restricted matters are best carried as workspace or profile-based security, so that new documents pick it up. Document-by-document access lists copied from an old system are loaded only where the restriction was real.

More about moving into NetDocuments

How NewLaw runs it

Four steps, in this order.

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

  1. Analysis

    We read what eBillity holds and how it is organised, then agree with you where each kind of record will sit in NetDocuments. 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 NetDocuments and checked against eBillity: 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 eBillity, a final pass over a weekend picks up what changed since the trial. 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 toNetDocuments

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

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

Beyond the load, NetDocuments has to be designed: how many cabinets the firm needs, which profile attributes every document must carry, and what a new matter’s workspace looks like on its first day. After that it is connected to the practice management system so client and matter lists stay current, and ndOffice and the email filing tools are set up for each person, with training on profiling.

Set-up decisions in NetDocuments

  • Cabinet design: one for the firm, or several by purpose
  • Profile attributes, lookup tables and the client and matter hierarchy
  • Workspace layout with default folders, filters and saved searches
  • User groups, cabinet membership and security for restricted matters
  • A feed of new clients and matters from practice management
  • ndOffice, ndMail and Outlook filing on every desk, with training

Questions

eBillity to NetDocuments: 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 NetDocuments?

No. NetDocuments does not keep trust ledgers. Trust records from eBillity 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 NetDocuments has no place for?

On this route that is contacts, calendar entries, time entries, billing records and trust ledgers. They are exported from eBillity 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 eBillity data is loaded into NetDocuments?

Matters 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 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

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

Moving from eBillity to NetDocuments?

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

We reply within one business day.