Skip to content
NEWLAW.COM
+61 1300 495 281
Let’s talk

Data migration route

LollyLaw to Filevine migration

LollyLaw is a cloud practice management system for immigration work, and Filevine is a cloud case management system. Matter records move into cases, and the firm decides where its accounting runs from the cutover date.

FromLollyLawCloud
  1. Matters: Carried across
  2. Contacts: Carried across
  3. Documents: Carried across
  4. Calendar: Carried across
  5. Tasks: Carried across
  6. Time and expenses: Carried with mapping
  7. Billing: Carried with mapping
  8. Trust money: Carried with mapping
  9. Templates: Carried with mapping
  10. Intake: Carried with mapping
  11. Emails: Confirmed in the analysis
  12. Notes: Confirmed in the analysis
  13. Firm accounts: Confirmed in the analysis
  14. Custom fields: Confirmed in the analysis
ToFilevineCloud
  • 5 carried
  • 5 mapped
  • 4 to confirm
What the two products hold. The analysis confirms it field by field.

What moves

What moves from LollyLaw to Filevine

Each row is a kind of record LollyLaw holds, whether Filevine has a place for it, and what is planned. On this route five kinds of record carry across, five kinds need mapping and four kinds are confirmed in the analysis.

Records in LollyLaw and their place in Filevine
RecordIn LollyLawIn FilevineWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldImmigration matters with workflow steps, milestones and the forms attached to them.Has a placeLoaded as projects of a defined project type.Carried across
ContactsClients, other parties and referrersHeldContact records hold form data such as addresses, passport numbers and employment.Has a placeContact cards, linked to projects.Carried across
DocumentsFiles stored in or linked from the systemHeldLollyDrive, with folders, labels and versions; other cloud drives can be linked.Has a placeDocs section with folders. Templated project folders can be set per type.Carried across
EmailsEmails saved to matters or to the storeTo be confirmedHas a placeHeld in the activity feed of the project.Confirmed in the analysis
NotesFile notes, matter notes and contact notesTo be confirmedHas a placeHeld as notes in the activity feed.Confirmed in the analysis
CalendarAppointments, court dates and deadlinesHeld in partWorkflows create deadlines and meetings; a full calendar was not confirmed.Has a placeDeadlines and calendar events.Carried across
TasksTo-dos and workflow steps assigned to peopleHeldTasks come from workflows and can be assigned to staff or to clients.Has a placeCarried across
Time and expensesTime and expense entries, billed and unbilledHeldHas a place in partNeeds the Billing product enabled.Carried with mapping
BillingInvoices, payments and debtor balancesHeldInvoices, online payments and custom payment plans.Has a place in partNeeds the Billing product enabled.Carried with mapping
Trust moneyTrust or client account ledgers and balancesHeldShows the flow of funds between a matter’s trust and operating accounts.Has a place in partTrust accounts sit in Payments by Filevine. Loading history is confirmed in the analysis.Carried with mapping
Firm accountsGeneral ledger, office account and payablesTo be confirmedTo be confirmedConfirmed in the analysis
Custom fieldsFields and record types the firm added itselfTo be confirmedHas a placeCustom sections and fields per project type.Confirmed in the analysis
TemplatesPrecedents, document templates and automationHeld in partGovernment forms and questionnaires; general document templates were not confirmed.Has a place in partTemplates are rebuilt as Filevine document templates. They are not converted.Carried with mapping
IntakeLeads, enquiries, intake forms and pipelinesHeldOnboarding questionnaires sent by email or text, in more than 20 languages.Has a place in partLeads belong in Lead Docket, which passes signed clients to Filevine.Carried with mapping

What the plans mean

Carried across
Filevine has a place for this kind of record. It is loaded there and checked against LollyLaw.
Carried with mapping
Filevine 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.

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

Matters become cases. The ledgers need a home.

Going from a practice management system to a case management system is a move towards the file and away from the ledger. Matters, parties, documents, notes and deadlines have a natural place in Filevine. Time, invoices, trust and the general ledger often do not, or only in part, and the table above shows which. Before the move is planned the firm settles where billing and trust accounting will run, because that decides what is loaded and what is archived.

Case systems are usually built around a practice area, with their own stages, roles and document sets. A general matter from LollyLaw has to be given a case type in Filevine, and that choice drives which fields and workflows it gets. The mapping is agreed type by type. Financial history with no place in Filevine is exported as reports and ledgers the firm can open without LollyLaw, and kept as the record of what was billed and held.

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 Filevine are finished.

Where the data is now

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.

  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. 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.

More about moving off LollyLaw

Where it is going

Loading a firm into Filevine depends on the project types being built first. Until the sections and fields exist there is nowhere for the data to go, so configuration and migration are planned together. The old system’s parties, insurers, providers and key dates are mapped to sections, and its notes and emails are loaded into each project’s activity feed.

  1. Project types before data

    Each area of practice needs a project type with its sections, fields and phases defined in the Customs Editor. Changes made there apply to every project of that type. The types are drafted from the old system’s data, tested with a few real cases, and only then is the bulk load run.

  2. One contact card per person

    Contacts are held as contact cards. A doctor or adjuster who appears on many projects is best loaded as one card, not one for each project. Duplicates in the old system are merged before loading where they can be identified. Loading them as they are produces several cards for the same person, and staff then pick the wrong one when adding a party.

  3. Lists become collection items

    Anything the old system held as a list against a matter, such as providers, liens, insurance policies or expenses, is loaded as items in a collection section. Each column needs a matching field. Totals per project are compared with the old system afterwards, since those figures feed the settlement and disbursal sheets.

  4. History goes into the feed

    File notes, emails and completed tasks from the old system are loaded into the activity feed with their original dates and authors. Authors must exist as users or be recorded in the text. The feed is long on an old case, so staff are shown how to filter it before go-live.

  5. Billing is a separate switch

    The Billing section only appears once Billing is enabled for the firm. Time entries, invoices and trust balances from the old system need that in place before they can be loaded. A firm that leaves it off can still record case costs in a collection section built for the purpose.

More about moving into Filevine

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.

  1. Analysis

    We read what LollyLaw holds and how its records link, then agree with you, field by field, where each piece will sit in Filevine. Anything with no place there comes across as a note or stays behind, and you see which before the move.

  2. 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.

  3. Trial load

    The data is loaded into Filevine 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.

  4. Cutover

    Changes in LollyLaw are frozen for an agreed window, the data is collected a final time and Filevine 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

Step 1 of 5: Start with the route

Moving fromLollyLaw
Moving toFilevine

The route comes from this page. Four short steps follow. Nothing you send commits your firm to anything.

What happens after you send it

  1. A free first call

    We go through your answers with you and ask about anything they leave open.

  2. An analysis of what LollyLaw holds

    What is in it, how its records link, and where each piece would sit in Filevine. Anything with no place there comes across as a note or stays behind, and you see which before the move.

  3. 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 Filevine

Loaded data is not yet a working system. This is what NewLaw sets up in Filevine, beyond the migration, so that people can work in it from the first day.

Filevine arrives as a platform to be configured, and most of the implementation is design. Someone has to decide what a project looks like for each kind of work the firm does, what moves it from one phase to the next, and who can see what. Those decisions are made with the people who run the files, then built and tested.

Set-up decisions in Filevine

  • Design project types, sections and fields for each practice area
  • Define phases and the tasks each phase should trigger
  • Build document templates that fill from project fields
  • Set teams, permissions and protected sections for restricted matters
  • Decide whether Billing and Payments are switched on
  • Connect Lead Docket so signed leads become projects

Questions

LollyLaw to Filevine: 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 Filevine?

In part. Trust accounts sit in Payments by Filevine. Loading history is confirmed in the analysis. The analysis sets out which trust records have a place in Filevine and which are kept as an archive, and the trust cutover is rehearsed on a full trial load before the real one.

Does everything in LollyLaw have a place in Filevine?

Most of it does on paper. Emails, notes, the firm’s accounts and custom fields could not be confirmed from the two products’ own material, so those are checked in the analysis. Anything that turns out to have no place in Filevine is kept as a readable archive, and you see which before the move.

What has to be decided before LollyLaw data is loaded into Filevine?

Time entries, billing records, trust ledgers, templates and intake records 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.

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.

How we do itDiscovery to rollout, step by step

LollyLaw and Filevine are the names and marks of their owners, used here only to identify the two systems.

Moving from LollyLaw to Filevine?

Tell us what you are moving. You get a plan and a fixed price after the analysis.

We reply within one business day.