Data migration route
LSSe64 to SurePoint Finance Enterprise migration
LSSe64 is a server-based practice management system, and SurePoint Finance Enterprise is a cloud one. Both run a whole practice, so this is a full move, and the financial records set the timetable.
LSSe64Server- Matters: Carried across
- Contacts: Carried across
- Calendar: Carried across
- Time and expenses: Carried across
- Billing: Carried across
- Trust money: Carried across
- Firm accounts: Carried across
- Documents: Confirmed in the analysis
- Emails: Confirmed in the analysis
- Notes: Confirmed in the analysis
- Tasks: Confirmed in the analysis
- Custom fields: Confirmed in the analysis
- Templates: Confirmed in the analysis
- Intake: Confirmed in the analysis
SurePoint Finance EnterpriseCloud- 7 carried
- 7 to confirm
What moves
What moves from LSSe64 to SurePoint Finance Enterprise
Each row is a kind of record LSSe64 holds, whether SurePoint Finance Enterprise has a place for it, and what is planned. On this route seven kinds of record carry across and seven 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 place | Carried across |
| ContactsClients, other parties and referrers | HeldContact Management and mailing lists. | Has a place | Carried across |
| DocumentsFiles stored in or linked from the system | HeldFiles kept in native format; profiles held in a separate indexed database. | To be confirmed | Confirmed in the analysis |
| 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 placeCalendar entries and dockets. | Carried across |
| TasksTo-dos and workflow steps assigned to people | Held in partWorkflow Management routes intake forms and change requests. | To be confirmed | Confirmed in the analysis |
| Time and expensesTime and expense entries, billed and unbilled | HeldTime, cost and expense entry, with a timer and batch entry. | Has a place | Carried across |
| BillingInvoices, payments and debtor balances | HeldPaper and electronic billing from one billing dashboard. | Has a place | Carried across |
| Trust moneyTrust or client account ledgers and balances | HeldMultiple trust accounts, with detail kept at client and matter level. | Has a place | Carried across |
| Firm accountsGeneral ledger, office account and payables | HeldGeneral Ledger, Accounts Payable and bank reconciliation. | Has a placeGeneral ledger and payables, by entity. | Carried across |
| 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 | To be confirmed | Confirmed in the analysis |
| IntakeLeads, enquiries, intake forms and pipelines | HeldElectronic client and matter intake forms, and potential client records. | To be confirmed | Confirmed in the analysis |
What the plans mean
- Carried across
- SurePoint Finance Enterprise 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
The whole practice moves, accounts included.
A move between two practice management systems is the widest kind there is. LSSe64 and SurePoint Finance Enterprise each keep matters, contacts, documents, time and money in one place, but no two systems link those records the same way. In one, a client is a contact with a role on the matter. In another, every matter carries its own client card. Most of the analysis goes into those links, because a matter that arrives without its client or its documents is the first thing staff find.
The financial side decides the dates. Unbilled time, debtor balances and trust ledgers have to agree with LSSe64’s own reports as at one day, and a new system usually wants them as opening balances, not as years of transactions. So the firm decides early how much history comes across as live records and how much is kept as reports. Matter and document loads can be repeated until they are right. The money is loaded once.
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. SurePoint Finance Enterprise 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 SurePoint Finance Enterprise
Moving into SurePoint Finance Enterprise, the system long sold as LMS, is an accounting implementation with a data load inside it. The entity structure, chart of accounts and billing rules are designed before records arrive, because every time entry and payment posts into them. Smaller systems rarely hold data at that level of detail, so part of the preparation is adding what the source never recorded.
Entities and tax IDs first
The system can hold several legal entities and tax IDs. A firm coming from a single QuickBooks file, or from two files for two offices, decides how it wants to be structured from here on. That decision fixes where each bank account and matter belongs, and it is hard to revisit once history is posted.
History has to balance
Billing, trust and the general ledger are parts of one system, so loaded history must agree across all three. A receivable carried in for a matter needs the invoice behind it and the ledger entry behind that. Source systems that kept billing and accounts apart are reconciled to each other before extraction.
E-billing detail on time entries
For LEDES e-billing, time entries need task and activity codes and timekeepers need the classifications clients expect. A small-firm system may never have captured them. The firm decides whether historic entries are loaded uncoded as history only, with coding starting on new work from go-live.
Dockets as well as appointments
Calendars and dockets are both kept. In many source systems a court deadline and a client lunch are the same kind of record. The two are separated on the way in, using event types or keywords, and the docket entries for open matters are checked by the lawyers responsible.
Cost recovery codes
Disbursements such as copying and postage arrive through cost recovery and post to the matter. The cost types and their rates are set up to match how the firm charges today. Unbilled disbursements from the old system are then loaded against those types so they can be billed normally.
How NewLaw runs it
Four steps, in this order.
Trust money moves on this route, so the trust cutover gets a rehearsal of its own.
Analysis
We read what LSSe64 holds and how its records link, then agree with you, field by field, where each piece will sit in SurePoint Finance Enterprise. Anything with no place there comes across as a note or stays behind, and you see which before the move.
Clean-up
Duplicate contacts and matters are merged where they can be identified, and inconsistent entries are put into one format, in LSSe64, before extraction. It is not always possible to find every one, so some may carry across.
Trial load
The data is loaded into SurePoint Finance Enterprise as a trial and checked against LSSe64: record counts, trust and debtor totals, the links between records, document dates. Exceptions are listed for you to decide.
Cutover
Changes in LSSe64 are frozen for an agreed window, the data is collected a final time and SurePoint Finance Enterprise goes live over a weekend. The trust and financial cutover is rehearsed on a full trial load first, because it cannot be re-run the way a document load can. 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 SurePoint Finance Enterprise. 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 SurePoint Finance Enterprise
Loaded data is not yet a working system. This is what NewLaw sets up in SurePoint Finance Enterprise, beyond the migration, so that people can work in it from the first day.
The set-up decisions in Finance Enterprise are mostly made by the finance team. They cover the firm’s entity structure, its chart of accounts, how bills are approved and sent, and what each client’s e-billing portal demands. Timekeepers need rates and classifications. The reports used for partner compensation are specified early, because they test whether the structure underneath is right.
Set-up decisions in SurePoint Finance Enterprise
- Entity structure, tax IDs and the chart of accounts
- Bank and trust accounts with reconciliation set-up
- Timekeeper rates, classifications and task code sets
- Pre-bill approval steps and client billing rules
- LEDES e-billing formats for each corporate client
- Management and compensation reports the partners use
Questions
LSSe64 to SurePoint Finance Enterprise: 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 SurePoint Finance Enterprise?
Yes. SurePoint Finance Enterprise keeps trust ledgers. Balances are loaded by matter and agreed to the trust report from LSSe64 as at the cutover date. That load cannot be re-run the way a document load can, so it is rehearsed on a full trial load first.
Does everything in LSSe64 have a place in SurePoint Finance Enterprise?
Most of it does on paper. Documents, emails, notes, tasks, custom fields, templates and intake records 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 SurePoint Finance Enterprise is kept as a readable archive, and you see which before the move.
What has to be decided before LSSe64 data is loaded into SurePoint Finance Enterprise?
Documents, emails, notes, tasks, custom fields, templates and intake records are confirmed in the analysis. The firm also sets the cutover date and how much financial history comes across as live records.
Other routes
Other routes from LSSe64 and into SurePoint Finance Enterprise
Other destinations from LSSe64
Other systems that move into SurePoint Finance Enterprise
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 SurePoint Finance Enterprise are the names and marks of their owners, used here only to identify the two systems.
Moving from LSSe64 to SurePoint Finance Enterprise?
Tell us what you are moving. You get a plan and a fixed price after the analysis.
We reply within one business day.