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

Data migration route

CityLaw to Neos migration

CityLaw is a server-based case management system for local government 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.

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

What moves

What moves from CityLaw to Neos

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

Records in CityLaw and their place in Neos
RecordIn CityLawIn NeosWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldAssignments, lawsuits, claims, contracts and prosecution cases.Has a placeCases by case type.Carried across
ContactsClients, other parties and referrersTo be confirmedHas a placeParties, providers and case contacts. Contacts can be imported from CSV.Confirmed in the analysis
DocumentsFiles stored in or linked from the systemHeldAlmost any file type saved to a matter, organised in virtual folders.Has a placeCase Docs tab, organised in sub-tabs.Carried across
EmailsEmails saved to matters or to the storeHeldEmail can be saved directly to a matter.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 notesTo be confirmedHas a placeConfirmed in the analysis
CalendarAppointments, court dates and deadlinesHeldTwo-way sync with Outlook; court-rule deadlines through CalendarRules.Has a placeCase calendar entries.Carried across
TasksTo-dos and workflow steps assigned to peopleHeldTasks assigned to staff sync to their Outlook task lists.Has a placeLoaded as checklist items.Carried across
Time and expensesTime and expense entries, billed and unbilledHeld in partTime management is listed among its functions.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 partBilling and payment processing are listed among its functions.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 itselfHeld in partEntry fields can be enabled, disabled or made required in each module.Has a placeUser-defined fields are created on the relevant tab first.Carried with mapping
TemplatesPrecedents, document templates and automationHeldWord templates filled from matter data by macro.Has a place in partTemplates are rebuilt for Neos document generation.Carried with mapping
IntakeLeads, enquiries, intake forms and pipelinesTo be confirmedHas a placeIntakes tab. Simple intake imports from CSV are supported.Confirmed in the analysis

What the plans mean

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

CityLaw 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

A CityLaw office holds its data on its own SQL Server, which makes extraction a matter of access and permission inside the agency. The harder part is fit. Assignments, claims and prosecution cases are public-sector record types, and a system designed for private practice has to be told what each one becomes. Procurement and records-retention rules usually set the timetable.

  1. Modules, not one matter list

    Work is split across Assignments, Litigation and Claims, with contract and prosecution records beside them. Each module has its own entry screen and its own fields. They are extracted separately and mapped separately, usually to different matter types in the destination, so that a claim against the city does not arrive looking like an advice file.

  2. Virtual folders

    Documents are saved to a matter and arranged in virtual folders. A virtual folder is an arrangement inside the system and may not exist as a directory on the server. Where that is so, the export has to rebuild each document’s path from the database, and we test it on matters with deep folder trees before trusting it across the whole set.

  3. Calendar entries live twice

    Appointments and tasks sync both ways with Outlook, but deleting one in Outlook does not remove it from CityLaw’s master calendar. The two can therefore disagree. We treat the master calendar as the record, and deadlines generated from court rules are checked against the rules service the new system uses.

  4. Templates driven by Word macros

    Document assembly works by importing matter data into Word templates through Visual Basic macros, which offices can write themselves. Those macros read CityLaw and nothing else. Each template in use is rebuilt with the destination’s merge fields, and any logic inside a macro is written down first so it is not lost in the rebuild.

  5. Fields each office switched on

    Entry screens can be customised by enabling or disabling fields and marking some as required. Two offices on the same version may be recording different things. The analysis works from the fields that actually contain data, not from the full list the product offers.

More about moving off CityLaw

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

  1. Analysis

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

  4. Cutover

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

CityLaw to Neos: what firms ask

Can a system built for private firms hold claims and assignments?

Often, with configuration. A claim becomes a matter type with its own fields for claimant, incident and amounts. An assignment becomes an advice matter for a client department. What a private-practice system may lack is prosecution case handling, and whether it can serve that work is tested during the analysis, before any commitment is made.

Some of our documents are in OnBase. What then?

Cycom offers an integration with the OnBase document management system. Where an office uses it, some documents may be in CityLaw and others in OnBase. We establish which store holds which matters, and whether OnBase is staying. If it stays, the new system only needs links. Otherwise both stores are moved.

How far back should the history go?

Public records rules usually answer this before preference does. The office’s retention schedule decides which closed matters must stay retrievable and for how long. Those inside the schedule either move or stay in the read-only CityLaw database, which the agency already hosts. Matters past retention are handled under the agency’s disposal process.

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

Most of it does on paper. Contacts, notes, trust ledgers, the firm’s accounts and intake records 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 CityLaw 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. Contacts, notes, trust ledgers, the firm’s accounts and intake records 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

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

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