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

Data migration route

DLex to SurePoint Finance Enterprise migration

DLex is a server-based practice management system, and SurePoint Finance Enterprise 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. Calendar: Carried across
  4. Time and expenses: Carried across
  5. Billing: Carried across
  6. Firm accounts: Carried across
  7. Documents: Confirmed in the analysis
  8. Emails: Confirmed in the analysis
  9. Notes: 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
ToSurePoint Finance EnterpriseCloud
  • 6 carried
  • 8 to confirm
What the two products hold. The analysis confirms it field by field.

What moves

What moves from DLex to SurePoint Finance Enterprise

Each row is a kind of record DLex holds, whether SurePoint Finance Enterprise has a place for it, and what is planned. On this route six kinds of record carry across and eight kinds are confirmed in the analysis.

Records in DLex and their place in SurePoint Finance Enterprise
RecordIn DLexIn SurePoint Finance EnterpriseWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldCalled dossiers.Has a placeCarried across
ContactsClients, other parties and referrersHeldClients, opposing parties and other persons, with identity and bank details.Has a placeCarried across
DocumentsFiles stored in or linked from the systemHeldFiles and templates sit in a server directory, beside the SQL database.To be confirmedConfirmed 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.Has a placeCalendar entries and dockets.Carried across
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 and payables, by entity.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
SurePoint Finance Enterprise 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 whole practice moves, accounts included.

A move between two practice management systems is the widest kind there is. DLex and SurePoint Finance Enterprise 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. SurePoint Finance Enterprise 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

Moving into SurePoint Finance Enterprise, the system long sold as LMS, is an accounting implementation with a data load inside it. The entity structure, chart of accounts and billing rules are designed before records arrive, because every time entry and payment posts into them. Smaller systems rarely hold data at that level of detail, so part of the preparation is adding what the source never recorded.

  1. Entities and tax IDs first

    The system can hold several legal entities and tax IDs. A firm coming from a single QuickBooks file, or from two files for two offices, decides how it wants to be structured from here on. That decision fixes where each bank account and matter belongs, and it is hard to revisit once history is posted.

  2. History has to balance

    Billing, trust and the general ledger are parts of one system, so loaded history must agree across all three. A receivable carried in for a matter needs the invoice behind it and the ledger entry behind that. Source systems that kept billing and accounts apart are reconciled to each other before extraction.

  3. E-billing detail on time entries

    For LEDES e-billing, time entries need task and activity codes and timekeepers need the classifications clients expect. A small-firm system may never have captured them. The firm decides whether historic entries are loaded uncoded as history only, with coding starting on new work from go-live.

  4. Dockets as well as appointments

    Calendars and dockets are both kept. In many source systems a court deadline and a client lunch are the same kind of record. The two are separated on the way in, using event types or keywords, and the docket entries for open matters are checked by the lawyers responsible.

  5. Cost recovery codes

    Disbursements such as copying and postage arrive through cost recovery and post to the matter. The cost types and their rates are set up to match how the firm charges today. Unbilled disbursements from the old system are then loaded against those types so they can be billed normally.

More about moving into SurePoint Finance Enterprise

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 SurePoint Finance Enterprise. 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 SurePoint Finance Enterprise 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 SurePoint Finance Enterprise 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 toSurePoint Finance Enterprise

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 SurePoint Finance Enterprise. 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 SurePoint Finance Enterprise

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

The set-up decisions in Finance Enterprise are mostly made by the finance team. They cover the firm’s entity structure, its chart of accounts, how bills are approved and sent, and what each client’s e-billing portal demands. Timekeepers need rates and classifications. The reports used for partner compensation are specified early, because they test whether the structure underneath is right.

Set-up decisions in SurePoint Finance Enterprise

  • Entity structure, tax IDs and the chart of accounts
  • Bank and trust accounts with reconciliation set-up
  • Timekeeper rates, classifications and task code sets
  • Pre-bill approval steps and client billing rules
  • LEDES e-billing formats for each corporate client
  • Management and compensation reports the partners use

Questions

DLex to SurePoint Finance Enterprise: 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 SurePoint Finance Enterprise?

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 SurePoint Finance Enterprise 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 SurePoint Finance Enterprise?

Most of it does on paper. Documents, emails, notes, 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 SurePoint Finance Enterprise is kept as a readable archive, and you see which before the move.

What has to be decided before DLex data is loaded into SurePoint Finance Enterprise?

Documents, emails, notes, 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 SurePoint Finance Enterprise are the names and marks of their owners, used here only to identify the two systems.

Moving from DLex to SurePoint Finance Enterprise?

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

We reply within one business day.