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

Data migration route

CityLaw to Server drives migration

CityLaw is a server-based case management system for local government work, and Server drives are plain files on equipment the firm controls. Documents move into a folder for each client and matter, and the data behind them is kept as an export.

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

What moves

What moves from CityLaw to Server drives

Each row is a kind of record CityLaw holds, whether Server drives have a place for it, and what is planned. On this route one kind of record carries across, two kinds need mapping, six kinds have no place in Server drives and are archived and five kinds are confirmed in the analysis.

Records in CityLaw and their place in Server drives
RecordIn CityLawIn Server drivesWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldAssignments, lawsuits, claims, contracts and prosecution cases.No placeA matter becomes a folder; its details survive only in an index file.Kept as a readable archive
ContactsClients, other parties and referrersTo be confirmedNo placeCan be kept only as an exported spreadsheet.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 placeFiles in folders, named and dated during the load.Carried across
EmailsEmails saved to matters or to the storeHeldEmail can be saved directly to a matter.Has a place in partAs .msg or .eml files in each matter’s correspondence folder.Carried with mapping
NotesFile notes, matter notes and contact notesTo be confirmedHas a place in partAs a text or PDF file per matter, not as separate records.Confirmed in the analysis
CalendarAppointments, court dates and deadlinesHeldTwo-way sync with Outlook; court-rule deadlines through CalendarRules.No placeKept as a readable archive
TasksTo-dos and workflow steps assigned to peopleHeldTasks assigned to staff sync to their Outlook task lists.No placeKept as a readable archive
Time and expensesTime and expense entries, billed and unbilledHeld in partTime management is listed among its functions.No placeOnly as exported reports or spreadsheets.Kept as a readable archive
BillingInvoices, payments and debtor balancesHeld in partBilling and payment processing are listed among its functions.Has a place in partInvoices as PDF files; no ledger.Kept as a readable archive
Trust moneyTrust or client account ledgers and balancesTo be confirmedNo placeOnly as exported ledger reports kept as files.Confirmed in the analysis
Firm accountsGeneral ledger, office account and payablesTo be confirmedNo placeConfirmed 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.No placeKept as a readable archive
TemplatesPrecedents, document templates and automationHeldWord templates filled from matter data by macro.Has a place in partPrecedents as Word files; merge fields tied to the old system stop working.Carried with mapping
IntakeLeads, enquiries, intake forms and pipelinesTo be confirmedNo placeConfirmed in the analysis

What the plans mean

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

Out of the system, into folders the firm can read.

File storage has folders and files and nothing else. Moving from CityLaw into Server drives means turning matters into a folder tree, usually client, then matter, then the folders used inside it. The naming rule is agreed first, because it is hard to change once thousands of folders exist: whether the matter number leads, how closed matters are separated, what happens to characters Server drives do not allow in a name.

Everything that is not a document needs somewhere to go. Contacts, notes, time, invoices and trust ledgers have no place in a folder, so they are exported as spreadsheets and reports and stored alongside, often as a summary file in each matter folder and a full set in an archive area. Firms choose this route to keep a readable copy of a system they are retiring, or as a staging step. The export is checked either way: folders against matters, files against the document register in CityLaw.

Both ends are on equipment the firm controls, so the work is done on the firm’s own network with its IT provider. Disk space for a second full copy is checked first. The original in CityLaw stays untouched until the copy in Server drives has been checked.

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

Some firms leave a practice or document system and keep their documents on a server drive, either as the working store or as the archive of a system being switched off. The files will arrive without the database that described them. Everything the firm wants to keep knowing about a document has to be put into its path, its name or an index file.

  1. Agree the tree and the names

    A fixed pattern is chosen, for example client name and number, then matter number and short description, then a standard set of subfolders. Document titles from the old system become file names. Where two documents share a title, a date or sequence number is added so nothing is overwritten.

  2. Budget the path length

    Share name, client, matter, subfolder and file name all count towards the 260 character limit that many Windows programs still apply. The pattern is tested against the firm’s longest client names and document titles before the load. Descriptions are trimmed by rule, never by cutting off the file extension.

  3. Dates have to be set deliberately

    A file written to the server today is dated today unless its modified date is set from the old system’s record. Document dates are how lawyers find things in a folder. Which date each file is to carry is agreed in the analysis, and the trial load checks a sample.

  4. Emails become message files

    Emails filed to matters in the old system are written out as .msg or .eml files in a correspondence folder, named by date, sender and subject so they sort in order. Attachments stay inside the message. Subjects with characters Windows forbids are cleaned, and long ones cut.

  5. Keep an index beside the files

    A spreadsheet or small database listing every document with its matter, author, original date, document type and new path is the only place the old system’s profile data survives. It lets someone find a document by something other than its name. What the index records, and who keeps it, is decided in the analysis.

More about moving into Server drives

How NewLaw runs it

Four steps, in this order.

Nothing financial lands in Server drives on this route, which makes it repeatable: a load can be run again until it is right.

  1. Analysis

    We read what CityLaw holds and how it is organised, then agree with you where each kind of record will sit in Server drives. Anything with no place there stays behind or is archived, and you see which before the move.

  2. Clean-up

    Duplicate clients, matters and folders are merged where they can be identified, and naming is put into one format, before anything is copied. It is not always possible to find every one, so some may carry across.

  3. Trial load

    A trial is loaded into Server drives and checked against CityLaw: record and file counts, the links between records, document dates, and a sample opened by your own people. Exceptions are listed for you to decide.

  4. Cutover

    There is no financial cutover on this route. After a short freeze on changes in CityLaw, a final pass over a weekend picks up what changed since the trial. 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 toServer drives

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 Server drives. 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

Structure, permissions and handover

Server drives are storage, not an application, so there is no product to configure. What is agreed and set up is the folder structure, who can open what, and how the result is handed to the firm.

A server drive does only what the firm and its IT provider make it do. Setting one up as a document store means building the share, deciding who can open which folders, and arranging the protections a document system would have supplied: backups, earlier versions and a way to recover a deleted folder. The filing rule is written down and taught.

What is agreed and set up

  • Share and top-level folders for clients, precedents and administration
  • Security groups and folder permissions, with restricted matters separate
  • Drive letter mapped for every user at sign-in
  • Backup schedule and shadow copies for earlier versions
  • Written naming rule for client, matter and document names
  • Read-only area for closed matters and archived system exports

Questions

CityLaw to Server drives: 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 Server drives?

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 Server drives 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 Server drives have no place for?

On this route that is matters, calendar entries, tasks, time entries, billing records and custom fields. They are exported from CityLaw 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 CityLaw data is loaded into Server drives?

Emails 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 decides which closed matters and how many versions of a document are in scope.

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 Server drives are the names and marks of their owners, used here only to identify the two systems.

Moving from CityLaw to Server drives?

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

We reply within one business day.