Data migration route
CityLaw to SurePoint Finance Enterprise migration
CityLaw is a server-based case management system for local government work, and SurePoint Finance Enterprise is a cloud practice management system. Case records move into matters, and time, billing and trust are set up in SurePoint Finance Enterprise, often from a separate accounts package.
- Matters: Carried across
- Calendar: Carried across
- Time and expenses: Carried across
- Billing: Carried across
- Contacts: Confirmed in the analysis
- Documents: Confirmed in the analysis
- Emails: 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
- Custom fields: Confirmed in the analysis
- Templates: Confirmed in the analysis
- Intake: Confirmed in the analysis
SurePoint Finance EnterpriseCloud- 4 carried
- 10 to confirm
What moves
What moves from CityLaw to SurePoint Finance Enterprise
Each row is a kind of record CityLaw holds, whether SurePoint Finance Enterprise has a place for it, and what is planned. On this route four kinds of record carry across and ten 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 | Carried across |
| ContactsClients, other parties and referrers | To be confirmed | Has a 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. | To be confirmed | Confirmed in the analysis |
| EmailsEmails saved to matters or to the store | HeldEmail can be saved directly to a matter. | To be confirmed | Confirmed in the analysis |
| NotesFile notes, matter notes and contact notes | To be confirmed | To be confirmed | Confirmed in the analysis |
| CalendarAppointments, court dates and deadlines | HeldTwo-way sync with Outlook; court-rule deadlines through CalendarRules. | Has a placeCalendar entries and dockets. | Carried across |
| 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. | Has a place | Carried across |
| BillingInvoices, payments and debtor balances | Held in partBilling and payment processing are listed among its functions. | Has a place | Carried across |
| Trust moneyTrust or client account ledgers and balances | To be confirmed | Has a place | Confirmed in the analysis |
| Firm accountsGeneral ledger, office account and payables | To be confirmed | Has a placeGeneral ledger and payables, by entity. | 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. | To be confirmed | Confirmed in the analysis |
| TemplatesPrecedents, document templates and automation | HeldWord templates filled from matter data by macro. | To be confirmed | Confirmed in the analysis |
| IntakeLeads, enquiries, intake forms and pipelines | To be confirmed | To be confirmed | Confirmed in the analysis |
What the plans mean
- Carried across
- SurePoint Finance Enterprise has a place for this kind of record. It is loaded there and checked against CityLaw.
- 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
Cases come across. The accounts are set up new.
A case management system holds the working file: parties, notes, deadlines, documents and the fields a practice area needs. It is not usually the firm’s ledger, so time, invoices and trust often sit in an accounting package beside it. Moving to SurePoint Finance Enterprise brings those two sources together. The case records come from CityLaw. Opening balances for debtors and trust, where they move at all, come from the accounts package and are agreed to its reports.
Case systems are heavy with custom fields, and that is where the mapping work is. A personal injury or immigration file can carry dozens of fields that a general practice system has no standard place for. Each one is matched to a field in SurePoint Finance Enterprise, created there as a custom field, or written into a note on the matter. The firm sees which before the load. Workflows and task templates are rebuilt, not copied.
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. SurePoint Finance Enterprise 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 SurePoint Finance Enterprise
Moving into SurePoint Finance Enterprise, the system long sold as LMS, is an accounting implementation with a data load inside it. The entity structure, chart of accounts and billing rules are designed before records arrive, because every time entry and payment posts into them. Smaller systems rarely hold data at that level of detail, so part of the preparation is adding what the source never recorded.
Entities and tax IDs first
The system can hold several legal entities and tax IDs. A firm coming from a single QuickBooks file, or from two files for two offices, decides how it wants to be structured from here on. That decision fixes where each bank account and matter belongs, and it is hard to revisit once history is posted.
History has to balance
Billing, trust and the general ledger are parts of one system, so loaded history must agree across all three. A receivable carried in for a matter needs the invoice behind it and the ledger entry behind that. Source systems that kept billing and accounts apart are reconciled to each other before extraction.
E-billing detail on time entries
For LEDES e-billing, time entries need task and activity codes and timekeepers need the classifications clients expect. A small-firm system may never have captured them. The firm decides whether historic entries are loaded uncoded as history only, with coding starting on new work from go-live.
Dockets as well as appointments
Calendars and dockets are both kept. In many source systems a court deadline and a client lunch are the same kind of record. The two are separated on the way in, using event types or keywords, and the docket entries for open matters are checked by the lawyers responsible.
Cost recovery codes
Disbursements such as copying and postage arrive through cost recovery and post to the matter. The cost types and their rates are set up to match how the firm charges today. Unbilled disbursements from the old system are then loaded against those types so they can be billed normally.
How NewLaw runs it
Four steps, in this order.
Financial records move on this route, so the balances are rehearsed before the real cutover.
Analysis
We read what CityLaw holds and how its records link, then agree with you, field by field, where each piece will sit in SurePoint Finance Enterprise. Anything with no place there comes across as a note or stays behind, and you see which before the move.
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.
Trial load
The data is loaded into SurePoint Finance Enterprise as a trial and checked against CityLaw: record counts, financial totals, the links between records, document dates. Exceptions are listed for you to decide.
Cutover
Changes in CityLaw are frozen for an agreed window, the data is collected a final time and SurePoint Finance Enterprise 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
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 SurePoint Finance Enterprise. 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 SurePoint Finance Enterprise
Loaded data is not yet a working system. This is what NewLaw sets up in SurePoint Finance Enterprise, beyond the migration, so that people can work in it from the first day.
The set-up decisions in Finance Enterprise are mostly made by the finance team. They cover the firm’s entity structure, its chart of accounts, how bills are approved and sent, and what each client’s e-billing portal demands. Timekeepers need rates and classifications. The reports used for partner compensation are specified early, because they test whether the structure underneath is right.
Set-up decisions in SurePoint Finance Enterprise
- Entity structure, tax IDs and the chart of accounts
- Bank and trust accounts with reconciliation set-up
- Timekeeper rates, classifications and task code sets
- Pre-bill approval steps and client billing rules
- LEDES e-billing formats for each corporate client
- Management and compensation reports the partners use
Questions
CityLaw to SurePoint Finance Enterprise: 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 SurePoint Finance Enterprise?
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 SurePoint Finance Enterprise 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 SurePoint Finance Enterprise?
Most of it does on paper. Contacts, documents, emails, notes, tasks, trust ledgers, the firm’s accounts, custom fields, templates 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 SurePoint Finance Enterprise is kept as a readable archive, and you see which before the move.
What has to be decided before CityLaw data is loaded into SurePoint Finance Enterprise?
Contacts, documents, emails, notes, tasks, trust ledgers, the firm’s accounts, custom fields, templates 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.
Other routes
Other routes from CityLaw and into SurePoint Finance Enterprise
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 SurePoint Finance Enterprise are the names and marks of their owners, used here only to identify the two systems.
Moving from CityLaw to SurePoint Finance Enterprise?
Tell us what you are moving. You get a plan and a fixed price after the analysis.
We reply within one business day.