Data migration route
LEAP Desktop to Smokeball migration
LEAP Desktop and Smokeball are each a practice management system that runs on the desktop and keeps its data in its maker’s cloud. Both run a whole practice, so this is a full move, and the financial records set the timetable.
LEAP DesktopDesktop and cloud- Matters: Carried across
- Contacts: Carried across
- Documents: Carried across
- Emails: Carried across
- Calendar: Carried across
- Time and expenses: Carried across
- Billing: Carried across
- Intake: Carried across
- Trust money: Carried with mapping
- Custom fields: Carried with mapping
- Templates: Carried with mapping
- Notes: Confirmed in the analysis
- Tasks: Confirmed in the analysis
SmokeballDesktop and cloud- Firm accounts: Kept as a readable archive
- 8 carried
- 3 mapped
- 2 to confirm
- 1 archived
What moves
What moves from LEAP Desktop to Smokeball
Each row is a kind of record LEAP Desktop holds, whether Smokeball has a place for it, and what is planned. On this route eight kinds of record carry across, three kinds need mapping, one kind has no place in Smokeball and is archived and two kinds are confirmed in the analysis.
| Record | What is planned | ||
|---|---|---|---|
| MattersMatters or cases, with their numbers, types, parties and status | HeldElectronic matters built on LEAP’s pre-configured matter types. | Has a placeEach needs a Smokeball matter type; leads import alongside matters. | Carried across |
| ContactsClients, other parties and referrers | HeldHeld as cards and attached to matters. | Has a placeMatter roles import on the Grow and Prosper+ plans only. | Carried across |
| DocumentsFiles stored in or linked from the system | HeldDocuments, correspondence, searches and forms are stored in the matter. | Has a placeFiles and folders import into a matter with the folder structure kept. | Carried across |
| EmailsEmails saved to matters or to the store | HeldSaved to the matter through the Outlook integration. | Has a placeKept in the matter with other files. | Carried across |
| NotesFile notes, matter notes and contact notes | To be confirmed | Has a placeAs memos; not importable on the Bill plan. | Confirmed in the analysis |
| CalendarAppointments, court dates and deadlines | Held in partCritical dates on matters; other calendar records are confirmed in the analysis. | Has a placeCalendar events and critical dates; plan limits apply. | Carried across |
| TasksTo-dos and workflow steps assigned to people | To be confirmed | Has a placeNot importable on the Bill plan. | Confirmed in the analysis |
| Time and expensesTime and expense entries, billed and unbilled | HeldTimesheet entries and automatic time recording. | Has a placeUnbilled time, fee and expense entries, with activity codes. | Carried across |
| BillingInvoices, payments and debtor balances | Held | Has a placeInvoices and billed invoice entries are on the import list. | Carried across |
| Trust moneyTrust or client account ledgers and balances | HeldIn-built trust accounting, including controlled money. | Has a place in partMatter account balances load as opening balances; past transactions are not on the import list. | Carried with mapping |
| Firm accountsGeneral ledger, office account and payables | Held in partAn office accounting module, with integrations to Xero and MYOB. | No placeNo general ledger; the firm’s books stay in an accounting package. | Kept as a readable archive |
| Custom fieldsFields and record types the firm added itself | Held in partMatter tables and custom matter types; fields otherwise come from LEAP’s matter types. | Has a place in partValues need a matching field in the matter type’s layouts. | Carried with mapping |
| TemplatesPrecedents, document templates and automation | HeldLEAP’s forms library, the firm’s own precedents and a Clause Library. | Has a placeFirm precedents are rebuilt as Smokeball templates. | Carried with mapping |
| IntakeLeads, enquiries, intake forms and pipelines | HeldLEAP CRM records enquiries and converts them to matters. | Has a placeLeads are a record type of their own and can be converted to matters. | Carried across |
What the plans mean
- Carried across
- Smokeball has a place for this kind of record. It is loaded there and checked against LEAP Desktop.
- Carried with mapping
- Smokeball 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
- Smokeball has no place for it. It is exported in a format that opens without LEAP Desktop 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
The whole practice moves, accounts included.
A move between two practice management systems is the widest kind there is. LEAP Desktop and Smokeball each keep matters, contacts, documents, time and money in one place, but no two systems link those records the same way. In one, a client is a contact with a role on the matter. In another, every matter carries its own client card. Most of the analysis goes into those links, because a matter that arrives without its client or its documents is the first thing staff find.
The financial side decides the dates. Unbilled time, debtor balances and trust ledgers have to agree with LEAP Desktop’s own reports as at one day, and a new system usually wants them as opening balances, not as years of transactions. So the firm decides early how much history comes across as live records and how much is kept as reports. Matter and document loads can be repeated until they are right. The money is loaded once.
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 Smokeball are finished.
Where the data is now
Leaving LEAP Desktop
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.
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.
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.
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.
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.
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.
Where it is going
Arriving in Smokeball
Smokeball has a data import tool that reads spreadsheets of staff, contacts, matters, balances, unbilled time, invoices, memos, tasks and calendar events. Some of those are only available on the higher plans. Documents are brought in separately, with their folders. Before the first trial, every incoming matter is given a Smokeball matter type, since nothing else about the matter can be placed without one.
Every matter needs a type
Smokeball’s matter types are specific to an area of law and a state or jurisdiction, and each brings its own fields. The old system’s matter types are mapped to them one by one. It is worth getting right the first time: changing a matter’s type later can drop the details held in layouts the new type does not have.
The plan decides what loads
Matter roles, tags, critical dates and archive details import only on the Grow and Prosper+ plans. Memos, tasks and calendar events do not import on the Bill plan. The firm’s plan is confirmed before the mapping is written, so nobody maps the other side’s solicitor to a role that the subscription cannot hold.
Leave auto-numbering until after
Smokeball’s guidance for firms still bringing matters in is to wait before setting up automatic Internal References. Imported matters arrive with the numbers they already had. Once the load is accepted, the reference format and the counter’s starting number are set so the first new matter follows on from the last old one.
Documents arrive by folder
Importing a folder into a matter keeps its subfolders, and default folders can also be defined per matter type. The firm decides which wins where they differ: the old structure as it was, or its new standard layout with old folders mapped into it.
An opening balance per matter
Matter account balances are on the import list, along with unbilled time and expenses, invoices and billed invoice entries. Past trust transactions are not on that list. The trust position is therefore loaded as an opening balance for each matter and rehearsed on a full trial, with the transaction history kept in the old system.
How NewLaw runs it
Four steps, in this order.
Trust money moves on this route, so the trust cutover gets a rehearsal of its own.
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 Smokeball. Anything with no place there comes across as a note or stays behind, and you see which before the move.
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.
Trial load
The data is loaded into Smokeball as a trial and checked against LEAP Desktop: record counts, trust and debtor totals, the links between records, document dates. Exceptions are listed for you to decide.
Cutover
Changes in LEAP Desktop are frozen for an agreed window, the data is collected a final time and Smokeball goes live over a weekend. The trust and financial cutover is rehearsed on a full trial load first, because it cannot be re-run the way a document load can. 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
What happens after you send it
- A free first call
We go through your answers with you and ask about anything they leave open.
- An analysis of what LEAP Desktop holds
What is in it, how its records link, and where each piece would sit in Smokeball. Anything with no place there comes across as a note or stays behind, and you see which before the move.
- 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 Smokeball
Loaded data is not yet a working system. This is what NewLaw sets up in Smokeball, beyond the migration, so that people can work in it from the first day.
A Smokeball set-up is partly on the firm’s PCs and partly in firm settings. The desktop app and its Word and Outlook add-ins go on each Windows machine. In settings, the firm chooses the matter types it will use, defines default folders for each and sets its numbering. Trust accounts and the accounting connection are configured before the first invoice is raised.
Set-up decisions in Smokeball
- Matter types in use, with default document folders for each
- Internal Reference format and the starting number for new matters
- Trust account details and the link to the accounting package
- Staff roles and permissions, including who sees billing and trust
- Firm precedents and letterhead rebuilt as Smokeball templates
- Desktop app, Word and Outlook add-ins on every PC
Questions
LEAP Desktop to Smokeball: 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 Smokeball?
In part. Matter account balances load as opening balances; past transactions are not on the import list. The analysis sets out which trust records have a place in Smokeball and which are kept as an archive, and the trust cutover is rehearsed on a full trial load before the real one.
What happens to records Smokeball has no place for?
On this route that is the firm’s accounts. They are exported from LEAP Desktop 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 Desktop data is loaded into Smokeball?
Trust ledgers, custom fields and templates are carried with mapping, so each mapping is agreed with you first. Notes and tasks are confirmed in the analysis. The firm also sets the cutover date and how much financial history comes across as live records.
Other routes
Other routes from LEAP Desktop and into Smokeball
Other destinations from LEAP Desktop
Other systems that move into Smokeball
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.
Choose your systems
Technology stack selection
Decide which practice management system your firm runs, with the evidence and the cost beside it.
About four weeks for a firm of about 15 people. Fixed price, set after a free first call.
Move your data
Data migration
Your data is cleaned up before anything moves, then a trial load is checked against the old system.
Fixed price, agreed after the analysis.
Set up your new system
Implementation
Your new system set up around the way your firm works: configuration, document automation and training.
A small firm of 1 to 10 users typically takes 4 to 8 weeks. A mid-sized firm of 10 to 50 users takes 8 to 16 weeks.
Put AI to work
AI advisory and enablement
A small group of your people learn to use an approved AI tool on real work, under written rules.
Two to four weeks for a small first group. Fixed price, set after a free first call.
LEAP Desktop and Smokeball are the names and marks of their owners, used here only to identify the two systems.
Moving from LEAP Desktop to Smokeball?
Tell us what you are moving. You get a plan and a fixed price after the analysis.
We reply within one business day.