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

Data migration route

LEAP 365 to Neos migration

LEAP 365 is a cloud practice management system, and Neos is a cloud case management system for personal injury work. Matter records move into cases, and the firm decides where its accounting runs from the cutover date.

FromLEAP 365Cloud
  1. Matters: Carried across
  2. Contacts: Carried across
  3. Documents: Carried across
  4. Calendar: Carried across
  5. Intake: Carried across
  6. Emails: Carried with mapping
  7. Time and expenses: Carried with mapping
  8. Billing: Carried with mapping
  9. Custom fields: Carried with mapping
  10. Templates: Carried with mapping
  11. Notes: Confirmed in the analysis
  12. Tasks: Confirmed in the analysis
  13. Trust money: Confirmed in the analysis
ToNeosCloud
  1. Firm accounts: Kept as a readable archive
Readable archiveNo place in Neos
  • 5 carried
  • 5 mapped
  • 3 to confirm
  • 1 archived
What the two products hold. The analysis confirms it field by field.

What moves

What moves from LEAP 365 to Neos

Each row is a kind of record LEAP 365 holds, whether Neos has a place for it, and what is planned. On this route five kinds of record carry across, five kinds need mapping, one kind has no place in Neos and is archived and three kinds are confirmed in the analysis.

Records in LEAP 365 and their place in Neos
RecordIn LEAP 365In NeosWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldThe same electronic matters as the desktop program.Has a placeCases by case type.Carried across
ContactsClients, other parties and referrersHeldCards, as in the rest of LEAP.Has a placeParties, providers and case contacts. Contacts can be imported from CSV.Carried across
DocumentsFiles stored in or linked from the systemHeldStored in the matter on LEAP’s servers.Has a placeCase Docs tab, organised in sub-tabs.Carried across
EmailsEmails saved to matters or to the storeHeldOnly emails that were saved to a matter.Has a place in partEmails tagged to a case are held. Loading old mail is scoped in the analysis.Carried with mapping
NotesFile notes, matter notes and contact notesTo be confirmedHas a placeConfirmed in the analysis
CalendarAppointments, court dates and deadlinesHeld in partCritical dates sit on the matter; anything further is confirmed in the analysis.Has a placeCase calendar entries.Carried across
TasksTo-dos and workflow steps assigned to peopleTo be confirmedHas a placeLoaded as checklist items.Confirmed in the analysis
Time and expensesTime and expense entries, billed and unbilledHeldHas a place in partTime can be held as value items. The treatment of old entries is confirmed in the analysis.Carried with mapping
BillingInvoices, payments and debtor balancesHeldHas a place in partInvoices exist in Neos. Loading past invoices is confirmed in the analysis.Carried with mapping
Trust moneyTrust or client account ledgers and balancesHeldLEAP’s in-built trust accounting.To be confirmedConfirmed in the analysis
Firm accountsGeneral ledger, office account and payablesHeld in partLEAP’s office accounting module, or Xero or MYOB through an integration.No placeThe general ledger stays in QuickBooks.Kept as a readable archive
Custom fieldsFields and record types the firm added itselfHeld in partFields come mainly from LEAP’s matter types, with matter tables for repeating data.Has a placeUser-defined fields are created on the relevant tab first.Carried with mapping
TemplatesPrecedents, document templates and automationHeldLEAP’s forms library and the firm’s own precedents.Has a place in partTemplates are rebuilt for Neos document generation.Carried with mapping
IntakeLeads, enquiries, intake forms and pipelinesHeldEnquiries are recorded in LEAP CRM.Has a placeIntakes tab. Simple intake imports from CSV are supported.Carried across

What the plans mean

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

Matters become cases. The ledgers need a home.

Going from a practice management system to a case management system is a move towards the file and away from the ledger. Matters, parties, documents, notes and deadlines have a natural place in Neos. Time, invoices, trust and the general ledger often do not, or only in part, and the table above shows which. Before the move is planned the firm settles where billing and trust accounting will run, because that decides what is loaded and what is archived.

Case systems are usually built around a practice area, with their own stages, roles and document sets. A general matter from LEAP 365 has to be given a case type in Neos, and that choice drives which fields and workflows it gets. The mapping is agreed type by type. Financial history with no place in Neos is exported as reports and ledgers the firm can open without LEAP 365, and kept as the record of what was billed and held.

Both are hosted by their makers, so nothing is collected from the firm’s office. What can be taken out of LEAP 365 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 LEAP 365 is kept running until the checks on Neos are finished.

Where the data is now

For a firm on LEAP 365 the migration is a LEAP migration. The browser is only the window; the records sit in LEAP’s cloud and are extracted from there. What differs is the firm’s working habits. Browser-first firms often have people on Macs or at home with no LEAP software installed, so nothing can be gathered from local machines.

  1. One account, two front ends

    LEAP 365 and LEAP Desktop open the same account. A firm with some staff in the browser and others on the desktop program has one set of data, and it is moved once. The matter list a partner sees in Chrome at home is the list the office sees, with the same matter numbers.

  2. No local copies to rely on

    With the browser version there is no installed program holding working copies of documents. Every file has to come from LEAP’s export. We test the export for completeness by counting documents per matter against what LEAP shows on screen, for a sample of large and small files, before the trial load.

  3. Emails that were never saved

    Only correspondence saved to a matter is in LEAP. Emails still sitting in a lawyer’s mailbox are not part of the export, whichever version of LEAP was used. If the firm wants them on the file in the new system, they are saved to the matter before the freeze or handled as a separate mailbox exercise.

  4. Enquiries in LEAP CRM

    LEAP CRM keeps enquiries that have not become matters, with a record of calls and emails and the conflict details taken at first contact. They are not in the matter list. The firm decides whether open enquiries move to the new system’s intake tool and whether old ones are kept at all.

  5. Month end before cutover

    Trust accounting in LEAP includes an end-of-month process with reconciliation and statements. Cutover is timed so that process has been completed in LEAP for the final period. The closing trust balance on each matter is then the figure loaded, and it reads the same in the browser, the desktop program and the reports.

More about moving off LEAP 365

Where it is going

Neos expects personal injury data in its own tab structure, so loading a firm means deciding which tab each old record belongs on. Parties, insurance and counsel map directly from most injury systems. Money maps to value items. Anything the standard tabs lack becomes a user-defined field, which has to be created before the load.

  1. Every figure needs a value code

    Costs, medical bills, fees and settlement amounts are loaded as value items, and each carries a value code. The code list is agreed with the firm’s accounts staff first. A figure loaded under the wrong code is reported in the wrong place, so the list is tested on real cases before the bulk load.

  2. Lists are set up first

    Cases are loaded against case types, statuses and staff assignments that already exist in Neos. Those lists are set up, and the old system’s values tidied to match, before the trial load. Misspelt attorney names and unused case types in the source are cleaned out at the same stage.

  3. Documents go to sub-tabs

    Files land on the Case Docs tab under sub-tabs, which staff can view as a list or as folders. The old system’s folders or categories are mapped to a fixed set of sub-tabs. Without that, every personal habit of naming folders is reproduced and the folder view becomes hard to read.

  4. Reminders split two ways

    Neos fills its dashboards from checklists and case calendars. Old diary entries and tasks are sorted between them: dated appointments and court events to the calendar, and to-dos to the checklist. An item assigned to several people in the old system may need one named owner, and the firm chooses who.

  5. Assembly runs its own conversions

    Assembly migrates firms into Neos with its own team and tooling, and offers routes from self-service templates to a full conversion. Where the firm uses that service, outside help goes on the work around it: cleaning the source, checking the converted cases against the old system, and listing exceptions.

More about moving into Neos

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 Neos 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 LEAP 365 and checking each trial against LEAP 365.

  1. Analysis

    We read what LEAP 365 holds and how its records link, then agree with you, field by field, where each piece will sit in Neos. 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 LEAP 365, before extraction. It is not always possible to find every one, so some may carry across.

  3. Trial load

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

  4. Cutover

    Changes in LEAP 365 are frozen for an agreed window, the data is collected a final time and Neos 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 LEAP 365 as at the cutover date. LEAP 365 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 LEAP 365 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 fromLEAP 365
Moving toNeos

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 LEAP 365 holds

    What is in it, how its records link, and where each piece would sit in Neos. 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 Neos

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

Neos comes set up for injury work, so implementation is mostly choosing among its options and connecting the firm’s other tools. The lists that drive reporting are decided first, then checklists, then documents. Assembly provides its own implementation team, and the firm’s internal lead still has to make the decisions listed below.

Set-up decisions in Neos

  • Set case types, statuses and staff roles
  • Agree the value code list with accounts staff
  • Build checklists for each case type and stage
  • Create user-defined fields for data the tabs lack
  • Prepare document templates for the generation wizard
  • Connect Microsoft 365, QuickBooks and the phone system

Questions

LEAP 365 to Neos: what firms ask

We only use LEAP in the browser. Is the move simpler?

The data work is the same, because the records are held by LEAP either way. There is less to do on the firm’s computers, as no program has to be uninstalled. Training can be easier where the new system is also used in a browser, since staff already work that way.

Can we keep using LEAP 365 to look things up afterwards?

Only for as long as the firm’s LEAP agreement allows access. That is read from the agreement before notice is given. If access ends on a fixed date, the records the firm must keep, including trust and billing history, are exported as reports and documents before then and stored where the firm can reach them.

Do our matter numbers change?

They need not. LEAP’s matter number is loaded as the matter number in the new system where that system accepts one. Documents are matched to matters on that number, so it has to be unique. Any duplicates found in the analysis are corrected in LEAP before extraction.

Do trust balances in LEAP 365 have a place in Neos?

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 LEAP 365 before the plan is fixed. If Neos turns out to have no place for trust ledgers, they are kept as a readable archive and the firm decides where trust accounting runs.

What happens to records Neos has no place for?

On this route that is the firm’s accounts. They are exported from LEAP 365 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 LEAP 365 data is loaded into Neos?

Emails, time entries, billing records, custom fields and templates are carried with mapping, so each mapping is agreed with you first. Notes, tasks and trust ledgers 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

LEAP 365 and Neos are the names and marks of their owners, used here only to identify the two systems.

Moving from LEAP 365 to Neos?

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

We reply within one business day.