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

Data migration route

ProLaw to iManage Cloud migration

ProLaw is a server-based 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.

FromProLawServer
  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. Tasks: 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. Time and expenses: Kept as a readable archive
  4. Billing: Kept as a readable archive
  5. Trust money: 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 ProLaw to iManage Cloud

Each row is a kind of record ProLaw 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 ProLaw and their place in iManage Cloud
RecordIn ProLawIn 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 referrersHeldOne database of clients, prospects and relationships, also used for conflict checks.No placeKept as a readable archive
DocumentsFiles stored in or linked from the systemHeldDocuments are reached from the matter, with Word, Outlook and Adobe integration.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 partThrough the Outlook integration.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 deadlinesHeldRules-based docketing and calendaring.No placeKept as a readable archive
TasksTo-dos and workflow steps assigned to peopleTo be confirmedNo placeiManage Tracker is a separate product with its own set-up.Confirmed in the analysis
Time and expensesTime and expense entries, billed and unbilledHeldNo placeKept as a readable archive
BillingInvoices, payments and debtor balancesHeldBilling history and invoicing status are held with the matter.No placeKept as a readable archive
Trust moneyTrust or client account ledgers and balancesHeldPart of the back office accounting.No placeKept as a readable archive
Firm accountsGeneral ledger, office account and payablesHeldFinancial accounting, budgeting and cost recovery, including contingency case accounting.No placeKept as a readable archive
Custom fieldsFields and record types the firm added itselfHeldCustom tabs, which can also link to other applications.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 partProspects are kept in the same contact database as clients.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 ProLaw.
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 ProLaw 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 ProLaw 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 ProLaw for matters and billing, or into an archive.

ProLaw 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. iManage Cloud 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

A firm that runs both halves of ProLaw has a wide scope to move: matters, a shared contact database, documents, docket entries, records management, time, billing and the ledgers. Having it all in one system on the firm’s server helps. The effort goes into custom tabs, rules-based docket entries and deciding where the back office goes if the destination has no general ledger.

  1. Front office and back office

    The front office holds matters, contacts, documents, events and conflicts, and the back office holds billing and the firm’s accounts. A firm may have licensed one half and run another product for the rest. Which halves are in use, and what the other product is, sets the shape of the whole move.

  2. Custom tabs

    ProLaw lets a firm add its own tabs and connect them to other applications. Years of practice-specific data end up there. Each tab is listed with its fields and how many matters use them, and the firm chooses which become fields in the new system and which become a note.

  3. Docket entries from rules

    Deadlines can be generated from court rules, so one trigger date produces a set of related events. The dates come across as calendar entries, but the tie back to the rule does not, so a changed hearing date will not recalculate the old set. Open matters with rule-based deadlines are flagged for the lawyers to review.

  4. One contact, many uses

    A single contact database serves clients, prospects, other parties and marketing lists, and the conflict check reads the same people. Duplicates therefore distort conflict results as well as mailings. They are merged in ProLaw before extraction where they can be identified, and each relationship type is mapped.

  5. Physical file records

    Records management tracks paper files and where they are kept. It is easy to forget until someone needs a file from storage. The location recorded for each matter’s paper file is carried to a field or note on the matter in the destination.

More about moving off ProLaw

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

ProLaw to iManage Cloud: what firms ask

Who makes ProLaw now?

Elite. ProLaw was sold under the Thomson Reuters name for years, and Elite, once a Thomson Reuters business, now publishes it as a separate company. Elite’s own site carries ProLaw customer news and a ProLaw summit for 2026. Your support contract shows which entity you deal with.

Do documents keep their matter links?

Documents saved through ProLaw are recorded against a matter. The record and the file are brought together again in the destination, under the same matter and with the original dates. Files saved outside ProLaw, on desktops or shared drives, are a separate source that the firm identifies during the analysis.

Can contingency matters and their costs move?

Yes, but they need more care than hourly matters. Advanced costs and expected fees are extracted per matter and agreed to ProLaw’s reports. Where the destination handles contingency work differently, the firm’s accounts staff decide how each balance is to be shown before the trial load.

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

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

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

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

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