Data migration route
CP Financial to iManage Cloud migration
CP Financial is a server-based accounting and billing system, and iManage Cloud is a cloud document management system. Only files and their details have a place there, so this route carries the documents and archives the rest.
CP FinancialServer- Documents: Carried across
- Matters: Carried with mapping
- Emails: Confirmed in the analysis
- Custom fields: Confirmed in the analysis
- Templates: Confirmed in the analysis
iManage CloudCloud- Contacts: Kept as a readable archive
- Notes: Kept as a readable archive
- Time and expenses: Kept as a readable archive
- Billing: Kept as a readable archive
- Trust money: Kept as a readable archive
- Firm accounts: Kept as a readable archive
- 1 carried
- 1 mapped
- 3 to confirm
- 6 archived
What moves
What moves from CP Financial to iManage Cloud
Each row is a kind of record CP Financial holds, whether iManage Cloud has a place for it, and what is planned. On this route one kind of record carries across, one kind needs mapping, six kinds have no place in iManage Cloud and are archived and three kinds are confirmed in the analysis.
| Record | What is planned | ||
|---|---|---|---|
| MattersMatters or cases, with their numbers, types, parties and status | HeldClients and matters as billing records; case detail is in the case management program. | Has a place in partAs a workspace with client and matter metadata. Parties and status stay in practice management. | Carried with mapping |
| ContactsClients, other parties and referrers | Held in partClients, vendors and the names used for conflict checks. | No place | Kept as a readable archive |
| DocumentsFiles stored in or linked from the system | Held in partA financial document repository holds documents saved from within accounting. | Has a placeEach needs a workspace and valid client and matter values; its class sets default security. | Carried across |
| EmailsEmails saved to matters or to the store | To be confirmed | Has a placeLoaded as email documents into the workspace’s email folders. | Confirmed in the analysis |
| NotesFile notes, matter notes and contact notes | Held in partCollections correspondence is tracked against receivables. | No placeFile notes can be loaded as documents on the matter. | Kept as a readable archive |
| Time and expensesTime and expense entries, billed and unbilled | HeldIncludes task-based and electronic billing. | No place | Kept as a readable archive |
| BillingInvoices, payments and debtor balances | HeldReceivables, reminder statements, late fees and a collections module. | No place | Kept as a readable archive |
| Trust moneyTrust or client account ledgers and balances | HeldTrust accounting and escrow administration. | No place | Kept as a readable archive |
| Firm accountsGeneral ledger, office account and payables | HeldGeneral ledger with reconciliation, and accounts payable with 1099 production. | No place | Kept as a readable archive |
| Custom fieldsFields and record types the firm added itself | To be confirmed | Has a place in partA fixed number of custom profile fields, each a validated list. | Confirmed in the analysis |
| TemplatesPrecedents, document templates and automation | To be confirmed | Has a place in partPrecedents load as documents. Automation is rebuilt in the firm’s drafting tools. | Confirmed in the analysis |
What the plans mean
- Carried across
- iManage Cloud has a place for this kind of record. It is loaded there and checked against CP Financial.
- Carried with mapping
- iManage Cloud 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
- iManage Cloud has no place for it. It is exported in a format that opens without CP Financial 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
Only the documents have a place here.
iManage Cloud is a document management system: it takes files and the details that describe them. Most of what CP Financial holds is not files. Entries, balances, settings and lists have no place in a document store, and the table above is short for that reason. What can move is any document CP Financial produced or stored: invoices as PDFs, signed agreements, attachments, exported reports. Each is filed under the client or matter it relates to.
The useful version of this job is often an archive. A firm retiring a system wants its records readable later without keeping the subscription or the old PC. The data is exported in open formats, spreadsheets and PDFs, and filed in iManage Cloud in a workspace set aside for it, with access limited to the people who need it. That gives the firm one place to look, under the same retention rules as the rest of its documents.
CP Financial 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. iManage Cloud 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 CP Financial
Moving off CP Financial means moving a law firm’s whole back office: work in progress, the debtor ledger, trust and escrow, payables and the general ledger. Each is agreed to a report at a period end. The case management side of the suite is a separate source with its own records, and the two are tied together on client and matter before anything is loaded.
Which financial system is it
Client Profiles sold two: Profiles Financial for defence and general practice, and Profiles Plaintiff for contingency firms. Staff may call either one CP Financial. Settling which is installed is the first step, because a contingency firm’s case costs and settlements raise questions that an hourly firm’s books do not.
Expense recovery feeds
The expense recovery module takes charges from third-party cost collection systems and puts them on the matter. Unbilled recovered costs are part of work in progress and move with it. The device feeds themselves are an integration to set up again in the destination, or to retire.
Collections history
The collections module keeps correspondence about unpaid accounts, reminder statements, late fees and a risk rating. Most practice systems hold the balance and the invoice but not the chase history. That history is carried to the matter or the client as dated entries, and the rating is dropped unless the firm asks for a field.
Reports the firm relies on
More than 300 standard reports shipped with it, all built in Crystal Reports so that firms could copy and change them. The month-end pack the partners read is often a set of those modified copies. They are listed in the analysis, and each is matched to a report in the new system or flagged as one to rebuild.
Documents inside accounting
The financial document repository stores documents against accounting records, which is where scanned supplier invoices and similar paper tend to end up. These are not matter documents and are easy to miss. They are exported with a reference to the vendor or transaction and filed with the firm’s accounts records.
Where it is going
Arriving in iManage Cloud
Administrators of an iManage Cloud library have API access only, so nothing is loaded by writing to a database. For cloudimanage.com, the newer of its two cloud platforms, iManage lists a supervised import API, sync APIs and a metadata loader. Nothing can be filed loose: every document goes into a workspace, with valid client and matter values. So the client and matter lists, the workspace template and the security groups are built first.
Client and matter lists first
Custom1 and custom2 are validated lists, with each matter a child of its client. A value that is not already in the list cannot be assigned to a document. The lists are loaded from the practice management system or the old document store before any content, closed matters with documents included.
One workspace per matter
Each matter gets a workspace generated from a template, so the template is designed before migration: its tabs, its folders, which are created up front and which on demand. Old folder trees rarely match it. The mapping says where each old folder lands and what happens to folders with no equivalent.
Authors must be known users
Author and operator are profile fields tied to users of the library. Documents written by people who left years ago need a decision: recreate those people as inactive users, or assign a placeholder author. That choice affects searching by author for as long as the firm uses the system.
Hybrid security
iManage calls its security model hybrid: where a user’s groups disagree, the most permissive access applies unless one of them is denied. On cloudimanage.com that model cannot be changed. Default security is normally set on the workspace and inherited below it. Restricted matters from the old system are loaded with their access list already in place.
New numbers, original dates
Documents are numbered by iManage as they are loaded, so old numbers do not carry over as numbers. On cloudimanage.com the file date setting is fixed to the file’s own date, and on imanage.work it can be set either way. Which dates display is checked on the trial load. The old reference can be carried in a custom field or the description where the firm wants to search by it.
How NewLaw runs it
Four steps, in this order.
Nothing financial lands in iManage Cloud on this route, which makes it repeatable: a load can be run again until it is right.
Analysis
We read what CP Financial holds and how it is organised, then agree with you where each kind of record will sit in iManage Cloud. 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 iManage Cloud and checked against CP Financial: 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 CP Financial, a final pass over a weekend picks up what changed since the trial. CP Financial 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 CP Financial 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 CP Financial holds
What is in it, how its records link, and where each piece would sit in iManage Cloud. 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 iManage Cloud
Loaded data is not yet a working system. This is what NewLaw sets up in iManage Cloud, beyond the migration, so that people can work in it from the first day.
Setting up iManage Cloud is mostly design work done before any user logs in: how many libraries, what a workspace looks like, which profile fields are captioned for what, and who can see which matters. Then come the links that keep it running day to day, such as creating a workspace when a matter is opened in the practice management system, and the add-ins on each desk.
Set-up decisions in iManage Cloud
- Library structure and captions for client, matter and other fields
- Workspace templates, folder names and Flexible Folders rules by practice area
- Document classes, subclasses and the profile fields each one requires
- Roles, groups, default security and walls for restricted matters
- Workspace creation fed from the practice management system’s matter list
- Work Desktop, Outlook email filing and Mobility on each device, with training
Questions
CP Financial to iManage Cloud: what firms ask
Can we move accounting and keep the case management side?
Technically the two can be separated, but the link between them is what carries time from cases to bills. Leaving one behind means building a new bridge or keying entries twice. Moving the two together avoids that. If only one is moving, the analysis spells out what the remaining side loses.
How is trust and escrow handled at cutover?
Balances are taken per client and matter for each trust or escrow bank account at the cutover date and loaded as opening entries. The rehearsal on a full trial load is where the totals are agreed before the real weekend. Uncleared cheques and deposits are listed separately so the first bank reconciliation in the new system works.
Do we lose prior year figures?
Not from the firm’s records, though they may not all sit in the new system. Closing balances are loaded, and comparative figures too where the destination’s ledger takes them. Older detail stays in the old database, kept read only, and in year-end reports saved as PDF.
Do trust balances in CP Financial have a place in iManage Cloud?
No. iManage Cloud does not keep trust ledgers. Trust records from CP Financial are exported as ledgers and statements that open without it, and the firm settles where its trust accounting runs from the cutover date before the move is planned.
What happens to records iManage Cloud has no place for?
On this route that is contacts, notes, time entries, billing records, trust ledgers and the firm’s accounts. They are exported from CP Financial 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 CP Financial data is loaded into iManage Cloud?
Matters are carried with mapping, so each mapping is agreed with you first. Emails, custom fields and templates 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 CP Financial and into iManage Cloud
Other destinations from CP Financial
Other systems that move into iManage Cloud
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.
CP Financial and iManage Cloud are the names and marks of their owners, used here only to identify the two systems.
Moving from CP Financial to iManage Cloud?
Tell us what you are moving. You get a plan and a fixed price after the analysis.
We reply within one business day.