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

Data migration route

iManage Work to SimpleLaw migration

iManage Work is a server-based document management system, and SimpleLaw is a cloud practice management system. Documents and email move out of a store organised by profile and onto the matters they belong to.

FromiManage WorkServer
  1. Matters: Carried across
  2. Documents: Carried across
  3. Tasks: Carried across
  4. Custom fields: Carried with mapping
  5. Templates: Carried with mapping
  6. Emails: Confirmed in the analysis
ToSimpleLawCloud
  • 3 carried
  • 2 mapped
  • 1 to confirm
What the two products hold. The analysis confirms it field by field.

What moves

What moves from iManage Work to SimpleLaw

Each row is a kind of record iManage Work holds, whether SimpleLaw has a place for it, and what is planned. On this route three kinds of record carry across, two kinds need mapping and one kind is confirmed in the analysis.

Records in iManage Work and their place in SimpleLaw
RecordIn iManage WorkIn SimpleLawWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeld in partA workspace usually stands for a matter, with client and matter held as custom1 and custom2.Has a placeCarried across
DocumentsFiles stored in or linked from the systemHeldEach is identified by its library name, a document number and a version number.Has a placeUploaded to SimpleLaw storage or held in a linked Dropbox, Google Drive or OneDrive.Carried across
EmailsEmails saved to matters or to the storeHeldFiled emails are stored as documents, usually in email folders inside the workspace.To be confirmedConfirmed in the analysis
TasksTo-dos and workflow steps assigned to peopleHeld in partTask lists are kept in iManage Tracker, a separate product.Has a placeCarried across
Custom fieldsFields and record types the firm added itselfHeldCustom profile fields with validated lists, captioned by the firm, such as practice area.Has a placeCarried with mapping
TemplatesPrecedents, document templates and automationHeld in partPrecedents are held as documents. Workspace templates only set folder structure.Has a place in partTemplates are rebuilt using SimpleLaw’s own automation.Carried with mapping

What the plans mean

Carried across
SimpleLaw has a place for this kind of record. It is loaded there and checked against iManage Work.
Carried with mapping
SimpleLaw 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.

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

Profiled documents become matter documents.

A document management system files by profile: client, matter, author, document type, version. A practice management system files by matter. The move from iManage Work to SimpleLaw is a translation from one to the other, and it depends on the client and matter numbers in iManage Work matching matters that exist in SimpleLaw. Where they do not match, documents have nowhere to land. So the matter list is settled first and the documents follow it.

Versions and security each need a decision. Some practice systems keep every version of a document, others keep the latest and treat the rest as separate files. A restricted workspace has to become a restricted matter, or the restriction is lost on the way. Filed email comes across as message files against the matter. A document store holds no ledgers, so this route has no financial cutover.

iManage Work runs on the firm’s own equipment, so the data is collected there: a copy of the database and the folders its documents sit in, taken with the firm’s IT provider or over a remote session. SimpleLaw is hosted by its maker, so loading depends on the import tools and access it provides. The old machine is kept, read only, as the fall-back record.

Where the data is now

Moving off an on-premises library starts with access to its database and its file store, because the profiles, security and version history are read from the database. The stored files on their own are not usable: each one has to be matched to its profile. Most of the planning goes into client and matter numbers, security, and which versions come across.

  1. The database carries the meaning

    The title, author, client, matter, class and folder location of every document are rows in the library database, not properties of the stored file. An extraction that copies only the file store brings none of that with it. The database and the files therefore have to be collected together, at the same point in time.

  2. Client and matter are custom fields

    Custom1 and custom2 are a parent and child pair, normally captioned Client and Matter, and every value has to exist in a validated list. That list is usually fed from the practice management system. The analysis compares it with the destination’s matter list, since closed or renumbered matters often exist in one and not the other.

  3. Document numbers get quoted

    A document is identified by library, number and version, and lawyers quote those numbers in emails, footers and other documents. The firm decides whether every version moves or only the latest, and whether the old number is kept as a searchable field or in the document name so an old reference can still be traced.

  4. Security is layered

    Each workspace, folder and document has a default security of private, view, public or inherited, and users or groups can be granted or denied access on top of that. Private documents and walled-off matters are either reproduced in the destination or deliberately opened up. That is decided group by group before the trial load.

  5. Emails are documents here

    A filed email is stored as a document in its own right, often in an email folder inside the workspace, and the same message may have been filed by several people. Volumes are large. The trial load reports how many emails each matter holds and how repeated copies were treated.

More about moving off iManage Work

Where it is going

Loading a firm into SimpleLaw is mostly a job of sorting contacts and setting up each matter’s billing type. The CRM holds leads, clients and everyone else, so every incoming contact needs a status. Where documents will be stored is decided early as well, since that choice determines where the files are sent. Accounting history stays in QuickBooks or the old system.

  1. Lead, client or contact

    A person is tracked from first enquiry to client in one CRM, with tasks and appointments kept against the contact. Source systems that only ever held clients load simply. Systems with separate intake records need each enquiry classed as a live lead, a lost one or a duplicate of an existing client.

  2. Billing type on each matter

    Every matter is billed as hourly, flat fee, instalments, contingency, pro bono, trust or LEDES. The source may record this loosely or not at all. During the trial load a billing type is set on each matter and checked by the person who raises the bills, because it controls how the invoice is built.

  3. Storage chosen before loading

    If the firm stores documents with SimpleLaw, files are uploaded against each matter. Where it prefers Dropbox, Google Drive or OneDrive, the files go there, and what the connection does with folders already in place is checked first. Switching later means moving everything again, so the choice is made at the start with the firm’s IT support.

  4. Custom fields named for templates

    Custom fields supply intake forms and document automation as well as reports. A field brought across from the old system is only useful if templates can call on it. Fields are therefore named and typed with the firm’s main documents in mind, and one template is tested against loaded data.

  5. Portal access client by client

    The client portal is optional and the firm chooses who has access and what each client can see. Nothing is exposed by loading data. After go-live, access is switched on for chosen clients, starting with a few, once the firm has reviewed what their matters show.

More about moving into SimpleLaw

How NewLaw runs it

Four steps, in this order.

Nothing financial lands in SimpleLaw on this route, which makes it repeatable: a load can be run again until it is right.

  1. Analysis

    We read what iManage Work holds and how it is organised, then agree with you where each kind of record will sit in SimpleLaw. 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 SimpleLaw and checked against iManage Work: 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 iManage Work, a final pass over a weekend picks up what changed since the trial. iManage Work 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 iManage Work 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 fromiManage Work
Moving toSimpleLaw

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 iManage Work holds

    What is in it, how its records link, and where each piece would sit in SimpleLaw. 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 SimpleLaw

Loaded data is not yet a working system. This is what NewLaw sets up in SimpleLaw, beyond the migration, so that people can work in it from the first day.

The set-up work is in making the product reflect the firm. Labels are adjusted to the firm’s terms. Intake forms and the custom fields behind them are built for each practice area, then document templates are made to draw on those fields. Workflows are written for the case types that follow a standard path, and the QuickBooks and payment connections are made last.

Set-up decisions in SimpleLaw

  • Labels for documents, activities, expenses and contact IDs
  • Custom fields and intake forms for each practice area
  • Document templates and the attorney-client agreement
  • Workflows for case types that follow a standard process
  • User permission sets and client portal visibility
  • QuickBooks connection and the online payment processor

Questions

iManage Work to SimpleLaw: what firms ask

Can we keep our iManage document numbers?

The number is assigned by the library, so the new system will issue its own. What can be kept is the old number as a reference: in a custom field, in the document name, or in a lookup list. Which is possible depends on the destination, and it is settled in the analysis because footers and old emails quote the numbers.

Do all versions of a document come across?

They can be extracted, since each version has its own profile. Whether the destination keeps them as versions of one document or as separate documents depends on that system. A common choice is every version for open matters and the latest version only for matters that closed some years ago.

Is moving to iManage Cloud the same job as moving to another product?

No. Going to iManage’s own cloud keeps the same structure of libraries, workspaces, profiles and security, and iManage publishes its own resources for that move. Moving to a different product means mapping each of those concepts onto something else, which is where the analysis time goes.

Do documents from iManage Work keep their folders and dates in SimpleLaw?

SimpleLaw stores documents. Uploaded to SimpleLaw storage or held in a linked Dropbox, Google Drive or OneDrive. Each file is placed under the client and matter it came from, and created and modified dates are carried, so a document still shows when it was written. The trial load is checked by count and by opening a sample.

Does everything in iManage Work have a place in SimpleLaw?

Most of it does on paper. Emails could not be confirmed from the two products’ own material, so those are checked in the analysis. Anything that turns out to have no place in SimpleLaw is kept as a readable archive, and you see which before the move.

What has to be decided before iManage Work data is loaded into SimpleLaw?

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

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

Moving from iManage Work to SimpleLaw?

Tell us what you are moving. You get a plan and a fixed price after the analysis.

We reply within one business day.