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

Data migration route

DLex to MyCase migration

DLex is a server-based practice management system, and MyCase 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. Calendar: Carried across
  5. Time and expenses: Carried across
  6. Emails: Carried with mapping
  7. Billing: Carried with mapping
  8. Firm accounts: 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
ToMyCaseCloud
  • 5 carried
  • 5 mapped
  • 4 to confirm
What the two products hold. The analysis confirms it field by field.

What moves

What moves from DLex to MyCase

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

Records in DLex and their place in MyCase
RecordIn DLexIn MyCaseWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldCalled dossiers.Has a placeAs cases, with name, number, practice area, open and closed dates and lead attorney.Carried across
ContactsClients, other parties and referrersHeldClients, opposing parties and other persons, with identity and bank details.Has a placePeople and companies load separately and are then linked to cases.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 folders under each case.Carried across
EmailsEmails saved to matters or to the storeHeldEmails are held as documents with a typed or sent status, through Outlook.Has a place in partSaved emails can be filed to a case; it does not hold mailboxes.Carried with mapping
NotesFile notes, matter notes and contact notesTo be confirmedHas a placeConfirmed in the analysis
CalendarAppointments, court dates and deadlinesHeld in partSynchronises with Outlook and Exchange; what is synchronised was not confirmed.Has a placeCarried across
TasksTo-dos and workflow steps assigned to peopleTo be confirmedHas a placeConfirmed 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 place in partAn outstanding balance per case is supported; fuller invoice history is confirmed in the analysis.Carried with mapping
Trust moneyTrust or client account ledgers and balancesTo be confirmedHas a placeBalances by client and case; the depth of ledger history is agreed first.Confirmed in the analysis
Firm accountsGeneral ledger, office account and payablesHeldBookkeeping, including the Belgian VAT return and client listings.Has a place in partOnly with the MyCase Accounting add-on or a linked QuickBooks file.Carried with mapping
Custom fieldsFields and record types the firm added itselfHeldExtra fields (extra velden) the firm defines itself.Has a placeFields are created on cases or contacts before records are loaded.Carried with mapping
TemplatesPrecedents, document templates and automationHeldDocument models (modellen) stored beside the documents.Has a place in partTemplates are rebuilt as Word documents with MyCase merge fields.Carried with mapping
IntakeLeads, enquiries, intake forms and pipelinesTo be confirmedHas a place in partLeads and intake forms exist; loading open leads in bulk is confirmed in the analysis.Confirmed in the analysis

What the plans mean

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

Loading a firm into MyCase means turning matters into cases and deciding what each case is called, numbered and filed under. The users, practice areas and custom fields have to exist first, because the records point at them. Money needs the most thought: an opening balance can be brought in simply, but how much invoice and trust history is rebuilt behind it is agreed in the analysis.

  1. Every case name is unique

    MyCase will not accept two cases with the same name. A firm with forty matters called Estate Planning, or two files for the same pair of litigants, needs a naming pattern before the trial load. Client surname plus the old matter number is one option, and it keeps the old number in view.

  2. Old numbers fit as they are

    The case number field takes letters, digits and punctuation, so a number such as 2019-0457/LIT can be kept without reformatting. It is worth keeping it tidy: the email tools match incoming mail to a case by finding the case number in the subject line.

  3. Open or closed, nothing between

    A case in MyCase is either open or closed, with a closed date. Source systems often have more states than that: pending, on hold, archived, awaiting payment. Each is mapped to open or closed during the analysis, and the original status can be kept in a custom field.

  4. Practice areas build themselves

    On import, MyCase creates a practice area for every distinct value it is given. Family, Family Law and Fam. Law would become three. The source list is reduced to one agreed set during clean-up, so the firm starts with a short list of practice areas it chose.

  5. Lead attorney must exist

    The lead attorney on a case has to be a user in the account. Departed fee earners who still own closed matters are a common snag. They are either mapped to a current user, or their name is recorded in a custom field on the case.

More about moving into MyCase

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 MyCase. 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 MyCase 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 MyCase 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 toMyCase

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

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

A loaded MyCase account is not yet a working one. The firm still has to decide how cases are classified, who can see what, how money is handled and what clients are shown in the portal. Document templates are rebuilt against MyCase’s own merge fields, since precedents written for another system’s field codes will not merge here. Staff are trained on their own cases once the trial load has been checked.

Set-up decisions in MyCase

  • Practice areas and custom fields for cases and contacts
  • Trust and operating bank accounts with opening balances per case
  • Word document templates rebuilt with MyCase merge fields
  • Intake forms and lead pipeline for each practice area
  • User roles and who can open which cases
  • QuickBooks sync or the MyCase Accounting add-on

Questions

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

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

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 MyCase is kept as a readable archive, and you see which before the move.

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

Emails, billing records, the firm’s accounts, 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 MyCase are the names and marks of their owners, used here only to identify the two systems.

Moving from DLex to MyCase?

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

We reply within one business day.