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

Data migration route

LollyLaw to SharePoint migration

LollyLaw is a cloud practice management system for immigration work, and SharePoint is cloud file storage. Documents move into a folder for each client and matter, and the data behind them is kept as an export.

FromLollyLawCloud
  1. Documents: Carried across
  2. Matters: Carried with mapping
  3. Contacts: Carried with mapping
  4. Calendar: Carried with mapping
  5. Tasks: Carried with mapping
  6. Templates: Carried with mapping
  7. Emails: Confirmed in the analysis
  8. Notes: Confirmed in the analysis
  9. Firm accounts: Confirmed in the analysis
  10. Custom fields: Confirmed in the analysis
ToSharePointCloud
  1. Time and expenses: Kept as a readable archive
  2. Billing: Kept as a readable archive
  3. Trust money: Kept as a readable archive
  4. Intake: Kept as a readable archive
Readable archiveNo place in SharePoint
  • 1 carried
  • 5 mapped
  • 4 to confirm
  • 4 archived
What the two products hold. The analysis confirms it field by field.

What moves

What moves from LollyLaw to SharePoint

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

Records in LollyLaw and their place in SharePoint
RecordIn LollyLawIn SharePointWhat 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 place in partAs a site, library, folder or list row the firm designs; no built-in matter record.Carried with mapping
ContactsClients, other parties and referrersHeldContact records hold form data such as addresses, passport numbers and employment.Has a place in partOnly as rows in a list built for the purpose.Carried with mapping
DocumentsFiles stored in or linked from the systemHeldLollyDrive, with folders, labels and versions; other cloud drives can be linked.Has a placeFiles in libraries, with columns and versions.Carried across
EmailsEmails saved to matters or to the storeTo be confirmedHas a place in partAs .msg or .eml files, with columns for sender and date if set up.Confirmed in the analysis
NotesFile notes, matter notes and contact notesTo be confirmedHas a place in partAs documents, or as rows in a notes list if one is built.Confirmed in the analysis
CalendarAppointments, court dates and deadlinesHeld in partWorkflows create deadlines and meetings; a full calendar was not confirmed.Has a place in partPossible as a list; usually left in Outlook.Carried with mapping
TasksTo-dos and workflow steps assigned to peopleHeldTasks come from workflows and can be assigned to staff or to clients.Has a place in partPossible as a list; no legal workflow built in.Carried with mapping
Time and expensesTime and expense entries, billed and unbilledHeldNo placeKept as a readable archive
BillingInvoices, payments and debtor balancesHeldInvoices, online payments and custom payment plans.No placeKept as a readable archive
Trust moneyTrust or client account ledgers and balancesHeldShows the flow of funds between a matter’s trust and operating accounts.No placeKept as a readable archive
Firm accountsGeneral ledger, office account and payablesTo be confirmedNo placeConfirmed in the analysis
Custom fieldsFields and record types the firm added itselfTo be confirmedHas a placeColumns and content types on libraries and lists.Confirmed in the analysis
TemplatesPrecedents, document templates and automationHeld in partGovernment forms and questionnaires; general document templates were not confirmed.Has a place in partPrecedents as files; templates can be offered from a library.Carried with mapping
IntakeLeads, enquiries, intake forms and pipelinesHeldOnboarding questionnaires sent by email or text, in more than 20 languages.No placeKept as a readable archive

What the plans mean

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

Out of the system, into folders the firm can read.

File storage has folders and files and nothing else. Moving from LollyLaw into SharePoint 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 SharePoint 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 LollyLaw.

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 SharePoint 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

SharePoint will take a firm’s documents in almost any arrangement, which is the difficulty. The structure has to be chosen before the load: what a client is, what a matter is, and where security is applied. Changing it afterwards means moving every file again. Most of the effort goes into that design and into the columns that describe each document.

  1. Site, library or folder per matter

    A matter can be a site, a library within a client site, or a folder in one large library. Each choice has consequences for permissions, for search and for how a new matter is opened. The firm makes that decision, and the people who open matters every day should be part of it.

  2. Columns are built before content

    If documents are to carry matter number, client, document type or author as columns, those columns and any content types exist before loading, so each file can be tagged as it arrives. Tagging hundreds of thousands of documents afterwards is a second project that seldom gets finished.

  3. The 400 character path

    SharePoint limits the full decoded path, site and library and folders and file name, to 400 characters. A deep tree copied from a server drive under a long site name can cross it. Path lengths are calculated against the planned structure, not the old one, before any file moves.

  4. Large libraries and the view threshold

    A library can hold millions of files, but a view that tries to show more than 5,000 items at once runs into the list view threshold. One flat library with a folder per matter needs indexed columns and filtered views from the start, or views begin to fail as the library fills.

  5. Security by library, not by file

    Microsoft supports up to 50,000 unique permissions in a library and recommends staying under 5,000. Restricting matters one folder at a time reaches that sooner than firms expect. Restricted work is better grouped into its own site or library, so the permission is set once.

More about moving into SharePoint

How NewLaw runs it

Four steps, in this order.

Nothing financial lands in SharePoint on this route, which makes it repeatable: a load can be run again until it is right.

  1. Analysis

    We read what LollyLaw holds and how it is organised, then agree with you where each kind of record will sit in SharePoint. Anything with no place there stays behind or is archived, and you see which before the move.

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

  3. Trial load

    A trial is loaded into SharePoint 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.

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

Step 1 of 5: Start with the route

Moving fromLollyLaw
Moving toSharePoint

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

Structure, permissions and handover

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

Making SharePoint work as a firm’s document store is a design and build job in its own right. The sites, libraries, columns and permission groups are created, a way of opening a new matter is put in place so the structure repeats itself, and the Outlook and Teams habits around it are agreed. Search is tested with real questions from fee earners.

What is agreed and set up

  • Site and library structure for clients and matters
  • Columns and content types for matter number and document type
  • Permission groups, with restricted matters in their own libraries
  • A repeatable way to create each new matter’s workspace
  • Version history limits and retention labels for closed matters
  • Views, indexed columns and search tested on loaded data

Questions

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

No. SharePoint 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 SharePoint has no place for?

On this route that is 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 SharePoint?

Matters, contacts, calendar entries, tasks 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.

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 SharePoint are the names and marks of their owners, used here only to identify the two systems.

Moving from LollyLaw to SharePoint?

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

We reply within one business day.