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

Data migration route

Neos to Actionstep migration

Neos is a cloud case management system for personal injury work, and Actionstep is a cloud practice management system. Case records move into matters, and time, billing and trust are set up in Actionstep, often from a separate accounts package.

FromNeosCloud
  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. Intake: Carried across
  11. Billing: Carried with mapping
  12. Custom fields: Carried with mapping
  13. Templates: Carried with mapping
ToActionstepCloud
  • 10 carried
  • 3 mapped
What the two products hold. The analysis confirms it field by field.

What moves

What moves from Neos to Actionstep

Each row is a kind of record Neos holds, whether Actionstep has a place for it, and what is planned. On this route ten kinds of record carry across and three kinds need mapping.

Records in Neos and their place in Actionstep
RecordIn NeosIn ActionstepWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldCases laid out in tabs, with a Management tab for fee and referral details.Has a placeImported with a matter type, a status and the old number as File Reference.Carried across
ContactsClients, other parties and referrersHeldParties, providers, counsel, case contacts and related contacts.Has a placeImported first, then linked to matters through a parties import.Carried across
DocumentsFiles stored in or linked from the systemHeldCase Docs tab with sub-tabs, viewable as a list or as folders.Has a placeFiled in matter folders; not part of the spreadsheet import tool.Carried across
EmailsEmails saved to matters or to the storeHeldEmails can be tagged to the case file. Outlook is integrated.Has a placeSaved emails sit on the matter they were filed to.Carried across
NotesFile notes, matter notes and contact notesHeldCase notes, including Special Notes.Has a placeThe import tool has a file notes template.Carried across
CalendarAppointments, court dates and deadlinesHeldCase calendars, with statute and deadline alerts.Has a placeAppointments have a place; the standard import templates do not cover them.Carried across
TasksTo-dos and workflow steps assigned to peopleHeldChecklists and case tasks, which feed staff dashboards.Has a placeThe import tool has a tasks template.Carried across
Time and expensesTime and expense entries, billed and unbilledHeldTimers on a case, which can create value items.Has a placeTime entries and disbursements each have an import template.Carried across
BillingInvoices, payments and debtor balancesHeldInvoices in PDF, Word or LEDES format. Payments through LawPay.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 balancesHeld in partTrust requests can be raised and paid through LawPay.Has a placeTrust balances load per matter through the trust accounts import.Carried across
Custom fieldsFields and record types the firm added itselfHeldUser-defined fields can be added to case tabs.Has a placeData collections are built per matter type before values are loaded.Carried with mapping
TemplatesPrecedents, document templates and automationHeldA document generation wizard merges templates for one case or many.Has a placeRebuilt as Actionstep templates with its merge fields.Carried with mapping
IntakeLeads, enquiries, intake forms and pipelinesHeldIntakes tab and intake forms.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 Neos.
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.

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

Cases come across. The accounts are set up new.

A case management system holds the working file: parties, notes, deadlines, documents and the fields a practice area needs. It is not usually the firm’s ledger, so time, invoices and trust often sit in an accounting package beside it. Moving to Actionstep brings those two sources together. The case records come from Neos. Opening balances for debtors and trust, where they move at all, come from the accounts package and are agreed to its reports.

Case systems are heavy with custom fields, and that is where the mapping work is. A personal injury or immigration file can carry dozens of fields that a general practice system has no standard place for. Each one is matched to a field in Actionstep, created there as a custom field, or written into a note on the matter. The firm sees which before the load. Workflows and task templates are rebuilt, not copied.

Both are hosted by their makers, so nothing is collected from the firm’s office. What can be taken out of Neos depends on its export tools and on what its maker provides on request, and that is confirmed during the analysis, before a date is set. The subscription to Neos is kept running until the checks on Actionstep are finished.

Where the data is now

A firm leaving Neos is leaving a cloud system whose data sits in a database dedicated to that firm. The structure runs tab by tab, and each tab is in effect a table. Many Neos firms came from Needles or Trialworks, so the data often carries conventions two systems old, and the analysis has to read those as well.

  1. A database per firm

    Assembly holds each firm’s records in a separate Azure SQL database. For a migration that means the data set is self-contained, with nothing shared with other customers. How a copy is obtained is arranged with the firm at the start, and the copy and the document files are taken at the same point in time.

  2. Value items hold the money

    Bills, costs, time and settlement entries are value items on the Value tab, with transactions beneath them for payments. A general system splits those across disbursements, time, invoices and receipts. Each value code is mapped to one of them, and the case totals are compared before and after.

  3. Fields inherited from Trialworks

    When a Trialworks firm is converted to Neos, some standard fields land in user-defined fields and in document sub-tabs named after the old tabs. A firm that has been through that carries two layers of structure. Both are read, so a field that looks custom is recognised as the old system’s standard field.

  4. Checklists and calendars

    Work in progress is split between checklist items and case calendar entries, and dashboards are built from both. Open checklist items become tasks in the destination. Calendar entries become events. The two are counted separately in the trial load, because losing either leaves a fee earner with an empty list on the first morning.

More about moving off Neos

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 Neos 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 Neos, 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 Neos: record counts, trust and debtor totals, the links between records, document dates. Exceptions are listed for you to decide.

  4. Cutover

    Changes in Neos 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. Neos 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 Neos 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 fromNeos
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 Neos 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

Neos to Actionstep: what firms ask

We have seen NEOS Web and NEOS DB listed. Are they different from Neos?

Assembly’s own site describes a single product, Neos, used in a browser, with each firm’s records in a dedicated Azure SQL database. Some software lists show NEOS Web and NEOS DB as separate entries. Which system a firm actually holds, and where its data sits, is identified at the start of the analysis.

We are on Needles. Is Neos just an upgrade?

No, it is a migration. Needles keeps its data in a SAP ASE database on the firm’s server and Neos uses Azure SQL in the cloud, so records and documents are converted, not upgraded in place. Assembly says the case logic is the same, which shortens the mapping compared with a move elsewhere.

Can Neos replace our accounting system?

Not the general ledger. Neos records case money as value items, raises invoices and trust requests, and takes payments through LawPay, and it links to QuickBooks Desktop or Online for the books. A firm moving from a system with built-in accounting plans a QuickBooks set-up as part of the same project.

Do trust balances in Neos 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 Neos 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 Neos have a place in Actionstep?

On paper, yes: each kind of record Neos holds has a place in Actionstep. Whether every field fits is a separate question, and the analysis answers it field by field. Anything with no place comes across as a note or stays behind, and you see which before the move.

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

Billing records, custom fields and templates are carried with mapping, so each mapping is agreed with you first. 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

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

Moving from Neos 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.