Data migration route
CloudLex to Box migration
CloudLex is a cloud case management system for personal injury work, 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.
CloudLexCloud- Documents: Carried across
- Emails: Carried with mapping
- Notes: Carried with mapping
- Templates: Carried with mapping
- Time and expenses: Confirmed in the analysis
- Billing: Confirmed in the analysis
- Trust money: Confirmed in the analysis
- Firm accounts: Confirmed in the analysis
- Custom fields: Confirmed in the analysis
BoxCloud- Matters: Kept as a readable archive
- Contacts: Kept as a readable archive
- Calendar: Kept as a readable archive
- Tasks: Kept as a readable archive
- Intake: Kept as a readable archive
- 1 carried
- 3 mapped
- 5 to confirm
- 5 archived
What moves
What moves from CloudLex to Box
Each row is a kind of record CloudLex holds, whether Box has a place for it, and what is planned. On this route one kind of record carries across, three kinds need mapping, five kinds have no place in Box and are archived and five kinds are confirmed in the analysis.
| Record | What is planned | ||
|---|---|---|---|
| MattersMatters or cases, with their numbers, types, parties and status | HeldMatters with type, status and sub-status. Intakes are a separate record. | No placeA matter is a folder, optionally with metadata; there is no matter record. | Kept as a readable archive |
| ContactsClients, other parties and referrers | HeldA firm-level directory, linked to matters by role. | No place | Kept as a readable archive |
| DocumentsFiles stored in or linked from the system | HeldPer matter, in categories and folders, with version control and party association. | Has a placeFiles and folders, named and dated as they are loaded. | Carried across |
| EmailsEmails saved to matters or to the store | HeldMatter email syncs with Microsoft 365. Gmail and Outlook add-ins file to a matter. | Has a place in partAs .msg or .eml files in the matter folder. | Carried with mapping |
| NotesFile notes, matter notes and contact notes | HeldMatter notes, also reachable from the global side panel. | Has a place in partAs documents in the matter folder, not as a notes record. | Carried with mapping |
| CalendarAppointments, court dates and deadlines | HeldEvents tied to the matter, including deadlines. | No place | Kept as a readable archive |
| TasksTo-dos and workflow steps assigned to people | HeldManual tasks and tasks generated by workflow templates. | No place | Kept as a readable archive |
| Time and expensesTime and expense entries, billed and unbilled | To be confirmed | No place | Confirmed in the analysis |
| BillingInvoices, payments and debtor balances | To be confirmed | No place | Confirmed in the analysis |
| Trust moneyTrust or client account ledgers and balances | To be confirmed | No place | Confirmed in the analysis |
| Firm accountsGeneral ledger, office account and payables | To be confirmed | No place | Confirmed in the analysis |
| Custom fieldsFields and record types the firm added itself | To be confirmed | Has a place in partMetadata templates can hold fields such as matter number and client. | Confirmed in the analysis |
| TemplatesPrecedents, document templates and automation | Held in partWorkflow templates by matter type and status. Document templates were not confirmed. | Has a place in partPrecedents load as ordinary files; no document automation. | Carried with mapping |
| IntakeLeads, enquiries, intake forms and pipelines | HeldLead Manager and Intake Manager. An intake is converted to a matter. | No place | Kept as a readable archive |
What the plans mean
- Carried across
- Box has a place for this kind of record. It is loaded there and checked against CloudLex.
- 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 CloudLex 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 CloudLex 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 CloudLex.
Both are hosted by their makers, so nothing is collected from the firm’s office. What can be taken out of CloudLex 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 CloudLex is kept running until the checks on Box are finished.
Where the data is now
Leaving CloudLex
Leaving CloudLex is a three-part job, because the firm’s records are split between Intake Manager, Matter Manager and Digital Archiver. Active matters carry the most structure, in the Details sections. Archived matters carry the most volume. The plan covers each part separately and states which archived files, if any, are being brought into the new system.
The Details sections
Medical information, medical bills, insurance, liens, expenses and settlement are separate sections of a matter, each a list of rows with amounts and dates. They map well to an injury-specific destination. In a general one, each section needs a home agreed in advance, and the outstanding balances on bills and liens are checked after loading.
Closed matters in Digital Archiver
Closed files are moved off the active list into Digital Archiver, where they stay searchable for the retention period. They are easy to forget when counting matters. The archive is inventoried at the start, and the firm chooses between loading those files, keeping an export, or leaving them where they are until retention ends.
Negotiations and the settlement calculator
A matter records its negotiations, and a calculator applies settlement rules to work out fees and the client’s share. The negotiation history is useful in the next system as a dated list. Calculator rules are firm settings, and they are entered again in the destination if it has an equivalent.
Contacts linked by role
One contact record serves every matter it appears on, as a provider, adjuster, attorney or referrer. That is tidy, and it means a merge or a typo affects many matters at once. Roles are extracted with the link, so an insurer on forty matters arrives once and is attached forty times.
Client messages and texts
Texts sent through Client Messenger are logged against the intake or matter. They are part of the file and often the only record of what a client was told. Such messages are carried as dated notes or as a transcript document on the matter, depending on what the destination can display.
Where it is going
Arriving in Box
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.
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.
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.
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.
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.
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.
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.
Analysis
We read what CloudLex 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.
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.
Trial load
A trial is loaded into Box and checked against CloudLex: 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.
Cutover
There is no financial cutover on this route. After a short freeze on changes in CloudLex, a final pass over a weekend picks up what changed since the trial. CloudLex 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 CloudLex 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 CloudLex 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.
- 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
CloudLex to Box: what firms ask
CloudLex calls them matters. Does that make the move simpler?
Only in the naming. The structure under a matter is still personal injury data: treatment, bills, liens, insurance and settlement. A destination that also says matter may have no sections for those. What decides the effort is whether the new system has a place for each Details section, and that is settled in the analysis.
What do we do about files in Digital Archiver?
Decide early. Archived matters are retained for years and are rarely opened, so loading them into the new system is optional. The options are a full load, a summary record with documents, or an export held by the firm. Whatever is chosen, the count of archived matters is agreed and checked.
Will emails filed to a matter come across?
Emails saved to a matter from Outlook, Gmail or the built-in mail are part of the matter record and are in scope. They move as email files or as documents, with the date sent preserved so the correspondence still sorts in order. Mailboxes themselves stay in Microsoft 365 or Google and are not touched.
Do trust balances in CloudLex 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 CloudLex 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, tasks and intake records. They are exported from CloudLex 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 CloudLex data is loaded into Box?
Emails, notes and templates are carried with mapping, so each mapping is agreed with you first. Time entries, billing records, trust ledgers, 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.
Other routes
Other routes from CloudLex and into Box
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.
CloudLex and Box are the names and marks of their owners, used here only to identify the two systems.
Moving from CloudLex 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.