Data migration route
LEAP Desktop to iManage Cloud migration
LEAP Desktop is a practice management system that runs on the desktop and keeps its data in its maker’s cloud, and iManage Cloud is a cloud document management system. Documents and email move, filed under the matters they came from. Time, billing and trust have no place in a document system.
LEAP DesktopDesktop and cloud- Documents: Carried across
- Emails: Carried across
- Matters: Carried with mapping
- Custom fields: Carried with mapping
- Templates: Carried with mapping
- Notes: Confirmed in the analysis
- Tasks: Confirmed in the analysis
iManage CloudCloud- 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
- Intake: Kept as a readable archive
- 2 carried
- 3 mapped
- 2 to confirm
- 7 archived
What moves
What moves from LEAP Desktop to iManage Cloud
Each row is a kind of record LEAP Desktop holds, whether iManage Cloud has a place for it, and what is planned. On this route two kinds of record carry across, three kinds need mapping, seven kinds have no place in iManage Cloud 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. | Has a place in partAs a workspace with client and matter metadata. Parties and status stay in practice management. | Carried with mapping |
| ContactsClients, other parties and referrers | HeldHeld as cards and attached to matters. | No place | 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 placeEach needs a workspace and valid client and matter values; its class sets default security. | Carried across |
| EmailsEmails saved to matters or to the store | HeldSaved to the matter through the Outlook integration. | Has a placeLoaded as email documents into the workspace’s email folders. | Carried across |
| NotesFile notes, matter notes and contact notes | To be confirmed | No placeFile notes can be loaded as documents on the matter. | Confirmed in the analysis |
| CalendarAppointments, court dates and deadlines | Held in partCritical dates on matters; other calendar records are confirmed in the analysis. | No place | Kept as a readable archive |
| TasksTo-dos and workflow steps assigned to people | To be confirmed | No placeiManage Tracker is a separate product with its own set-up. | 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. | Has a place in partA fixed number of custom profile fields, each a validated list. | Carried with mapping |
| 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 documents. Automation is rebuilt in the firm’s drafting tools. | 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
- iManage Cloud has a place for this kind of record. It is loaded there and checked against LEAP Desktop.
- Carried with mapping
- iManage Cloud 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
- iManage Cloud 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 documents move. The accounts do not.
Moving from a matter system into a document management system is a documents job. iManage Cloud has no place for time, invoices or trust, so there is no financial cutover on this route. What it does want is structure. Every document from LEAP Desktop is filed into a workspace or folder for its client and matter, with a profile that says what it is. The client and matter list becomes that structure, which is why it is cleaned before any file is copied.
A document’s own details count for more here than anywhere. Created and modified dates, author, document type and version become searchable profile fields, and a wrong date on a few thousand files is hard to undo. Email filed to matters is carried as messages. Document copies can be run again, so the trial is repeated until counts and dates agree. Matter data that iManage Cloud cannot hold goes to whatever replaces LEAP Desktop for matters and billing, or into an archive.
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 iManage Cloud 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 iManage Cloud
Administrators of an iManage Cloud library have API access only, so nothing is loaded by writing to a database. For cloudimanage.com, the newer of its two cloud platforms, iManage lists a supervised import API, sync APIs and a metadata loader. Nothing can be filed loose: every document goes into a workspace, with valid client and matter values. So the client and matter lists, the workspace template and the security groups are built first.
Client and matter lists first
Custom1 and custom2 are validated lists, with each matter a child of its client. A value that is not already in the list cannot be assigned to a document. The lists are loaded from the practice management system or the old document store before any content, closed matters with documents included.
One workspace per matter
Each matter gets a workspace generated from a template, so the template is designed before migration: its tabs, its folders, which are created up front and which on demand. Old folder trees rarely match it. The mapping says where each old folder lands and what happens to folders with no equivalent.
Authors must be known users
Author and operator are profile fields tied to users of the library. Documents written by people who left years ago need a decision: recreate those people as inactive users, or assign a placeholder author. That choice affects searching by author for as long as the firm uses the system.
Hybrid security
iManage calls its security model hybrid: where a user’s groups disagree, the most permissive access applies unless one of them is denied. On cloudimanage.com that model cannot be changed. Default security is normally set on the workspace and inherited below it. Restricted matters from the old system are loaded with their access list already in place.
New numbers, original dates
Documents are numbered by iManage as they are loaded, so old numbers do not carry over as numbers. On cloudimanage.com the file date setting is fixed to the file’s own date, and on imanage.work it can be set either way. Which dates display is checked on the trial load. The old reference can be carried in a custom field or the description where the firm wants to search by it.
How NewLaw runs it
Four steps, in this order.
Nothing financial lands in iManage Cloud 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 iManage Cloud. 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 iManage Cloud 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 iManage Cloud. 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 iManage Cloud
Loaded data is not yet a working system. This is what NewLaw sets up in iManage Cloud, beyond the migration, so that people can work in it from the first day.
Setting up iManage Cloud is mostly design work done before any user logs in: how many libraries, what a workspace looks like, which profile fields are captioned for what, and who can see which matters. Then come the links that keep it running day to day, such as creating a workspace when a matter is opened in the practice management system, and the add-ins on each desk.
Set-up decisions in iManage Cloud
- Library structure and captions for client, matter and other fields
- Workspace templates, folder names and Flexible Folders rules by practice area
- Document classes, subclasses and the profile fields each one requires
- Roles, groups, default security and walls for restricted matters
- Workspace creation fed from the practice management system’s matter list
- Work Desktop, Outlook email filing and Mobility on each device, with training
Questions
LEAP Desktop to iManage Cloud: 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 iManage Cloud?
No. iManage Cloud 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 iManage Cloud has no place for?
On this route that is contacts, calendar entries, time entries, billing records, trust ledgers, the firm’s accounts 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 iManage Cloud?
Matters, 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 decides which closed matters and how many versions of a document are in scope.
Other routes
Other routes from LEAP Desktop and into iManage Cloud
Other destinations from LEAP Desktop
Other systems that move into iManage Cloud
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 iManage Cloud are the names and marks of their owners, used here only to identify the two systems.
Moving from LEAP Desktop to iManage Cloud?
Tell us what you are moving. You get a plan and a fixed price after the analysis.
We reply within one business day.