Data migration route
LollyLaw to Clio Manage migration
LollyLaw is a cloud practice management system for immigration work. Clio Manage is a practice management system, run the same way. Both run a whole practice, so this is a full move, and the financial records set the timetable.
LollyLawCloud- Matters: Carried across
- Contacts: Carried across
- Documents: Carried across
- Calendar: Carried across
- Tasks: Carried across
- Time and expenses: Carried with mapping
- Billing: Carried with mapping
- Trust money: 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
Clio ManageCloud- Intake: Kept as a readable archive
- 5 carried
- 4 mapped
- 4 to confirm
- 1 archived
What moves
What moves from LollyLaw to Clio Manage
Each row is a kind of record LollyLaw holds, whether Clio Manage has a place for it, and what is planned. On this route five kinds of record carry across, four kinds need mapping, one kind has no place in Clio Manage and is 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 placeImported from a matters template, after contacts. | Carried across |
| ContactsClients, other parties and referrers | HeldContact records hold form data such as addresses, passport numbers and employment. | Has a placePeople and companies, with related contacts linked to matters by a separate template. | Carried across |
| DocumentsFiles stored in or linked from the system | HeldLollyDrive, with folders, labels and versions; other cloud drives can be linked. | Has a placeFiled under the matter; Clio scopes document migration separately from data. | Carried across |
| EmailsEmails saved to matters or to the store | To be confirmed | Has a placeHeld as communications on the matter, with phone logs. | Confirmed in the analysis |
| NotesFile notes, matter notes and contact notes | To be confirmed | Has a placeMatter notes and contact notes each have a template. | Confirmed in the analysis |
| CalendarAppointments, court dates and deadlines | Held in partWorkflows create deadlines and meetings; a full calendar was not confirmed. | Has a placeCalendar events have a migration template. | Carried across |
| TasksTo-dos and workflow steps assigned to people | HeldTasks come from workflows and can be assigned to staff or to clients. | Has a placeTasks have a migration template. | Carried across |
| Time and expensesTime and expense entries, billed and unbilled | Held | Has a place in partUnbilled time entries load; billed time entries do not, by Clio’s migration guide. | Carried with mapping |
| BillingInvoices, payments and debtor balances | HeldInvoices, online payments and custom payment plans. | Has a place in partAn outstanding balance loads as one line per matter; past invoices do not. | Carried with mapping |
| Trust moneyTrust or client account ledgers and balances | HeldShows the flow of funds between a matter’s trust and operating accounts. | Has a place in partA trust balance loads as one line per matter or contact; past transactions do not. | Carried with mapping |
| Firm accountsGeneral ledger, office account and payables | To be confirmed | No placeNot in Clio Manage. Books sit in a linked accounting package, or in Clio Accounting where Clio offers it. | Confirmed in the analysis |
| Custom fieldsFields and record types the firm added itself | To be confirmed | Has a placeCreated first, then filled from the custom field templates. | Confirmed in the analysis |
| TemplatesPrecedents, document templates and automation | Held in partGovernment forms and questionnaires; general document templates were not confirmed. | Has a placeRebuilt as Clio document templates with its merge fields. | Carried with mapping |
| IntakeLeads, enquiries, intake forms and pipelines | HeldOnboarding questionnaires sent by email or text, in more than 20 languages. | No placeLeads and intake forms belong in Clio Grow. | Kept as a readable archive |
What the plans mean
- Carried across
- Clio Manage has a place for this kind of record. It is loaded there and checked against LollyLaw.
- Carried with mapping
- Clio Manage 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
- Clio Manage 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 whole practice moves, accounts included.
A move between two practice management systems is the widest kind there is. LollyLaw and Clio Manage 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 LollyLaw’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 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 Clio Manage 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 Clio Manage
Clio Manage is loaded through its migration templates, one spreadsheet per kind of record, imported in a fixed order with contacts first. Clio’s own migration guide is plain about the limit: balances come across, financial history does not. So a load into Clio is planned as records plus opening positions, with the old system kept for the history behind them.
Matters link by client name
The matters template ties each matter to its client by an exact match on first name, last name or company name. A client spelt two ways in the old system becomes two contacts, or a matter assigned to an unknown client. This is why contact clean-up is finished before the first trial load, not after it.
Decide the numbering scheme first
Clio numbers imported matters itself unless the account is set to manual numbering, in which case the old number is supplied in the template. That setting and the firm’s preferred scheme are decided before any matter is loaded. The Client Reference field is available for an old file number the firm still wants to see.
Balances, one line each
Under Clio’s standard migration, an outstanding balance arrives as one line per matter and a trust balance as one line per matter or contact. Past invoices, billed time, payments and trust transactions are listed as data that cannot be migrated. The trust total is reconciled against the old system’s closing report on the trial load.
Custom fields must exist
Matter and contact custom fields are created in Clio before their values are imported, each with a field type. Accounts set up for a particular practice area come with preconfigured fields and matter templates, which affects the mapping. We compare those with the old system’s fields and add only what is missing.
Rates and permissions by hand
Billable rates for users, clients and matters are not part of an import. Neither are user permissions or settings. They are entered in Clio during set-up from a schedule the firm confirms, and a sample of imported unbilled time is checked against that schedule before the trial load is signed off.
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 LollyLaw holds and how its records link, then agree with you, field by field, where each piece will sit in Clio Manage. 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 LollyLaw, before extraction. It is not always possible to find every one, so some may carry across.
Trial load
The data is loaded into Clio Manage as a trial and checked against LollyLaw: record counts, trust and debtor totals, the links between records, document dates. Exceptions are listed for you to decide.
Cutover
Changes in LollyLaw are frozen for an agreed window, the data is collected a final time and Clio Manage 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. 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 Clio Manage. 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 Clio Manage
Loaded data is not yet a working system. This is what NewLaw sets up in Clio Manage, beyond the migration, so that people can work in it from the first day.
Much of a Clio Manage set-up is firm-wide settings. The numbering scheme, practice areas, matter stages, billing preferences and trust accounts apply to everyone, so they are agreed once and early. Trust and accounting features are not the same in every country Clio sells in, so the firm’s own region is checked first. Document templates and custom fields follow. Email and document integrations are then installed for each user and tested on a real matter.
Set-up decisions in Clio Manage
- Matter numbering scheme, practice areas and matter stages
- Custom fields for matters and contacts, by practice area
- Document templates with merge fields, uploaded from Word or PDF
- Billing settings, user and client rates, and trust accounts
- Roles and permissions for each user
- Outlook add-in, Clio Drive and the accounting connection
Questions
LollyLaw to Clio Manage: 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 Clio Manage?
In part. A trust balance loads as one line per matter or contact; past transactions do not. The analysis sets out which trust records have a place in Clio Manage 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 Clio Manage has no place for?
On this route that is 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 Clio Manage?
Time entries, billing records, trust ledgers 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 sets the cutover date and how much financial history comes across as live records.
Other routes
Other routes from LollyLaw and into Clio Manage
Other destinations from LollyLaw
Other systems that move into Clio Manage
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 Clio Manage are the names and marks of their owners, used here only to identify the two systems.
Moving from LollyLaw to Clio Manage?
Tell us what you are moving. You get a plan and a fixed price after the analysis.
We reply within one business day.