Data migration route
LollyLaw to iManage Cloud migration
LollyLaw is a cloud practice management system for immigration work, 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.
LollyLawCloud- Documents: Carried across
- Matters: Carried with mapping
- Templates: Carried with mapping
- Emails: Confirmed in the analysis
- Notes: Confirmed in the analysis
- Firm accounts: Confirmed in the analysis
- Custom fields: Confirmed in the analysis
iManage CloudCloud- Contacts: Kept as a readable archive
- Calendar: Kept as a readable archive
- Tasks: 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
- Intake: Kept as a readable archive
- 1 carried
- 2 mapped
- 4 to confirm
- 7 archived
What moves
What moves from LollyLaw to iManage Cloud
Each row is a kind of record LollyLaw holds, whether iManage Cloud has a place for it, and what is planned. On this route one kind of record carries across, two kinds need mapping, seven kinds have no place in iManage Cloud and are archived and four kinds are confirmed in the analysis.
| Record | What is planned | ||
|---|---|---|---|
| MattersMatters or cases, with their numbers, types, parties and status | HeldImmigration matters with workflow steps, milestones and the forms attached to them. | 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 | HeldContact records hold form data such as addresses, passport numbers and employment. | No place | Kept as a readable archive |
| DocumentsFiles stored in or linked from the system | HeldLollyDrive, with folders, labels and versions; other cloud drives can be linked. | 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 | To be confirmed | Has a placeLoaded as email documents into the workspace’s email folders. | Confirmed in the analysis |
| 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 partWorkflows create deadlines and meetings; a full calendar was not confirmed. | No place | Kept as a readable archive |
| TasksTo-dos and workflow steps assigned to people | HeldTasks come from workflows and can be assigned to staff or to clients. | No placeiManage Tracker is a separate product with its own set-up. | Kept as a readable archive |
| Time and expensesTime and expense entries, billed and unbilled | Held | No place | Kept as a readable archive |
| BillingInvoices, payments and debtor balances | HeldInvoices, online payments and custom payment plans. | No place | Kept as a readable archive |
| Trust moneyTrust or client account ledgers and balances | HeldShows the flow of funds between a matter’s trust and operating accounts. | No place | Kept as a readable archive |
| Firm accountsGeneral ledger, office account and payables | To be confirmed | No place | Confirmed in the analysis |
| Custom fieldsFields and record types the firm added itself | To be confirmed | Has a place in partA fixed number of custom profile fields, each a validated list. | Confirmed in the analysis |
| TemplatesPrecedents, document templates and automation | Held in partGovernment forms and questionnaires; general document templates were not confirmed. | 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 | HeldOnboarding questionnaires sent by email or text, in more than 20 languages. | 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 LollyLaw.
- 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 LollyLaw 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 LollyLaw 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 LollyLaw 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 LollyLaw 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 LollyLaw is kept running until the checks on iManage Cloud are finished.
Where the data is now
Leaving LollyLaw
An immigration firm’s most valuable data in LollyLaw is not the matter list. It is the detail collected about each person so that forms could be filled: every address, passport, employer and family member. Moving off LollyLaw is mostly a question of whether the destination has fields for that detail, and what is done with it if it has not.
Form data on the contact
Names, addresses, passport numbers and employment are stored once on the contact and matter and then flow into each form. An immigration system will have matching fields, and the mapping is done field by field. A general practice system will not. There the data goes to custom fields, or the completed forms are kept as PDFs.
Receipt numbers
After an online filing, LollyLaw stores the USCIS receipt number against the case. Staff use those numbers every day to check status. They are treated as a must-have field in the analysis and are counted in the trial load, matter by matter, since a missing receipt number is not something a paralegal can easily look up again.
Workflows part-way through
Each case type runs on a workflow of tasks, deadlines and milestones, and an open matter is somewhere in the middle of one. Completed and outstanding steps can be carried as tasks. The workflow itself is rebuilt in the destination, and open matters are placed at the right step during the trial load.
LollyDrive and linked drives
Files uploaded to LollyDrive are in the vendor’s storage, with labels and a version trail. Anything reached through a linked Google Drive, Dropbox, OneDrive or Box account is held in that account, and whether a copy also sits in LollyDrive is checked in the analysis. The two sets are listed separately so that linked files are not counted as missing.
Payment plans in progress
Many immigration clients pay by instalments set up through LollyPayments. The schedule and the amounts already paid can be recorded in the new system. Stored card or bank details belong to the payment processor and do not transfer, so clients on a plan are contacted to authorise payments again.
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 LollyLaw 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 LollyLaw: 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 LollyLaw, a final pass over a weekend picks up what changed since the trial. LollyLaw 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 LollyLaw 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 LollyLaw 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
LollyLaw to iManage Cloud: what firms ask
We are moving to a general practice management system. What happens to the immigration forms?
Finished forms are kept as PDF documents on each matter. The data behind them needs a decision, because a general system has no passport or A-number fields of its own. A common answer is a set of custom fields for the items staff look up most, with the remainder left in the forms.
Do client questionnaire answers come across?
Where the answers were used to fill contact and matter fields, those fields move. A questionnaire as the client completed it, in their own language, is a separate record. Where the destination has nothing similar it is saved as a document on the matter so the original wording is not lost.
Can we move while cases are pending with USCIS?
Yes. Immigration matters run for years, so there is never a moment with nothing pending. What matters is that receipt numbers, filing dates and the next deadline for each open case are checked in the trial load against LollyLaw before the firm stops using it.
Do trust balances in LollyLaw have a place in iManage Cloud?
No. iManage Cloud does not keep trust ledgers. Trust records from LollyLaw 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, tasks, time entries, billing records, trust ledgers and intake records. They are exported from LollyLaw 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 LollyLaw data is loaded into iManage Cloud?
Matters and templates are carried with mapping, so each mapping is agreed with you first. Emails, notes, the firm’s accounts and custom fields 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 LollyLaw and into iManage Cloud
Other destinations from LollyLaw
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.
LollyLaw and iManage Cloud are the names and marks of their owners, used here only to identify the two systems.
Moving from LollyLaw 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.