Data migration route
Centerbase to iManage Cloud migration
Centerbase is a cloud practice management system, and iManage Cloud 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.
CenterbaseCloud- Documents: Carried across
- Emails: Carried across
- Matters: Carried with mapping
- Custom fields: Carried with mapping
- Templates: Carried with mapping
iManage CloudCloud- Contacts: Kept as a readable archive
- Notes: 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
- Trust money: Kept as a readable archive
- Firm accounts: Kept as a readable archive
- Intake: Kept as a readable archive
- 2 carried
- 3 mapped
- 9 archived
What moves
What moves from Centerbase to iManage Cloud
Each row is a kind of record Centerbase holds, whether iManage Cloud has a place for it, and what is planned. On this route two kinds of record carry across, three kinds need mapping and nine kinds have no place in iManage Cloud and are archived.
| Record | What is planned | ||
|---|---|---|---|
| MattersMatters or cases, with their numbers, types, parties and status | HeldMatters sit under clients and inherit client-level billing and accounting settings. | 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 | HeldClients, parties and other contacts, with a saved conflict check history. | No place | Kept as a readable archive |
| DocumentsFiles stored in or linked from the system | HeldBuilt-in Document Storage, or NetDocuments, iManage or SharePoint connected to matters. | 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 | Held in partEmails and attachments filed to a matter through the Outlook integration. | Has a placeLoaded as email documents into the workspace’s email folders. | Carried across |
| NotesFile notes, matter notes and contact notes | Held | No placeFile notes can be loaded as documents on the matter. | Kept as a readable archive |
| CalendarAppointments, court dates and deadlines | HeldTwo-way sync with Outlook; court rules through LawToolBox. | No place | Kept as a readable archive |
| TasksTo-dos and workflow steps assigned to people | HeldTasks can be created by automated workflows. | No placeiManage Tracker is a separate product with its own set-up. | Kept as a readable archive |
| Time and expensesTime and expense entries, billed and unbilled | HeldIncludes passive time capture from Outlook and Word. | No place | Kept as a readable archive |
| BillingInvoices, payments and debtor balances | HeldElectronic pre-bill approval, multi-payor bills and LEDES formats. | No place | Kept as a readable archive |
| Trust moneyTrust or client account ledgers and balances | HeldSeveral trust and retainer accounts can be held under one matter or at client level. | No place | Kept as a readable archive |
| Firm accountsGeneral ledger, office account and payables | HeldFull general ledger on a cash or accrual basis, with online banking and payables. | No place | Kept as a readable archive |
| Custom fieldsFields and record types the firm added itself | HeldUnlimited custom fields and configurable page layouts. | Has a place in partA fixed number of custom profile fields, each a validated list. | Carried with mapping |
| TemplatesPrecedents, document templates and automation | HeldDocument templates filled with client and matter data; bill templates. | Has a place in partPrecedents load as documents. Automation is rebuilt in the firm’s drafting tools. | Carried with mapping |
| IntakeLeads, enquiries, intake forms and pipelines | HeldWeb form enquiries arrive as Potential New Client records. | No place | Kept as a readable archive |
What the plans mean
- Carried across
- iManage Cloud has a place for this kind of record. It is loaded there and checked against Centerbase.
- 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.
- Kept as a readable archive
- iManage Cloud has no place for it. It is exported in a format that opens without Centerbase 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. iManage Cloud 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 Centerbase 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 iManage Cloud cannot hold goes to whatever replaces Centerbase for matters and billing, or into an archive.
Both are hosted by their makers, so nothing is collected from the firm’s office. What can be taken out of Centerbase depends on its export tools and on what its maker provides on request, and that is confirmed during the analysis, before a date is set. The subscription to Centerbase is kept running until the checks on iManage Cloud are finished.
Where the data is now
Leaving Centerbase
No two Centerbase sites look alike, because the product is configured around each firm. A firm leaving it is moving its own design as much as its data: the fields it added, the workflows it automated, the way bills are approved. The analysis begins by documenting that configuration, since the meaning of many records depends on it, and then deals with the general ledger and trust accounts.
Each site is configured
Custom fields are unlimited and page layouts are designed per firm, so the same information may be stored in quite different places from one Centerbase site to the next. A field list is extracted with usage counts. Fields that were added and abandoned are common in a long-lived site, and the firm decides which are worth carrying.
Settings inherited from clients
Billing arrangements, rate tables and accounting preferences are set on the client and applied to its matters. A destination that holds these on the matter needs them copied down to every matter, and one that has no rate tables needs rates entered another way. Either route is tested on a client with unusual terms.
Several trusts per matter
One matter can have more than one trust or retainer account, and funds can also be tracked at client level. Many systems allow a single trust ledger per matter. Where that is so, the firm decides how the separate balances are shown, and each one is still reconciled to its Centerbase figure before cutover.
Pre-bills in the approval chain
Pre-bills move electronically through reviewers, collecting mark-ups as they go. A pre-bill caught mid-approval at cutover has edits that live nowhere else. It is simplest to finish the billing cycle before the freeze, so that what moves is either unbilled time or a finished invoice.
Where documents really are
Documents may be in Centerbase’s own Document Storage, or in NetDocuments, iManage or SharePoint with Centerbase supplying the matter link. Only the first set has to be extracted. For the others the files stay put and the work is re-attaching each workspace to its matter in the new system.
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 Centerbase 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 Centerbase: 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 Centerbase, a final pass over a weekend picks up what changed since the trial. Centerbase 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 Centerbase 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 Centerbase 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
Centerbase to iManage Cloud: what firms ask
We keep our accounts in Centerbase. Do we have to change accounting systems as well?
Only if the destination does not have a general ledger. Centerbase holds the firm’s books and its trust records together, so the two leave together. Where the new system is practice management only, an accounting package is chosen and opened first, and opening balances are taken at a closed period end.
Can our financial history be loaded into Centerbase, or just balances?
The vendor describes moving practice management, billing, trust and accounting data, with a test migration validated before go-live. How many years of transactions are worth loading is a separate question. It is settled in the analysis by looking at what the source can supply cleanly and what the firm really reports on.
Our documents are in iManage. Does anything change for them?
The documents do not move. Centerbase connects to iManage and to NetDocuments, so the files stay in the document system the firm already uses. The work is matching each workspace to the right client and matter number, which is why matter numbering is fixed before the trial load.
Do trust balances in Centerbase have a place in iManage Cloud?
No. iManage Cloud does not keep trust ledgers. Trust records from Centerbase 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, calendar entries, tasks, time entries, billing records, trust ledgers, the firm’s accounts and intake records. They are exported from Centerbase 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 Centerbase data is loaded into iManage Cloud?
Matters, custom fields and templates are carried with mapping, so each mapping is agreed with you first. The firm also decides which closed matters and how many versions of a document are in scope.
Other routes
Other routes from Centerbase and into iManage Cloud
Other destinations from Centerbase
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.
Centerbase and iManage Cloud are the names and marks of their owners, used here only to identify the two systems.
Moving from Centerbase 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.