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

Data migration route

Harvest to iManage Cloud migration

Harvest is a cloud accounting and billing system, and iManage Cloud is a cloud document management system. Only files and their details have a place there, so this route carries the documents and archives the rest.

FromHarvestCloud
  1. Matters: Carried with mapping
  2. Documents: Confirmed in the analysis
  3. Custom fields: Confirmed in the analysis
  4. Templates: Confirmed in the analysis
ToiManage CloudCloud
  1. Contacts: Kept as a readable archive
  2. Notes: 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
Readable archiveNo place in iManage Cloud
  • 1 mapped
  • 3 to confirm
  • 5 archived
What the two products hold. The analysis confirms it field by field.

What moves

What moves from Harvest to iManage Cloud

Each row is a kind of record Harvest holds, whether iManage Cloud has a place for it, and what is planned. On this route one kind needs mapping, five kinds have no place in iManage Cloud and are archived and three kinds are confirmed in the analysis.

Records in Harvest and their place in iManage Cloud
RecordIn HarvestIn iManage CloudWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeld in partProjects under clients stand in for matters; there are three project types.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 referrersHeld in partClients and client contacts, kept mainly as invoice recipients.No placeKept as a readable archive
DocumentsFiles stored in or linked from the systemTo be confirmedHas a placeEach needs a workspace and valid client and matter values; its class sets default security.Confirmed in the analysis
NotesFile notes, matter notes and contact notesHeld in partFree-text notes on each time entry.No placeFile notes can be loaded as documents on the matter.Kept as a readable archive
TasksTo-dos and workflow steps assigned to peopleHeld in partTasks are categories of work for time entries, not to-dos.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 timesheets by person, project and task, with approvals.No placeKept as a readable archive
BillingInvoices, payments and debtor balancesHeldInvoices and estimates, with online payment through Stripe or PayPal.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 automationTo be confirmedHas a place in partPrecedents load as documents. Automation is rebuilt in the firm’s drafting tools.Confirmed in the analysis

What the plans mean

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 Harvest 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

Only the documents have a place here.

iManage Cloud is a document management system: it takes files and the details that describe them. Most of what Harvest holds is not files. Entries, balances, settings and lists have no place in a document store, and the table above is short for that reason. What can move is any document Harvest produced or stored: invoices as PDFs, signed agreements, attachments, exported reports. Each is filed under the client or matter it relates to.

The useful version of this job is often an archive. A firm retiring a system wants its records readable later without keeping the subscription or the old PC. The data is exported in open formats, spreadsheets and PDFs, and filed in iManage Cloud in a workspace set aside for it, with access limited to the people who need it. That gives the firm one place to look, under the same retention rules as the rest of its documents.

Both are hosted by their makers, so nothing is collected from the firm’s office. What can be taken out of Harvest 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 Harvest is kept running until the checks on iManage Cloud are finished.

Where the data is now

Harvest knows about clients, projects, tasks, people, time entries, expenses, invoices and estimates. It does not know about matters or trust money. A firm leaving it for a practice system is turning projects into matters and carrying across time and invoice history, while the firm’s books stay in the accounting package Harvest was feeding.

  1. Client, then project

    A Harvest client record holds a name, an address and a currency, with contacts added mainly so invoices reach the right person. The detail a legal system wants about a client, such as other parties or a responsible lawyer, was never recorded here and is gathered from elsewhere or added after loading.

  2. Tasks are not to-dos

    In Harvest a task is a category of work, such as drafting or attendance, that a time entry is logged against, and it can carry its own billable rate. Tasks map to activity codes in a practice system. They are not a list of things waiting to be done on a matter.

  3. Three ways to set rates

    A Time & Materials project bills at a project rate, a rate per person or a rate per task. The same lawyer can therefore have different rates on different projects. Historical time is loaded with the rate it was recorded at, and the going-forward rate table is built separately in the new system.

  4. Invoices copied to the ledger

    Where the QuickBooks Online or Xero integration is on, invoices and payments were copied across, but time and expenses went only as invoice lines. The accounting package holds the receivables and Harvest holds the time behind them. Both are read, and the invoice numbers are used to match one to the other.

  5. Archived clients and projects

    Clients and projects that are finished can be archived instead of deleted, and archived records are easy to leave out of an export. The analysis counts active and archived records separately, and the firm chooses whether closed work comes across as closed matters or stays behind in the Harvest account.

More about moving off Harvest

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

Harvest to iManage Cloud: what firms ask

Harvest has projects, not matters. How does that convert?

Each project becomes a matter under the same client, keeping its name and any code as the matter reference. Firms that used one long-running project per client, with all work logged to it, decide during clean-up whether to split it into separate matters or carry it as a single general matter.

Will our old time entries keep their notes?

Time entries are read with their date, person, project, task, hours, billable flag and the notes typed on them. In the new system the notes become the narrative on each entry. Entries already invoiced are linked to their invoice where the destination supports that, and listed as billed where it does not.

We have no trust records in Harvest. Is that a problem?

It is common. Harvest has no trust accounting, so client money has been tracked in the accounting package or a spreadsheet. Those records become the source for opening trust balances in the new system, and each one is agreed to the trust bank statement before it is loaded.

Does billing history from Harvest move into iManage Cloud?

No. iManage Cloud has no place for invoices or payments. Billing history from Harvest is exported as reports and invoice copies and kept as a readable archive.

What happens to records iManage Cloud has no place for?

On this route that is contacts, notes, tasks, time entries and billing records. They are exported from Harvest 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 Harvest data is loaded into iManage Cloud?

Matters are carried with mapping, so each mapping is agreed with you first. Documents, custom fields 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

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

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