Data migration route
LSSe64 to Gladiate migration
LSSe64 is a server-based practice management system, and Gladiate is a cloud case management system for personal injury work. Matter records move into cases, and the firm decides where its accounting runs from the cutover date.
LSSe64Server- Matters: Carried across
- Contacts: Carried across
- Documents: Carried across
- Calendar: Carried across
- Tasks: Carried across
- Intake: Carried across
- Emails: Confirmed in the analysis
- Notes: Confirmed in the analysis
- 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
- Templates: Confirmed in the analysis
GladiateCloud- 6 carried
- 8 to confirm
What moves
What moves from LSSe64 to Gladiate
Each row is a kind of record LSSe64 holds, whether Gladiate has a place for it, and what is planned. On this route six kinds of record carry across and eight 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. | Has a placePersonal injury cases. | Carried across |
| ContactsClients, other parties and referrers | HeldContact Management and mailing lists. | Has a placeClients, leads and referral sources. | Carried across |
| DocumentsFiles stored in or linked from the system | HeldFiles kept in native format; profiles held in a separate indexed database. | Has a placeFiled to the firm’s folder structure. | Carried across |
| EmailsEmails saved to matters or to the store | HeldSaved from Outlook with a client and matter profile; attachments are text-indexed. | To be confirmed | Confirmed in the analysis |
| NotesFile notes, matter notes and contact notes | HeldCase Notes component. | To be confirmed | Confirmed in the analysis |
| CalendarAppointments, court dates and deadlines | HeldRules-based calendar. | Has a placeEvents sync with Outlook and Google Calendar. | Carried across |
| TasksTo-dos and workflow steps assigned to people | Held in partWorkflow Management routes intake forms and change requests. | Has a placeTasks and task plans. | Carried across |
| Time and expensesTime and expense entries, billed and unbilled | HeldTime, cost and expense entry, with a timer and batch entry. | To be confirmed | Confirmed in the analysis |
| BillingInvoices, payments and debtor balances | HeldPaper and electronic billing from one billing dashboard. | To be confirmed | Confirmed in the analysis |
| Trust moneyTrust or client account ledgers and balances | HeldMultiple trust accounts, with detail kept at client and matter level. | To be confirmed | Confirmed in the analysis |
| Firm accountsGeneral ledger, office account and payables | HeldGeneral Ledger, Accounts Payable and bank reconciliation. | To be confirmed | Confirmed in the analysis |
| Custom fieldsFields and record types the firm added itself | To be confirmed | To be confirmed | Confirmed in the analysis |
| TemplatesPrecedents, document templates and automation | To be confirmed | Has a place in partFirm templates are set up again in Gladiate. Old templates are not converted. | Confirmed in the analysis |
| IntakeLeads, enquiries, intake forms and pipelines | HeldElectronic client and matter intake forms, and potential client records. | Has a placeLeads and client sign-up. | Carried across |
What the plans mean
- Carried across
- Gladiate has a place for this kind of record. It is loaded there and checked against LSSe64.
- 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.
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
Matters become cases. The ledgers need a home.
Going from a practice management system to a case management system is a move towards the file and away from the ledger. Matters, parties, documents, notes and deadlines have a natural place in Gladiate. Time, invoices, trust and the general ledger often do not, or only in part, and the table above shows which. Before the move is planned the firm settles where billing and trust accounting will run, because that decides what is loaded and what is archived.
Case systems are usually built around a practice area, with their own stages, roles and document sets. A general matter from LSSe64 has to be given a case type in Gladiate, and that choice drives which fields and workflows it gets. The mapping is agreed type by type. Financial history with no place in Gladiate is exported as reports and ledgers the firm can open without LSSe64, and kept as the record of what was billed and held.
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. Gladiate 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 Gladiate
Gladiate is a destination for personal injury firms, and what it expects is injury data: a client, an incident, coverage, providers and a case status. Loading a firm into it means shaping the old system’s records into that pattern and preparing the templates, task plans and folder structure that the vendor’s onboarding asks each firm to supply.
Injury fields come first
Coverage, liability and medical details are what the product is designed to put in front of staff. In the old system they may be in custom fields, notes or a spreadsheet. They are pulled into columns during the analysis, so a loaded case shows its insurer and policy details and not an empty panel.
Templates and task plans
The vendor’s onboarding has each firm set up its own document templates, task plans, litigation deadlines and questionnaires. These are prepared from what the firm uses now. Merge fields in old templates are replaced with Gladiate’s, and task plans are written down stage by stage before anyone builds them.
A folder structure per case
Documents are filed in a folder structure the firm defines. The old system’s folders or categories are mapped to it once, and every case is loaded to the same pattern. Files with no clear category go to a holding folder on the case and are listed, not scattered.
What it may not hold
Time records, invoices and trust ledgers are not described on the vendor’s public pages. A firm that needs those carried over has it confirmed in the analysis. If there is no place for them, balances stay in the accounting package and the detailed history is kept in the old system, read only.
How NewLaw runs it
Four steps, in this order.
No financial cutover is planned on this route, so a load can be run again until it is right. If the analysis finds financial records with a place in Gladiate, they get a rehearsed cutover of their own.
Analysis
We read what LSSe64 holds and how it is organised, then agree with you where each kind of record will sit in Gladiate. 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 Gladiate 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
After a short freeze on changes in LSSe64, a final pass over a weekend picks up what changed since the trial. If the analysis found financial records to move, their cutover is rehearsed on a full trial load first. 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 Gladiate. 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
Setting up Gladiate
Loaded data is not yet a working system. This is what NewLaw sets up in Gladiate, beyond the migration, so that people can work in it from the first day.
Gladiate is delivered ready for injury work, so set-up is about making it the firm’s own. The vendor’s onboarding covers templates, task plans, folder structure, litigation deadlines and client questionnaires. Each of those is a decision the firm has to make, and it goes faster when current practice has been written down beforehand.
Set-up decisions in Gladiate
- Set up and test the firm’s document templates
- Write task plans for each stage of a case
- Agree one folder structure for case documents
- Enter litigation deadlines for the firm’s jurisdictions
- Prepare client questionnaires, surveys and scheduled case updates
- Connect Outlook or Google calendars for two-way sync
Questions
LSSe64 to Gladiate: 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 Gladiate?
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 LSSe64 before the plan is fixed. If Gladiate turns out to have no place for trust ledgers, they are kept as a readable archive and the firm decides where trust accounting runs.
Does everything in LSSe64 have a place in Gladiate?
Most of it does on paper. Emails, notes, time entries, billing records, trust ledgers, the firm’s accounts, custom fields and templates could not be confirmed from the two products’ own material, so those are checked in the analysis. Anything that turns out to have no place in Gladiate is kept as a readable archive, and you see which before the move.
What has to be decided before LSSe64 data is loaded into Gladiate?
Emails, notes, time entries, billing records, trust ledgers, the firm’s accounts, 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 Gladiate
Other destinations from LSSe64
Other systems that move into Gladiate
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 Gladiate are the names and marks of their owners, used here only to identify the two systems.
Moving from LSSe64 to Gladiate?
Tell us what you are moving. You get a plan and a fixed price after the analysis.
We reply within one business day.