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

Data migration route

Curo365 to iManage Cloud migration

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

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

What moves

What moves from Curo365 to iManage Cloud

Each row is a kind of record Curo365 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 three kinds are confirmed in the analysis.

Records in Curo365 and their place in iManage Cloud
RecordIn Curo365In iManage CloudWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldHas 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 referrersHeldClient records and relationships are held in Dynamics 365.No placeKept as a readable archive
DocumentsFiles stored in or linked from the systemHeldManaged in SharePoint.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 partMail stays in Exchange and Outlook; what is filed to a matter was not confirmed.Has a placeLoaded as email documents into the workspace’s email folders.Carried across
NotesFile notes, matter notes and contact notesTo be confirmedNo placeFile notes can be loaded as documents on the matter.Confirmed in the analysis
CalendarAppointments, court dates and deadlinesHeldCalendars are Exchange and Outlook.No placeKept as a readable archive
TasksTo-dos and workflow steps assigned to peopleHeld in partAutomated workflows for firm processes; task records were not confirmed.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 unbilledHeldTime can be entered from Outlook.No placeKept as a readable archive
BillingInvoices, payments and debtor balancesHeldBilling and invoicing are part of the product.No placeKept as a readable archive
Trust moneyTrust or client account ledgers and balancesTo be confirmedNo placeConfirmed in the analysis
Firm accountsGeneral ledger, office account and payablesHeld in partKept in Microsoft Business Central or QuickBooks, not inside Curo365 itself.No placeKept as a readable archive
Custom fieldsFields and record types the firm added itselfHeldBuilt on Dynamics 365, where a firm can add its own fields.Has a place in partA fixed number of custom profile fields, each a validated list.Carried with mapping
TemplatesPrecedents, document templates and automationTo be confirmedHas a place in partPrecedents load as documents. Automation is rebuilt in the firm’s drafting tools.Confirmed in the analysis
IntakeLeads, enquiries, intake forms and pipelinesHeld in partClient management and marketing use Dynamics 365 CRM functions.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 Curo365.
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 Curo365 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 Curo365 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 Curo365 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 Curo365 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 Curo365 is kept running until the checks on iManage Cloud are finished.

Where the data is now

Curo365 is one product on the screen and several Microsoft services underneath. Matters are in Dynamics 365, documents in SharePoint, email and diaries in Exchange, the ledger in Business Central or QuickBooks. Leaving it means collecting from each of those and putting the links back together. The documents and mail are in the firm’s own Microsoft 365, which changes what has to move at all.

  1. Four places, one matter

    A single matter has its details in Dynamics 365, its files in SharePoint, its emails and appointments in Outlook and its money in the accounting package. Each is extracted separately and joined on the matter number. The first trial load is mainly a test of that join: does every document folder find its matter.

  2. Documents may not need moving

    The files are in SharePoint in the firm’s Microsoft 365. If the new system can work with SharePoint, they can stay where they are and be linked. If it has its own document store, they are copied in with their folder structure and dates. That choice is the largest single factor in the size of the job.

  3. The ledger is beside it

    Accounting is done in Microsoft Business Central or in QuickBooks, so the general ledger and payables are taken from that package and not from Curo365. Billing history and the debtor ledger are compared before cutover so that both agree on what each client owes. Where client money is recorded is confirmed in the analysis.

  4. Calendars belong to mailboxes

    Appointments are ordinary Outlook items in each person’s mailbox, and they remain there after the move. What can be lost is the link from an appointment to its matter. Court dates and limitation dates are identified and loaded into the new system’s own calendar, so they do not depend on one lawyer’s mailbox.

  5. Power BI reports

    Partners often run the firm from Power BI dashboards that read Curo365 data. A dashboard is not a record and cannot be migrated. The reports people open each week are listed, with the figures each one shows, and rebuilt against the new system or replaced by its own reporting.

More about moving off Curo365

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

Curo365 to iManage Cloud: what firms ask

Our documents are already in SharePoint. Do we have to move them?

Not always. They are in the firm’s own Microsoft 365 and remain there whatever happens to the practice system. If the destination can link to SharePoint, the folders are re-attached to the new matters. If it stores documents itself, they are copied across and the SharePoint library is kept read only for a period.

We have customised Curo365 heavily. Does that complicate a move?

It adds work, and the work is predictable. Dynamics 365 lets a firm add fields, tables and workflows, and those additions are visible in the configuration. The analysis lists each one with how many records use it. Fields with real data are mapped. Workflows are described in plain words so they can be rebuilt or dropped.

Will entering time from Outlook still work?

The entries already made are in Curo365 and move as time records, billed and unbilled. Entering time from Outlook afterwards depends on whether the new system has an Outlook add-in of its own. That is confirmed for the chosen destination in the analysis, and fee earners are shown the new method before go-live.

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

That is confirmed in the analysis. We could not establish it from the two products’ own material, so it is checked against your data in Curo365 before the plan is fixed. If iManage Cloud turns out to have no place for trust ledgers, they are kept as a readable archive and the firm decides where trust accounting runs.

What happens to records iManage Cloud has no place for?

On this route that is contacts, calendar entries, tasks, time entries, billing records, the firm’s accounts and intake records. They are exported from Curo365 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 Curo365 data is loaded into iManage Cloud?

Matters and custom fields are carried with mapping, so each mapping is agreed with you first. Notes, trust ledgers and templates 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

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

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