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

Data migration route

LEAP 365 data to Full data export

LEAP 365 is a cloud practice management system, and Full data export 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 LEAP 365 holds and keeps it readable and open to queries.

FromLEAP 365Cloud
  1. Matters: Exported in full
  2. Contacts: Exported in full
  3. Documents: Exported in full
  4. Calendar: Exported in full
  5. Time and expenses: Exported in full
  6. Billing: Exported in full
  7. Trust money: Exported in full
  8. Emails: Exported with mapping
  9. Firm accounts: Exported with mapping
  10. Custom fields: Exported with mapping
  11. Templates: Exported with mapping
  12. Intake: Exported with mapping
  13. Notes: Confirmed in the analysis
  14. Tasks: Confirmed in the analysis
ToFull data exportFiles
  • 7 carried
  • 5 mapped
  • 2 to confirm
What the two products hold. The analysis confirms it field by field.

What moves

What moves from LEAP 365 to Full data export

Each row is a kind of record LEAP 365 holds, whether Full data export has a place for it, and what is planned. On this route seven kinds of record carry across, five kinds need mapping and two kinds are confirmed in the analysis.

Records in LEAP 365 and their place in Full data export
RecordIn LEAP 365In Full data exportWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldThe same electronic matters as the desktop program.Has a placeA matters table keyed by the original matter number.Exported in full
ContactsClients, other parties and referrersHeldCards, as in the rest of LEAP.Has a placeA contacts table and a table of each contact’s role on each matter.Exported in full
DocumentsFiles stored in or linked from the systemHeldStored in the matter on LEAP’s servers.Has a placeFiles under their original names, in client and matter folders.Exported in full
EmailsEmails saved to matters or to the storeHeldOnly emails that were saved to a matter.Has a place in partFiled emails as message files in the matter’s folder, if the source exposes them.Exported with mapping
NotesFile notes, matter notes and contact notesTo be confirmedHas a placeA notes table with matter, author and date for each note.Confirmed in the analysis
CalendarAppointments, court dates and deadlinesHeld in partCritical dates sit on the matter; anything further is confirmed in the analysis.Has a placeA table of appointments and key dates; nothing shows it as a diary.Exported in full
TasksTo-dos and workflow steps assigned to peopleTo be confirmedHas a placeA table of tasks with assignee, due date and status.Confirmed in the analysis
Time and expensesTime and expense entries, billed and unbilledHeldHas a placeA time entries table with fee earner, matter, units, rate and billed status.Exported in full
BillingInvoices, payments and debtor balancesHeldHas a placeInvoice, line and receipt tables; invoice PDFs can be kept beside them.Exported in full
Trust moneyTrust or client account ledgers and balancesHeldLEAP’s in-built trust accounting.Has a placeA trust transactions table; ledger reports can be kept as PDF beside it.Exported in full
Firm accountsGeneral ledger, office account and payablesHeld in partLEAP’s office accounting module, or Xero or MYOB through an integration.Has a place in partJournals and account balances, where the source held a general ledger.Exported with mapping
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 placeExtra columns under their original field names.Exported with mapping
TemplatesPrecedents, document templates and automationHeldLEAP’s forms library and the firm’s own precedents.Has a place in partTemplate files only; the merge fields in them will not run.Exported with mapping
IntakeLeads, enquiries, intake forms and pipelinesHeldEnquiries are recorded in LEAP CRM.Has a place in partAn enquiries table, where the source tracked leads.Exported with mapping

What the plans mean

Exported in full
Full data export has a place for this kind of record. It is loaded there and checked against LEAP 365.
Exported with mapping
Full data export 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 LEAP 365 out to Full data export 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 LEAP 365 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.

LEAP 365 is hosted by its maker and Full data export sits on equipment the firm controls. The data leaves a service that was backed up for the firm and arrives somewhere the firm must back up itself, so backup and access are arranged before the export is copied in. What LEAP 365 will release depends on its export tools, and that is confirmed in the analysis.

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

A full export is judged by whether a stranger can use it. In five years the question will be something like: what was the trust balance on this matter the day it closed, and where is the signed agreement. The export is planned backwards from questions of that kind, and it is checked against the live system while the live system can still be opened.

  1. Tables that still join up

    Each kind of record becomes its own table: matters, contacts, time entries, invoices, trust transactions. The identifiers that link them are kept in every table, so a time entry can still be traced to its matter and its fee earner. An export that keeps the rows and drops the keys cannot be rejoined later.

  2. Documents with an index

    Documents are written to folders by client and matter under their original names. On their own they can be found only by name. An index listing each file with its matter number, title, author, dates and path is what lets someone find the right version of a lease among forty thousand files without the old system’s search. What the index records is settled in the analysis.

  3. Reports a person can read

    Raw tables do not satisfy an auditor or a former client. The firm decides which reports are also printed to PDF from the old system as at the final date: trust ledgers, matter ledgers, debtor lists and issued invoices are the usual candidates. They cannot be regenerated once the licence ends.

  4. What an export does not keep

    Screens, workflows, document automation, saved searches and user permissions belong to the software and stay with it. Figures the system calculated on the fly, such as a matter’s unbilled total, exist in an export only if they were captured as a report. The firm is told which of these are being let go.

  5. Checked while the source is open

    Record counts and financial totals in the export are reconciled to the live system: number of matters, sum of trust balances, total debtors, document count per matter on a sample. This is done before the subscription lapses or the server is turned off, because afterwards there is nothing left to compare against.

More about moving into Full data export

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

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 Full data export. 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

Full data export 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.

With no product to configure, the set-up is custody, and the decisions are the firm’s. Someone there owns the export, knows where it is kept and can open it. Access needs restricting, because it contains every client’s affairs in one place with none of the old system’s security. The firm sets a destruction date from its retention obligations and decides how the next custodian will learn to use it.

What is agreed and set up

  • Folder layout for tables, documents and reports
  • What the key to tables, columns and identifiers records
  • Where the copies are stored and who is custodian
  • Who may open it, as approved by a partner
  • Which look-ups staff must be able to do unaided
  • Retention period and the date it is next reviewed

Questions

LEAP 365 to Full data export: 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.

Does the copy in Full data export hold trust ledgers from LEAP 365?

Yes. A trust transactions table; ledger reports can be kept as PDF beside it. Trust ledgers are written out with the rest, and counts and totals are agreed to the reports in LEAP 365 as at the export date.

Does everything in LEAP 365 have a place in Full data export?

Most of it does on paper. Notes 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 Full data export is kept as a readable archive, and you see which before the move.

What has to be decided before LEAP 365 is written out to Full data export?

Emails, the firm’s accounts, custom fields, templates and intake records are exported with mapping, so each mapping is agreed with you first. Notes 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

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

Moving from LEAP 365 to Full data export?

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

We reply within one business day.