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

Data migration route

LEAP Desktop to SmartAdvocate migration

LEAP Desktop is a practice management system that runs on the desktop and keeps its data in its maker’s cloud, and SmartAdvocate 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 DesktopDesktop and cloud
  1. Matters: Carried across
  2. Contacts: Carried across
  3. Documents: Carried across
  4. Emails: Carried across
  5. Calendar: Carried across
  6. Time and expenses: Carried across
  7. Intake: Carried across
  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
  14. Firm accounts: Confirmed in the analysis
ToSmartAdvocateCloud
  • 7 carried
  • 3 mapped
  • 4 to confirm
What the two products hold. The analysis confirms it field by field.

What moves

What moves from LEAP Desktop to SmartAdvocate

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

Records in LEAP Desktop and their place in SmartAdvocate
RecordIn LEAP DesktopIn SmartAdvocateWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldElectronic matters built on LEAP’s pre-configured matter types.Has a placeCases by case type, with master and member relationships.Carried across
ContactsClients, other parties and referrersHeldHeld as cards and attached to matters.Has a placeCarried across
DocumentsFiles stored in or linked from the systemHeldDocuments, correspondence, searches and forms are stored in the matter.Has a placeDocuments page, by category and subcategory.Carried across
EmailsEmails saved to matters or to the storeHeldSaved to the matter through the Outlook integration.Has a placeEmails are attached to cases.Carried across
NotesFile notes, matter notes and contact notesTo be confirmedHas a placeConfirmed in the analysis
CalendarAppointments, court dates and deadlinesHeld in partCritical dates on matters; other calendar records are confirmed in the analysis.Has a placeAppointments and critical deadlines.Carried across
TasksTo-dos and workflow steps assigned to peopleTo be confirmedHas a placeConfirmed in the analysis
Time and expensesTime and expense entries, billed and unbilledHeldTimesheet entries and automatic time recording.Has a placeTracked time entries.Carried across
BillingInvoices, payments and debtor balancesHeldHas a place in partInvoices for hourly matters. Past invoices are scoped in the analysis.Carried with mapping
Trust moneyTrust or client account ledgers and balancesHeldIn-built trust accounting, including controlled money.To be confirmedConfirmed in the analysis
Firm accountsGeneral ledger, office account and payablesHeld in partAn office accounting module, with integrations to Xero and MYOB.To be confirmedConfirmed in the analysis
Custom fieldsFields and record types the firm added itselfHeld in partMatter tables and custom matter types; fields otherwise come from LEAP’s matter types.Has a place in partConfirmed in the analysis for each field with no standard home.Carried with mapping
TemplatesPrecedents, document templates and automationHeldLEAP’s forms library, the firm’s own precedents and a Clause Library.Has a place in partTemplates are rebuilt with SmartAdvocate merge codes.Carried with mapping
IntakeLeads, enquiries, intake forms and pipelinesHeldLEAP CRM records enquiries and converts them to matters.Has a placeIntake and lead records.Carried across

What the plans mean

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

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 SmartAdvocate. 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 Desktop has to be given a case type in SmartAdvocate, and that choice drives which fields and workflows it gets. The mapping is agreed type by type. Financial history with no place in SmartAdvocate is exported as reports and ledgers the firm can open without LEAP Desktop, 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 Desktop 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 Desktop is kept running until the checks on SmartAdvocate are finished.

Where the data is now

LEAP runs on the PC but keeps the firm’s data in its own cloud, so there is no database in the office to copy. The move is planned around the export: what LEAP provides, in what format, and by when. A firm leaving LEAP is also replacing things LEAP supplied, such as its matter types, court forms and the forms library.

  1. Nothing to copy from the office

    The desktop program synchronises with LEAP’s servers. What sits on the PC is a working copy, not the firm’s record. A complete set of matters, cards, documents and accounting data has to come from LEAP’s side. We ask early how that export is delivered, and check the first copy against LEAP’s own reports before relying on it.

  2. Cards, and the same person twice

    LEAP calls a contact a card. A card is attached to a matter, and the same person can end up with several: once as a client, again as the other side on someone else’s matter. Cards are compared on name, address, email and phone, and merged in LEAP before extraction where they are clearly one person.

  3. Matter types came from LEAP

    A matter’s detail fields come from its LEAP matter type, and LEAP maintains more than a thousand of them. The destination will not have the same types or the same fields. Each type the firm really uses is mapped, and fields with no home are brought across as a note or left behind, as agreed beforehand.

  4. Forms stay, precedents are rebuilt

    Court and government forms in LEAP come from LEAP’s own library and stay with it. The firm’s own precedents move. Their merge fields are LEAP’s, so each one is replaced with the new system’s equivalent. Clause Library content is listed too, because it is easy to forget until someone goes looking for a clause.

  5. Office accounts: module or package

    Trust accounting is inside LEAP. Office accounting may be in LEAP’s office module or in Xero or MYOB through the integration. We establish which before anything else financial is planned, because it decides whether the firm’s own books are part of the move or only the trust ledgers and debtor balances.

More about moving off LEAP Desktop

Where it is going

SmartAdvocate keeps injury detail in structured fields and screens, so mapping counts for more than usual: the more precisely the old data is placed, the more of those screens are filled on the first day. Parties, incidents, insurers, providers and bills are loaded to their own screens, and the vendor’s implementation team runs conversions into it.

  1. Map to fields, not notes

    The case summary, dashboards and settlement screen read from structured fields. Injury details, insurance limits and provider bills dumped into a note leave those screens empty. The mapping takes each old field to its SmartAdvocate counterpart, and only what truly has no counterpart is loaded as a note.

  2. Case types and statuses

    Cases are loaded against case types and statuses that drive WorkPlans and reports. These are agreed with the firm before the trial load, and old statuses are translated to the new list. A status with no match is not guessed at. It is listed, and someone who knows the files decides.

  3. Document categories

    Documents are searched by category, subcategory, sender, recipient and date as well as by folder. The old system’s folders are translated into categories on the way in. Files that arrive uncategorised can still be found by description, but they fall outside the category views staff are trained to use.

  4. Working with the vendor’s conversion

    SmartAdvocate’s implementation team converts client data into the system and trains staff through its own classes. The firm’s side of that is supplying a clean source, checking the converted cases against the old system, and deciding what to do with the exceptions. Independent help is used on those tasks.

  5. Choosing Server or Cloud

    The firm decides before loading whether it will run the Server edition on its own Windows server or use the hosted Cloud edition. Either way the data load is the same. What differs is who looks after backups, updates and remote access afterwards, and that is settled with the firm’s IT provider.

More about moving into SmartAdvocate

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 SmartAdvocate 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 Desktop and checking each trial against LEAP Desktop.

  1. Analysis

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

  3. Trial load

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

  4. Cutover

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

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 Desktop holds

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

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

Setting up SmartAdvocate is a matter of deciding how much of its detail the firm will use from the start. Case types, statuses and WorkPlans come first because they drive everything else. Templates follow. The vendor trains staff through its own classes, and the decisions below are best made before the first of those.

Set-up decisions in SmartAdvocate

  • Choose the Server or Cloud edition with IT
  • Define case types, statuses and staff roles
  • Build WorkPlans and Automated Procedures for each case type
  • Convert letters and forms into templates with merge codes
  • Install the Outlook plugin and agree email filing habits
  • Set up intake screens, lead sources and dashboards

Questions

LEAP Desktop to SmartAdvocate: what firms ask

Is LEAP Desktop different from LEAP 365 for a migration?

No. They are two ways into the same LEAP account, and the data is the same whichever one staff use. One migration covers both. The only practical difference is on the PCs: the desktop program and its Office integration are removed once the firm no longer needs read-only access.

What happens to our closed matters?

They can move in full, move as documents only, or stay in the archive. A common pattern is that open matters and recent closed ones move as full records, and older files come across as documents attached to a matter shell. How long LEAP access continues after notice is read from the firm’s agreement.

Will trust history come across?

Balances move. Each matter’s trust balance is loaded as an opening balance and checked against LEAP’s trust reports at the cutover date. The transactions behind those balances normally stay in the old record or in exported reports, because few systems accept another system’s trust history as live ledger entries.

Do trust balances in LEAP Desktop have a place in SmartAdvocate?

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 Desktop before the plan is fixed. If SmartAdvocate 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 LEAP Desktop have a place in SmartAdvocate?

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

What has to be decided before LEAP Desktop data is loaded into SmartAdvocate?

Billing records, custom fields and templates are carried with mapping, so each mapping is agreed with you first. Notes, 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

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

Moving from LEAP Desktop to SmartAdvocate?

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

We reply within one business day.