Data migration route
CityLaw to NetDocuments migration
CityLaw is a server-based case management system for local government work, and NetDocuments is a cloud document management system. Documents and email move, filed under the matters they came from. Time, billing and trust have no place in a document system.
- Documents: Carried across
- Emails: Carried across
- Matters: Carried with mapping
- Custom fields: Carried with mapping
- Templates: Carried with mapping
- Contacts: Confirmed in the analysis
- Notes: Confirmed in the analysis
- Tasks: Confirmed in the analysis
- Trust money: Confirmed in the analysis
- Firm accounts: Confirmed in the analysis
- Intake: Confirmed in the analysis
NetDocumentsCloud- Calendar: Kept as a readable archive
- Time and expenses: Kept as a readable archive
- Billing: Kept as a readable archive
- 2 carried
- 3 mapped
- 6 to confirm
- 3 archived
What moves
What moves from CityLaw to NetDocuments
Each row is a kind of record CityLaw holds, whether NetDocuments has a place for it, and what is planned. On this route two kinds of record carry across, three kinds need mapping, three kinds have no place in NetDocuments and are archived and six 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. | Has a place in partAs a client and matter value with its workspace. Other matter details stay in practice management. | Carried with mapping |
| 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 placeImported with profile values, folder, dates and access set per document. | Carried across |
| EmailsEmails saved to matters or to the store | HeldEmail can be saved directly to a matter. | Has a placeLoaded as email items profiled to the matter. | Carried across |
| NotesFile notes, matter notes and contact notes | To be confirmed | No placeFile notes are loaded as documents in the matter workspace. | 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. | To be confirmed | Confirmed in the analysis |
| 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 placeAs custom profile attributes, created in the repository before the load. | Carried with mapping |
| TemplatesPrecedents, document templates and automation | HeldWord templates filled from matter data by macro. | Has a place in partLoaded as documents in a precedents cabinet or workspace. Automation is set up afresh. | Carried with mapping |
| IntakeLeads, enquiries, intake forms and pipelines | To be confirmed | No place | Confirmed in the analysis |
What the plans mean
- Carried across
- NetDocuments has a place for this kind of record. It is loaded there and checked against CityLaw.
- Carried with mapping
- NetDocuments 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
- NetDocuments 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
The documents move. The accounts do not.
Moving from a matter system into a document management system is a documents job. NetDocuments has no place for time, invoices or trust, so there is no financial cutover on this route. What it does want is structure. Every document from CityLaw is filed into a workspace or folder for its client and matter, with a profile that says what it is. The client and matter list becomes that structure, which is why it is cleaned before any file is copied.
A document’s own details count for more here than anywhere. Created and modified dates, author, document type and version become searchable profile fields, and a wrong date on a few thousand files is hard to undo. Email filed to matters is carried as messages. Document copies can be run again, so the trial is repeated until counts and dates agree. Matter data that NetDocuments cannot hold goes to whatever replaces CityLaw for matters and billing, or into an archive.
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. NetDocuments 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 NetDocuments
Loading into NetDocuments means every document arrives with a profile. The cabinet, its profile attributes and the client and matter lookup tables are built first. Documents are then imported with an instruction file that says, line by line, which file gets which client, matter, author, document type, folder and access. Preparing that file from the old system’s data is most of the work.
Lookup tables before documents
Client and matter are validated attributes, with matter the child of client. A value missing from the lookup table cannot be used to profile a document. The tables are loaded from the practice management system first, closed matters included, and each matter is flagged open or closed so old ones stay out of pick lists.
Workspaces come from the profile
A workspace shows whatever is profiled to its matter. So the question is not where to put a folder tree but how to profile each file. Old folder names are often turned into a document type attribute, or kept as a workspace folder, and the mapping decides which for each one.
Import files are unforgiving
The import file is comma-separated text, and NetDocuments itself warns that opening one in Excel can strip leading zeros from numbers and alter dates. A matter number of 00123 that becomes 123 will not match its lookup value. The files are kept as plain text from start to finish and are not opened in a spreadsheet.
Folder limits and depth
A folder can hold any number of documents but no more than 500 subfolders. Deep trees copied from a file server also work against the way the system is searched. Where a matter arrives with hundreds of nested folders, the plan flattens them and keeps the lost path in the document name or an attribute.
Security at the right level
Access can be set on the cabinet, by profile value, on a workspace or on a single document. Restricted matters are best carried as workspace or profile-based security, so that new documents pick it up. Document-by-document access lists copied from an old system are loaded only where the restriction was real.
How NewLaw runs it
Four steps, in this order.
Nothing financial lands in NetDocuments 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 NetDocuments. 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 NetDocuments 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 NetDocuments. 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
Setting up NetDocuments
Loaded data is not yet a working system. This is what NewLaw sets up in NetDocuments, beyond the migration, so that people can work in it from the first day.
Beyond the load, NetDocuments has to be designed: how many cabinets the firm needs, which profile attributes every document must carry, and what a new matter’s workspace looks like on its first day. After that it is connected to the practice management system so client and matter lists stay current, and ndOffice and the email filing tools are set up for each person, with training on profiling.
Set-up decisions in NetDocuments
- Cabinet design: one for the firm, or several by purpose
- Profile attributes, lookup tables and the client and matter hierarchy
- Workspace layout with default folders, filters and saved searches
- User groups, cabinet membership and security for restricted matters
- A feed of new clients and matters from practice management
- ndOffice, ndMail and Outlook filing on every desk, with training
Questions
CityLaw to NetDocuments: 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 NetDocuments?
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 NetDocuments 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 NetDocuments has no place for?
On this route that is calendar entries, 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 NetDocuments?
Matters, custom fields and templates are carried with mapping, so each mapping is agreed with you first. Contacts, notes, tasks, 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 NetDocuments
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 NetDocuments are the names and marks of their owners, used here only to identify the two systems.
Moving from CityLaw to NetDocuments?
Tell us what you are moving. You get a plan and a fixed price after the analysis.
We reply within one business day.