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

Data migration route

Open Case Management (OCM) to Neos migration

Open Case Management (OCM) is a server-based case management system for legal aid work, and Neos is a cloud case management system for personal injury work. The records line up case for case, and the detail is in the fields and stages.

FromOpen Case Management (OCM)Server
  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. Time and expenses: Carried with mapping
  9. Custom fields: Carried with mapping
  10. Templates: Carried with mapping
  11. Emails: Confirmed in the analysis
ToNeosCloud
  • 7 carried
  • 3 mapped
  • 1 to confirm
What the two products hold. The analysis confirms it field by field.

What moves

What moves from Open Case Management (OCM) to Neos

Each row is a kind of record Open Case Management (OCM) holds, whether Neos has a place for it, and what is planned. On this route seven kinds of record carry across, three kinds need mapping and one kind is confirmed in the analysis.

Records in Open Case Management (OCM) and their place in Neos
RecordIn Open Case Management (OCM)In NeosWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldCases, each started from an intake.Has a placeCases by case type.Carried across
ContactsClients, other parties and referrersHeldClients, adverse parties and contacts on every case, with duplicate merging.Has a placeParties, providers and case contacts. Contacts can be imported from CSV.Carried across
DocumentsFiles stored in or linked from the systemHeldUploaded files indexed for search, including PDFs and WordPerfect documents.Has a placeCase Docs tab, organised in sub-tabs.Carried across
EmailsEmails saved to matters or to the storeTo be confirmedHas a place in partEmails tagged to a case are held. Loading old mail is scoped in the analysis.Confirmed in the analysis
NotesFile notes, matter notes and contact notesHeldHas a placeCarried across
CalendarAppointments, court dates and deadlinesHeldShared calendars with iCal feeds.Has a placeCase calendar entries.Carried across
TasksTo-dos and workflow steps assigned to peopleHeldTicklers.Has a placeLoaded as checklist items.Carried across
Time and expensesTime and expense entries, billed and unbilledHeldTimeslips on every case.Has a place in partTime can be held as value items. The treatment of old entries is confirmed in the analysis.Carried with mapping
Custom fieldsFields and record types the firm added itselfHeldCustom fields, HTML fields and editable menus.Has a placeUser-defined fields are created on the relevant tab first.Carried with mapping
TemplatesPrecedents, document templates and automationHeldForm letters and generated documents using configurable template tags.Has a place in partTemplates are rebuilt for Neos document generation.Carried with mapping
IntakeLeads, enquiries, intake forms and pipelinesHeldIntake with financial and citizenship eligibility, conflict and duplicate checks.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 Open Case Management (OCM).
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.

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

Case to case, field by field.

Two case management systems look alike from a distance and differ in almost every detail. Each has its own idea of a case type, a stage, a party role and a deadline. Open Case Management (OCM) and Neos may both hold a limitation date, yet one calculates it and the other stores what was typed. The mapping goes field by field and status by status, and the trial load is checked by opening real cases in both systems side by side.

Custom fields hold most of what the firm has built up. Years of intake answers, injury details or visa histories sit in fields the firm added itself. Each is matched to a field in Neos, and anything unmatched is kept as a note on the case so that it can still be searched. Workflows and document templates are rebuilt in the new system’s own tools. Open tasks come across with their owners and due dates.

Open Case Management (OCM) 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. Neos 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

Where OCM is self-hosted, the database and the uploaded files are on a server the program or its host controls. That makes collection simple and makes the mapping the real work. The records were designed for legal aid reporting: intakes that may never become cases, eligibility answers, timeslips and the codes that funders count. Each needs a place or a decision.

  1. Intakes that never became cases

    An intake is started, screened for financial and citizenship eligibility, checked for conflicts and duplicates, then reviewed and assigned. Many stop before a case is opened. Those records still matter, because a person turned away last year is a conflict check hit this year. They are loaded as contacts with a note, or as closed enquiries.

  2. WordPerfect files in the store

    Uploaded documents are indexed for search, and the project documents support for WordPerfect files as well as PDFs. Programs that have run for decades often have both. Files move in their original format. Whether the new system can preview or search a WordPerfect document is tested in the trial load, not assumed.

  3. Menus the program edited

    Menus, custom fields and HTML fields can all be changed by the program, so the values on a case come from lists that are local to that site. Every list is exported with its codes and labels. Retired values that still appear on old cases are kept, since deleting them would blank the field on those records.

  4. MegaReport queries

    Staff build their own ad hoc reports with a tool called MegaReport, alongside the built-in reports and LSC case service reporting. Saved queries are not data and do not migrate. The ones still used are listed, and each is either rebuilt in the new system or replaced by an export the program can run itself.

  5. Peer transfers between programs

    Cases can be transferred to a peer program running the same software. A transferred case has a history that began somewhere else. These are identified in the analysis so that the originating program, the transfer date and any documents that arrived with the case are preserved on the record.

More about moving off Open Case Management (OCM)

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 Open Case Management (OCM) and checking each trial against Open Case Management (OCM).

  1. Analysis

    We read what Open Case Management (OCM) 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 Open Case Management (OCM), 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 Open Case Management (OCM): record counts, financial totals, the links between records, document dates. Exceptions are listed for you to decide.

  4. Cutover

    Changes in Open Case Management (OCM) 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 Open Case Management (OCM) as at the cutover date. Open Case Management (OCM) 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 Open Case Management (OCM) 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 fromOpen Case Management (OCM)
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 Open Case Management (OCM) 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

Open Case Management (OCM) to Neos: what firms ask

We run OCM on our own server. Does that make moving easier?

It makes getting the data out easier, because the database and the uploaded files are under the program’s control and can be copied in full. It does not shorten the mapping or the checking. A complete copy is taken for the trial load, and a second one at cutover after changes are frozen.

We are told OCM has been renamed. Does that force a move?

No one has to move because of a name. The open-source code is still published and receives security and bug fixes, and the commercial version continues as Ciprocity. Whether and when to move is the program’s own decision. If a move is planned, the installed version is identified first.

What happens to closed cases and old intakes?

Both are normally brought across. Legal aid programs rely on old records for conflict checks and funder audits, so leaving them behind saves little. If volume is a concern, the names and case numbers are loaded for every record and the full detail only from a chosen year onwards, with the remainder kept read only.

Do documents from Open Case Management (OCM) keep their folders and dates in Neos?

Neos stores documents. Case Docs tab, organised in sub-tabs. Each file is placed under the client and matter it came from, and created and modified dates are carried, so a document still shows when it was written. The trial load is checked by count and by opening a sample.

Does everything in Open Case Management (OCM) have a place in Neos?

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

What has to be decided before Open Case Management (OCM) data is loaded into Neos?

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

Open Case Management (OCM) and Neos are the names and marks of their owners, used here only to identify the two systems.

Moving from Open Case Management (OCM) 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.