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

Data migration route

Elite 3E to Litify migration

Elite 3E is a server-based accounting and billing system, and Litify is a cloud case management system. Only part of what Elite 3E holds has a place in a case file: clients and jobs move, and the table shows how much of the billing side does.

FromElite 3EServer
  1. Matters: Carried across
  2. Contacts: Carried across
  3. Time and expenses: Carried across
  4. Intake: Carried across
  5. Billing: Carried with mapping
  6. Custom fields: Carried with mapping
  7. Templates: Carried 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. Trust money: Confirmed in the analysis
  14. Firm accounts: Confirmed in the analysis
ToLitifyCloud
  • 4 carried
  • 3 mapped
  • 7 to confirm
What the two products hold. The analysis confirms it field by field.

What moves

What moves from Elite 3E to Litify

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

Records in Elite 3E and their place in Litify
RecordIn Elite 3EIn LitifyWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldClients and matters are the core of the financial record.Has a placeMatters, by case type.Carried across
ContactsClients, other parties and referrersHeld in partClients, timekeepers and vendors as financial records.Has a placeLoaded as parties and connected by roles.Carried across
DocumentsFiles stored in or linked from the systemTo be confirmedHas a placeLoaded to the document component and attached to matters.Confirmed in the analysis
EmailsEmails saved to matters or to the storeTo be confirmedHas a place in partShown on the activity timeline. How old email is loaded is confirmed in the analysis.Confirmed in the analysis
NotesFile notes, matter notes and contact notesTo be confirmedTo be confirmedConfirmed in the analysis
CalendarAppointments, court dates and deadlinesTo be confirmedHas a placeCalendar events on the matter.Confirmed in the analysis
TasksTo-dos and workflow steps assigned to peopleTo be confirmedHas a placeConfirmed in the analysis
Time and expensesTime and expense entries, billed and unbilledHeldTime capture feeding work in progress on each matter.Has a placeTime entries on the matter.Carried across
BillingInvoices, payments and debtor balancesHeldProformas, invoices, e-billing through eBillingHub, payments and collections.Has a place in partBilling is part of the product. Loading past invoices is scoped in the analysis.Carried with mapping
Trust moneyTrust or client account ledgers and balancesHeldTrust is one of the areas 3E Notify covers, with billing, payables and the ledger.To be confirmedConfirmed in the analysis
Firm accountsGeneral ledger, office account and payablesHeldMulti-entity, multi-currency general ledger, accounts payable and budgeting.To be confirmedConfirmed in the analysis
Custom fieldsFields and record types the firm added itselfHeldElite’s own migration guide inventories each firm’s customisations.Has a placeCustom fields are created before loading.Carried with mapping
TemplatesPrecedents, document templates and automationHeld in partProforma and invoice templates.Has a place in partTemplates are rebuilt in Litify’s document generation.Carried with mapping
IntakeLeads, enquiries, intake forms and pipelinesHeld in partClient and matter intake, which Elite’s data tools standardise.Has a placeLoaded as intakes.Carried across

What the plans mean

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

Clients and jobs move. The books stay books.

An accounting or billing system and a case management system overlap less than firms expect. Elite 3E knows clients, jobs, time and invoices. Litify knows cases, parties, documents and deadlines. The client list moves well, and jobs can seed the case list. Time and invoice history has a place only where the case system has a billing side, and the table above shows whether this one does. A general ledger does not belong in a case system.

So the plan has two halves. Records with a place in Litify are loaded and checked there. The rest is exported from Elite 3E as reports and ledgers that open without it, and the firm decides where its accounts run from then on. If Elite 3E is staying as the accounting system, nothing financial needs to move at all, and the job is to line up client and case numbers so the two can be reconciled.

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. Litify 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 a firm into Litify is done inside a Salesforce environment that has been configured for that firm, normally by Litify or one of its implementation partners. The data work fits around that project. Old records are mapped to parties, roles, intakes and matters and loaded into the Salesforce objects behind them, and documents are loaded separately and attached.

  1. The design comes first

    Case types, stages and page layouts are decided during discovery, before any load. A load into a half-configured environment has to be repeated when a field changes. The data mapping is written against the agreed design and updated whenever the design moves, so the two stay in step.

  2. One party, many roles

    Contacts from the old system become parties, and each appearance on a matter becomes a role. Duplicate contacts turn into duplicate parties with their roles divided between them. Duplicates are merged before the load where they can be identified, since separating them afterwards means pointing every role at the right party again.

  3. Open enquiries load as intakes

    Leads and enquiries that have not signed belong in intakes, not matters. They are loaded with their source and status so that conversion reports start from a true position. Old declined enquiries are loaded only if the firm wants them for conflict checking, and are marked so they do not count as live.

  4. Documents load after records

    Files are loaded into the document component once the matters exist, because each one is attached to a matter record. Folder structure is set per case type beforehand. Large injury files with medical records and video take time to transfer, and that time is planned into the cutover weekend.

  5. Validation rules reject bad rows

    A configured environment enforces required fields and validation rules, and old data seldom satisfies all of them. Rows that fail are reported by the load. They are fixed in the source and run again, or the rule is relaxed for migrated records, and the firm decides which for each rule.

More about moving into Litify

How NewLaw runs it

Four steps, in this order.

Financial records move on this route, so the balances are rehearsed before the real cutover. The maker of Litify says that it, or its partners, load firms into the product. Where the firm uses that service, NewLaw’s part is the work around it: the analysis, the clean-up in Elite 3E and checking each trial against Elite 3E.

  1. Analysis

    We read what Elite 3E holds and how its records link, then agree with you, field by field, where each piece will sit in Litify. Anything with no place there comes across as a note or stays behind, and you see which before the move.

  2. Clean-up

    Duplicate contacts and matters are merged where they can be identified, and inconsistent entries are put into one format, in Elite 3E, before extraction. It is not always possible to find every one, so some may carry across.

  3. Trial load

    The data is loaded into Litify as a trial and checked against Elite 3E: record counts, financial totals, the links between records, document dates. Exceptions are listed for you to decide.

  4. Cutover

    Changes in Elite 3E are frozen for an agreed window, the data is collected a final time and Litify goes live over a weekend. The financial cutover is rehearsed on a full trial load first, so that opening balances agree with the reports in Elite 3E as at the cutover date. 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 toLitify

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

Loaded data is not yet a working system. The maker of Litify runs or arranges the set-up of its product, so this is what has to be decided and put in place in Litify, whoever does the work, before people rely on it from the first day.

A Litify implementation is a configuration project on Salesforce, run by Litify or an implementation partner with the firm’s own project team. Discovery sessions with each department come first. The decisions that follow shape the system: what an intake asks, how a matter moves through its stages, who sees what, and which other systems are connected.

Set-up decisions in Litify

  • Define intake questionnaires and the rules for conversion
  • Set case types, matter stages and page layouts
  • Build matter plans that create tasks at each stage
  • Design document folders and generation templates per case type
  • Configure user roles and sharing for restricted matters
  • Decide on timekeeping, billing and accounting integrations

Questions

Elite 3E to Litify: 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 Litify?

That is confirmed in the analysis. We could not establish it from the two products’ own material, so it is checked against your data in Elite 3E before the plan is fixed. If Litify turns out to have no place for trust ledgers, they are kept as a readable archive and the firm decides where trust accounting runs.

Does everything in Elite 3E have a place in Litify?

Most of it does on paper. Documents, emails, notes, calendar entries, tasks, trust ledgers and the firm’s accounts 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 Litify is kept as a readable archive, and you see which before the move.

What has to be decided before Elite 3E data is loaded into Litify?

Billing records, custom fields and templates are carried with mapping, so each mapping is agreed with you first. Documents, emails, notes, calendar entries, tasks, trust ledgers and the firm’s accounts are confirmed in the analysis. The firm also sets the cutover date and how much financial history comes across as live records.

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

Moving from Elite 3E to Litify?

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

We reply within one business day.