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

Data migration route

DLex to Actionstep migration

DLex is a server-based practice management system, and Actionstep is a cloud one. Both run a whole practice, so this is a full move, and the financial records set the timetable.

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

What moves

What moves from DLex to Actionstep

Each row is a kind of record DLex holds, whether Actionstep has a place for it, and what is planned. On this route seven kinds of record carry across, three kinds need mapping and four kinds are confirmed in the analysis.

Records in DLex and their place in Actionstep
RecordIn DLexIn ActionstepWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldCalled dossiers.Has a placeImported with a matter type, a status and the old number as File Reference.Carried across
ContactsClients, other parties and referrersHeldClients, opposing parties and other persons, with identity and bank details.Has a placeImported first, then linked to matters through a parties import.Carried across
DocumentsFiles stored in or linked from the systemHeldFiles and templates sit in a server directory, beside the SQL database.Has a placeFiled in matter folders; not part of the spreadsheet import tool.Carried across
EmailsEmails saved to matters or to the storeHeldEmails are held as documents with a typed or sent status, through Outlook.Has a placeSaved emails sit on the matter they were filed to.Carried across
NotesFile notes, matter notes and contact notesTo be confirmedHas a placeThe import tool has a file notes template.Confirmed in the analysis
CalendarAppointments, court dates and deadlinesHeld in partSynchronises with Outlook and Exchange; what is synchronised was not confirmed.Has a placeAppointments have a place; the standard import templates do not cover them.Carried across
TasksTo-dos and workflow steps assigned to peopleTo be confirmedHas a placeThe import tool has a tasks template.Confirmed in the analysis
Time and expensesTime and expense entries, billed and unbilledHeldRegistered services (prestaties) and costs.Has a placeTime entries and disbursements each have an import template.Carried across
BillingInvoices, payments and debtor balancesHeldFee statements, invoices and reminders.Has a place in partUnpaid invoices load as accounts receivable; older invoice history is confirmed in the analysis.Carried with mapping
Trust moneyTrust or client account ledgers and balancesTo be confirmedHas a placeTrust balances load per matter through the trust accounts import.Confirmed in the analysis
Firm accountsGeneral ledger, office account and payablesHeldBookkeeping, including the Belgian VAT return and client listings.Has a placeOpening balances are entered against the general ledger, or the books stay in Xero.Carried across
Custom fieldsFields and record types the firm added itselfHeldExtra fields (extra velden) the firm defines itself.Has a placeData collections are built per matter type before values are loaded.Carried with mapping
TemplatesPrecedents, document templates and automationHeldDocument models (modellen) stored beside the documents.Has a placeRebuilt as Actionstep templates with its merge fields.Carried with mapping
IntakeLeads, enquiries, intake forms and pipelinesTo be confirmedHas a placeConfirmed in the analysis

What the plans mean

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

The whole practice moves, accounts included.

A move between two practice management systems is the widest kind there is. DLex and Actionstep each keep matters, contacts, documents, time and money in one place, but no two systems link those records the same way. In one, a client is a contact with a role on the matter. In another, every matter carries its own client card. Most of the analysis goes into those links, because a matter that arrives without its client or its documents is the first thing staff find.

The financial side decides the dates. Unbilled time, debtor balances and trust ledgers have to agree with DLex’s own reports as at one day, and a new system usually wants them as opening balances, not as years of transactions. So the firm decides early how much history comes across as live records and how much is kept as reports. Matter and document loads can be repeated until they are right. The money is loaded once.

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

Actionstep has its own import tool, which takes spreadsheets in a set order: contacts, then matters, then the parties that join them. Tasks, time entries, trust balances, disbursements, unpaid invoices and file notes follow once the matters exist. None of it can start until the matter types, participant types and data collections have been built, because every imported row refers to them.

  1. Matter types before any data

    A matter’s type decides its workflow steps, its document folders, which party roles are available and which custom data it carries. So the first job is deciding how the old system’s matter types map to Actionstep’s, and building any that are missing. An imported matter also needs a step to sit at, usually the one closest to its old status.

  2. Old numbers go to File Reference

    Actionstep assigns its own Matter ID to each imported matter. The number the firm has always used goes into the File Reference field, which the quick search reads from the start of the reference. Staff can keep finding matters by the number printed on old letters and file covers.

  3. Check before anyone edits

    The import tool can roll back a load, but only while the imported records are untouched. Once someone edits them, the rollback no longer works. Trial loads are therefore checked straight away against the old system, and nobody outside the project works in the new records until the counts and balances agree.

  4. Folders come from the matter type

    Default document folders are set per matter type. There is no single folder list that applies across all matters. Before documents are loaded, the old folder names are mapped to the folders each matter type will have, so a conveyancing file and a litigation file each open with the layout the firm designed for them.

  5. Opening balances can be locked

    Trust balances load against matters, unpaid invoices load as accounts receivable, and general ledger opening balances are entered on the accounts list. An opening balance that has been locked cannot be edited afterwards. The figures are rehearsed on a trial load and agreed with the firm’s accountant before the lock is applied in the live system.

More about moving into Actionstep

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 Actionstep. 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 Actionstep 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 Actionstep 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 toActionstep

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

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

Most of the work in an Actionstep set-up is design. The firm decides what its matter types are, what steps each one moves through and what happens at each step. Templates, billing and trust settings are then built around those matter types. People are trained on their own workflows, since a generic demonstration looks little like the firm’s finished system.

Set-up decisions in Actionstep

  • Matter types, with workflow steps and default document folders
  • Participant types and data collections for each matter type
  • Document and email templates rebuilt with Actionstep merge fields
  • Trust accounts, chart of accounts and the optional Xero link
  • System roles and data permissions for each group of staff
  • Outlook add-in, divisions and the firm’s billing preferences

Questions

DLex to Actionstep: 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 Actionstep?

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

Most of it does on paper. Notes, tasks, trust ledgers 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 Actionstep is kept as a readable archive, and you see which before the move.

What has to be decided before DLex data is loaded into Actionstep?

Billing records, custom fields and templates are carried with mapping, so each mapping is agreed with you first. Notes, tasks, trust ledgers 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 Actionstep are the names and marks of their owners, used here only to identify the two systems.

Moving from DLex to Actionstep?

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

We reply within one business day.