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

Data migration route

DLex to Soluno migration

DLex is a server-based practice management system, and Soluno is a cloud accounting and billing system. The firm’s books move into Soluno, and the matter records go to another system or into an archive.

FromDLexServer
  1. Matters: Carried across
  2. Contacts: Carried across
  3. Time and expenses: Carried across
  4. Billing: Carried across
  5. Firm accounts: Carried across
  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. Trust money: Confirmed in the analysis
  12. Custom fields: Confirmed in the analysis
  13. Templates: Confirmed in the analysis
  14. Intake: Confirmed in the analysis
ToSolunoCloud
  • 5 carried
  • 9 to confirm
What the two products hold. The analysis confirms it field by field.

What moves

What moves from DLex to Soluno

Each row is a kind of record DLex holds, whether Soluno has a place for it, and what is planned. On this route five kinds of record carry across and nine kinds are confirmed in the analysis.

Records in DLex and their place in Soluno
RecordIn DLexIn SolunoWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldCalled dossiers.Has a placeAs files, with number, area of practice, responsible lawyer and billing settings.Carried across
ContactsClients, other parties and referrersHeldClients, opposing parties and other persons, with identity and bank details.Has a placeEach contact is numbered; a file must have a primary contact.Carried across
DocumentsFiles stored in or linked from the systemHeldFiles and templates sit in a server directory, beside the SQL database.To be confirmedNo matter document store is described; NetDocuments can be linked.Confirmed in the analysis
EmailsEmails saved to matters or to the storeHeldEmails are held as documents with a typed or sent status, through Outlook.To be confirmedConfirmed in the analysis
NotesFile notes, matter notes and contact notesTo be confirmedTo be confirmedConfirmed in the analysis
CalendarAppointments, court dates and deadlinesHeld in partSynchronises with Outlook and Exchange; what is synchronised was not confirmed.To be confirmedConfirmed in the analysis
TasksTo-dos and workflow steps assigned to peopleTo be confirmedTo be confirmedConfirmed in the analysis
Time and expensesTime and expense entries, billed and unbilledHeldRegistered services (prestaties) and costs.Has a placeCarried across
BillingInvoices, payments and debtor balancesHeldFee statements, invoices and reminders.Has a placeCarried across
Trust moneyTrust or client account ledgers and balancesTo be confirmedHas a placeConfirmed in the analysis
Firm accountsGeneral ledger, office account and payablesHeldBookkeeping, including the Belgian VAT return and client listings.Has a placeGeneral ledger; history is loaded into open periods that are then closed in order.Carried across
Custom fieldsFields and record types the firm added itselfHeldExtra fields (extra velden) the firm defines itself.To be confirmedConfirmed in the analysis
TemplatesPrecedents, document templates and automationHeldDocument models (modellen) stored beside the documents.To be confirmedConfirmed in the analysis
IntakeLeads, enquiries, intake forms and pipelinesTo be confirmedTo be confirmedConfirmed 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 DLex.
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

The firm’s books move. The matters need another home.

Moving from a practice system to a general accounting package separates two things DLex kept together. Soluno will hold the chart of accounts, clients as customers, invoices, payments and balances. It has no matter file, no documents and no court dates. So this route is usually half of a larger plan, with the matter side going to another system, and the first decision is which system issues invoices from now on.

Trust money needs particular care. A general accounting package is not built as a legal trust ledger: client funds can be shown as a liability, but matter by matter trust records are another thing. Where the table above shows trust without a place in Soluno, the firm settles where trust accounting will run before anything is moved. Opening balances are agreed to the trial balance and aged debtors in DLex as at the cutover date.

DLex runs on the firm’s own equipment, so the data is collected there: a copy of the database and the folders its documents sit in, taken with the firm’s IT provider or over a remote session. Soluno is hosted by its maker, so loading depends on the import tools and access it provides. The old machine is kept, read only, as the fall-back record.

Where the data is now

DLex is installed on the firm’s own server, so its SQL database and its document directory are both in the building or with the firm’s IT provider. It was made for Belgian practice. The labels are Dutch or French, the accounting follows Belgian VAT rules, and it talks to the Belgian lawyers’ platform. A move to an international product has to translate more than the data.

  1. Database and files apart

    The SQL Server database holds the dossiers and the record of their documents. The documents and templates themselves are files in a directory on the server. Both are copied at the same moment, because a database taken on Friday and files taken on Monday will disagree, and the missing ones only show up when someone opens a dossier.

  2. Belgian accounting inside

    DLex turns registered time and costs into fee statements and invoices, sends reminders, and prepares the VAT return and the client listing. A product built for another country will not produce Belgian filings. The firm decides whether the destination handles them, or whether accounting moves to a separate Belgian package fed by the new system.

  3. Email status depends on Outlook

    An email written from DLex is saved as a document of type e-mail, and its status changes from typed to sent only when it goes out through the default Outlook account. Some stored emails will therefore be drafts that were never sent. Status is carried across so that a draft is not later read as correspondence.

  4. DPA and DLexConnect

    The connection to the DPA and the DLexConnect extranet are services, not data. Filings made through the DPA remain on that platform. Clients who log in to DLexConnect lose that access when DLex is switched off. The firm decides how clients will see their files afterwards and tells them before cutover.

  5. Two languages, extra fields

    Belgian firms often work in both Dutch and French, and DLex lets them add extra fields with their own titles. Field names, document types and code lists may exist in either language. Each is mapped once to a single value in the new system, and the firm confirms the wording that staff will see.

More about moving off DLex

Where it is going

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.

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

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

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

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

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

More about moving into Soluno

How NewLaw runs it

Four steps, in this order.

Financial records move on this route, so the balances are rehearsed before the real cutover.

  1. Analysis

    We read what DLex 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.

  2. Clean-up

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

  3. Trial load

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

  4. Cutover

    Changes in DLex 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 DLex as at the cutover date. DLex 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 DLex 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 fromDLex
Moving toSoluno

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

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

DLex to Soluno: what firms ask

Can we move from DLex to a system that is not Belgian?

Yes for dossiers, contacts, documents, time and invoices. The Belgian parts need a plan: the VAT return and client listing, the DPA connection and local invoice requirements. Either the destination covers them, or a Belgian accounting package runs beside it. The analysis sets out which, before a price is agreed.

Where are our documents physically?

On your own server, or your IT provider’s, in the directory that was chosen when DLex was installed. They are normal files. The database records which dossier each belongs to, its type and its status. Both parts are needed: the files without the database are just a very large folder with no matter numbers.

Do the extra fields we added come across?

They can. Extra fields are listed with their titles and how many dossiers or contacts use each one. Those in real use are created as custom fields in the new system where it allows them. Ones that hold a handful of old values are usually moved into a note, with the firm’s agreement.

Do trust balances in DLex 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 DLex 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 DLex have a place in Soluno?

Most of it does on paper. Documents, emails, notes, calendar entries, tasks, trust ledgers, 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 DLex data is loaded into Soluno?

Documents, emails, notes, calendar entries, tasks, trust ledgers, 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

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

Moving from DLex 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.