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

Data migration route

LSSe64 to SharePoint migration

LSSe64 is a server-based practice management system, and SharePoint is cloud file storage. Documents move into a folder for each client and matter, and the data behind them is kept as an export.

FromLSSe64Server
  1. Documents: Carried across
  2. Matters: Carried with mapping
  3. Contacts: Carried with mapping
  4. Emails: Carried with mapping
  5. Notes: Carried with mapping
  6. Calendar: Carried with mapping
  7. Tasks: Carried with mapping
  8. Custom fields: Confirmed in the analysis
  9. Templates: Confirmed in the analysis
ToSharePointCloud
  1. Time and expenses: Kept as a readable archive
  2. Billing: Kept as a readable archive
  3. Trust money: Kept as a readable archive
  4. Firm accounts: Kept as a readable archive
  5. Intake: Kept as a readable archive
Readable archiveNo place in SharePoint
  • 1 carried
  • 6 mapped
  • 2 to confirm
  • 5 archived
What the two products hold. The analysis confirms it field by field.

What moves

What moves from LSSe64 to SharePoint

Each row is a kind of record LSSe64 holds, whether SharePoint has a place for it, and what is planned. On this route one kind of record carries across, six kinds need mapping, five kinds have no place in SharePoint and are archived and two kinds are confirmed in the analysis.

Records in LSSe64 and their place in SharePoint
RecordIn LSSe64In SharePointWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldClient and matter numbers, with related parties and conflict records.Has a place in partAs a site, library, folder or list row the firm designs; no built-in matter record.Carried with mapping
ContactsClients, other parties and referrersHeldContact Management and mailing lists.Has a place in partOnly as rows in a list built for the purpose.Carried with mapping
DocumentsFiles stored in or linked from the systemHeldFiles kept in native format; profiles held in a separate indexed database.Has a placeFiles in libraries, with columns and versions.Carried across
EmailsEmails saved to matters or to the storeHeldSaved from Outlook with a client and matter profile; attachments are text-indexed.Has a place in partAs .msg or .eml files, with columns for sender and date if set up.Carried with mapping
NotesFile notes, matter notes and contact notesHeldCase Notes component.Has a place in partAs documents, or as rows in a notes list if one is built.Carried with mapping
CalendarAppointments, court dates and deadlinesHeldRules-based calendar.Has a place in partPossible as a list; usually left in Outlook.Carried with mapping
TasksTo-dos and workflow steps assigned to peopleHeld in partWorkflow Management routes intake forms and change requests.Has a place in partPossible as a list; no legal workflow built in.Carried with mapping
Time and expensesTime and expense entries, billed and unbilledHeldTime, cost and expense entry, with a timer and batch entry.No placeKept as a readable archive
BillingInvoices, payments and debtor balancesHeldPaper and electronic billing from one billing dashboard.No placeKept as a readable archive
Trust moneyTrust or client account ledgers and balancesHeldMultiple trust accounts, with detail kept at client and matter level.No placeKept as a readable archive
Firm accountsGeneral ledger, office account and payablesHeldGeneral Ledger, Accounts Payable and bank reconciliation.No placeKept as a readable archive
Custom fieldsFields and record types the firm added itselfTo be confirmedHas a placeColumns and content types on libraries and lists.Confirmed in the analysis
TemplatesPrecedents, document templates and automationTo be confirmedHas a place in partPrecedents as files; templates can be offered from a library.Confirmed in the analysis
IntakeLeads, enquiries, intake forms and pipelinesHeldElectronic client and matter intake forms, and potential client records.No placeKept as a readable archive

What the plans mean

Carried across
SharePoint has a place for this kind of record. It is loaded there and checked against LSSe64.
Carried with mapping
SharePoint 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
SharePoint 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 SharePoint 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 SharePoint 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. SharePoint 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

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.

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

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

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

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

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

More about moving off LSSe64

Where it is going

SharePoint will take a firm’s documents in almost any arrangement, which is the difficulty. The structure has to be chosen before the load: what a client is, what a matter is, and where security is applied. Changing it afterwards means moving every file again. Most of the effort goes into that design and into the columns that describe each document.

  1. Site, library or folder per matter

    A matter can be a site, a library within a client site, or a folder in one large library. Each choice has consequences for permissions, for search and for how a new matter is opened. The firm makes that decision, and the people who open matters every day should be part of it.

  2. Columns are built before content

    If documents are to carry matter number, client, document type or author as columns, those columns and any content types exist before loading, so each file can be tagged as it arrives. Tagging hundreds of thousands of documents afterwards is a second project that seldom gets finished.

  3. The 400 character path

    SharePoint limits the full decoded path, site and library and folders and file name, to 400 characters. A deep tree copied from a server drive under a long site name can cross it. Path lengths are calculated against the planned structure, not the old one, before any file moves.

  4. Large libraries and the view threshold

    A library can hold millions of files, but a view that tries to show more than 5,000 items at once runs into the list view threshold. One flat library with a folder per matter needs indexed columns and filtered views from the start, or views begin to fail as the library fills.

  5. Security by library, not by file

    Microsoft supports up to 50,000 unique permissions in a library and recommends staying under 5,000. Restricting matters one folder at a time reaches that sooner than firms expect. Restricted work is better grouped into its own site or library, so the permission is set once.

More about moving into SharePoint

How NewLaw runs it

Four steps, in this order.

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

  1. Analysis

    We read what LSSe64 holds and how it is organised, then agree with you where each kind of record will sit in SharePoint. 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 SharePoint 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.

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

Step 1 of 5: Start with the route

Moving fromLSSe64
Moving toSharePoint

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

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

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

Making SharePoint work as a firm’s document store is a design and build job in its own right. The sites, libraries, columns and permission groups are created, a way of opening a new matter is put in place so the structure repeats itself, and the Outlook and Teams habits around it are agreed. Search is tested with real questions from fee earners.

What is agreed and set up

  • Site and library structure for clients and matters
  • Columns and content types for matter number and document type
  • Permission groups, with restricted matters in their own libraries
  • A repeatable way to create each new matter’s workspace
  • Version history limits and retention labels for closed matters
  • Views, indexed columns and search tested on loaded data

Questions

LSSe64 to SharePoint: 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 SharePoint?

No. SharePoint 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 SharePoint has no place for?

On this route that is 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 SharePoint?

Matters, contacts, emails, notes, calendar entries and tasks 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.

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

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

Moving from LSSe64 to SharePoint?

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

We reply within one business day.