Data migration route
LSSe64 to Box migration
LSSe64 is a server-based practice 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.
LSSe64Server- Documents: Carried across
- Emails: Carried with mapping
- Notes: Carried with mapping
- Custom fields: Confirmed in the analysis
- Templates: 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
- Time and expenses: Kept as a readable archive
- Billing: Kept as a readable archive
- Trust money: Kept as a readable archive
- Firm accounts: Kept as a readable archive
- Intake: Kept as a readable archive
- 1 carried
- 2 mapped
- 2 to confirm
- 9 archived
What moves
What moves from LSSe64 to Box
Each row is a kind of record LSSe64 holds, whether Box has a place for it, and what is planned. On this route one kind of record carries across, two kinds need mapping, nine kinds have no place in Box and are archived and two kinds are confirmed in the analysis.
| Record | What is planned | ||
|---|---|---|---|
| MattersMatters or cases, with their numbers, types, parties and status | HeldClient and matter numbers, with related parties and conflict records. | No placeA matter is a folder, optionally with metadata; there is no matter record. | Kept as a readable archive |
| ContactsClients, other parties and referrers | HeldContact Management and mailing lists. | No place | Kept as a readable archive |
| DocumentsFiles stored in or linked from the system | HeldFiles kept in native format; profiles held in a separate indexed database. | Has a placeFiles and folders, named and dated as they are loaded. | Carried across |
| EmailsEmails saved to matters or to the store | HeldSaved from Outlook with a client and matter profile; attachments are text-indexed. | Has a place in partAs .msg or .eml files in the matter folder. | Carried with mapping |
| NotesFile notes, matter notes and contact notes | HeldCase Notes component. | Has a place in partAs documents in the matter folder, not as a notes record. | Carried with mapping |
| CalendarAppointments, court dates and deadlines | HeldRules-based calendar. | No place | Kept as a readable archive |
| TasksTo-dos and workflow steps assigned to people | Held in partWorkflow Management routes intake forms and change requests. | No place | Kept as a readable archive |
| Time and expensesTime and expense entries, billed and unbilled | HeldTime, cost and expense entry, with a timer and batch entry. | No place | Kept as a readable archive |
| BillingInvoices, payments and debtor balances | HeldPaper and electronic billing from one billing dashboard. | No place | Kept as a readable archive |
| Trust moneyTrust or client account ledgers and balances | HeldMultiple trust accounts, with detail kept at client and matter level. | No place | Kept as a readable archive |
| Firm accountsGeneral ledger, office account and payables | HeldGeneral Ledger, Accounts Payable and bank reconciliation. | No place | Kept as a readable archive |
| 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 | To be confirmed | Has a place in partPrecedents load as ordinary files; no document automation. | Confirmed in the analysis |
| IntakeLeads, enquiries, intake forms and pipelines | HeldElectronic client and matter intake forms, and potential client records. | 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 LSSe64.
- 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 LSSe64 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 LSSe64 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 LSSe64.
LSSe64 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
Leaving LSSe64
LSSe64 keeps the firm’s whole operation in one SQL Server database: time, billing, trust, the general ledger, payables, documents and calendar. So a move off it is a finance migration as much as a matter migration. The first things to establish are which components the firm licensed, whether it is on LSSe64 or the older legacy system, and whether LSS hosts it.
Legacy LSS or LSSe64
LSS has had four generations of software. The third, a 32-bit Windows system, is now called legacy LSS and the vendor describes it as obsolete. LSSe64 was a complete redesign. A firm that says it is on LSS could be on either, and the two are structured differently, so the version is confirmed before any estimate is made.
Licensed by component
The system can be bought whole or as single components, and Document Management can run as a stand-alone application. One firm may have accounting only, another everything. Where a component was never licensed, that kind of record is somewhere else: in folders, in Outlook or in another product. The analysis covers those places too.
Payables feed client bills
A client expense entered in Accounts Payable appears on the client’s account and bill, and a scanned invoice attached to it can be printed with the billing statement. Trust disbursements are also entered through payables. Unbilled expenses therefore have a supplier invoice and sometimes an image behind them, and both are carried with the entry.
Documents by profile
Each saved file has a profile: client and matter number, document type, author, typist and optional fields. The file is stored in its native format and the profile in an indexed database. Loading into a folder-based system means turning profiles into folders, and the firm agrees that layout on sample matters before the full run.
Minimum trust balances
A matter can be given a minimum required trust balance, and the billing statement then asks the client for the amount needed to restore it. Trust deposits can also carry a clear date before which funds are not disbursed. Both settings are per matter and are recorded so they can be set again after the move.
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 LSSe64 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 LSSe64: 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 LSSe64, a final pass over a weekend picks up what changed since the trial. LSSe64 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 LSSe64 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 LSSe64 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
LSSe64 to Box: what firms ask
LSS hosts our system. Can the data still be collected?
It is the same data in a different place. Hosted firms use the same software on remote desktops run by LSS, so the database is on LSS’s servers instead of the firm’s. Access is arranged with LSS on the firm’s authority. The collection is done once for the trial load and again after the freeze at cutover.
Can our general ledger history move, or only balances?
That depends on what the destination accepts. Some systems accept years of ledger transactions, others take opening balances and expect history to remain in the old books. Trust is settled separately: each matter’s balance is loaded and checked, and whether the transactions behind it follow depends on the destination. The analysis states which approach applies, and the old system is kept read only for the rest.
We only use LSS for accounting. What about our matters?
Then the client and matter list, time, billing and ledgers come from LSS, and everything else comes from wherever it is kept now. Documents on a server drive and calendars in Outlook are brought in alongside, matched to the same matter numbers. The matter number ties the sources together, so gaps in it are fixed first.
Do trust balances in LSSe64 have a place in Box?
No. Box does not keep trust ledgers. Trust records from LSSe64 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 Box has no place for?
On this route that is matters, contacts, calendar entries, tasks, time entries, billing records, trust ledgers, the firm’s accounts and intake records. They are exported from LSSe64 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 LSSe64 data is loaded into Box?
Emails and notes are carried with mapping, so each mapping is agreed with you first. Custom fields and templates 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 LSSe64 and into Box
Other destinations from LSSe64
Other systems that move 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.
LSSe64 and Box are the names and marks of their owners, used here only to identify the two systems.
Moving from LSSe64 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.