Data migration route
DLex to SimpleLaw migration
DLex is a server-based practice management system, and SimpleLaw is a cloud one. Both run a whole practice, so this is a full move, and the financial records set the timetable.
DLexServer- Matters: Carried across
- Contacts: Carried across
- Documents: Carried across
- Calendar: Carried across
- Time and expenses: Carried across
- Billing: Carried with mapping
- Custom fields: Carried with mapping
- Templates: Carried with mapping
- Emails: Confirmed in the analysis
- Notes: Confirmed in the analysis
- Tasks: Confirmed in the analysis
- Trust money: Confirmed in the analysis
- Intake: Confirmed in the analysis
SimpleLawCloud- Firm accounts: Kept as a readable archive
- 5 carried
- 3 mapped
- 5 to confirm
- 1 archived
What moves
What moves from DLex to SimpleLaw
Each row is a kind of record DLex holds, whether SimpleLaw has a place for it, and what is planned. On this route five kinds of record carry across, three kinds need mapping, one kind has no place in SimpleLaw and is archived and five kinds are confirmed in the analysis.
| Record | What is planned | ||
|---|---|---|---|
| MattersMatters or cases, with their numbers, types, parties and status | HeldCalled dossiers. | Has a place | Carried across |
| ContactsClients, other parties and referrers | HeldClients, opposing parties and other persons, with identity and bank details. | Has a placeAs leads, clients or other contacts in the CRM. | Carried across |
| DocumentsFiles stored in or linked from the system | HeldFiles and templates sit in a server directory, beside the SQL database. | Has a placeUploaded to SimpleLaw storage or held in a linked Dropbox, Google Drive or OneDrive. | Carried across |
| EmailsEmails saved to matters or to the store | HeldEmails are held as documents with a typed or sent status, through Outlook. | To be confirmed | Confirmed in the analysis |
| 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 place | Carried across |
| TasksTo-dos and workflow steps assigned to people | To be confirmed | Has a place | Confirmed in the analysis |
| Time and expensesTime and expense entries, billed and unbilled | HeldRegistered services (prestaties) and costs. | Has a place | Carried across |
| BillingInvoices, payments and debtor balances | HeldFee statements, invoices and reminders. | 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 balances | To be confirmed | Has a place in partTrust balances are supported; history depth is confirmed in the analysis. | Confirmed in the analysis |
| Firm accountsGeneral ledger, office account and payables | HeldBookkeeping, including the Belgian VAT return and client listings. | No placeGeneral ledger stays in QuickBooks or another accounting package. | Kept as a readable archive |
| Custom fieldsFields and record types the firm added itself | HeldExtra fields (extra velden) the firm defines itself. | Has a place | Carried with mapping |
| TemplatesPrecedents, document templates and automation | HeldDocument models (modellen) stored beside the documents. | Has a place in partTemplates are rebuilt using SimpleLaw’s own automation. | Carried with mapping |
| IntakeLeads, enquiries, intake forms and pipelines | To be confirmed | Has 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 DLex.
- 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 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
The whole practice moves, accounts included.
A move between two practice management systems is the widest kind there is. DLex and SimpleLaw 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. SimpleLaw 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 SimpleLaw
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.
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.
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.
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.
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.
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.
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 DLex 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.
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 SimpleLaw 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 SimpleLaw 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 SimpleLaw. 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 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
DLex to SimpleLaw: 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 SimpleLaw?
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 SimpleLaw 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 SimpleLaw 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 SimpleLaw?
Billing records, custom fields and templates are carried with mapping, so each mapping is agreed with you first. Emails, 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 SimpleLaw
Other destinations from DLex
Other systems that move into SimpleLaw
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 SimpleLaw are the names and marks of their owners, used here only to identify the two systems.
Moving from DLex 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.