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

Data migration route

Microsoft Dynamics 365 to Box migration

Microsoft Dynamics 365 is a cloud CRM and intake system, and Box is cloud file storage. What moves is the files, plus a readable export of everything else the old system holds.

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

What moves

What moves from Microsoft Dynamics 365 to Box

Each row is a kind of record Microsoft Dynamics 365 holds, whether Box has a place for it, and what is planned. On this route one kind of record carries across, four kinds need mapping and four kinds have no place in Box and are archived.

Records in Microsoft Dynamics 365 and their place in Box
RecordIn Microsoft Dynamics 365In BoxWhat is planned
ContactsClients, other parties and referrersHeldAccounts and contacts, with leads held separately.No placeKept 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 placeFiles and folders, named and dated as they are loaded.Carried across
EmailsEmails saved to matters or to the storeHeld in partEmails tracked against a record are stored as activities.Has a place in partAs .msg or .eml files in the matter folder.Carried with mapping
NotesFile notes, matter notes and contact notesHeldNotes on a record’s timeline, with optional attachments.Has a place in partAs documents in the matter folder, not as a notes record.Carried with mapping
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.No placeKept as a readable archive
Custom fieldsFields and record types the firm added itselfHeldCustom columns and custom tables are part of most implementations.Has a place in partMetadata templates can hold fields such as matter number and client.Carried with mapping
TemplatesPrecedents, document templates and automationHeld in partEmail and Word templates.Has a place in partPrecedents load as ordinary files; no document automation.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
Box has a place for this kind of record. It is loaded there and checked against Microsoft Dynamics 365.
Carried with mapping
Box holds this differently, or in part. Each field or value is matched to its place before loading, and you see the mapping first.
Kept as a readable archive
Box 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

An export the firm can open without the system.

Box holds files, and most of what Microsoft Dynamics 365 holds is records. This route is therefore an export job. Each kind of record is written out in a format that opens without the system it came from: lists as spreadsheets, statements and invoices as PDFs, attachments as the files they were. The export is laid out in folders that make sense to someone who never used Microsoft Dynamics 365, by client or by year, with a short index file saying what is where.

Firms do this when a subscription is ending, when a system is being retired, or to meet a retention rule. The test of the result is whether a question can still be answered from it years later: what was this client invoiced, who signed this agreement and when. So the trial export is checked by asking those questions of it. Totals are agreed to the system’s own reports, and access to the folder in Box is limited before the export is copied in.

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 Box 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

Loading a firm’s files into Box means deciding the folder tree and its owners first, because permissions follow the tree. Box has no matter record. A matter is a folder, and anything else the firm knew about it, such as the matter number, client or status, survives only in the folder name or in metadata fields set up before the load.

  1. Decide who owns the top level

    Box’s own planning guidance sets out two models: users create their own top-level folders, or administrators own them all and invite people in. For matter files most later decisions depend on this one, including who can share outside the firm and whose storage allowance the files count against.

  2. Restricted matters go near the top

    Access in Box only flows downward. A person who can open a client folder can open every matter under it, and a subfolder cannot be hidden from them. Matters behind an information barrier therefore need their own top-level folders, and the list of those matters is agreed before the structure is built.

  3. Names Box will not accept

    Box rejects a slash or backslash anywhere in a file or folder name, and spaces at the start or end. Files from older systems and from Macs often have both. They are renamed by rule before loading and the firm receives the list, so that a document cited by its old name can still be found.

  4. Matter details become metadata

    A metadata template can hold the matter number, client name, practice area and closed date against each matter folder. The template has to exist before the files arrive so the values can be written during the load. Without it, the folder name is the only place that information lives.

  5. File size follows the owner’s plan

    The largest file Box accepts depends on the plan of whoever owns the folder. Litigation matters with video or forensic images are where this bites. Oversized files are found in the analysis, and the firm chooses between a higher plan and keeping those files somewhere else.

More about moving into Box

How NewLaw runs it

Four steps, in this order.

Nothing financial lands in Box on this route, which makes it repeatable: a load can be run again until it is right.

  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 Box. 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 Box 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 toBox

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

Structure, permissions and handover

Box is storage, not an application, so there is no product to configure. What is agreed and set up is the folder structure, who can open what, and how the result is handed to the firm.

Most of a Box set-up is governance. The folder tree, the groups that are invited into it and the rules on sharing outside the firm are decided and built before any file is loaded. After the load, staff need Box Drive on their PCs and a short written guide to where a new matter folder is created and who creates it.

What is agreed and set up

  • Top-level folder structure and who owns each folder
  • Groups for teams, mapped to collaborator roles
  • Metadata template for matter number, client and status
  • Shared link defaults and rules for external collaborators
  • Box Drive installed and signed in on each PC
  • Version limits and retention agreed with the firm’s records policy

Questions

Microsoft Dynamics 365 to Box: 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 Box?

Box stores documents. Files and folders, named and dated as they are loaded. 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 Box has no place for?

On this route that is contacts, calendar entries, tasks 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 Box?

Emails, notes, custom fields and templates are carried with mapping, so each mapping is agreed with you first. 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 Box are the names and marks of their owners, used here only to identify the two systems.

Moving from Microsoft Dynamics 365 to Box?

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

We reply within one business day.