Data migration route
LEAP Desktop to Google Drive migration
LEAP Desktop is a practice management system that runs on the desktop and keeps its data in its maker’s cloud, and Google Drive is cloud file storage. Documents move into a folder for each client and matter, and the data behind them is kept as an export.
LEAP DesktopDesktop and cloud- Documents: Carried across
- Emails: Carried with mapping
- Templates: Carried with mapping
- Notes: Confirmed in the analysis
- Tasks: Confirmed in the analysis
Google DriveCloud- Matters: Kept as a readable archive
- Contacts: Kept as a readable archive
- Calendar: Kept as a readable archive
- Time and expenses: Kept as a readable archive
- Billing: Kept as a readable archive
- Trust money: Kept as a readable archive
- Firm accounts: Kept as a readable archive
- Custom fields: Kept as a readable archive
- Intake: Kept as a readable archive
- 1 carried
- 2 mapped
- 2 to confirm
- 9 archived
What moves
What moves from LEAP Desktop to Google Drive
Each row is a kind of record LEAP Desktop holds, whether Google Drive has a place for it, and what is planned. On this route one kind of record carries across, two kinds need mapping, nine kinds have no place in Google Drive and are 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. | No placeA matter is a folder inside a shared drive. | Kept as a readable archive |
| ContactsClients, other parties and referrers | HeldHeld as cards and attached to matters. | No placeContacts belong in Google Contacts, not Drive. | Kept as a readable archive |
| DocumentsFiles stored in or linked from the system | HeldDocuments, correspondence, searches and forms are stored in the matter. | Has a placeAny file type, stored as uploaded or converted to Google formats. | Carried across |
| EmailsEmails saved to matters or to the store | HeldSaved to the matter through the Outlook integration. | Has a place in partAs .eml or .msg files in the matter folder; not as Gmail messages. | Carried with mapping |
| NotesFile notes, matter notes and contact notes | To be confirmed | Has a place in partAs a Doc or Word file in the matter’s folder. | Confirmed in the analysis |
| CalendarAppointments, court dates and deadlines | Held in partCritical dates on matters; other calendar records are confirmed in the analysis. | No placeCalendar entries belong in Google Calendar. | Kept as a readable archive |
| TasksTo-dos and workflow steps assigned to people | To be confirmed | No place | Confirmed in the analysis |
| Time and expensesTime and expense entries, billed and unbilled | HeldTimesheet entries and automatic time recording. | No place | Kept as a readable archive |
| BillingInvoices, payments and debtor balances | Held | No place | Kept as a readable archive |
| Trust moneyTrust or client account ledgers and balances | HeldIn-built trust accounting, including controlled money. | No place | Kept as a readable archive |
| Firm accountsGeneral ledger, office account and payables | Held in partAn office accounting module, with integrations to Xero and MYOB. | No place | 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. | No place | Kept as a readable archive |
| TemplatesPrecedents, document templates and automation | HeldLEAP’s forms library, the firm’s own precedents and a Clause Library. | Has a place in partPrecedents load as files; the load does not rebuild Word automation in Docs. | Carried with mapping |
| IntakeLeads, enquiries, intake forms and pipelines | HeldLEAP CRM records enquiries and converts them to matters. | No place | Kept as a readable archive |
What the plans mean
- Carried across
- Google Drive has a place for this kind of record. It is loaded there and checked against LEAP Desktop.
- Carried with mapping
- Google Drive 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
- Google Drive 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
Out of the system, into folders the firm can read.
File storage has folders and files and nothing else. Moving from LEAP Desktop into Google Drive means turning matters into a folder tree, usually client, then matter, then the folders used inside it. The naming rule is agreed first, because it is hard to change once thousands of folders exist: whether the matter number leads, how closed matters are separated, what happens to characters Google Drive does not allow in a name.
Everything that is not a document needs somewhere to go. Contacts, notes, time, invoices and trust ledgers have no place in a folder, so they are exported as spreadsheets and reports and stored alongside, often as a summary file in each matter folder and a full set in an archive area. Firms choose this route to keep a readable copy of a system they are retiring, or as a staging step. The export is checked either way: folders against matters, files against the document register in LEAP Desktop.
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 Google Drive 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 Google Drive
Putting a firm’s matter files into Google Drive means choosing shared drives over personal ones and then deciding how many shared drives there should be. That second decision is driven by Google’s limits and by who is allowed to see what, since access is granted mainly at the level of the whole shared drive.
Shared drives, not My Drive
Files loaded into a shared drive belong to the firm and remain when the person who loaded them leaves. Anything loaded into someone’s My Drive belongs to that person. Matter files therefore go to shared drives, and My Drive is left for personal working papers.
One drive cannot hold everything
Google caps a shared drive at 500,000 items, counting folders, shortcuts and anything in the trash, and at 100 levels of nested folders. A firm with twenty years of matters can pass the item cap in a single drive. The split is planned up front, commonly by practice group, or by open and closed matters.
Membership is the main control
Every member of a shared drive can see all of it unless a Manager restricts a particular folder. Matters that only certain people may open are simpler to protect in a shared drive of their own. The firm supplies the list of restricted matters and partners’ private folders before the drives are created.
The daily upload limit
Each user can upload 750 GB to Drive in 24 hours, and then has to wait. For a large document set that limit sets the shortest time the load can take. The total size is measured in the analysis, so the firm knows before the freeze whether its documents fit inside a weekend.
Keep Office files as Office files
Word and Excel files can be stored in Drive as they are or converted to Google formats. Unless the firm asks otherwise they are loaded unconverted, so court documents and automated precedents arrive as they left. The firm decides afterwards which templates are worth rebuilding as Google Docs.
How NewLaw runs it
Four steps, in this order.
Nothing financial lands in Google Drive on this route, which makes it repeatable: a load can be run again until it is right.
Analysis
We read what LEAP Desktop holds and how it is organised, then agree with you where each kind of record will sit in Google Drive. Anything with no place there stays behind or is archived, and you see which before the move.
Clean-up
Duplicate clients, matters and folders are merged where they can be identified, and naming is put into one format, before anything is copied. It is not always possible to find every one, so some may carry across.
Trial load
A trial is loaded into Google Drive and checked against LEAP Desktop: record and file counts, the links between records, document dates, and a sample opened by your own people. Exceptions are listed for you to decide.
Cutover
There is no financial cutover on this route. After a short freeze on changes in LEAP Desktop, a final pass over a weekend picks up what changed since the trial. 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 Google Drive. 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
Structure, permissions and handover
Google Drive is storage, not an application, so there is no product to configure. What is agreed and set up is the folder structure, who can open what, and how the result is handed to the firm.
A Drive set-up for a law firm is a small number of deliberate choices made in the Workspace Admin console and then left alone. Which shared drives exist, who manages each, whether staff may share outside the firm, and whether people work from the browser or from Drive for desktop. Staff also need to be shown where a new matter folder goes.
What is agreed and set up
- Shared drives by practice group, with a naming pattern
- Managers and member access levels for each shared drive
- External sharing rules set in the Admin console
- Drive for desktop on PCs that need Explorer access
- A standard subfolder set copied into every new matter
- Transfer of leavers’ My Drive files as a standing procedure
Questions
LEAP Desktop to Google Drive: 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 Google Drive?
No. Google Drive does not keep trust ledgers. Trust records from LEAP Desktop are exported as ledgers and statements that open without it, and the firm settles where its trust accounting runs from the cutover date before the move is planned.
What happens to records Google Drive has no place for?
On this route that is matters, contacts, calendar entries, time entries, billing records, trust ledgers, the firm’s accounts, custom fields and intake records. 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 Google Drive?
Emails 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 decides which closed matters and how many versions of a document are in scope.
Other routes
Other routes from LEAP Desktop and into Google Drive
Other destinations from LEAP Desktop
Other systems that move into Google Drive
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 Google Drive are the names and marks of their owners, used here only to identify the two systems.
Moving from LEAP Desktop to Google Drive?
Tell us what you are moving. You get a plan and a fixed price after the analysis.
We reply within one business day.