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

Data migration route

Ciprocity to Neos migration

Ciprocity is a cloud case management system for legal aid work. Neos is a case management system for personal injury work, run the same way. The records line up case for case, and the detail is in the fields and stages.

FromCiprocityCloud
  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
  14. Firm accounts: Confirmed in the analysis
ToNeosCloud
  • 7 carried
  • 5 mapped
  • 2 to confirm
What the two products hold. The analysis confirms it field by field.

What moves

What moves from Ciprocity to Neos

Each row is a kind of record Ciprocity 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 and two kinds are confirmed in the analysis.

Records in Ciprocity and their place in Neos
RecordIn CiprocityIn NeosWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldCases with problem codes, funding codes, assignments, closing codes and outcomes.Has a placeCases by case type.Carried across
ContactsClients, other parties and referrersHeldOne contact can appear on many cases in different roles; aliases are kept.Has a placeParties, providers and case contacts. Contacts can be imported from CSV.Carried across
DocumentsFiles stored in or linked from the systemHeldA documents browser on each case, with OCR run on scanned uploads.Has a placeCase Docs tab, organised in sub-tabs.Carried across
EmailsEmails saved to matters or to the storeHeld in partInbound email from staff accounts threads into the case; SMS messages are kept too.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 notesHeldNotes are one kind of activity on the case.Has a placeCarried across
CalendarAppointments, court dates and deadlinesHeldAppointments and ticklers on a shared calendar, with iCal and Office 365 sync.Has a placeCase calendar entries.Carried across
TasksTo-dos and workflow steps assigned to peopleHeldTicklers, and workflow rules that create them.Has a placeLoaded as checklist items.Carried across
Time and expensesTime and expense entries, billed and unbilledHeldTime slips with activity type and funding source; optional supervisor approval.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 balancesHeld in partNo client invoicing described; a grants manager keeps funder ledgers.Has 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 balancesTo be confirmedTo be confirmedConfirmed in the analysis
Firm accountsGeneral ledger, office account and payablesTo be confirmedNo placeThe general ledger stays in QuickBooks.Confirmed in the analysis
Custom fieldsFields and record types the firm added itselfHeldCustom fields and case tabs built by the program’s administrator.Has a placeUser-defined fields are created on the relevant tab first.Carried with mapping
TemplatesPrecedents, document templates and automationHeldDocument assembly from .docx and RTF templates, form letters and docassemble.Has a place in partTemplates are rebuilt for Neos document generation.Carried with mapping
IntakeLeads, enquiries, intake forms and pipelinesHeldPrescreen, eligibility against poverty guidelines, duplicate and conflict 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 Ciprocity.
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. Ciprocity 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.

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

Where the data is now

Ciprocity gives each program its own instance and database, so the data to be moved belongs to one customer and nobody else’s is mixed in. The record design is specific to legal aid. People are contacts with roles on cases, work is a single stream of activities, and nearly everything is coded for a funder. A destination outside legal aid needs most of that translated.

  1. Roles belong to the case

    A contact holds the name, phone and address. Whether that person is the client, the opposing party or opposing counsel is recorded on the case, and one contact can hold different roles on different cases. Systems that file a contact as a client or as an other party need a rule for people who have been both.

  2. One stream of activities

    Notes, time slips, ticklers and appointments are all activities and share one history on the case. A destination system will split them into file notes, time entries, tasks and calendar events. Each activity type is mapped separately, and the trial load is checked by counting each type per case, not just the total.

  3. Closed means a date

    A case counts as closed when Date Closed is filled in, and closing also records a closing code and an outcome. Changing the status alone does not close it. Cases with a closed-looking status and no date are found in the analysis and put right, or they will arrive in the new system as open work.

  4. Three assignment slots

    Each case has a Primary Counsel, a co-counsel and a third assignee that is labelled Case Manager unless the program renamed it. Pro bono attorneys and referral recipients can also be recorded. A destination with one responsible lawyer per matter needs somewhere for the others, usually as related staff or a custom field.

  5. Locked and approved time

    Older time periods are locked so that months already reported to funders stay closed, and where approval is used, approved entries cannot be edited in the ordinary way. That state is part of the record. Time is loaded with its funding source and its approval status so a past grant report can be matched to the hours behind it.

More about moving off Ciprocity

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 Ciprocity and checking each trial against Ciprocity.

  1. Analysis

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

  4. Cutover

    Changes in Ciprocity 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 Ciprocity as at the cutover date. Ciprocity 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 Ciprocity 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 fromCiprocity
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 Ciprocity 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

Ciprocity to Neos: what firms ask

Our contacts appear on dozens of cases. Will they be duplicated?

They should arrive once each. A Ciprocity contact is a single record linked to every case it has a role on, so the load creates the contact first and then the links. Duplicates that already exist are a separate matter. A merge pass before extraction is worthwhile for those.

Can ethical walls be carried across?

The walls themselves are a security setting in Ciprocity and cannot be copied into another product. The list of who is walled off from which case can be. It is extracted with the cases and used to set restrictions in the new system before any user logs in, then tested with an account that should be blocked.

What about the HUD, VAWA and immigration modules?

These are optional modules with their own fields and reports, switched on per program. Their data sits on the case and is moved as fields. The reporting they produce, such as HUD 9902 submissions, is a function of the software. If the destination cannot produce it, that reporting needs another home before cutover.

Do trust balances in Ciprocity 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 Ciprocity 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.

Does everything in Ciprocity have a place in Neos?

Most of it does on paper. Trust ledgers and the firm’s accounts 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 Ciprocity 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 and the firm’s accounts 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

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

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