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

Data migration route

MerusCase to iManage Cloud migration

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

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

What moves

What moves from MerusCase to iManage Cloud

Each row is a kind of record MerusCase 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, eight kinds have no place in iManage Cloud and are archived and two kinds are confirmed in the analysis.

Records in MerusCase and their place in iManage Cloud
RecordIn MerusCaseIn iManage CloudWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldCases, with fields that depend on the case type. Finished cases are archived.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 referrersHeldSeparate contact and company lists, with duplicate removal.No placeKept as a readable archive
DocumentsFiles stored in or linked from the systemHeldUploaded or batch scanned, then linked to the case file.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 storeHeldEmail accounts sync into the product and messages are linked to cases.Has a placeLoaded as email documents into the workspace’s email folders.Carried across
NotesFile notes, matter notes and contact notesHeldCase notes, which can be merged into forms and documents.No placeFile notes can be loaded as documents on the matter.Kept as a readable archive
CalendarAppointments, court dates and deadlinesHeldEvents and deadlines, which can be attached to a case.No placeKept as a readable archive
TasksTo-dos and workflow steps assigned to peopleHeldAssignments delegated to team members, with reminders.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 unbilledHeldTimers and time entries on case ledgers.No placeKept as a readable archive
BillingInvoices, payments and debtor balancesHeldInvoices, payments and electronic billing formats including LEDES.No placeKept as a readable archive
Trust moneyTrust or client account ledgers and balancesHeld in partDescribed by the vendor as trust accounting tracking, on case ledgers.No placeKept as a readable archive
Firm accountsGeneral ledger, office account and payablesHeld in partOperating receivables are built in. Payables were not confirmed.No placeKept as a readable archive
Custom fieldsFields and record types the firm added itselfTo be confirmedHas a place in partA fixed number of custom profile fields, each a validated list.Confirmed in the analysis
TemplatesPrecedents, document templates and automationHeldWord templates and PDF court forms that fill from the case.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 pipelinesTo be confirmedNo placeConfirmed 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 MerusCase.
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 MerusCase 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 MerusCase 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 MerusCase 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 MerusCase 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 MerusCase is kept running until the checks on iManage Cloud are finished.

Where the data is now

MerusCase keeps a good deal inside one system: the firm’s email, scanned post, court forms and ledgers as well as the cases. A move off it has to account for each. The case data and documents are the bulk of the work. Email and the books need decisions, because the destination may expect those to live somewhere else.

  1. The Activity tab

    A case’s documents and other activity are listed together on its Activity tab, each entry with a type and a date. That list is the file. It is extracted in full and split by type, so documents go to the document store and notes to file notes, each keeping its original date and description.

  2. Email inside the product

    Staff can run their mailboxes through MerusCase and link messages to cases as they go. Linked messages are case records and move with the case. Messages never linked remain in the underlying mail account. The firm is told which is which, so nobody expects an unlinked email to appear in the new system.

  3. Batch-scanned documents

    Post is scanned in batches, separated into individual documents by the system and then linked to case files. Any pages still unlinked at cutover belong to no case. That queue is cleared before the final extraction, or exported as a folder for someone to file by hand afterwards.

  4. Case types change the fields

    The fields on a case depend on its case type, so a workers’ compensation case and an immigration case do not share a layout. Each case type is mapped on its own. Fields that exist for only one type are easy to miss in a general mapping, and are checked against sample cases of every type.

  5. Ledgers and trust tracking

    Time, charges, invoices, payments and trust entries are kept on case ledgers in the Books area. Unbilled time and outstanding invoices are reconciled per case before loading. Trust balances are agreed to the bank statement first, and that part of the cutover is rehearsed in a full trial load.

More about moving off MerusCase

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

MerusCase to iManage Cloud: what firms ask

Our court forms are built into MerusCase. What happens to them?

Forms already completed are saved on the case as PDFs and move as documents. The form library itself belongs to MerusCase, with its jurisdiction settings and merge fields. In the new system the firm uses that system’s forms or a forms service, and its own Word templates are rebuilt there.

Can archived cases come across?

Yes. Archived cases are still in the system and can be extracted with their documents and activity. They are kept out of the active lists in the new system by loading them as closed. The firm sets a cut-off if it does not want every year, and the count on each side is checked.

What about emails our staff never linked to a case?

Those are not part of any case, so they do not move with the case data. They remain in the mail account that was connected to MerusCase. If the firm wants old correspondence on the file, the time to link it is before the freeze, and fee earners are asked to do so for their open cases.

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

No. iManage Cloud does not keep trust ledgers. Trust records from MerusCase 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 and the firm’s accounts. They are exported from MerusCase 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 MerusCase data is loaded into iManage Cloud?

Matters and templates are carried with mapping, so each mapping is agreed with you first. Custom fields and intake records 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

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

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