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

Moving off a system

Migrating from CityLaw

Legal case management for city and county attorney offices, covering assignments, litigation, claims, contracts and prosecution. This page sets out what CityLaw holds, what moving off it involves and where its records can go.

Where it can go

Routes from CityLaw

Each route has a page of its own: what moves, what has no place in the destination and how the move is run.

What it holds

The records CityLaw keeps

Fourteen kinds of record matter to a move. CityLaw keeps nine of them, three in part, and five could not be confirmed from its maker’s own material.

  • MattersYesAssignments, lawsuits, claims, contracts and prosecution cases.
  • ContactsTo be confirmedClients, other parties and referrers
  • DocumentsYesAlmost any file type saved to a matter, organised in virtual folders.
  • EmailsYesEmail can be saved directly to a matter.
  • NotesTo be confirmedFile notes, matter notes and contact notes
  • CalendarYesTwo-way sync with Outlook; court-rule deadlines through CalendarRules.
  • TasksYesTasks assigned to staff sync to their Outlook task lists.
  • Time and expensesIn partTime management is listed among its functions.
  • BillingIn partBilling and payment processing are listed among its functions.
  • Trust moneyTo be confirmedTrust or client account ledgers and balances
  • Firm accountsTo be confirmedGeneral ledger, office account and payables
  • Custom fieldsIn partEntry fields can be enabled, disabled or made required in each module.
  • TemplatesYesWord templates filled from matter data by macro.
  • IntakeTo be confirmedLeads, enquiries, intake forms and pipelines

Moving off it

Leaving CityLaw

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.

The system

What CityLaw is

CityLaw is case management software for municipal law departments, made by Cycom Data Systems. The same system is sold to counties as CountyLaw. Cycom says it was first installed in 1985 and has since been installed throughout the United States. It is built for public agencies, so its record types reflect a city attorney’s work more than a private firm’s.

It runs on the agency’s own Windows server with a Microsoft SQL Server database, and staff reach it through a browser with Microsoft Office on the workstation. Work is organised in modules for Assignments, Litigation and Claims, alongside contracts and prosecution. Files of almost any type are saved to a matter in virtual folders, and the calendar syncs with Outlook.

Kind
Case management, local government
Runs as
On the firm’s server or a hosted server
Made by
Cycom Data Systems
Mainly used in
The United States
Also known as
City Law, CountyLaw, CYCOM

How NewLaw runs it

Four steps, in this order.

Financial records move on most routes, so the balances are rehearsed before the real cutover.

  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 the new system. 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 the new system 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 the new system 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

Choose where the CityLaw data is going, or tell us you have not decided. 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

Not decided yet is a fine answer.

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 the new system. 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.

After the move

Setting up the system you move to

A migration ends with data in a new system. Whether people can work in it on the first day depends on how that system was set up: matter types, templates, billing, permissions. NewLaw does that work as well, and each destination’s page says what its set-up involves.

Questions

Moving off CityLaw: 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.

Where to start

Still deciding where to move?

Choose the system before you plan the move, and see where AI fits once your data is in it.

How we do itDiscovery to rollout, step by step

CityLaw and the other product names and logos on this page belong to their owners and are used only to identify the systems.

Moving off CityLaw?

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

We reply within one business day.