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

Data migration route

LawBase to Box migration

LawBase is a case management system, and Box is cloud file storage. Documents move into a folder for each client and matter, and the data behind them is kept as an export.

FromLawBaseCase management
  1. Emails: Carried with mapping
  2. Notes: Carried with mapping
  3. Custom fields: Carried with mapping
  4. Templates: Carried with mapping
  5. Documents: Confirmed in the analysis
  6. Time and expenses: Confirmed in the analysis
  7. Billing: Confirmed in the analysis
  8. Trust money: Confirmed in the analysis
  9. Firm accounts: Confirmed in the analysis
  10. Intake: Confirmed in the analysis
ToBoxCloud
  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
Readable archiveNo place in Box
  • 4 mapped
  • 6 to confirm
  • 4 archived
What the two products hold. The analysis confirms it field by field.

What moves

What moves from LawBase to Box

Each row is a kind of record LawBase holds, whether Box has a place for it, and what is planned. On this route four kinds need mapping, four kinds have no place in Box and are archived and six kinds are confirmed in the analysis.

Records in LawBase and their place in Box
RecordIn LawBaseIn BoxWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldScreens and fields are designed per office and practice area.No placeA matter is a folder, optionally with metadata; there is no matter record.Kept as a readable archive
ContactsClients, other parties and referrersHeldA configurable address book; contacts are entered once and linked to matters.No placeKept as a readable archive
DocumentsFiles stored in or linked from the systemTo be confirmedHas a placeFiles and folders, named and dated as they are loaded.Confirmed in the analysis
EmailsEmails saved to matters or to the storeHeld in partBi-directional integration with Microsoft Outlook.Has a place in partAs .msg or .eml files in the matter folder.Carried with mapping
NotesFile notes, matter notes and contact notesHeldCase notes of unlimited free text.Has a place in partAs documents in the matter folder, not as a notes record.Carried with mapping
CalendarAppointments, court dates and deadlinesHeldDocketing of appointments and tasks through the email calendar.No placeKept as a readable archive
TasksTo-dos and workflow steps assigned to peopleHeldNo placeKept as a readable archive
Time and expensesTime and expense entries, billed and unbilledTo be confirmedNo placeConfirmed in the analysis
BillingInvoices, payments and debtor balancesTo be confirmedNo placeConfirmed in the analysis
Trust moneyTrust or client account ledgers and balancesTo be confirmedNo placeConfirmed in the analysis
Firm accountsGeneral ledger, office account and payablesTo be confirmedNo placeConfirmed in the analysis
Custom fieldsFields and record types the firm added itselfHeldThe whole database layout is defined by the office.Has a place in partMetadata templates can hold fields such as matter number and client.Carried with mapping
TemplatesPrecedents, document templates and automationHeldDocument assembly through HotDocs.Has a place in partPrecedents load as ordinary files; no document automation.Carried with mapping
IntakeLeads, enquiries, intake forms and pipelinesTo be confirmedNo placeConfirmed in the analysis

What the plans mean

Carried with mapping
Box 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
Box has no place for it. It is exported in a format that opens without LawBase 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 LawBase into Box 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 Box 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 LawBase.

How LawBase is run at the firm is settled at the start of the analysis, because its maker’s own material does not settle it. The usual arrangement is assumed here. LawBase runs on the firm’s own equipment, so the data is collected there: a copy of the database and the folders its documents sit in, taken with the firm’s IT provider or over a remote session. Box is hosted by its maker, so loading depends on the import tools and access it provides. The old machine is kept, read only, as the fall-back record.

Where the data is now

No two LawBase databases are the same, because each office designed its own screens and fields. A move off it starts with reading that design: what tables exist, what each field means in this office, and which are still used. Offices that have run it for decades also hold very long case histories, and the retention decision is made early.

  1. A database the office designed

    LawBase lets an office lay out its own screens and choose its own fields for each practice area. A field labelled Adjuster or Docket Number exists because someone asked for it. There is no standard layout to map from. We document the one in use, with the office’s own people explaining what each field has come to mean.

  2. SmartFolders are groupings

    SmartFolders group files automatically by attorney, subject or any other value in the system. They behave like saved searches, not containers, so there is nothing in them to move. The useful ones are recreated as saved views or reports in the destination, once the fields they depend on have been loaded.

  3. HotDocs templates

    Document assembly runs through HotDocs, and producing a document can also create notes and tasks. The templates are HotDocs files with their own variables and logic. If the destination also works with HotDocs, they may be reused with remapped variables. Otherwise each template is rebuilt in the new system’s own tool.

  4. File room records

    LawBase is used for file room management, tracking physical files as well as electronic records. Those entries say where a paper file is. Few cloud systems have a file room module. The location data is brought across in custom fields, or exported as a register for whoever looks after the firm’s storage.

  5. Workflow fired by field changes

    Changing a single field can trigger an email, a document, other field updates, a note or calendar tasks. Over the years offices build many of these rules. They are listed during the analysis, because staff often no longer know which steps the system does for them until the new one fails to do it.

More about moving off LawBase

Where it is going

Loading a firm’s files into Box means deciding the folder tree and its owners first, because permissions follow the tree. Box has no matter record. A matter is a folder, and anything else the firm knew about it, such as the matter number, client or status, survives only in the folder name or in metadata fields set up before the load.

  1. Decide who owns the top level

    Box’s own planning guidance sets out two models: users create their own top-level folders, or administrators own them all and invite people in. For matter files most later decisions depend on this one, including who can share outside the firm and whose storage allowance the files count against.

  2. Restricted matters go near the top

    Access in Box only flows downward. A person who can open a client folder can open every matter under it, and a subfolder cannot be hidden from them. Matters behind an information barrier therefore need their own top-level folders, and the list of those matters is agreed before the structure is built.

  3. Names Box will not accept

    Box rejects a slash or backslash anywhere in a file or folder name, and spaces at the start or end. Files from older systems and from Macs often have both. They are renamed by rule before loading and the firm receives the list, so that a document cited by its old name can still be found.

  4. Matter details become metadata

    A metadata template can hold the matter number, client name, practice area and closed date against each matter folder. The template has to exist before the files arrive so the values can be written during the load. Without it, the folder name is the only place that information lives.

  5. File size follows the owner’s plan

    The largest file Box accepts depends on the plan of whoever owns the folder. Litigation matters with video or forensic images are where this bites. Oversized files are found in the analysis, and the firm chooses between a higher plan and keeping those files somewhere else.

More about moving into Box

How NewLaw runs it

Four steps, in this order.

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

  1. Analysis

    We read what LawBase holds and how it is organised, then agree with you where each kind of record will sit in Box. 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 Box and checked against LawBase: 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 LawBase, a final pass over a weekend picks up what changed since the trial. LawBase 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 LawBase 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 fromLawBase
Moving toBox

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 LawBase holds

    What is in it, how its records link, and where each piece would sit in Box. 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

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

Most of a Box set-up is governance. The folder tree, the groups that are invited into it and the rules on sharing outside the firm are decided and built before any file is loaded. After the load, staff need Box Drive on their PCs and a short written guide to where a new matter folder is created and who creates it.

What is agreed and set up

  • Top-level folder structure and who owns each folder
  • Groups for teams, mapped to collaborator roles
  • Metadata template for matter number, client and status
  • Shared link defaults and rules for external collaborators
  • Box Drive installed and signed in on each PC
  • Version limits and retention agreed with the firm’s records policy

Questions

LawBase to Box: what firms ask

Our LawBase has thirty years of cases. Do they all move?

They can, but the office does not have to take them all. Open matters and those inside the retention period move as full records. Older ones can come across as a summary record with notes, or remain in the LawBase database kept read only. The office’s retention policy and how often old files are consulted decide the line.

Does LawBase hold our billing?

The vendor’s material describes case, matter and practice management and does not describe a billing ledger, so we do not assume one. If your office records time or costs in LawBase fields it designed, those are found in the analysis. Any separate billing system is scoped as its own source.

Can our custom screens be recreated?

The fields can, where the destination supports custom fields by matter type. Exact screen layouts usually cannot, and they are rarely worth chasing. We agree with each practice group which fields they still need on screen, load the rest where they can be reported on, and drop fields that have sat empty for years.

Do trust balances in LawBase have a place in Box?

That is confirmed in the analysis. We could not establish it from the two products’ own material, so it is checked against your data in LawBase before the plan is fixed. If Box turns out to have no place for trust ledgers, they are kept as a readable archive and the firm decides where trust accounting runs.

What happens to records Box has no place for?

On this route that is matters, contacts, calendar entries and tasks. They are exported from LawBase 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 LawBase data is loaded into Box?

Emails, notes, custom fields and templates are carried with mapping, so each mapping is agreed with you first. Documents, time entries, billing records, trust ledgers, the firm’s accounts and intake records 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

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

Moving from LawBase to Box?

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

We reply within one business day.