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

Data migration route

LollyLaw to Server drives migration

LollyLaw is a cloud practice management system for immigration work, and Server drives are plain files on equipment the firm controls. 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. Templates: Carried with mapping
  3. Emails: Confirmed in the analysis
  4. Notes: Confirmed in the analysis
  5. Firm accounts: Confirmed in the analysis
  6. Custom fields: Confirmed in the analysis
ToServer drivesFiles
  1. Matters: Kept as a readable archive
  2. Contacts: Kept as a readable archive
  3. Calendar: Kept as a readable archive
  4. Tasks: Kept as a readable archive
  5. Time and expenses: Kept as a readable archive
  6. Billing: Kept as a readable archive
  7. Trust money: Kept as a readable archive
  8. Intake: Kept as a readable archive
Readable archiveNo place in Server drives
  • 1 carried
  • 1 mapped
  • 4 to confirm
  • 8 archived
What the two products hold. The analysis confirms it field by field.

What moves

What moves from LollyLaw to Server drives

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

Records in LollyLaw and their place in Server drives
RecordIn LollyLawIn Server drivesWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldImmigration matters with workflow steps, milestones and the forms attached to them.No placeA matter becomes a folder; its details survive only in an index file.Kept as a readable archive
ContactsClients, other parties and referrersHeldContact records hold form data such as addresses, passport numbers and employment.No placeCan be kept only as an exported spreadsheet.Kept as a readable archive
DocumentsFiles stored in or linked from the systemHeldLollyDrive, with folders, labels and versions; other cloud drives can be linked.Has a placeFiles in folders, named and dated during the load.Carried across
EmailsEmails saved to matters or to the storeTo be confirmedHas a place in partAs .msg or .eml files in each matter’s correspondence folder.Confirmed in the analysis
NotesFile notes, matter notes and contact notesTo be confirmedHas a place in partAs a text or PDF file per matter, not as separate records.Confirmed in the analysis
CalendarAppointments, court dates and deadlinesHeld in partWorkflows create deadlines and meetings; a full calendar was not confirmed.No placeKept as a readable archive
TasksTo-dos and workflow steps assigned to peopleHeldTasks come from workflows and can be assigned to staff or to clients.No placeKept as a readable archive
Time and expensesTime and expense entries, billed and unbilledHeldNo placeOnly as exported reports or spreadsheets.Kept as a readable archive
BillingInvoices, payments and debtor balancesHeldInvoices, online payments and custom payment plans.Has a place in partInvoices as PDF files; no ledger.Kept 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 placeOnly as exported ledger reports kept as files.Kept 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 confirmedNo placeConfirmed 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 Word files; merge fields tied to the old system stop working.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
Server drives has a place for this kind of record. It is loaded there and checked against LollyLaw.
Carried with mapping
Server drives 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
Server drives 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 Server drives 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 Server drives do 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.

LollyLaw is hosted by its maker and Server drives sit on equipment the firm controls. The data leaves a service that was backed up for the firm and arrives somewhere the firm must back up itself, so backup and access are arranged before the export is copied in. What LollyLaw will release depends on its export tools, and that is confirmed in the analysis.

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

Some firms leave a practice or document system and keep their documents on a server drive, either as the working store or as the archive of a system being switched off. The files will arrive without the database that described them. Everything the firm wants to keep knowing about a document has to be put into its path, its name or an index file.

  1. Agree the tree and the names

    A fixed pattern is chosen, for example client name and number, then matter number and short description, then a standard set of subfolders. Document titles from the old system become file names. Where two documents share a title, a date or sequence number is added so nothing is overwritten.

  2. Budget the path length

    Share name, client, matter, subfolder and file name all count towards the 260 character limit that many Windows programs still apply. The pattern is tested against the firm’s longest client names and document titles before the load. Descriptions are trimmed by rule, never by cutting off the file extension.

  3. Dates have to be set deliberately

    A file written to the server today is dated today unless its modified date is set from the old system’s record. Document dates are how lawyers find things in a folder. Which date each file is to carry is agreed in the analysis, and the trial load checks a sample.

  4. Emails become message files

    Emails filed to matters in the old system are written out as .msg or .eml files in a correspondence folder, named by date, sender and subject so they sort in order. Attachments stay inside the message. Subjects with characters Windows forbids are cleaned, and long ones cut.

  5. Keep an index beside the files

    A spreadsheet or small database listing every document with its matter, author, original date, document type and new path is the only place the old system’s profile data survives. It lets someone find a document by something other than its name. What the index records, and who keeps it, is decided in the analysis.

More about moving into Server drives

How NewLaw runs it

Four steps, in this order.

Nothing financial lands in Server drives 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 Server drives. 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 Server drives 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 toServer drives

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 Server drives. 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

Server drives are 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.

A server drive does only what the firm and its IT provider make it do. Setting one up as a document store means building the share, deciding who can open which folders, and arranging the protections a document system would have supplied: backups, earlier versions and a way to recover a deleted folder. The filing rule is written down and taught.

What is agreed and set up

  • Share and top-level folders for clients, precedents and administration
  • Security groups and folder permissions, with restricted matters separate
  • Drive letter mapped for every user at sign-in
  • Backup schedule and shadow copies for earlier versions
  • Written naming rule for client, matter and document names
  • Read-only area for closed matters and archived system exports

Questions

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

No. Server drives do not keep trust ledgers. Only as exported ledger reports kept as files. 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 Server drives have no place for?

On this route that is matters, 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 Server drives?

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

Moving from LollyLaw to Server drives?

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

We reply within one business day.