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

Data migration route

Elite 3E data to Microsoft SQL Server

Elite 3E is a server-based 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 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. Templates: Exported with mapping
  10. Documents: Confirmed in the analysis
  11. Emails: Confirmed in the analysis
  12. Notes: Confirmed in the analysis
  13. Calendar: Confirmed in the analysis
  14. Tasks: Confirmed in the analysis
ToMicrosoft SQL ServerServer
  • 7 carried
  • 2 mapped
  • 5 to confirm
What the two products hold. The analysis confirms it field by field.

What moves

What moves from Elite 3E to Microsoft SQL Server

Each row is a kind of record Elite 3E holds, whether Microsoft SQL Server has a place for it, and what is planned. On this route seven kinds of record carry across, two kinds need mapping and five kinds are confirmed in the analysis.

Records in Elite 3E and their place in Microsoft SQL Server
RecordIn Elite 3EIn Microsoft SQL ServerWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldClients and matters are the core of the financial record.Has a placeA table of matters linked to clients, parties and fee earners.Exported in full
ContactsClients, other parties and referrersHeld in partClients, timekeepers and vendors as financial 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 unbilledHeldTime capture feeding work in progress on each matter.Has a placeTime and expense rows with rates and billed status.Exported in full
BillingInvoices, payments and debtor balancesHeldProformas, invoices, e-billing through eBillingHub, payments and collections.Has a placeInvoices, lines and receipts as rows; 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 placeTransactions and balances for look-up; it is not a trust accounting system.Exported in full
Firm accountsGeneral ledger, office account and payablesHeldMulti-entity, multi-currency general ledger, accounts payable and budgeting.Has a placeGeneral ledger journals and balances, 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 placeAs added columns, or a table of field names and values.Exported with mapping
TemplatesPrecedents, document templates and automationHeld in partProforma and invoice templates.Has a place in partPrecedent files can be stored; automation does not run here.Exported with mapping
IntakeLeads, enquiries, intake forms and pipelinesHeld in partClient and matter intake, which Elite’s data tools standardise.Has a placeEnquiry rows, where the source recorded them.Exported in full

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

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 Elite 3E holds, table by table, and agree with you what the copy in Microsoft SQL Server 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 Microsoft SQL Server 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 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 Elite 3E 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

Elite 3E to Microsoft SQL Server: 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 Microsoft SQL Server hold trust ledgers from Elite 3E?

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 Elite 3E as at the export date.

Does everything in Elite 3E have a place in Microsoft SQL Server?

Most of it does on paper. Documents, emails, notes, calendar entries and tasks 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 Elite 3E is written out to Microsoft SQL Server?

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

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