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

Data migration route

Soluno to Clio Manage migration

Soluno is a cloud accounting and billing system, and Clio Manage is a cloud practice management system. The financial records lead: balances and open items move, and the matters in Clio Manage are built around them.

FromSolunoCloud
  1. Matters: Carried across
  2. Contacts: Carried across
  3. Time and expenses: Carried with mapping
  4. Billing: Carried with mapping
  5. Trust money: Carried with mapping
  6. Documents: Confirmed in the analysis
  7. Emails: Confirmed in the analysis
  8. Notes: Confirmed in the analysis
  9. Calendar: Confirmed in the analysis
  10. Tasks: Confirmed in the analysis
  11. Custom fields: Confirmed in the analysis
  12. Templates: Confirmed in the analysis
  13. Intake: Confirmed in the analysis
ToClio ManageCloud
  1. Firm accounts: Kept as a readable archive
Readable archiveNo place in Clio Manage
  • 2 carried
  • 3 mapped
  • 8 to confirm
  • 1 archived
What the two products hold. The analysis confirms it field by field.

What moves

What moves from Soluno to Clio Manage

Each row is a kind of record Soluno holds, whether Clio Manage has a place for it, and what is planned. On this route two kinds of record carry across, three kinds need mapping, one kind has no place in Clio Manage and is archived and eight kinds are confirmed in the analysis.

Records in Soluno and their place in Clio Manage
RecordIn SolunoIn Clio ManageWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldCalled files. Each has a file number, area of practice, responsible lawyer and file staff.Has a placeImported from a matters template, after contacts.Carried across
ContactsClients, other parties and referrersHeldNumbered contacts; contacts can be grouped for split billing.Has a placePeople and companies, with related contacts linked to matters by a separate template.Carried across
DocumentsFiles stored in or linked from the systemTo be confirmedHelp centre describes invoices and statements kept on a contact, and a NetDocuments link.Has a placeFiled under the matter; Clio scopes document migration separately from data.Confirmed in the analysis
EmailsEmails saved to matters or to the storeTo be confirmedHas a placeHeld as communications on the matter, with phone logs.Confirmed in the analysis
NotesFile notes, matter notes and contact notesTo be confirmedHas a placeMatter notes and contact notes each have a template.Confirmed in the analysis
CalendarAppointments, court dates and deadlinesTo be confirmedHas a placeCalendar events have a migration template.Confirmed in the analysis
TasksTo-dos and workflow steps assigned to peopleTo be confirmedHas a placeTasks have a migration template.Confirmed in the analysis
Time and expensesTime and expense entries, billed and unbilledHeldFee and time entries with task and activity codes.Has a place in partUnbilled time entries load; billed time entries do not, by Clio’s migration guide.Carried with mapping
BillingInvoices, payments and debtor balancesHeldPre-bills, invoices, billing groups and retainer arrangements.Has a place in partAn outstanding balance loads as one line per matter; past invoices do not.Carried with mapping
Trust moneyTrust or client account ledgers and balancesHeldTrust balances by contact and file; a file cannot close while trust is held.Has a place in partA trust balance loads as one line per matter or contact; past transactions do not.Carried with mapping
Firm accountsGeneral ledger, office account and payablesHeldGeneral ledger with financial periods, banking and bank reconciliation.No placeNot in Clio Manage. Books sit in a linked accounting package, or in Clio Accounting where Clio offers it.Kept as a readable archive
Custom fieldsFields and record types the firm added itselfTo be confirmedHas a placeCreated first, then filled from the custom field templates.Confirmed in the analysis
TemplatesPrecedents, document templates and automationTo be confirmedHas a placeRebuilt as Clio document templates with its merge fields.Confirmed in the analysis
IntakeLeads, enquiries, intake forms and pipelinesTo be confirmedNo placeLeads and intake forms belong in Clio Grow.Confirmed in the analysis

What the plans mean

Carried across
Clio Manage has a place for this kind of record. It is loaded there and checked against Soluno.
Carried with mapping
Clio Manage 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
Clio Manage 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

Time, bills and balances move. How much history is a decision.

Coming from an accounting or billing system, the records that count are balances: unbilled time, unpaid invoices, client funds, the ledger. A practice management system takes these as opening positions on a matter. So every client and job in Soluno needs a matter to land on, and the first piece of work is building that matter list, often from client and project codes that were never meant to be matter numbers.

How much history to bring is the main choice. Paid invoices from years ago can be loaded as records, kept as PDF copies on the matter, or left in a read-only copy of Soluno. Most firms bring open items and a period of history, and keep the rest as reports. Opening balances in Clio Manage are agreed to the trial balance and aged debtors from Soluno as at the cutover date, and that load is rehearsed before it is done for real.

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 Clio Manage are finished.

Where the data is now

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.

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

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

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

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

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

More about moving off Soluno

Where it is going

Clio Manage is loaded through its migration templates, one spreadsheet per kind of record, imported in a fixed order with contacts first. Clio’s own migration guide is plain about the limit: balances come across, financial history does not. So a load into Clio is planned as records plus opening positions, with the old system kept for the history behind them.

  1. Matters link by client name

    The matters template ties each matter to its client by an exact match on first name, last name or company name. A client spelt two ways in the old system becomes two contacts, or a matter assigned to an unknown client. This is why contact clean-up is finished before the first trial load, not after it.

  2. Decide the numbering scheme first

    Clio numbers imported matters itself unless the account is set to manual numbering, in which case the old number is supplied in the template. That setting and the firm’s preferred scheme are decided before any matter is loaded. The Client Reference field is available for an old file number the firm still wants to see.

  3. Balances, one line each

    Under Clio’s standard migration, an outstanding balance arrives as one line per matter and a trust balance as one line per matter or contact. Past invoices, billed time, payments and trust transactions are listed as data that cannot be migrated. The trust total is reconciled against the old system’s closing report on the trial load.

  4. Custom fields must exist

    Matter and contact custom fields are created in Clio before their values are imported, each with a field type. Accounts set up for a particular practice area come with preconfigured fields and matter templates, which affects the mapping. We compare those with the old system’s fields and add only what is missing.

  5. Rates and permissions by hand

    Billable rates for users, clients and matters are not part of an import. Neither are user permissions or settings. They are entered in Clio during set-up from a schedule the firm confirms, and a sample of imported unbilled time is checked against that schedule before the trial load is signed off.

More about moving into Clio Manage

How NewLaw runs it

Four steps, in this order.

Trust money moves on this route, so the trust cutover gets a rehearsal of its own.

  1. Analysis

    We read what Soluno holds and how its records link, then agree with you, field by field, where each piece will sit in Clio Manage. Anything with no place there comes across as a note or stays behind, and you see which before the move.

  2. Clean-up

    Duplicate contacts and matters are merged where they can be identified, and inconsistent entries are put into one format, in Soluno, before extraction. It is not always possible to find every one, so some may carry across.

  3. Trial load

    The data is loaded into Clio Manage as a trial and checked against Soluno: record counts, trust and debtor totals, the links between records, document dates. Exceptions are listed for you to decide.

  4. Cutover

    Changes in Soluno are frozen for an agreed window, the data is collected a final time and Clio Manage goes live over a weekend. The trust and financial cutover is rehearsed on a full trial load first, because it cannot be re-run the way a document load can. 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

Step 1 of 5: Start with the route

Moving fromSoluno
Moving toClio Manage

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

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

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

Much of a Clio Manage set-up is firm-wide settings. The numbering scheme, practice areas, matter stages, billing preferences and trust accounts apply to everyone, so they are agreed once and early. Trust and accounting features are not the same in every country Clio sells in, so the firm’s own region is checked first. Document templates and custom fields follow. Email and document integrations are then installed for each user and tested on a real matter.

Set-up decisions in Clio Manage

  • Matter numbering scheme, practice areas and matter stages
  • Custom fields for matters and contacts, by practice area
  • Document templates with merge fields, uploaded from Word or PDF
  • Billing settings, user and client rates, and trust accounts
  • Roles and permissions for each user
  • Outlook add-in, Clio Drive and the accounting connection

Questions

Soluno to Clio Manage: 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 Clio Manage?

In part. A trust balance loads as one line per matter or contact; past transactions do not. The analysis sets out which trust records have a place in Clio Manage and which are kept as an archive, and the trust cutover is rehearsed on a full trial load before the real one.

What happens to records Clio Manage has no place for?

On this route that is 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 Clio Manage?

Time entries, billing records and trust ledgers 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 sets the cutover date and how much financial history comes across as live records.

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

Soluno and Clio Manage are the names and marks of their owners, used here only to identify the two systems.

Moving from Soluno to Clio Manage?

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

We reply within one business day.