Data migration route
iManage Work to Soluno migration
iManage Work is a server-based 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.
iManage WorkServer- Matters: Carried across
- Documents: Confirmed in the analysis
- Emails: Confirmed in the analysis
- Tasks: Confirmed in the analysis
- Custom fields: Confirmed in the analysis
- Templates: Confirmed in the analysis
SolunoCloud- 1 carried
- 5 to confirm
What moves
What moves from iManage Work to Soluno
Each row is a kind of record iManage Work 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.
| Record | What is planned | ||
|---|---|---|---|
| MattersMatters or cases, with their numbers, types, parties and status | Held in partA workspace usually stands for a matter, with client and matter held as custom1 and custom2. | Has a placeAs files, with number, area of practice, responsible lawyer and billing settings. | Carried across |
| DocumentsFiles stored in or linked from the system | HeldEach is identified by its library name, a document number and a version number. | To be confirmedNo matter document store is described; NetDocuments can be linked. | Confirmed in the analysis |
| EmailsEmails saved to matters or to the store | HeldFiled emails are stored as documents, usually in email folders inside the workspace. | To be confirmed | Confirmed in the analysis |
| TasksTo-dos and workflow steps assigned to people | Held in partTask lists are kept in iManage Tracker, a separate product. | To be confirmed | Confirmed in the analysis |
| Custom fieldsFields and record types the firm added itself | HeldCustom profile fields with validated lists, captioned by the firm, such as practice area. | To be confirmed | Confirmed in the analysis |
| TemplatesPrecedents, document templates and automation | Held in partPrecedents are held as documents. Workspace templates only set folder structure. | To be confirmed | Confirmed 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 Work.
- 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 Work, 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 Work holds is exported in open formats and kept as an archive, or moved on a different route to a system built for it.
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. Soluno 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
Leaving iManage Work
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.
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.
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.
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.
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.
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.
Where it is going
Arriving in Soluno
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.
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.
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.
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.
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.
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.
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.
Analysis
We read what iManage Work 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.
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.
Trial load
A trial is loaded into Soluno 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.
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
What happens after you send it
- A free first call
We go through your answers with you and ask about anything they leave open.
- An analysis of what iManage Work 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.
- 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 Work to Soluno: 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 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 Work before the plan is fixed. Documents that have no place in Soluno are exported into folders by client and matter.
Does everything in iManage Work 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 Work 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.
Other routes
Other routes from iManage Work and into Soluno
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.
Choose your systems
Technology stack selection
Decide which practice management system your firm runs, with the evidence and the cost beside it.
About four weeks for a firm of about 15 people. Fixed price, set after a free first call.
Move your data
Data migration
Your data is cleaned up before anything moves, then a trial load is checked against the old system.
Fixed price, agreed after the analysis.
Set up your new system
Implementation
Your new system set up around the way your firm works: configuration, document automation and training.
A small firm of 1 to 10 users typically takes 4 to 8 weeks. A mid-sized firm of 10 to 50 users takes 8 to 16 weeks.
Put AI to work
AI advisory and enablement
A small group of your people learn to use an approved AI tool on real work, under written rules.
Two to four weeks for a small first group. Fixed price, set after a free first call.
iManage Work and Soluno are the names and marks of their owners, used here only to identify the two systems.
Moving from iManage Work 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.