Skip to content
NEWLAW.COM
+61 1300 495 281
Let’s talk

Data migration route

CasePeer to iManage Cloud migration

CasePeer is a cloud case management system for personal injury work, 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.

FromCasePeerCloud
  1. Documents: Carried across
  2. Emails: Carried across
  3. Matters: Carried with mapping
  4. Templates: Carried with mapping
  5. Billing: Confirmed in the analysis
  6. Custom fields: Confirmed in the analysis
ToiManage CloudCloud
  1. Contacts: Kept as a readable archive
  2. Notes: Kept as a readable archive
  3. Calendar: Kept as a readable archive
  4. Tasks: Kept as a readable archive
  5. Time and expenses: Kept as a readable archive
  6. Trust money: Kept as a readable archive
  7. Intake: Kept as a readable archive
Readable archiveNo place in iManage Cloud
  • 2 carried
  • 2 mapped
  • 2 to confirm
  • 7 archived
What the two products hold. The analysis confirms it field by field.

What moves

What moves from CasePeer to iManage Cloud

Each row is a kind of record CasePeer holds, whether iManage Cloud has a place for it, and what is planned. On this route two kinds of record carry across, two kinds need mapping, seven kinds have no place in iManage Cloud and are archived and two kinds are confirmed in the analysis.

Records in CasePeer and their place in iManage Cloud
RecordIn CasePeerIn iManage CloudWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldPersonal injury cases with statutes, status and links to connected cases.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 referrersHeldClients, defendants, insurers, providers and referral sources.No placeKept as a readable archive
DocumentsFiles stored in or linked from the systemHeldUnlimited storage, a mail centre for incoming post, and Dropbox or OneDrive links.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 storeHeld in partText and email messages with clients are tied to the case.Has a placeLoaded as email documents into the workspace’s email folders.Carried across
NotesFile notes, matter notes and contact notesHeldCase notes, including notes written automatically by workflows.No placeFile notes can be loaded as documents on the matter.Kept as a readable archive
CalendarAppointments, court dates and deadlinesHeldEvents, statutes and litigation event plans. Syncs to Outlook, Google or iCal.No placeKept as a readable archive
TasksTo-dos and workflow steps assigned to peopleHeldTask manager with workflows triggered by case status, age or client details.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 unbilledHeld in partTime logging is built in. The product is designed for contingency fee work.No placeKept as a readable archive
BillingInvoices, payments and debtor balancesTo be confirmedClient payments are taken through LawPay. Invoicing was not confirmed.No placeConfirmed in the analysis
Trust moneyTrust or client account ledgers and balancesHeld in partClient trust tracking by case. Trust accounting itself runs in a linked package.No placeKept as a readable archive
Custom fieldsFields and record types the firm added itselfTo be confirmedSold as pre-configured. How far fields can be added was not confirmed.Has a place in partA fixed number of custom profile fields, each a validated list.Confirmed in the analysis
TemplatesPrecedents, document templates and automationHeldDocument automation from case data.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 pipelinesHeldIntake manager with forms, checklists and conversion reporting.No placeKept 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 CasePeer.
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 CasePeer 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 CasePeer 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 CasePeer 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 CasePeer 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 CasePeer is kept running until the checks on iManage Cloud are finished.

Where the data is now

CasePeer holds an injury case in a fixed shape that suits the work: treatment, bills, liens, costs and settlement each have their own place. Leaving it means finding where each of those sits in the destination. A system built for injury work will have most of them. A general system needs fields or record types set up first.

  1. Treatment and medical bills

    Each provider on a case carries treatment, billed amounts and the status of the requests made for records and bills. This is the bulk of the structured data and the part clients ring about. It is mapped provider by provider, and billed totals per case are compared after the trial load, since they feed the demand.

  2. Liens and settlement distribution

    Liens are tracked against the case, and the settlement figures work out fees, costs, lien payments and the client’s net. For settled cases the final distribution is a record the firm must be able to produce later. It is carried as data where the destination can hold it, and otherwise as a saved statement on the case.

  3. Cost requests and accounting

    Staff raise cost requests in CasePeer and the payment itself is made in the accounting package. The cost history on a case therefore depends on that link having been used consistently. Case cost totals are reconciled to the accounting package before cutover, so the amount recovered at settlement is the amount actually spent.

  4. Client trust tracking

    The product tracks client trust money by case. Those balances are compared with the firm’s bank and accounting records before any figure is loaded into a new trust ledger. Because a trust cutover cannot be run again like a document load, it is rehearsed on a full trial load first.

  5. Mail centre and flagged documents

    Incoming post is sorted through a mail centre, and documents can be flagged for review. Items still waiting in that queue at cutover belong to no finished process in the new system. The queue is cleared or listed during the freeze window, so nothing sits unread in the old one.

More about moving off CasePeer

Where it is going

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.

  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. 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.

More about moving into iManage Cloud

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.

  1. Analysis

    We read what CasePeer 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.

  2. 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.

  3. Trial load

    A trial is loaded into iManage Cloud and checked against CasePeer: 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.

  4. Cutover

    There is no financial cutover on this route. After a short freeze on changes in CasePeer, a final pass over a weekend picks up what changed since the trial. CasePeer 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 CasePeer 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

Step 1 of 5: Start with the route

Moving fromCasePeer
Moving toiManage Cloud

The route comes from this page. Four short steps follow. Nothing you send commits your firm to anything.

What happens after you send it

  1. A free first call

    We go through your answers with you and ask about anything they leave open.

  2. An analysis of what CasePeer 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.

  3. 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

CasePeer to iManage Cloud: what firms ask

Is CASEpeer the same product as 8am CasePeer?

Yes. The product was written CASEpeer for years, and its owner now brands it 8am CasePeer alongside 8am MyCase, LawPay and DocketWise. Nothing about what the system stores changed with the rename. A firm that knows it under any of these names is using the same personal injury system.

Can our treatment and lien data go into a general practice system?

It can, but someone has to build the place for it first. General systems hold parties and documents well and usually have nothing for provider visits, bills and lien balances. Custom fields or record types are set up at the analysis stage, and where the destination cannot hold a table of bills, a schedule is saved to the case.

What happens to leads that never became cases?

Leads in the intake manager are separate from cases. Declined and unconverted leads can move to the new system’s intake module if it has one, be loaded as contacts with a note, or be left in an export. Referral sources are kept in every option, because the marketing reports depend on them.

Do trust balances in CasePeer have a place in iManage Cloud?

No. iManage Cloud does not keep trust ledgers. Trust records from CasePeer 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, trust ledgers and intake records. They are exported from CasePeer 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 CasePeer data is loaded into iManage Cloud?

Matters and templates are carried with mapping, so each mapping is agreed with you first. Billing records and custom fields are confirmed in the analysis. The firm also decides which closed matters and how many versions of a document are in scope.

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.

How we do itDiscovery to rollout, step by step

CasePeer and iManage Cloud are the names and marks of their owners, used here only to identify the two systems.

Moving from CasePeer 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.