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

Data migration route

iManage Cloud to SurePoint Finance Enterprise migration

iManage Cloud is a cloud document management system, and SurePoint Finance Enterprise 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 CloudCloud
  1. Matters: Carried across
  2. Documents: Confirmed in the analysis
  3. Emails: Confirmed in the analysis
  4. Tasks: Confirmed in the analysis
  5. Custom fields: Confirmed in the analysis
  6. Templates: Confirmed in the analysis
ToSurePoint Finance EnterpriseCloud
  • 1 carried
  • 5 to confirm
What the two products hold. The analysis confirms it field by field.

What moves

What moves from iManage Cloud to SurePoint Finance Enterprise

Each row is a kind of record iManage Cloud holds, whether SurePoint Finance Enterprise has a place for it, and what is planned. On this route one kind of record carries across and five kinds are confirmed in the analysis.

Records in iManage Cloud and their place in SurePoint Finance Enterprise
RecordIn iManage CloudIn SurePoint Finance EnterpriseWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeld in partOne workspace per matter is the norm. It carries client and matter values, not parties or status.Has a placeCarried across
DocumentsFiles stored in or linked from the systemHeldProfiled, numbered and versioned, and always filed inside a workspace.To be confirmedConfirmed in the analysis
EmailsEmails saved to matters or to the storeHeldFiled from Outlook and held as documents with sender, recipients and sent date.To be confirmedConfirmed in the analysis
TasksTo-dos and workflow steps assigned to peopleHeld in partThrough iManage Tracker, which is sold separately and integrates with Work.To be confirmedConfirmed in the analysis
Custom fieldsFields and record types the firm added itselfHeldCustom1 to custom12, custom29 and custom30 hold validated lists the firm captions itself.To be confirmedConfirmed in the analysis
TemplatesPrecedents, document templates and automationHeld in partPrecedents are stored as ordinary documents, wherever the firm chose to keep them.To be confirmedConfirmed in the analysis

What the plans mean

Carried across
SurePoint Finance Enterprise has a place for this kind of record. It is loaded there and checked against iManage Cloud.
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 Cloud to SurePoint Finance Enterprise is a translation from one to the other, and it depends on the client and matter numbers in iManage Cloud matching matters that exist in SurePoint Finance Enterprise. 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.

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

Where the data is now

Administrators of a cloud library have API access and no SQL access, so documents, versions, profiles and permissions are read out through the API. That makes extraction slower to plan than on a server the firm owns. The trial load matters more than usual, because it is the first time the counts can be checked against what Control Center reports.

  1. Extraction runs through the API

    With no database to query, every document, version, profile and permission is requested through the REST API. A large library takes planning: which libraries go first, how long a full pass takes, and how the changes made since that pass are collected before cutover.

  2. Trash and Journal content

    On cloudimanage.com, the newer of the two cloud platforms, Trash and Journal are always enabled. They are not part of the live matter file. The firm decides whether deleted items and journal content are in scope. If nothing is said, they stay behind.

  3. Workspaces follow a template

    Workspaces are created from templates, and with Flexible Folders switched on the template controls which folders may exist at each level. That gives a cloud library a regular shape, with the same folder names recurring across thousands of matters. A mapping written once per template covers most content, and custom folders are handled as exceptions.

  4. Two cloud platforms exist

    iManage runs an earlier cloud platform at imanage.work and a newer one at cloudimanage.com. They differ in details such as maximum file size, email duplicate detection and whether Trash and Journal are always on. Which one the firm is on is established first, because it affects what comes back from the service and how the extraction is tested.

  5. Companion products hold data too

    Firms on the cloud often run other iManage products beside Work: Share folders for clients, Records Manager, Security Policy Manager for walls. Each holds information that is not in the document library itself. The analysis lists which are in use and what is to happen to their content.

More about moving off iManage Cloud

Where it is going

Moving into SurePoint Finance Enterprise, the system long sold as LMS, is an accounting implementation with a data load inside it. The entity structure, chart of accounts and billing rules are designed before records arrive, because every time entry and payment posts into them. Smaller systems rarely hold data at that level of detail, so part of the preparation is adding what the source never recorded.

  1. Entities and tax IDs first

    The system can hold several legal entities and tax IDs. A firm coming from a single QuickBooks file, or from two files for two offices, decides how it wants to be structured from here on. That decision fixes where each bank account and matter belongs, and it is hard to revisit once history is posted.

  2. History has to balance

    Billing, trust and the general ledger are parts of one system, so loaded history must agree across all three. A receivable carried in for a matter needs the invoice behind it and the ledger entry behind that. Source systems that kept billing and accounts apart are reconciled to each other before extraction.

  3. E-billing detail on time entries

    For LEDES e-billing, time entries need task and activity codes and timekeepers need the classifications clients expect. A small-firm system may never have captured them. The firm decides whether historic entries are loaded uncoded as history only, with coding starting on new work from go-live.

  4. Dockets as well as appointments

    Calendars and dockets are both kept. In many source systems a court deadline and a client lunch are the same kind of record. The two are separated on the way in, using event types or keywords, and the docket entries for open matters are checked by the lawyers responsible.

  5. Cost recovery codes

    Disbursements such as copying and postage arrive through cost recovery and post to the matter. The cost types and their rates are set up to match how the firm charges today. Unbilled disbursements from the old system are then loaded against those types so they can be billed normally.

More about moving into SurePoint Finance Enterprise

How NewLaw runs it

Four steps, in this order.

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

  1. Analysis

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

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 Cloud holds

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

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

The set-up decisions in Finance Enterprise are mostly made by the finance team. They cover the firm’s entity structure, its chart of accounts, how bills are approved and sent, and what each client’s e-billing portal demands. Timekeepers need rates and classifications. The reports used for partner compensation are specified early, because they test whether the structure underneath is right.

Set-up decisions in SurePoint Finance Enterprise

  • Entity structure, tax IDs and the chart of accounts
  • Bank and trust accounts with reconciliation set-up
  • Timekeeper rates, classifications and task code sets
  • Pre-bill approval steps and client billing rules
  • LEDES e-billing formats for each corporate client
  • Management and compensation reports the partners use

Questions

iManage Cloud to SurePoint Finance Enterprise: what firms ask

Can we get our documents out of iManage Cloud with their profiles?

Yes. Documents, versions, profile fields, folder locations and permissions can all be read through the API. They arrive as files plus a table of metadata. How much of that metadata the next system can hold, and under what field names, is worked out field by field in the analysis.

We are changing practice management systems. Does iManage have to change too?

No. The document system can stay where it is. What changes is the feed of clients and matters into it and the integration that opens a workspace from a matter. If matter numbers change in the new practice management system, the workspaces need renumbering or a cross-reference so the two still line up.

What happens to emails filed in workspaces?

They are stored as documents with sender, recipients and sent date in the profile, so they move like any other document. One email filed by three people can exist three times. The trial load reports how many there are per matter, and the firm chooses whether repeated copies are merged.

Do documents from iManage Cloud keep their folders and dates in SurePoint Finance Enterprise?

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 iManage Cloud before the plan is fixed. Documents that have no place in SurePoint Finance Enterprise are exported into folders by client and matter.

Does everything in iManage Cloud have a place in SurePoint Finance Enterprise?

Most of it does on paper. Documents, emails, tasks, custom fields and templates 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 SurePoint Finance Enterprise is kept as a readable archive, and you see which before the move.

What has to be decided before iManage Cloud data is loaded into SurePoint Finance Enterprise?

Documents, emails, tasks, 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

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

Moving from iManage Cloud to SurePoint Finance Enterprise?

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

We reply within one business day.