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

Data migration route

MyCase to iManage Cloud migration

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

FromMyCaseCloud
  1. Documents: Carried across
  2. Emails: Carried across
  3. Matters: Carried with mapping
  4. Custom fields: Carried with mapping
  5. Templates: Carried with mapping
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. Billing: Kept as a readable archive
  7. Trust money: Kept as a readable archive
  8. Firm accounts: Kept as a readable archive
  9. Intake: Kept as a readable archive
Readable archiveNo place in iManage Cloud
  • 2 carried
  • 3 mapped
  • 9 archived
What the two products hold. The analysis confirms it field by field.

What moves

What moves from MyCase to iManage Cloud

Each row is a kind of record MyCase 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.

Records in MyCase and their place in iManage Cloud
RecordIn MyCaseIn iManage CloudWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldCalled cases. Each has a unique name, an optional case number, a practice area and an open or closed state.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 referrersHeldContacts (people) and companies are separate record types, linked to cases.No placeKept as a readable archive
DocumentsFiles stored in or linked from the systemHeldStored against cases in folders, with version tracking and unlimited storage.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 partOnly emails linked through the Outlook or Gmail add-ins or a forwarding address.Has a placeLoaded as email documents into the workspace’s email folders.Carried across
NotesFile notes, matter notes and contact notesHeldNo placeFile notes can be loaded as documents on the matter.Kept as a readable archive
CalendarAppointments, court dates and deadlinesHeldCan sync with Google Calendar and Outlook.No placeKept as a readable archive
TasksTo-dos and workflow steps assigned to peopleHeldTasks can be created by workflow automation.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 unbilledHeldNo placeKept as a readable archive
BillingInvoices, payments and debtor balancesHeldNo placeKept as a readable archive
Trust moneyTrust or client account ledgers and balancesHeldNo placeKept as a readable archive
Firm accountsGeneral ledger, office account and payablesHeld in partMyCase Accounting is an add-on; a QuickBooks sync is the alternative.No placeKept as a readable archive
Custom fieldsFields and record types the firm added itselfHeldCustom fields on cases and on contacts.Has a place in partA fixed number of custom profile fields, each a validated list.Carried with mapping
TemplatesPrecedents, document templates and automationHeldWord-based document templates and automation.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 pipelinesHeldLeads in a Kanban view, with intake forms that can be embedded on a website.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 MyCase.
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 MyCase 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 MyCase 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 MyCase 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 MyCase 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 MyCase is kept running until the checks on iManage Cloud are finished.

Where the data is now

A firm leaving MyCase is moving a set of cases with everything tied to them, and the first job is working out which of those ties the next system can hold. Documents, time, invoices and trust balances have obvious homes. Portal messages, text conversations and the lead pipeline often do not, so each is given a destination or a reason to stay behind before any data is extracted.

  1. Cases, contacts and companies

    MyCase says case where most systems say matter, and it keeps people and companies as two separate record types. A destination that has one contact card for both, or that insists on a client record above each matter, needs a rule for which MyCase contact becomes the client when a case has several linked to it.

  2. Case numbers are optional

    The case number is a free-text field that a firm can leave empty or fill with a court file number. If the new system wants a unique matter number on every record, the analysis finds the cases with no number or a shared one, and the firm agrees how those are numbered.

  3. Only linked emails are there

    Emails reach a case through the Gmail or Outlook add-ins, or by forwarding to a personal MyCase address. Anything nobody linked is still in a mailbox, and emails the software could not match wait in an Unresolved Emails queue. That queue is worth clearing before extraction, because unmatched emails have no case to travel with.

  4. Books may sit elsewhere

    Invoices, payments and trust ledgers are inside MyCase. The general ledger is either the MyCase Accounting add-on or QuickBooks fed by a sync. Where QuickBooks is in use, debtor and trust totals are taken from both and compared before cutover, so the opening figures in the new system are ones the bookkeeper recognises.

  5. Messages and texts

    Client portal messages and text conversations are saved against the case. Few systems have a matching record type. They are usually carried as a dated note or a single document on each matter, and the firm sees an example of how that reads before deciding whether it is enough.

More about moving off MyCase

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 MyCase 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 MyCase: 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 MyCase, a final pass over a weekend picks up what changed since the trial. MyCase 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 MyCase 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 fromMyCase
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 MyCase 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

MyCase to iManage Cloud: what firms ask

Can we keep our existing matter numbers when we move to MyCase?

Yes. The case number field accepts letters, digits and special characters, so numbers can go in exactly as they are. MyCase does not require the number to follow a pattern. What it does require is a unique case name, so the naming rule usually takes more discussion than the numbering.

We are leaving MyCase. Do our client portal messages come with us?

They can be kept, but rarely as live messages. Most systems have no record that matches a MyCase portal thread, so the messages are carried as dated notes or one document per matter. Whether the destination has anything closer is confirmed in the analysis, and the firm sees a sample first.

What happens to closed cases?

They move as closed, with their closed date, documents and billing history where the destination has a place for it. Some firms bring across only matters closed within a set number of years and keep the older ones in the read-only copy of the old system. That choice is made before the trial load.

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

No. iManage Cloud does not keep trust ledgers. Trust records from MyCase 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 MyCase 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 MyCase 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.

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

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

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