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

Data migration route

Elite 3E data to SQLite

Elite 3E is a server-based accounting and billing system, and SQLite is a store of data kept as files the firm holds. This is not a move to a new working system: the route writes out what Elite 3E holds and keeps it readable and open to queries.

FromElite 3EServer
  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. Intake: Exported in full
  8. Custom fields: Exported with mapping
  9. Documents: Confirmed in the analysis
  10. Emails: Confirmed in the analysis
  11. Notes: Confirmed in the analysis
  12. Calendar: Confirmed in the analysis
  13. Tasks: Confirmed in the analysis
ToSQLiteFiles
  1. Templates: Kept as a readable archive
Readable archiveNo place in SQLite
  • 7 carried
  • 1 mapped
  • 5 to confirm
  • 1 archived
What the two products hold. The analysis confirms it field by field.

What moves

What moves from Elite 3E to SQLite

Each row is a kind of record Elite 3E holds, whether SQLite has a place for it, and what is planned. On this route seven kinds of record carry across, one kind needs mapping, one kind has no place in SQLite and is archived and five kinds are confirmed in the analysis.

Records in Elite 3E and their place in SQLite
RecordIn Elite 3EIn SQLiteWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldClients and matters are the core of the financial record.Has a placeA matters table keyed by matter number.Exported in full
ContactsClients, other parties and referrersHeld in partClients, timekeepers and vendors as financial records.Has a placeContacts and their roles on matters as linked tables.Exported in full
DocumentsFiles stored in or linked from the systemTo be confirmedHas a place in partListed in a table; the files themselves stay in folders beside the database.Confirmed in the analysis
EmailsEmails saved to matters or to the storeTo be confirmedHas a place in partAs message files in folders, indexed in a table.Confirmed in the analysis
NotesFile notes, matter notes and contact notesTo be confirmedHas a placeA notes table linked to matters.Confirmed in the analysis
CalendarAppointments, court dates and deadlinesTo be confirmedHas a placeA table of dated entries, with no calendar view.Confirmed in the analysis
TasksTo-dos and workflow steps assigned to peopleTo be confirmedHas a placeA table of tasks and their status at the final date.Confirmed in the analysis
Time and expensesTime and expense entries, billed and unbilledHeldTime capture feeding work in progress on each matter.Has a placeA table of time and expense entries.Exported in full
BillingInvoices, payments and debtor balancesHeldProformas, invoices, e-billing through eBillingHub, payments and collections.Has a placeInvoice and receipt tables; invoice PDFs kept as files.Exported in full
Trust moneyTrust or client account ledgers and balancesHeldTrust is one of the areas 3E Notify covers, with billing, payables and the ledger.Has a placeTrust transactions as rows, for look-up and not for accounting.Exported in full
Firm accountsGeneral ledger, office account and payablesHeldMulti-entity, multi-currency general ledger, accounts payable and budgeting.Has a placeLedger journals as rows, where the source held them.Exported in full
Custom fieldsFields and record types the firm added itselfHeldElite’s own migration guide inventories each firm’s customisations.Has a placeColumns added to the table they belonged to.Exported with mapping
TemplatesPrecedents, document templates and automationHeld in partProforma and invoice templates.No placePrecedent files are kept in folders, not in the database.Kept as a readable archive
IntakeLeads, enquiries, intake forms and pipelinesHeld in partClient and matter intake, which Elite’s data tools standardise.Has a placeAn enquiries table, where the source tracked them.Exported in full

What the plans mean

Exported in full
SQLite has a place for this kind of record. It is loaded there and checked against Elite 3E.
Exported with mapping
SQLite 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
SQLite 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

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

Writing Elite 3E out to SQLite 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 Elite 3E 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.

Both ends are on equipment the firm controls, so the work is done on the firm’s own network with its IT provider. Disk space for a second full copy is checked first. The original in Elite 3E stays untouched until the copy in SQLite has been checked.

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

A SQLite archive suits a firm that wants the old system’s records kept, seldom consulted, and free of any server or subscription. Everything structured goes into one file. That simplicity moves the responsibility elsewhere: the file has no security of its own and no administrator watching it, so where it is stored and who can reach it are the real decisions.

  1. One file, kept with the archive

    Matters, contacts, time, invoices and trust transactions become tables in a single file. It is stored with the firm’s closed-matter records and can be copied like any document. A checksum recorded when the file is finalised lets anyone confirm, years later, that the copy they hold has not been altered, and the firm decides whether to keep one.

  2. No logins inside the file

    SQLite has no users or passwords. Anyone who can open the file can read every client’s ledger. Protection comes from where it is kept, such as a restricted folder or an encrypted volume, and that choice is the firm’s. It can suit an archive consulted by two people, and it is said plainly so nobody assumes otherwise.

  3. Built for reading, not sharing

    Only one program can write to the file at a time, and SQLite’s authors point people to a client/server database where many users share data over a network. A finished archive never meets that limit. It is the reason SQLite is used here for records that are closed and not for anything staff still update.

  4. Documents stay outside it

    Documents remain ordinary files in matter folders, and a table in the database lists each one with its matter, title, dates and path. Keeping them as files means they open with a double-click and can be handed to a client. The table is how a file is found by matter number instead of by guessing its name.

  5. Someone has to open it

    SQLite publishes its own command-line program for opening a database file, and other tools read the format too. None of that helps if nobody remembers how. Saved queries for the usual look-ups and a short note on which tool to use can sit in the same folder as the file, and the firm decides what it needs.

More about moving into SQLite

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 Elite 3E holds, table by table, and agree with you what the copy in SQLite must be able to answer later. Everything Elite 3E 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 SQLite as a trial and checked against Elite 3E: record counts, totals where Elite 3E 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 Elite 3E, the export is run a final time and checked again. There is nothing to go live. Elite 3E 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 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 toSQLite

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

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

There is nothing to install on a server and nothing to license. The work is in making the file usable and safe to keep: naming it, documenting its tables, storing it where the firm’s records policy says archives go, and checking that a member of staff can open it and find a matter. Whether a second copy is held somewhere separate is the firm’s call.

What is agreed and set up

  • File name, storage location and whether a second copy exists
  • Whether a checksum is recorded for later verification
  • Saved queries for matter, ledger and document look-ups
  • Which tool staff will use to open the file
  • Who may open the folder the file sits in
  • Retention period and destruction date noted beside the file

Questions

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

Does the copy in SQLite hold trust ledgers from Elite 3E?

Yes. Trust transactions as rows, for look-up and not for accounting. Trust ledgers are written out with the rest, and counts and totals are agreed to the reports in Elite 3E as at the export date.

What happens to records SQLite has no place for?

On this route that is templates. 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 is written out to SQLite?

Custom fields are exported 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 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

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

Moving from Elite 3E to SQLite?

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

We reply within one business day.