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

Data migration route

iManage Cloud to Soluno migration

iManage Cloud is a cloud document management system, and Soluno is a cloud accounting and billing system. Only names and any financial records have a place in a set of books, so little of this moves.

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
ToSolunoCloud
  • 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 Soluno

Each row is a kind of record iManage Cloud holds, whether Soluno 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 Soluno
RecordIn iManage CloudIn SolunoWhat 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 placeAs files, with number, area of practice, responsible lawyer and billing settings.Carried across
DocumentsFiles stored in or linked from the systemHeldProfiled, numbered and versioned, and always filed inside a workspace.To be confirmedNo matter document store is described; NetDocuments can be linked.Confirmed 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
Soluno 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

Little of this belongs in the accounts.

Soluno is an accounting package. It takes customers, suppliers, invoices and ledger entries, and has no place for documents, case notes, calendars or leads. From iManage Cloud, that usually leaves the contact list, loaded as customers, and any financial records it happens to keep. The table above shows which. This is a small job, and it is better to say so plainly before a firm plans around it.

Loading customers into an accounting system has consequences a contact list elsewhere does not. Every customer can be invoiced, so duplicates and half-complete records turn into billing mistakes. The list is cleaned and matched against the customers already in Soluno before anything is added. The rest of what iManage Cloud holds is exported in open formats and kept as an archive, or moved on a different route to a system built for it.

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

Soluno, which Actionstep now sells as Actionstep Legal Accounting, is an accounting system first, and it expects accounting discipline from the data it is given. Contacts and files need numbers. Entries need dates that fall in open financial periods. Billing, rate and file groups should exist before files are created so that defaults apply. Where documents, calendars and case detail will live is settled alongside.

  1. Numbers for contacts and files

    Every contact has a number and every file has a file number, which Soluno can generate on its own or by contact. A firm can keep its old numbers by typing over the suggested value. The format is agreed first, since the help centre puts later number changes behind an administrator setting once NetDocuments is in use.

  2. Groups before files

    File, billing and rate groups set the defaults a new file picks up, and a file can override them. Loading thousands of files without the groups in place means fixing each one by hand later. The groups are designed from the source system’s rate tables and billing terms during the analysis.

  3. Periods must be open

    Soluno closes financial periods, and a file cannot be closed while it has entries dated after the last closed period. Historic transactions are loaded with the relevant periods open, checked, and then the periods are closed in order. That sequence is rehearsed on the full trial load with the firm’s accountant.

  4. Closed matters need zero balances

    A file closes only when it has no work in progress, no receivable and no retainer or trust balance. Old matters that the source system marked closed while still carrying a few dollars will not close here. Those small balances are written off or cleared in the source before extraction, with partner approval.

  5. Documents live beside it

    Its help centre covers accounting, banking, billing, contacts and files, and describes links to NetDocuments and to Actionstep practice management. It describes no matter document store. A firm arriving from an all-in-one product should expect to need a second destination for its documents, emails and calendar, and the two loads are planned together so matter numbers match in both.

More about moving into Soluno

How NewLaw runs it

Four steps, in this order.

Nothing financial lands in Soluno 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 Soluno. 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 Soluno 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 toSoluno

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

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

Most of the set-up in Soluno is financial structure. The chart of accounts, bank accounts and financial periods come first, then the groups that control billing and rates, then users and what each group of users may do. Lawyers need task code shortcuts and rates before they can enter time. If NetDocuments or Actionstep practice management is to be linked, that connection is made once numbering is final.

Set-up decisions in Soluno

  • Chart of accounts, bank accounts and opening financial periods
  • File, billing and rate groups with their default arrangements
  • Contact and file numbering format, set firm-wide or by contact
  • User groups and what each group may see or do
  • Task and activity codes and each lawyer’s shortcuts
  • Link to NetDocuments or to Actionstep practice management

Questions

iManage Cloud to Soluno: 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 Soluno?

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 Soluno are exported into folders by client and matter.

Does everything in iManage Cloud have a place in Soluno?

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 Soluno 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 Soluno?

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 Soluno are the names and marks of their owners, used here only to identify the two systems.

Moving from iManage Cloud to Soluno?

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

We reply within one business day.