Data migration route
Litify to Soluno migration
Litify is a cloud case 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.
LitifyCloud- Matters: Carried across
- Contacts: Carried across
- Time and expenses: Carried across
- Billing: Carried across
- 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
- Trust money: Confirmed in the analysis
- Firm accounts: Confirmed in the analysis
- Custom fields: Confirmed in the analysis
- Templates: Confirmed in the analysis
- Intake: Confirmed in the analysis
SolunoCloud- 4 carried
- 10 to confirm
What moves
What moves from Litify to Soluno
Each row is a kind of record Litify holds, whether Soluno has a place for it, and what is planned. On this route four kinds of record carry across and ten kinds are confirmed in the analysis.
| Record | What is planned | ||
|---|---|---|---|
| MattersMatters or cases, with their numbers, types, parties and status | HeldMatters, with parties, calendar events, tasks, time and costs attached. | Has a placeAs files, with number, area of practice, responsible lawyer and billing settings. | Carried across |
| ContactsClients, other parties and referrers | HeldParties, connected to intakes and matters through roles. | Has a placeEach contact is numbered; a file must have a primary contact. | Carried across |
| DocumentsFiles stored in or linked from the system | HeldHeld in Litify’s document component, with tags, versions and templates. | To be confirmedNo matter document store is described; NetDocuments can be linked. | Confirmed in the analysis |
| EmailsEmails saved to matters or to the store | Held in partEmails appear on the case activity timeline. Mailboxes stay in the mail system. | To be confirmed | Confirmed in the analysis |
| NotesFile notes, matter notes and contact notes | To be confirmed | To be confirmed | Confirmed in the analysis |
| CalendarAppointments, court dates and deadlines | HeldCalendar events on the matter and the activity timeline. | To be confirmed | Confirmed in the analysis |
| TasksTo-dos and workflow steps assigned to people | HeldTasks, including those generated by matter plans. | To be confirmed | Confirmed in the analysis |
| Time and expensesTime and expense entries, billed and unbilled | HeldTimekeeping, with time entries tied to the matter. | Has a place | Carried across |
| BillingInvoices, payments and debtor balances | HeldBilling and eBilling, aimed chiefly at insurance defence work. | Has a place | Carried across |
| Trust moneyTrust or client account ledgers and balances | To be confirmed | Has a place | Confirmed in the analysis |
| Firm accountsGeneral ledger, office account and payables | To be confirmed | Has a placeGeneral ledger; history is loaded into open periods that are then closed in order. | Confirmed in the analysis |
| Custom fieldsFields and record types the firm added itself | HeldFields are added through Salesforce configuration. | To be confirmed | Confirmed in the analysis |
| TemplatesPrecedents, document templates and automation | HeldDocument templates with conditional logic. Matter plans automate tasks. | To be confirmed | Confirmed in the analysis |
| IntakeLeads, enquiries, intake forms and pipelines | HeldIntakes with questionnaires, lead scoring and marketing source tracking. | 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 Litify.
- 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 Litify, 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 Litify 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 Litify 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 Litify is kept running until the checks on Soluno are finished.
Where the data is now
Leaving Litify
A firm leaving Litify is leaving a Salesforce environment that has usually been shaped by an implementation team and several years of administrators. Its data is all there and can be queried. The effort is in reading the configuration, separating Litify’s own objects from the firm’s additions, and collecting the documents, which are managed by a separate component.
Parties and roles
A person or company is a party, and a role ties that party to an intake or matter as client, defendant, insurer, provider or something the firm defined. One party can hold different roles on different matters. Roles are extracted with the party, so the destination gets one contact with its relationships and not a copy per matter.
Intakes become matters
An intake is its own record with a questionnaire and a status, converted to a matter when the client signs. Turned-down and referred-out intakes stay as intakes and can far outnumber matters in a high-volume practice. They are counted separately, and the firm decides how many go to the new system.
Documents sit beside the records
Files are managed by Docrio, Litify’s document component. How they are stored, and how a full copy is obtained, is established in the analysis. Records and files are generally extracted by different routes and joined on the matter. Counts are checked per matter after the join, including on closed matters.
Injury detail in related records
Plaintiff firms typically record damages, insurance, liens, negotiations and settlement figures in records related to the matter, and each firm names and extends them its own way. These lists are extracted as tables with the matter reference. Where the destination has no equivalent, each becomes a schedule saved to the matter.
Automation stays behind
Matter plans, flows and validation rules are Salesforce configuration. They explain why the data looks the way it does, for example why a field is always filled at a given stage, but they cannot be exported into another product. Each is documented and used as the specification for workflows in the destination.
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.
Financial records move on this route, so the balances are rehearsed before the real cutover.
Analysis
We read what Litify holds and how its records link, then agree with you, field by field, where each piece will sit in Soluno. Anything with no place there comes across as a note or stays behind, and you see which before the move.
Clean-up
Duplicate contacts and matters are merged where they can be identified, and inconsistent entries are put into one format, in Litify, before extraction. It is not always possible to find every one, so some may carry across.
Trial load
The data is loaded into Soluno as a trial and checked against Litify: record counts, financial totals, the links between records, document dates. Exceptions are listed for you to decide.
Cutover
Changes in Litify are frozen for an agreed window, the data is collected a final time and Soluno 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 Litify as at the cutover date. Litify 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 Litify 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 Litify 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
Litify to Soluno: what firms ask
Do we need a Salesforce administrator to get our data out?
Someone with administrator access is needed, yes. The extraction reads the environment’s objects directly, and the administrator grants that access and explains what was customised. If the person who built it has left, the configuration is read from the system itself, which takes longer.
Are our documents included when Litify data is exported?
Do not assume so. Documents are managed by a separate component, and an export of matter records should not be expected to contain the files themselves. Both routes are covered in the plan and joined on the matter. A matter is only counted as moved when its files are attached to it.
We are moving to Litify. Who does the configuration?
Litify or one of its implementation partners normally configures the system. The migration fits into that project: the data mapping follows their design, and trial loads go into a test environment before production. It helps to agree early who owns the field list, because data and configuration change each other.
Do trust balances in Litify have a place 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 Litify before the plan is fixed. If Soluno 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 Litify have a place in Soluno?
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 Soluno is kept as a readable archive, and you see which before the move.
What has to be decided before Litify data is loaded into Soluno?
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.
Other routes
Other routes from Litify 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.
Litify and Soluno are the names and marks of their owners, used here only to identify the two systems.
Moving from Litify 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.