Data migration route
DLex to Neos migration
DLex is a server-based practice management system, and Neos is a cloud case management system for personal injury work. Matter records move into cases, and the firm decides where its accounting runs from the cutover date.
DLexServer- Matters: Carried across
- Contacts: Carried across
- Documents: Carried across
- Calendar: Carried across
- Emails: Carried with mapping
- Time and expenses: Carried with mapping
- Billing: Carried with mapping
- Custom fields: Carried with mapping
- Templates: Carried with mapping
- Notes: Confirmed in the analysis
- Tasks: Confirmed in the analysis
- Trust money: Confirmed in the analysis
- Intake: Confirmed in the analysis
NeosCloud- Firm accounts: Kept as a readable archive
- 4 carried
- 5 mapped
- 4 to confirm
- 1 archived
What moves
What moves from DLex to Neos
Each row is a kind of record DLex holds, whether Neos has a place for it, and what is planned. On this route four kinds of record carry across, five kinds need mapping, one kind has no place in Neos and is archived and four kinds are confirmed in the analysis.
| Record | What is planned | ||
|---|---|---|---|
| MattersMatters or cases, with their numbers, types, parties and status | HeldCalled dossiers. | Has a placeCases by case type. | Carried across |
| ContactsClients, other parties and referrers | HeldClients, opposing parties and other persons, with identity and bank details. | Has a placeParties, providers and case contacts. Contacts can be imported from CSV. | Carried across |
| DocumentsFiles stored in or linked from the system | HeldFiles and templates sit in a server directory, beside the SQL database. | Has a placeCase Docs tab, organised in sub-tabs. | Carried across |
| EmailsEmails saved to matters or to the store | HeldEmails are held as documents with a typed or sent status, through Outlook. | Has a place in partEmails tagged to a case are held. Loading old mail is scoped in the analysis. | Carried with mapping |
| NotesFile notes, matter notes and contact notes | To be confirmed | Has a place | Confirmed in the analysis |
| CalendarAppointments, court dates and deadlines | Held in partSynchronises with Outlook and Exchange; what is synchronised was not confirmed. | Has a placeCase calendar entries. | Carried across |
| TasksTo-dos and workflow steps assigned to people | To be confirmed | Has a placeLoaded as checklist items. | Confirmed in the analysis |
| Time and expensesTime and expense entries, billed and unbilled | HeldRegistered services (prestaties) and costs. | Has a place in partTime can be held as value items. The treatment of old entries is confirmed in the analysis. | Carried with mapping |
| BillingInvoices, payments and debtor balances | HeldFee statements, invoices and reminders. | Has a place in partInvoices exist in Neos. Loading past invoices is confirmed in the analysis. | Carried with mapping |
| Trust moneyTrust or client account ledgers and balances | To be confirmed | To be confirmed | Confirmed in the analysis |
| Firm accountsGeneral ledger, office account and payables | HeldBookkeeping, including the Belgian VAT return and client listings. | No placeThe general ledger stays in QuickBooks. | Kept as a readable archive |
| Custom fieldsFields and record types the firm added itself | HeldExtra fields (extra velden) the firm defines itself. | Has a placeUser-defined fields are created on the relevant tab first. | Carried with mapping |
| TemplatesPrecedents, document templates and automation | HeldDocument models (modellen) stored beside the documents. | Has a place in partTemplates are rebuilt for Neos document generation. | Carried with mapping |
| IntakeLeads, enquiries, intake forms and pipelines | To be confirmed | Has a placeIntakes tab. Simple intake imports from CSV are supported. | Confirmed in the analysis |
What the plans mean
- Carried across
- Neos has a place for this kind of record. It is loaded there and checked against DLex.
- Carried with mapping
- Neos 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
- Neos has no place for it. It is exported in a format that opens without DLex 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
Matters become cases. The ledgers need a home.
Going from a practice management system to a case management system is a move towards the file and away from the ledger. Matters, parties, documents, notes and deadlines have a natural place in Neos. Time, invoices, trust and the general ledger often do not, or only in part, and the table above shows which. Before the move is planned the firm settles where billing and trust accounting will run, because that decides what is loaded and what is archived.
Case systems are usually built around a practice area, with their own stages, roles and document sets. A general matter from DLex has to be given a case type in Neos, and that choice drives which fields and workflows it gets. The mapping is agreed type by type. Financial history with no place in Neos is exported as reports and ledgers the firm can open without DLex, and kept as the record of what was billed and held.
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. Neos 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
Leaving DLex
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.
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.
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.
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.
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.
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.
Where it is going
Arriving in Neos
Neos expects personal injury data in its own tab structure, so loading a firm means deciding which tab each old record belongs on. Parties, insurance and counsel map directly from most injury systems. Money maps to value items. Anything the standard tabs lack becomes a user-defined field, which has to be created before the load.
Every figure needs a value code
Costs, medical bills, fees and settlement amounts are loaded as value items, and each carries a value code. The code list is agreed with the firm’s accounts staff first. A figure loaded under the wrong code is reported in the wrong place, so the list is tested on real cases before the bulk load.
Lists are set up first
Cases are loaded against case types, statuses and staff assignments that already exist in Neos. Those lists are set up, and the old system’s values tidied to match, before the trial load. Misspelt attorney names and unused case types in the source are cleaned out at the same stage.
Documents go to sub-tabs
Files land on the Case Docs tab under sub-tabs, which staff can view as a list or as folders. The old system’s folders or categories are mapped to a fixed set of sub-tabs. Without that, every personal habit of naming folders is reproduced and the folder view becomes hard to read.
Reminders split two ways
Neos fills its dashboards from checklists and case calendars. Old diary entries and tasks are sorted between them: dated appointments and court events to the calendar, and to-dos to the checklist. An item assigned to several people in the old system may need one named owner, and the firm chooses who.
Assembly runs its own conversions
Assembly migrates firms into Neos with its own team and tooling, and offers routes from self-service templates to a full conversion. Where the firm uses that service, outside help goes on the work around it: cleaning the source, checking the converted cases against the old system, and listing exceptions.
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 Neos 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 DLex and checking each trial against DLex.
Analysis
We read what DLex holds and how its records link, then agree with you, field by field, where each piece will sit in Neos. 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 DLex, before extraction. It is not always possible to find every one, so some may carry across.
Trial load
The data is loaded into Neos as a trial and checked against DLex: record counts, financial totals, the links between records, document dates. Exceptions are listed for you to decide.
Cutover
Changes in DLex are frozen for an agreed window, the data is collected a final time and Neos 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
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 DLex holds
What is in it, how its records link, and where each piece would sit in Neos. 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 Neos
Loaded data is not yet a working system. The maker of Neos runs or arranges the set-up of its product, so this is what has to be decided and put in place in Neos, whoever does the work, before people rely on it from the first day.
Neos comes set up for injury work, so implementation is mostly choosing among its options and connecting the firm’s other tools. The lists that drive reporting are decided first, then checklists, then documents. Assembly provides its own implementation team, and the firm’s internal lead still has to make the decisions listed below.
Set-up decisions in Neos
- Set case types, statuses and staff roles
- Agree the value code list with accounts staff
- Build checklists for each case type and stage
- Create user-defined fields for data the tabs lack
- Prepare document templates for the generation wizard
- Connect Microsoft 365, QuickBooks and the phone system
Questions
DLex to Neos: 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 Neos?
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 Neos turns out to have no place for trust ledgers, they are kept as a readable archive and the firm decides where trust accounting runs.
What happens to records Neos has no place for?
On this route that is the firm’s accounts. They are exported from DLex 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 DLex data is loaded into Neos?
Emails, time entries, 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.
Other routes
Other routes from DLex and into Neos
Other destinations from DLex
Other systems that move into Neos
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.
DLex and Neos are the names and marks of their owners, used here only to identify the two systems.
Moving from DLex to Neos?
Tell us what you are moving. You get a plan and a fixed price after the analysis.
We reply within one business day.