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

Data migration route

Soluno to SimpleLaw migration

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

FromSolunoCloud
  1. Matters: Carried across
  2. Contacts: Carried across
  3. Time and expenses: Carried across
  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
ToSimpleLawCloud
  1. Firm accounts: Kept as a readable archive
Readable archiveNo place in SimpleLaw
  • 3 carried
  • 2 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 SimpleLaw

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

Records in Soluno and their place in SimpleLaw
RecordIn SolunoIn SimpleLawWhat 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 placeCarried across
ContactsClients, other parties and referrersHeldNumbered contacts; contacts can be grouped for split billing.Has a placeAs leads, clients or other contacts in the CRM.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 placeUploaded to SimpleLaw storage or held in a linked Dropbox, Google Drive or OneDrive.Confirmed in the analysis
EmailsEmails saved to matters or to the storeTo be confirmedTo be confirmedConfirmed in the analysis
NotesFile notes, matter notes and contact notesTo be confirmedHas a placeConfirmed in the analysis
CalendarAppointments, court dates and deadlinesTo be confirmedHas a placeConfirmed 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 placeCarried across
BillingInvoices, payments and debtor balancesHeldPre-bills, invoices, billing groups and retainer arrangements.Has a place in partInvoices are created in the product; loading invoice history is confirmed 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.Has a place in partTrust balances are supported; history depth is confirmed in the analysis.Carried with mapping
Firm accountsGeneral ledger, office account and payablesHeldGeneral ledger with financial periods, banking and bank reconciliation.No placeGeneral ledger stays in QuickBooks or another accounting package.Kept as a readable archive
Custom fieldsFields and record types the firm added itselfTo be confirmedHas a placeConfirmed in the analysis
TemplatesPrecedents, document templates and automationTo be confirmedHas a place in partTemplates are rebuilt using SimpleLaw’s own automation.Confirmed in the analysis
IntakeLeads, enquiries, intake forms and pipelinesTo be confirmedHas a placeLeads and intake forms.Confirmed in the analysis

What the plans mean

Carried across
SimpleLaw has a place for this kind of record. It is loaded there and checked against Soluno.
Carried with mapping
SimpleLaw 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
SimpleLaw 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 SimpleLaw 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 SimpleLaw 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 SimpleLaw is mostly a job of sorting contacts and setting up each matter’s billing type. The CRM holds leads, clients and everyone else, so every incoming contact needs a status. Where documents will be stored is decided early as well, since that choice determines where the files are sent. Accounting history stays in QuickBooks or the old system.

  1. Lead, client or contact

    A person is tracked from first enquiry to client in one CRM, with tasks and appointments kept against the contact. Source systems that only ever held clients load simply. Systems with separate intake records need each enquiry classed as a live lead, a lost one or a duplicate of an existing client.

  2. Billing type on each matter

    Every matter is billed as hourly, flat fee, instalments, contingency, pro bono, trust or LEDES. The source may record this loosely or not at all. During the trial load a billing type is set on each matter and checked by the person who raises the bills, because it controls how the invoice is built.

  3. Storage chosen before loading

    If the firm stores documents with SimpleLaw, files are uploaded against each matter. Where it prefers Dropbox, Google Drive or OneDrive, the files go there, and what the connection does with folders already in place is checked first. Switching later means moving everything again, so the choice is made at the start with the firm’s IT support.

  4. Custom fields named for templates

    Custom fields supply intake forms and document automation as well as reports. A field brought across from the old system is only useful if templates can call on it. Fields are therefore named and typed with the firm’s main documents in mind, and one template is tested against loaded data.

  5. Portal access client by client

    The client portal is optional and the firm chooses who has access and what each client can see. Nothing is exposed by loading data. After go-live, access is switched on for chosen clients, starting with a few, once the firm has reviewed what their matters show.

More about moving into SimpleLaw

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 SimpleLaw. 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 SimpleLaw 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 SimpleLaw 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 toSimpleLaw

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

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

The set-up work is in making the product reflect the firm. Labels are adjusted to the firm’s terms. Intake forms and the custom fields behind them are built for each practice area, then document templates are made to draw on those fields. Workflows are written for the case types that follow a standard path, and the QuickBooks and payment connections are made last.

Set-up decisions in SimpleLaw

  • Labels for documents, activities, expenses and contact IDs
  • Custom fields and intake forms for each practice area
  • Document templates and the attorney-client agreement
  • Workflows for case types that follow a standard process
  • User permission sets and client portal visibility
  • QuickBooks connection and the online payment processor

Questions

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

In part. Trust balances are supported; history depth is confirmed in the analysis. The analysis sets out which trust records have a place in SimpleLaw 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 SimpleLaw 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 SimpleLaw?

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 SimpleLaw are the names and marks of their owners, used here only to identify the two systems.

Moving from Soluno to SimpleLaw?

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

We reply within one business day.