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

Data migration route

Elite 3E to NetDocuments migration

Elite 3E is a server-based 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.

FromElite 3EServer
  1. Matters: Carried with mapping
  2. Custom fields: Carried with mapping
  3. Templates: Carried with mapping
  4. Documents: Confirmed in the analysis
  5. Emails: Confirmed in the analysis
  6. Notes: Confirmed in the analysis
  7. Calendar: Confirmed in the analysis
  8. Tasks: Confirmed in the analysis
ToNetDocumentsCloud
  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
  6. Intake: Kept as a readable archive
Readable archiveNo place in NetDocuments
  • 3 mapped
  • 5 to confirm
  • 6 archived
What the two products hold. The analysis confirms it field by field.

What moves

What moves from Elite 3E to NetDocuments

Each row is a kind of record Elite 3E holds, whether NetDocuments has a place for it, and what is planned. On this route three kinds need mapping, six kinds have no place in NetDocuments and are archived and five kinds are confirmed in the analysis.

Records in Elite 3E and their place in NetDocuments
RecordIn Elite 3EIn NetDocumentsWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldClients and matters are the core of the financial record.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, timekeepers and vendors as financial records.No placeKept as a readable archive
DocumentsFiles stored in or linked from the systemTo be confirmedHas a placeImported with profile values, folder, dates and access set per document.Confirmed in the analysis
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 deadlinesTo be confirmedNo placeConfirmed in the analysis
TasksTo-dos and workflow steps assigned to peopleTo be confirmedTo be confirmedConfirmed in the analysis
Time and expensesTime and expense entries, billed and unbilledHeldTime capture feeding work in progress on each matter.No placeKept as a readable archive
BillingInvoices, payments and debtor balancesHeldProformas, invoices, e-billing through eBillingHub, payments and collections.No placeKept as a readable archive
Trust moneyTrust or client account ledgers and balancesHeldTrust is one of the areas 3E Notify covers, with billing, payables and the ledger.No placeKept as a readable archive
Firm accountsGeneral ledger, office account and payablesHeldMulti-entity, multi-currency general ledger, accounts payable and budgeting.No placeKept as a readable archive
Custom fieldsFields and record types the firm added itselfHeldElite’s own migration guide inventories each firm’s customisations.Has a placeAs custom profile attributes, created in the repository before the load.Carried with mapping
TemplatesPrecedents, document templates and automationHeld in partProforma and invoice templates.Has a place in partLoaded as documents in a precedents cabinet or workspace. Automation is set up afresh.Carried with mapping
IntakeLeads, enquiries, intake forms and pipelinesHeld in partClient and matter intake, which Elite’s data tools standardise.No placeKept as a readable archive

What the plans mean

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 Elite 3E 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 Elite 3E 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 Elite 3E 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.

Elite 3E runs on the firm’s own equipment, so the data is collected there: a copy of the database and the folders its documents sit in, taken with the firm’s IT provider or over a remote session. NetDocuments is hosted by its maker, so loading depends on the import tools and access it provides. The old machine is kept, read only, as the fall-back record.

Where the data is now

Firms on Elite are large, and so is the data: every time entry, proforma, invoice and ledger posting for the life of the firm, usually across more than one office or entity. Moving to a different system starts with which Elite product and version is in place, then with how much of that history has to be live in the new system on day one.

  1. Which Elite it is

    3E in Elite’s cloud, 3E on the firm’s own SQL Server and the older Enterprise system keep their data differently and are reached differently. An on-premises firm can copy its own database. A cloud firm works from what Elite’s service provides. The product, version and hosting are confirmed before anything is scoped.

  2. Proformas and write-downs

    Billing runs through proformas that partners edit before an invoice is posted, and the edits, write-downs and transfers are part of the record. Most destinations keep the final invoice only. The firm decides whether proforma history matters for reporting on realisation, and if so where it will be kept.

  3. More than one entity

    The 3E general ledger is built to consolidate several entities and currencies. A firm with offices in different countries may be one database with many sets of books. The new system’s structure for offices and currencies is settled first, since every matter and balance has to be assigned to one.

  4. Customisations get an inventory

    Elite’s own cloud migration program begins by listing every customisation a firm has in production, a sign of how much firm-specific configuration these systems carry. Custom fields, rules, reports and templates built in 3E are listed the same way here, and each is matched to something in the destination or dropped by decision.

  5. E-billing rules and client guidelines

    Firms that bill corporate clients electronically check invoices against client billing guidelines in Elite’s Validate and eBillingHub products before sending them. Those rules belong to the client relationship, not to the software. They are set up again in whatever the destination uses for e-billing, so invoices are not rejected in the first month.

More about moving off Elite 3E

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 Elite 3E 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 Elite 3E: 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 Elite 3E, a final pass over a weekend picks up what changed since the trial. Elite 3E 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 Elite 3E 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 fromElite 3E
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 Elite 3E 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

Elite 3E to NetDocuments: what firms ask

Does it matter whether we are on 3E or Enterprise?

It does. They are different systems with different databases, and 3E itself comes as a cloud service or an on-premises installation. The records are the same in kind: clients, matters, time, bills, trust and ledgers. How they are extracted and how the totals are checked is worked out for the product you have.

Can we bring all our financial history?

Rarely all of it as live transactions. Open matters, unbilled time, unpaid invoices, trust balances and opening ledger balances are the part that has to be live. Older detail is usually summarised, with the Elite database kept read only for look-ups. How far back the live detail goes is a decision for the finance team.

What about our matter numbers?

Client and matter numbers are read as they stand and carried into the new system wherever it allows the number to be set. Firms whose numbers join a client code to a matter code should check the destination’s field lengths early, which the field mapping in the analysis does.

Do trust balances in Elite 3E have a place in NetDocuments?

No. NetDocuments does not keep trust ledgers. Trust records from Elite 3E 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, time entries, billing records, trust ledgers, the firm’s accounts and intake records. They are exported from Elite 3E 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 Elite 3E data is loaded into NetDocuments?

Matters, custom fields and templates are carried with mapping, so each mapping is agreed with you first. Documents, emails, notes, calendar entries and tasks 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

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

Moving from Elite 3E 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.