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

Data migration route

Microsoft Dynamics 365 to LexWorkplace migration

Microsoft Dynamics 365 is a cloud CRM and intake system, and LexWorkplace is a cloud document management system. Only files and their details have a place there, so this route carries the documents and archives the rest.

FromMicrosoft Dynamics 365Cloud
  1. Documents: Carried across
  2. Emails: Carried across
  3. Notes: Carried across
  4. Custom fields: Carried with mapping
  5. Templates: Carried with mapping
  6. Tasks: Confirmed in the analysis
ToLexWorkplaceCloud
  1. Contacts: Kept as a readable archive
  2. Calendar: Kept as a readable archive
  3. Intake: Kept as a readable archive
Readable archiveNo place in LexWorkplace
  • 3 carried
  • 2 mapped
  • 1 to confirm
  • 3 archived
What the two products hold. The analysis confirms it field by field.

What moves

What moves from Microsoft Dynamics 365 to LexWorkplace

Each row is a kind of record Microsoft Dynamics 365 holds, whether LexWorkplace has a place for it, and what is planned. On this route three kinds of record carry across, two kinds need mapping, three kinds have no place in LexWorkplace and are archived and one kind is confirmed in the analysis.

Records in Microsoft Dynamics 365 and their place in LexWorkplace
RecordIn Microsoft Dynamics 365In LexWorkplaceWhat is planned
ContactsClients, other parties and referrersHeldAccounts and contacts, with leads held separately.No placeOnly a client name, status, attorneys and tags.Kept as a readable archive
DocumentsFiles stored in or linked from the systemHeld in partNote attachments sit in Dataverse file storage; documents are often kept in SharePoint.Has a placeFiled to a matter or to Firm Documents, in folders.Carried across
EmailsEmails saved to matters or to the storeHeld in partEmails tracked against a record are stored as activities.Has a placeOn the matter’s Email tab, in their own folders.Carried across
NotesFile notes, matter notes and contact notesHeldNotes on a record’s timeline, with optional attachments.Has a placeAs Matter Notes on the matter’s Notes tab.Carried across
CalendarAppointments, court dates and deadlinesHeld in partAppointments are activities on a record’s timeline.No placeKept as a readable archive
TasksTo-dos and workflow steps assigned to peopleHeldTasks are a type of activity.To be confirmedConfirmed in the analysis
Custom fieldsFields and record types the firm added itselfHeldCustom columns and custom tables are part of most implementations.Has a place in partOld categories can become document types, statuses or tags.Carried with mapping
TemplatesPrecedents, document templates and automationHeld in partEmail and Word templates.Has a place in partStored as files in Firm Documents.Carried with mapping
IntakeLeads, enquiries, intake forms and pipelinesHeldLeads, opportunities, marketing lists and campaigns.No placeKept as a readable archive

What the plans mean

Carried across
LexWorkplace has a place for this kind of record. It is loaded there and checked against Microsoft Dynamics 365.
Carried with mapping
LexWorkplace 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
LexWorkplace has no place for it. It is exported in a format that opens without Microsoft Dynamics 365 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

Only the documents have a place here.

LexWorkplace is a document management system: it takes files and the details that describe them. Most of what Microsoft Dynamics 365 holds is not files. Entries, balances, settings and lists have no place in a document store, and the table above is short for that reason. What can move is any document Microsoft Dynamics 365 produced or stored: invoices as PDFs, signed agreements, attachments, exported reports. Each is filed under the client or matter it relates to.

The useful version of this job is often an archive. A firm retiring a system wants its records readable later without keeping the subscription or the old PC. The data is exported in open formats, spreadsheets and PDFs, and filed in LexWorkplace in a workspace set aside for it, with access limited to the people who need it. That gives the firm one place to look, under the same retention rules as the rest of its documents.

Both are hosted by their makers, so nothing is collected from the firm’s office. What can be taken out of Microsoft Dynamics 365 depends on its export tools and on what its maker provides on request, and that is confirmed during the analysis, before a date is set. The subscription to Microsoft Dynamics 365 is kept running until the checks on LexWorkplace are finished.

Where the data is now

No two Dynamics systems are alike. The product is a platform, and what a firm has is whatever its implementer built: renamed tables, added columns, custom tables, workflows. A move begins by reading that design from the system itself. The data then comes out of Dataverse table by table, with the notes, activities and SharePoint documents collected alongside.

  1. Start from the customisations

    Accounts may have been renamed Clients, opportunities turned into Pitches, and a custom Matter table added beside them. None of that is in Microsoft’s documentation. The list of tables, columns and relationships is exported from the firm’s own environment first, and the field mapping is written against what is there.

  2. Excel export is for views

    The built-in Export to Excel takes the rows and columns of one view, and Microsoft notes that an export can time out depending on the number of rows, columns and lookups. It suits a spot check. A full extraction needs each table with its record identifiers, so the links between records survive.

  3. Notes, attachments and timeline

    What users see as one timeline is several tables underneath: notes, emails, phone calls, appointments, tasks. Files attached to notes and emails are held in Dataverse file storage, apart from the database rows. Each activity type is extracted with its link to the account, contact or custom record it belongs to.

  4. Documents may be in SharePoint

    Where document management is switched on, the documents shown on a record are files in a SharePoint folder and are not in Dynamics at all. They are moved as a SharePoint migration, using the links between folders and records to work out which client or matter each folder belongs to.

  5. Online or on-premises

    The online apps and the on-premises edition share most features but are reached differently. An on-premises system keeps its data in SQL Server databases on servers the firm controls. Which edition and version the firm runs is the first fact established, because it decides how the data is read.

More about moving off Microsoft Dynamics 365

Where it is going

LexWorkplace expects every document and email to belong to a matter, so loading it starts with the matter list: name, custom ID, client, type and dates. Uptime Legal states that it runs migration and onboarding for its customers itself. The preparation is getting the old system’s content into a clean client and matter structure, with the exceptions resolved, ready for that load.

  1. Matters carry little, by design

    A matter record holds a name, a custom ID, a client, a type, a location, assigned staff, tags and open and close dates. Parties, court details and financial data have no fields. Those stay in the practice management system, and the two are tied together by using the same matter number as the custom ID.

  2. Clients are only containers

    LexWorkplace says plainly that its clients are for grouping matters, not for client management. A client has a name, a status, primary attorneys and tags. Addresses, phone numbers and contact history from the old system are not loaded here. They go to the practice management system or stay behind.

  3. Three tabs per matter

    Content arrives as documents, emails or notes, each on its own tab with its own folders. Emails held as message files in an old folder tree have to be recognised and loaded as emails, not as documents, or they will not appear where lawyers look for correspondence.

  4. Closed matters and archive

    A matter is closed by giving it a close date, and closed matters can be moved to archive storage, where they keep their place but are not searched or indexed until un-archived. Old matters can therefore be loaded and archived straight away. The firm sets the cut-off year.

  5. Profiling is optional unless enforced

    Document type, status and tags are not required by default, though a firm can switch on mandatory profiling for matters. If the old system had document types, they are mapped to LexWorkplace types during the load. If it had none, the firm chooses between loading unprofiled and assigning types by folder name.

More about moving into LexWorkplace

How NewLaw runs it

Four steps, in this order.

Nothing financial lands in LexWorkplace on this route, which makes it repeatable: a load can be run again until it is right. The maker of LexWorkplace 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 Microsoft Dynamics 365 and checking each trial against Microsoft Dynamics 365.

  1. Analysis

    We read what Microsoft Dynamics 365 holds and how it is organised, then agree with you where each kind of record will sit in LexWorkplace. Anything with no place there stays behind or is archived, and you see which before the move.

  2. Clean-up

    Duplicate clients, matters and folders are merged where they can be identified, and naming is put into one format, before anything is copied. It is not always possible to find every one, so some may carry across.

  3. Trial load

    A trial is loaded into LexWorkplace and checked against Microsoft Dynamics 365: record and file counts, the links between records, document dates, and a sample opened by your own people. Exceptions are listed for you to decide.

  4. Cutover

    There is no financial cutover on this route. After a short freeze on changes in Microsoft Dynamics 365, a final pass over a weekend picks up what changed since the trial. Microsoft Dynamics 365 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 Microsoft Dynamics 365 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 fromMicrosoft Dynamics 365
Moving toLexWorkplace

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 Microsoft Dynamics 365 holds

    What is in it, how its records link, and where each piece would sit in LexWorkplace. 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 LexWorkplace

Loaded data is not yet a working system. The maker of LexWorkplace runs or arranges the set-up of its product, so this is what has to be decided and put in place in LexWorkplace, whoever does the work, before people rely on it from the first day.

Setting LexWorkplace up for a firm is a short list of decisions made in its settings, plus software on each computer. The decisions are what the firm calls its matter types, document types and statuses, who can open which matters by default, and whether versioning is automatic or manual. The Launcher and the Outlook add-in are then installed for every user.

Set-up decisions in LexWorkplace

  • Matter types, document types, statuses and tag conventions
  • Groups, rights and default permissions for new matters
  • Automatic or manual versioning, and whether profiling is mandatory
  • Linking matters to Clio Manage where the firm uses it
  • Launcher, Office and Outlook add-ins on each Windows or Mac computer
  • A Firm Documents structure for templates, policies and internal files

Questions

Microsoft Dynamics 365 to LexWorkplace: what firms ask

Our Dynamics was heavily customised. Does that make a move harder?

It makes the analysis longer. Custom tables and columns are read from the system and listed with how many records use each one. The firm then says which still matter. Fields with a home in the destination are mapped, and the rest come across as notes or stay in the read-only copy of the old system.

Can a practice management system replace what we do in Dynamics?

For client and matter records, yes. Pipeline tracking, marketing lists and relationship mapping depend on whether the destination has a CRM or intake module. Where it does not, firms either keep a smaller CRM beside it or accept simpler tracking. The analysis lists each function and where it would sit.

Do documents from Microsoft Dynamics 365 keep their folders and dates in LexWorkplace?

LexWorkplace stores documents. Filed to a matter or to Firm Documents, in folders. Each file is placed under the client and matter it came from, and created and modified dates are carried, so a document still shows when it was written. The trial load is checked by count and by opening a sample.

What happens to records LexWorkplace has no place for?

On this route that is contacts, calendar entries and intake records. They are exported from Microsoft Dynamics 365 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 Microsoft Dynamics 365 data is loaded into LexWorkplace?

Custom fields and templates are carried with mapping, so each mapping is agreed with you first. Tasks are confirmed in the analysis. The firm also decides which closed matters and how many versions of a document are in scope.

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

Microsoft Dynamics 365 and LexWorkplace are the names and marks of their owners, used here only to identify the two systems.

Moving from Microsoft Dynamics 365 to LexWorkplace?

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

We reply within one business day.