Data migration route
CityLaw to Box migration
CityLaw is a server-based case management system for local government work, and Box is cloud file storage. Documents move into a folder for each client and matter, and the data behind them is kept as an export.
- Documents: Carried across
- Emails: Carried with mapping
- Custom fields: Carried with mapping
- Templates: Carried with mapping
- Contacts: Confirmed in the analysis
- Notes: Confirmed in the analysis
- Trust money: Confirmed in the analysis
- Firm accounts: Confirmed in the analysis
- Intake: Confirmed in the analysis
BoxCloud- Matters: Kept as a readable archive
- Calendar: Kept as a readable archive
- Tasks: Kept as a readable archive
- Time and expenses: Kept as a readable archive
- Billing: Kept as a readable archive
- 1 carried
- 3 mapped
- 5 to confirm
- 5 archived
What moves
What moves from CityLaw to Box
Each row is a kind of record CityLaw holds, whether Box has a place for it, and what is planned. On this route one kind of record carries across, three kinds need mapping, five kinds have no place in Box and are archived and five kinds are confirmed in the analysis.
| Record | In CityLaw | What is planned | |
|---|---|---|---|
| MattersMatters or cases, with their numbers, types, parties and status | HeldAssignments, lawsuits, claims, contracts and prosecution cases. | No placeA matter is a folder, optionally with metadata; there is no matter record. | Kept as a readable archive |
| ContactsClients, other parties and referrers | To be confirmed | No place | Confirmed in the analysis |
| DocumentsFiles stored in or linked from the system | HeldAlmost any file type saved to a matter, organised in virtual folders. | Has a placeFiles and folders, named and dated as they are loaded. | Carried across |
| EmailsEmails saved to matters or to the store | HeldEmail can be saved directly to a matter. | Has a place in partAs .msg or .eml files in the matter folder. | Carried with mapping |
| NotesFile notes, matter notes and contact notes | To be confirmed | Has a place in partAs documents in the matter folder, not as a notes record. | Confirmed in the analysis |
| CalendarAppointments, court dates and deadlines | HeldTwo-way sync with Outlook; court-rule deadlines through CalendarRules. | No place | Kept as a readable archive |
| TasksTo-dos and workflow steps assigned to people | HeldTasks assigned to staff sync to their Outlook task lists. | No place | Kept as a readable archive |
| Time and expensesTime and expense entries, billed and unbilled | Held in partTime management is listed among its functions. | No place | Kept as a readable archive |
| BillingInvoices, payments and debtor balances | Held in partBilling and payment processing are listed among its functions. | No place | Kept as a readable archive |
| Trust moneyTrust or client account ledgers and balances | To be confirmed | No place | Confirmed in the analysis |
| Firm accountsGeneral ledger, office account and payables | To be confirmed | No place | Confirmed in the analysis |
| Custom fieldsFields and record types the firm added itself | Held in partEntry fields can be enabled, disabled or made required in each module. | Has a place in partMetadata templates can hold fields such as matter number and client. | Carried with mapping |
| TemplatesPrecedents, document templates and automation | HeldWord templates filled from matter data by macro. | Has a place in partPrecedents load as ordinary files; no document automation. | Carried with mapping |
| IntakeLeads, enquiries, intake forms and pipelines | To be confirmed | No place | Confirmed in the analysis |
What the plans mean
- Carried across
- Box has a place for this kind of record. It is loaded there and checked against CityLaw.
- Carried with mapping
- Box 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
- Box 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 Box 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 Box does 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.
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. Box 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
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.
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.
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.
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.
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.
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.
Where it is going
Arriving in Box
Loading a firm’s files into Box means deciding the folder tree and its owners first, because permissions follow the tree. Box has no matter record. A matter is a folder, and anything else the firm knew about it, such as the matter number, client or status, survives only in the folder name or in metadata fields set up before the load.
Decide who owns the top level
Box’s own planning guidance sets out two models: users create their own top-level folders, or administrators own them all and invite people in. For matter files most later decisions depend on this one, including who can share outside the firm and whose storage allowance the files count against.
Restricted matters go near the top
Access in Box only flows downward. A person who can open a client folder can open every matter under it, and a subfolder cannot be hidden from them. Matters behind an information barrier therefore need their own top-level folders, and the list of those matters is agreed before the structure is built.
Names Box will not accept
Box rejects a slash or backslash anywhere in a file or folder name, and spaces at the start or end. Files from older systems and from Macs often have both. They are renamed by rule before loading and the firm receives the list, so that a document cited by its old name can still be found.
Matter details become metadata
A metadata template can hold the matter number, client name, practice area and closed date against each matter folder. The template has to exist before the files arrive so the values can be written during the load. Without it, the folder name is the only place that information lives.
File size follows the owner’s plan
The largest file Box accepts depends on the plan of whoever owns the folder. Litigation matters with video or forensic images are where this bites. Oversized files are found in the analysis, and the firm chooses between a higher plan and keeping those files somewhere else.
How NewLaw runs it
Four steps, in this order.
Nothing financial lands in Box on this route, which makes it repeatable: a load can be run again until it is right.
Analysis
We read what CityLaw holds and how it is organised, then agree with you where each kind of record will sit in Box. Anything with no place there stays behind or is archived, and you see which before the move.
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.
Trial load
A trial is loaded into Box 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.
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
What happens after you send it
- A free first call
We go through your answers with you and ask about anything they leave open.
- An analysis of what CityLaw holds
What is in it, how its records link, and where each piece would sit in Box. Anything with no place there comes across as a note or stays behind, and you see which before the move.
- 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
Box is 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.
Most of a Box set-up is governance. The folder tree, the groups that are invited into it and the rules on sharing outside the firm are decided and built before any file is loaded. After the load, staff need Box Drive on their PCs and a short written guide to where a new matter folder is created and who creates it.
What is agreed and set up
- Top-level folder structure and who owns each folder
- Groups for teams, mapped to collaborator roles
- Metadata template for matter number, client and status
- Shared link defaults and rules for external collaborators
- Box Drive installed and signed in on each PC
- Version limits and retention agreed with the firm’s records policy
Questions
CityLaw to Box: 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 Box?
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 Box 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 Box has no place for?
On this route that is matters, calendar entries, tasks, time entries and billing records. 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 Box?
Emails, 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 decides which closed matters and how many versions of a document are in scope.
Other routes
Other routes from CityLaw and into Box
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.
Choose your systems
Technology stack selection
Decide which practice management system your firm runs, with the evidence and the cost beside it.
About four weeks for a firm of about 15 people. Fixed price, set after a free first call.
Move your data
Data migration
Your data is cleaned up before anything moves, then a trial load is checked against the old system.
Fixed price, agreed after the analysis.
Set up your new system
Implementation
Your new system set up around the way your firm works: configuration, document automation and training.
A small firm of 1 to 10 users typically takes 4 to 8 weeks. A mid-sized firm of 10 to 50 users takes 8 to 16 weeks.
Put AI to work
AI advisory and enablement
A small group of your people learn to use an approved AI tool on real work, under written rules.
Two to four weeks for a small first group. Fixed price, set after a free first call.
CityLaw and Box are the names and marks of their owners, used here only to identify the two systems.
Moving from CityLaw to Box?
Tell us what you are moving. You get a plan and a fixed price after the analysis.
We reply within one business day.