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

Data migration route

Actionstep to Neos migration

Actionstep is a cloud practice management system, and Neos 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.

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

What moves

What moves from Actionstep to Neos

Each row is a kind of record Actionstep holds, whether Neos has a place for it, and what is planned. On this route seven kinds of record carry across, five kinds need mapping, one kind has no place in Neos and is archived and one kind is confirmed in the analysis.

Records in Actionstep and their place in Neos
RecordIn ActionstepIn NeosWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldEach matter has a matter type, a workflow step, a system Matter ID and a free-text File Reference.Has a placeCases by case type.Carried across
ContactsClients, other parties and referrersHeldJoined to matters as participants, each with a participant type.Has a placeParties, providers and case contacts. Contacts can be imported from CSV.Carried across
DocumentsFiles stored in or linked from the systemHeldBuilt-in document management, with default folders set per matter type.Has a placeCase Docs tab, organised in sub-tabs.Carried across
EmailsEmails saved to matters or to the storeHeldSaved to matters through the Outlook add-in.Has a place in partEmails tagged to a case are held. Loading old mail is scoped in the analysis.Carried with mapping
NotesFile notes, matter notes and contact notesHeldFile notes on each matter.Has a placeCarried across
CalendarAppointments, court dates and deadlinesHeldHas a placeCase calendar entries.Carried across
TasksTo-dos and workflow steps assigned to peopleHeldTasks can be created by workflow steps.Has a placeLoaded as checklist items.Carried across
Time and expensesTime and expense entries, billed and unbilledHeldTime entries and disbursements.Has a place in partTime can be held as value items. The treatment of old entries is confirmed in the analysis.Carried with mapping
BillingInvoices, payments and debtor balancesHeldHas a place in partInvoices exist in Neos. Loading past invoices is confirmed in the analysis.Carried with mapping
Trust moneyTrust or client account ledgers and balancesHeldCalled client accounting in the UK.To be confirmedConfirmed in the analysis
Firm accountsGeneral ledger, office account and payablesHeldGeneral ledger on the accounting edition; a Xero integration is also offered.No placeThe general ledger stays in QuickBooks.Kept as a readable archive
Custom fieldsFields and record types the firm added itselfHeldData collections per matter type, single-row or multi-row, plus participant custom data.Has a placeUser-defined fields are created on the relevant tab first.Carried with mapping
TemplatesPrecedents, document templates and automationHeldDocument and email templates with merge fields.Has a place in partTemplates are rebuilt for Neos document generation.Carried with mapping
IntakeLeads, enquiries, intake forms and pipelinesHeldClient intake, CRM and marketing features are part of the platform.Has a placeIntakes tab. Simple intake imports from CSV are supported.Carried across

What the plans mean

Carried across
Neos has a place for this kind of record. It is loaded there and checked against Actionstep.
Carried with mapping
Neos 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
Neos has no place for it. It is exported in a format that opens without Actionstep 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

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 Neos. 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 Actionstep has to be given a case type in Neos, and that choice drives which fields and workflows it gets. The mapping is agreed type by type. Financial history with no place in Neos is exported as reports and ledgers the firm can open without Actionstep, and kept as the record of what was billed and held.

Both are hosted by their makers, so nothing is collected from the firm’s office. What can be taken out of Actionstep 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 Actionstep is kept running until the checks on Neos are finished.

Where the data is now

A move off Actionstep starts with how the firm configured it, because two Actionstep firms rarely look alike. Matter types, participant types and data collections were all set up by someone, and each needs a home in the new system. The accounting question comes next: whether the firm’s ledger lives in Actionstep or in Xero changes what has to move at cutover.

  1. Two numbers on every matter

    Actionstep gives each matter a system Matter ID and also has a free-text File Reference. Some firms quote the ID to clients, others the reference, and older matters may show both in use. We record both for every matter, load the one the firm actually uses as the matter number, and keep the other in a searchable field.

  2. Participant types are firm-defined

    Contacts are attached to matters as participants, each with a participant type. The list comes with defaults, but firms add their own, such as trustee, executor or insurer. A destination with a short fixed list of roles cannot take forty participant types as they are, so each one is mapped to a role, a relationship or a custom field.

  3. Multi-row data collections

    Custom fields live in data collections tied to a matter type. A single-row collection maps to ordinary custom fields. A multi-row collection is a table, such as a list of a debtor’s assets, and few systems have a field that holds a table. Those rows usually come across as a note or a document on the matter.

  4. Workflow steps and their history

    Every matter sits at a step in its matter type’s workflow, and Actionstep keeps a history of who completed each step and when. The current step usually maps to a stage or status in the new system. Most products have no equivalent for the step history, so the firm decides whether it is kept as a note.

  5. Where the firm’s books are

    Actionstep can run the general ledger itself or pass accounting entries to Xero. If the ledger is inside Actionstep and the new system has none, the firm is also choosing an accounting package, and opening balances have to be agreed for it. When Xero already holds the books, that part of the move is a reconnection.

More about moving off Actionstep

Where it is going

Neos expects personal injury data in its own tab structure, so loading a firm means deciding which tab each old record belongs on. Parties, insurance and counsel map directly from most injury systems. Money maps to value items. Anything the standard tabs lack becomes a user-defined field, which has to be created before the load.

  1. Every figure needs a value code

    Costs, medical bills, fees and settlement amounts are loaded as value items, and each carries a value code. The code list is agreed with the firm’s accounts staff first. A figure loaded under the wrong code is reported in the wrong place, so the list is tested on real cases before the bulk load.

  2. Lists are set up first

    Cases are loaded against case types, statuses and staff assignments that already exist in Neos. Those lists are set up, and the old system’s values tidied to match, before the trial load. Misspelt attorney names and unused case types in the source are cleaned out at the same stage.

  3. Documents go to sub-tabs

    Files land on the Case Docs tab under sub-tabs, which staff can view as a list or as folders. The old system’s folders or categories are mapped to a fixed set of sub-tabs. Without that, every personal habit of naming folders is reproduced and the folder view becomes hard to read.

  4. Reminders split two ways

    Neos fills its dashboards from checklists and case calendars. Old diary entries and tasks are sorted between them: dated appointments and court events to the calendar, and to-dos to the checklist. An item assigned to several people in the old system may need one named owner, and the firm chooses who.

  5. Assembly runs its own conversions

    Assembly migrates firms into Neos with its own team and tooling, and offers routes from self-service templates to a full conversion. Where the firm uses that service, outside help goes on the work around it: cleaning the source, checking the converted cases against the old system, and listing exceptions.

More about moving into Neos

How NewLaw runs it

Four steps, in this order.

Financial records move on this route, so the balances are rehearsed before the real cutover. The maker of Neos says that it, or its partners, load firms into the product. Where the firm uses that service, NewLaw’s part is the work around it: the analysis, the clean-up in Actionstep and checking each trial against Actionstep.

  1. Analysis

    We read what Actionstep holds and how its records link, then agree with you, field by field, where each piece will sit in Neos. 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 Actionstep, before extraction. It is not always possible to find every one, so some may carry across.

  3. Trial load

    The data is loaded into Neos as a trial and checked against Actionstep: record counts, financial totals, the links between records, document dates. Exceptions are listed for you to decide.

  4. Cutover

    Changes in Actionstep are frozen for an agreed window, the data is collected a final time and Neos goes live over a weekend. The financial cutover is rehearsed on a full trial load first, so that opening balances agree with the reports in Actionstep as at the cutover date. Actionstep 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 Actionstep 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 fromActionstep
Moving toNeos

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

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

Loaded data is not yet a working system. The maker of Neos runs or arranges the set-up of its product, so this is what has to be decided and put in place in Neos, whoever does the work, before people rely on it from the first day.

Neos comes set up for injury work, so implementation is mostly choosing among its options and connecting the firm’s other tools. The lists that drive reporting are decided first, then checklists, then documents. Assembly provides its own implementation team, and the firm’s internal lead still has to make the decisions listed below.

Set-up decisions in Neos

  • Set case types, statuses and staff roles
  • Agree the value code list with accounts staff
  • Build checklists for each case type and stage
  • Create user-defined fields for data the tabs lack
  • Prepare document templates for the generation wizard
  • Connect Microsoft 365, QuickBooks and the phone system

Questions

Actionstep to Neos: what firms ask

Can we keep our Actionstep matter numbers in the new system?

Usually, if the new system accepts a matter number supplied on import. First we settle which number the firm means: the system Matter ID or the File Reference. The one in daily use becomes the matter number, and the other is kept in a field or note so old correspondence can still be traced.

Our general ledger is in Actionstep. Does it move too?

The ledger does not move as a ledger. What moves is a set of opening balances, agreed with the firm’s accountant at the cutover date, into the new system or into an accounting package beside it. Transaction history stays in the read-only Actionstep copy or in exported reports. Which package holds the books is decided in the analysis.

What happens to our data collections?

Single-row collections map to custom fields where the new system has them. Multi-row collections are tables, and they are harder. Depending on the destination they become repeated records, a note on the matter or a saved document. The firm sees the proposed treatment for each collection before the trial load.

Do trust balances in Actionstep have a place in Neos?

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 Actionstep before the plan is fixed. If Neos turns out to have no place for trust ledgers, they are kept as a readable archive and the firm decides where trust accounting runs.

What happens to records Neos has no place for?

On this route that is the firm’s accounts. They are exported from Actionstep 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 Actionstep data is loaded into Neos?

Emails, time entries, billing records, custom fields and templates are carried with mapping, so each mapping is agreed with you first. Trust ledgers 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

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

Moving from Actionstep to Neos?

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

We reply within one business day.