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

Data migration route

Soluno to Litify migration

Soluno is a cloud accounting and billing system, and Litify is a cloud case management system. Only part of what Soluno holds has a place in a case file: clients and jobs move, and the table shows how much of the billing side does.

FromSolunoCloud
  1. Matters: Carried across
  2. Contacts: Carried across
  3. Time and expenses: Carried across
  4. Billing: Carried with mapping
  5. Documents: Confirmed in the analysis
  6. Emails: Confirmed in the analysis
  7. Notes: Confirmed in the analysis
  8. Calendar: Confirmed in the analysis
  9. Tasks: Confirmed in the analysis
  10. Trust money: Confirmed in the analysis
  11. Firm accounts: Confirmed in the analysis
  12. Custom fields: Confirmed in the analysis
  13. Templates: Confirmed in the analysis
  14. Intake: Confirmed in the analysis
ToLitifyCloud
  • 3 carried
  • 1 mapped
  • 10 to confirm
What the two products hold. The analysis confirms it field by field.

What moves

What moves from Soluno to Litify

Each row is a kind of record Soluno holds, whether Litify has a place for it, and what is planned. On this route three kinds of record carry across, one kind needs mapping and ten kinds are confirmed in the analysis.

Records in Soluno and their place in Litify
RecordIn SolunoIn LitifyWhat 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 placeMatters, by case type.Carried across
ContactsClients, other parties and referrersHeldNumbered contacts; contacts can be grouped for split billing.Has a placeLoaded as parties and connected by roles.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 placeLoaded to the document component and attached to matters.Confirmed in the analysis
EmailsEmails saved to matters or to the storeTo be confirmedHas a place in partShown on the activity timeline. How old email is loaded is confirmed in the analysis.Confirmed in the analysis
NotesFile notes, matter notes and contact notesTo be confirmedTo be confirmedConfirmed in the analysis
CalendarAppointments, court dates and deadlinesTo be confirmedHas a placeCalendar events on the matter.Confirmed in the analysis
TasksTo-dos and workflow steps assigned to peopleTo be confirmedHas a placeConfirmed in the analysis
Time and expensesTime and expense entries, billed and unbilledHeldFee and time entries with task and activity codes.Has a placeTime entries on the matter.Carried across
BillingInvoices, payments and debtor balancesHeldPre-bills, invoices, billing groups and retainer arrangements.Has a place in partBilling is part of the product. Loading past invoices is scoped in the analysis.Carried with mapping
Trust moneyTrust or client account ledgers and balancesHeldTrust balances by contact and file; a file cannot close while trust is held.To be confirmedConfirmed in the analysis
Firm accountsGeneral ledger, office account and payablesHeldGeneral ledger with financial periods, banking and bank reconciliation.To be confirmedConfirmed in the analysis
Custom fieldsFields and record types the firm added itselfTo be confirmedHas a placeCustom fields are created before loading.Confirmed in the analysis
TemplatesPrecedents, document templates and automationTo be confirmedHas a place in partTemplates are rebuilt in Litify’s document generation.Confirmed in the analysis
IntakeLeads, enquiries, intake forms and pipelinesTo be confirmedHas a placeLoaded as intakes.Confirmed in the analysis

What the plans mean

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

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

Clients and jobs move. The books stay books.

An accounting or billing system and a case management system overlap less than firms expect. Soluno knows clients, jobs, time and invoices. Litify knows cases, parties, documents and deadlines. The client list moves well, and jobs can seed the case list. Time and invoice history has a place only where the case system has a billing side, and the table above shows whether this one does. A general ledger does not belong in a case system.

So the plan has two halves. Records with a place in Litify are loaded and checked there. The rest is exported from Soluno as reports and ledgers that open without it, and the firm decides where its accounts run from then on. If Soluno is staying as the accounting system, nothing financial needs to move at all, and the job is to line up client and case numbers so the two can be reconciled.

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

Loading a firm into Litify is done inside a Salesforce environment that has been configured for that firm, normally by Litify or one of its implementation partners. The data work fits around that project. Old records are mapped to parties, roles, intakes and matters and loaded into the Salesforce objects behind them, and documents are loaded separately and attached.

  1. The design comes first

    Case types, stages and page layouts are decided during discovery, before any load. A load into a half-configured environment has to be repeated when a field changes. The data mapping is written against the agreed design and updated whenever the design moves, so the two stay in step.

  2. One party, many roles

    Contacts from the old system become parties, and each appearance on a matter becomes a role. Duplicate contacts turn into duplicate parties with their roles divided between them. Duplicates are merged before the load where they can be identified, since separating them afterwards means pointing every role at the right party again.

  3. Open enquiries load as intakes

    Leads and enquiries that have not signed belong in intakes, not matters. They are loaded with their source and status so that conversion reports start from a true position. Old declined enquiries are loaded only if the firm wants them for conflict checking, and are marked so they do not count as live.

  4. Documents load after records

    Files are loaded into the document component once the matters exist, because each one is attached to a matter record. Folder structure is set per case type beforehand. Large injury files with medical records and video take time to transfer, and that time is planned into the cutover weekend.

  5. Validation rules reject bad rows

    A configured environment enforces required fields and validation rules, and old data seldom satisfies all of them. Rows that fail are reported by the load. They are fixed in the source and run again, or the rule is relaxed for migrated records, and the firm decides which for each rule.

More about moving into Litify

How NewLaw runs it

Four steps, in this order.

Financial records move on this route, so the balances are rehearsed before the real cutover. The maker of Litify says that it, or its partners, load firms into the product. Where the firm uses that service, NewLaw’s part is the work around it: the analysis, the clean-up in Soluno and checking each trial against Soluno.

  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 Litify. 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 Litify as a trial and checked against Soluno: record counts, financial 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 Litify goes live over a weekend. The financial cutover is rehearsed on a full trial load first, so that opening balances agree with the reports in Soluno as at the cutover date. 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 toLitify

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

Loaded data is not yet a working system. The maker of Litify runs or arranges the set-up of its product, so this is what has to be decided and put in place in Litify, whoever does the work, before people rely on it from the first day.

A Litify implementation is a configuration project on Salesforce, run by Litify or an implementation partner with the firm’s own project team. Discovery sessions with each department come first. The decisions that follow shape the system: what an intake asks, how a matter moves through its stages, who sees what, and which other systems are connected.

Set-up decisions in Litify

  • Define intake questionnaires and the rules for conversion
  • Set case types, matter stages and page layouts
  • Build matter plans that create tasks at each stage
  • Design document folders and generation templates per case type
  • Configure user roles and sharing for restricted matters
  • Decide on timekeeping, billing and accounting integrations

Questions

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

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 Soluno before the plan is fixed. If Litify turns out to have no place for trust ledgers, they are kept as a readable archive and the firm decides where trust accounting runs.

Does everything in Soluno have a place in Litify?

Most of it does on paper. Documents, emails, notes, calendar entries, tasks, trust ledgers, the firm’s accounts, custom fields, templates and intake records 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 Litify is kept as a readable archive, and you see which before the move.

What has to be decided before Soluno data is loaded into Litify?

Billing records are carried with mapping, so each mapping is agreed with you first. Documents, emails, notes, calendar entries, tasks, trust ledgers, the firm’s accounts, 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 Litify are the names and marks of their owners, used here only to identify the two systems.

Moving from Soluno to Litify?

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

We reply within one business day.