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

Data migration route

LSSe64 to Actionstep migration

LSSe64 is a server-based practice management system, and Actionstep is a cloud one. Both run a whole practice, so this is a full move, and the financial records set the timetable.

FromLSSe64Server
  1. Matters: Carried across
  2. Contacts: Carried across
  3. Documents: Carried across
  4. Emails: Carried across
  5. Notes: Carried across
  6. Calendar: Carried across
  7. Tasks: Carried across
  8. Time and expenses: Carried across
  9. Trust money: Carried across
  10. Firm accounts: Carried across
  11. Intake: Carried across
  12. Billing: Carried with mapping
  13. Custom fields: Confirmed in the analysis
  14. Templates: Confirmed in the analysis
ToActionstepCloud
  • 11 carried
  • 1 mapped
  • 2 to confirm
What the two products hold. The analysis confirms it field by field.

What moves

What moves from LSSe64 to Actionstep

Each row is a kind of record LSSe64 holds, whether Actionstep has a place for it, and what is planned. On this route eleven kinds of record carry across, one kind needs mapping and two kinds are confirmed in the analysis.

Records in LSSe64 and their place in Actionstep
RecordIn LSSe64In ActionstepWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldClient and matter numbers, with related parties and conflict records.Has a placeImported with a matter type, a status and the old number as File Reference.Carried across
ContactsClients, other parties and referrersHeldContact Management and mailing lists.Has a placeImported first, then linked to matters through a parties import.Carried across
DocumentsFiles stored in or linked from the systemHeldFiles kept in native format; profiles held in a separate indexed database.Has a placeFiled in matter folders; not part of the spreadsheet import tool.Carried across
EmailsEmails saved to matters or to the storeHeldSaved from Outlook with a client and matter profile; attachments are text-indexed.Has a placeSaved emails sit on the matter they were filed to.Carried across
NotesFile notes, matter notes and contact notesHeldCase Notes component.Has a placeThe import tool has a file notes template.Carried across
CalendarAppointments, court dates and deadlinesHeldRules-based calendar.Has a placeAppointments have a place; the standard import templates do not cover them.Carried across
TasksTo-dos and workflow steps assigned to peopleHeld in partWorkflow Management routes intake forms and change requests.Has a placeThe import tool has a tasks template.Carried across
Time and expensesTime and expense entries, billed and unbilledHeldTime, cost and expense entry, with a timer and batch entry.Has a placeTime entries and disbursements each have an import template.Carried across
BillingInvoices, payments and debtor balancesHeldPaper and electronic billing from one billing dashboard.Has a place in partUnpaid invoices load as accounts receivable; older invoice history is confirmed in the analysis.Carried with mapping
Trust moneyTrust or client account ledgers and balancesHeldMultiple trust accounts, with detail kept at client and matter level.Has a placeTrust balances load per matter through the trust accounts import.Carried across
Firm accountsGeneral ledger, office account and payablesHeldGeneral Ledger, Accounts Payable and bank reconciliation.Has a placeOpening balances are entered against the general ledger, or the books stay in Xero.Carried across
Custom fieldsFields and record types the firm added itselfTo be confirmedHas a placeData collections are built per matter type before values are loaded.Confirmed in the analysis
TemplatesPrecedents, document templates and automationTo be confirmedHas a placeRebuilt as Actionstep templates with its merge fields.Confirmed in the analysis
IntakeLeads, enquiries, intake forms and pipelinesHeldElectronic client and matter intake forms, and potential client records.Has a placeCarried across

What the plans mean

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

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

Actionstep has its own import tool, which takes spreadsheets in a set order: contacts, then matters, then the parties that join them. Tasks, time entries, trust balances, disbursements, unpaid invoices and file notes follow once the matters exist. None of it can start until the matter types, participant types and data collections have been built, because every imported row refers to them.

  1. Matter types before any data

    A matter’s type decides its workflow steps, its document folders, which party roles are available and which custom data it carries. So the first job is deciding how the old system’s matter types map to Actionstep’s, and building any that are missing. An imported matter also needs a step to sit at, usually the one closest to its old status.

  2. Old numbers go to File Reference

    Actionstep assigns its own Matter ID to each imported matter. The number the firm has always used goes into the File Reference field, which the quick search reads from the start of the reference. Staff can keep finding matters by the number printed on old letters and file covers.

  3. Check before anyone edits

    The import tool can roll back a load, but only while the imported records are untouched. Once someone edits them, the rollback no longer works. Trial loads are therefore checked straight away against the old system, and nobody outside the project works in the new records until the counts and balances agree.

  4. Folders come from the matter type

    Default document folders are set per matter type. There is no single folder list that applies across all matters. Before documents are loaded, the old folder names are mapped to the folders each matter type will have, so a conveyancing file and a litigation file each open with the layout the firm designed for them.

  5. Opening balances can be locked

    Trust balances load against matters, unpaid invoices load as accounts receivable, and general ledger opening balances are entered on the accounts list. An opening balance that has been locked cannot be edited afterwards. The figures are rehearsed on a trial load and agreed with the firm’s accountant before the lock is applied in the live system.

More about moving into Actionstep

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.

  1. Analysis

    We read what LSSe64 holds and how its records link, then agree with you, field by field, where each piece will sit in Actionstep. Anything with no place there comes across as a note or stays behind, and you see which before the move.

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

  3. Trial load

    The data is loaded into Actionstep 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.

  4. Cutover

    Changes in LSSe64 are frozen for an agreed window, the data is collected a final time and Actionstep 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

Step 1 of 5: Start with the route

Moving fromLSSe64
Moving toActionstep

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

Setting up Actionstep

Loaded data is not yet a working system. This is what NewLaw sets up in Actionstep, beyond the migration, so that people can work in it from the first day.

Most of the work in an Actionstep set-up is design. The firm decides what its matter types are, what steps each one moves through and what happens at each step. Templates, billing and trust settings are then built around those matter types. People are trained on their own workflows, since a generic demonstration looks little like the firm’s finished system.

Set-up decisions in Actionstep

  • Matter types, with workflow steps and default document folders
  • Participant types and data collections for each matter type
  • Document and email templates rebuilt with Actionstep merge fields
  • Trust accounts, chart of accounts and the optional Xero link
  • System roles and data permissions for each group of staff
  • Outlook add-in, divisions and the firm’s billing preferences

Questions

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

Yes. Actionstep keeps trust ledgers. Trust balances load per matter through the trust accounts import. 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 Actionstep?

Most of it does on paper. 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 Actionstep is kept as a readable archive, and you see which before the move.

What has to be decided before LSSe64 data is loaded into Actionstep?

Billing records are carried with mapping, so each mapping is agreed with you first. Custom fields and templates are confirmed in the analysis. The firm also sets the cutover date and how much financial history comes across as live records.

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 Actionstep are the names and marks of their owners, used here only to identify the two systems.

Moving from LSSe64 to Actionstep?

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

We reply within one business day.