Data migration route
Soluno to iManage Cloud migration
Soluno is a cloud accounting and billing system, and iManage Cloud is a cloud document management system. Only files and their details have a place there, so this route carries the documents and archives the rest.
SolunoCloud- Matters: Carried with mapping
- Documents: Confirmed in the analysis
- Emails: Confirmed in the analysis
- Notes: Confirmed in the analysis
- Calendar: Confirmed in the analysis
- Tasks: Confirmed in the analysis
- Custom fields: Confirmed in the analysis
- Templates: Confirmed in the analysis
- Intake: Confirmed in the analysis
iManage CloudCloud- Contacts: Kept as a readable archive
- Time and expenses: Kept as a readable archive
- Billing: Kept as a readable archive
- Trust money: Kept as a readable archive
- Firm accounts: Kept as a readable archive
- 1 mapped
- 8 to confirm
- 5 archived
What moves
What moves from Soluno to iManage Cloud
Each row is a kind of record Soluno holds, whether iManage Cloud has a place for it, and what is planned. On this route one kind needs mapping, five kinds have no place in iManage Cloud and are archived and eight kinds are confirmed in the analysis.
| Record | What is planned | ||
|---|---|---|---|
| MattersMatters or cases, with their numbers, types, parties and status | HeldCalled files. Each has a file number, area of practice, responsible lawyer and file staff. | Has 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 referrers | HeldNumbered contacts; contacts can be grouped for split billing. | No place | Kept as a readable archive |
| DocumentsFiles stored in or linked from the system | To be confirmedHelp centre describes invoices and statements kept on a contact, and a NetDocuments link. | Has a placeEach needs a workspace and valid client and matter values; its class sets default security. | Confirmed in the analysis |
| EmailsEmails saved to matters or to the store | To be confirmed | Has a placeLoaded as email documents into the workspace’s email folders. | Confirmed in the analysis |
| NotesFile notes, matter notes and contact notes | To be confirmed | No placeFile notes can be loaded as documents on the matter. | Confirmed in the analysis |
| CalendarAppointments, court dates and deadlines | To be confirmed | No place | Confirmed in the analysis |
| TasksTo-dos and workflow steps assigned to people | To be confirmed | No placeiManage Tracker is a separate product with its own set-up. | Confirmed in the analysis |
| Time and expensesTime and expense entries, billed and unbilled | HeldFee and time entries with task and activity codes. | No place | Kept as a readable archive |
| BillingInvoices, payments and debtor balances | HeldPre-bills, invoices, billing groups and retainer arrangements. | No place | Kept as a readable archive |
| Trust moneyTrust or client account ledgers and balances | HeldTrust balances by contact and file; a file cannot close while trust is held. | No place | Kept as a readable archive |
| Firm accountsGeneral ledger, office account and payables | HeldGeneral ledger with financial periods, banking and bank reconciliation. | No place | Kept as a readable archive |
| Custom fieldsFields and record types the firm added itself | To be confirmed | Has a place in partA fixed number of custom profile fields, each a validated list. | Confirmed in the analysis |
| TemplatesPrecedents, document templates and automation | To be confirmed | Has 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 pipelines | To be confirmed | No place | Confirmed in the analysis |
What the plans mean
- 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 Soluno 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
Only the documents have a place here.
iManage Cloud is a document management system: it takes files and the details that describe them. Most of what Soluno holds is not files. Entries, balances, settings and lists have no place in a document store, and the table above is short for that reason. What can move is any document Soluno produced or stored: invoices as PDFs, signed agreements, attachments, exported reports. Each is filed under the client or matter it relates to.
The useful version of this job is often an archive. A firm retiring a system wants its records readable later without keeping the subscription or the old PC. The data is exported in open formats, spreadsheets and PDFs, and filed in iManage Cloud in a workspace set aside for it, with access limited to the people who need it. That gives the firm one place to look, under the same retention rules as the rest of its documents.
Both are hosted by their makers, so nothing is collected from the firm’s office. What can be taken out of Soluno 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 Soluno is kept running until the checks on iManage Cloud are finished.
Where the data is now
Leaving Soluno
A firm leaving Soluno is moving its accounting system, and the rules of an accounting system shape the work. Files close only when their balances are cleared and their entries sit in closed periods. Closed files drop out of everyday searches. The numbers on contacts and files may be tied to NetDocuments workspaces. Each of these affects what is extracted and how it is checked.
On-premises or cloud
Some firms run Soluno on their own server and others use the cloud version. Actionstep’s help centre says support for the on-premises edition is ending and that those firms are being moved to the cloud. The analysis starts by confirming which edition holds the live data, because the way it is reached differs.
Closed files are hidden
Closing a file removes it from routine searches and reports, although its transactions still count in the financial statements. Staff can easily underestimate how many files exist. Closed files are counted separately in the analysis, and the firm decides how many years of them the new system should hold.
Numbers tied to NetDocuments
Contact and file numbers can be changed in Soluno, but where NetDocuments is in use the help centre puts that change behind an administrator setting. During a move the numbers are kept exactly as they are, so whatever is filed against them in NetDocuments still matches when the new practice or accounting system is connected.
File staff and fee shares
A file lists its responsible lawyer, other file staff with roles such as Lead or Assigned, an introducing lawyer and an optional fee allocation percentage for the general ledger. Partner reporting often depends on these. They are mapped one by one, and a fee report is run from both systems to compare.
Split billing through groups
Bills are split between payers by adding contacts to a group on the primary contact. The destination may handle split billing on the matter, or not at all. Grouped contacts are listed with their files, and the firm sees how one of those bills would look in the new system before agreeing.
Where it is going
Arriving in iManage Cloud
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.
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.
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.
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.
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.
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.
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.
Analysis
We read what Soluno 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.
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 iManage Cloud and checked against Soluno: 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 Soluno, a final pass over a weekend picks up what changed since the trial. Soluno 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 Soluno 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 Soluno 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.
- 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
Soluno to iManage Cloud: what firms ask
Is Soluno still available now that Actionstep owns it?
Yes, under a new name. Actionstep’s help centre calls it Actionstep Legal Accounting, formerly Soluno, and describes weekly updates to the cloud version. Actionstep said at the time of the acquisition that the two products would remain available on their own as well as together.
We run Soluno with a separate practice management system. Which one do we move?
Either or both. Soluno holds time, bills, trust and the general ledger. The other system holds documents, calendar and case detail. They can be moved in one project or in two, provided the contact and file numbers that tie them together are kept the same throughout.
Why would a file refuse to close after it has been loaded?
Usually for one of the reasons Soluno itself enforces: unbilled time, a receivable, a retainer or trust balance, or an entry dated after the last closed period. The trial load is checked for these, so the list of files that cannot close is known and dealt with before go-live.
Do trust balances in Soluno have a place in iManage Cloud?
No. iManage Cloud does not keep trust ledgers. Trust records from Soluno 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, time entries, billing records, trust ledgers and the firm’s accounts. They are exported from Soluno 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 Soluno data is loaded into iManage Cloud?
Matters are carried with mapping, so each mapping is agreed with you first. Documents, emails, notes, calendar entries, tasks, custom fields, templates and intake records 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 Soluno and into iManage Cloud
Other destinations from Soluno
Other systems that move into iManage Cloud
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.
Soluno and iManage Cloud are the names and marks of their owners, used here only to identify the two systems.
Moving from Soluno 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.