D365 Data Migrator

D365 data migration tool that automates the entire ETL and package load

D365 Data Migrator is a PowerShell library for Dynamics 365 Finance and Operations that runs your whole data migration from one command. It extracts the source data, transforms it, prevalidates it against your mappings, builds the D365 data package, uploads it, starts the batch job and monitors that job until it finishes. The ETL process your team currently performs by hand becomes automated, repeatable and fast — and you receive the source code.

Book a demo See our AX 2012 deployment tool
  • 1–2 hoursinstall to first load
  • One commandruns the full pipeline
  • Exceltemplates and error reporting
  • 100%PowerShell source included

How it works

Six stages of a Dynamics 365 data migration, automated

Every stage below is something a migration team normally performs manually, often several times per entity across several dry runs.

  1. Extract the source data

    Records are pulled from your source system or files, so the same run can be repeated without anybody re-exporting spreadsheets by hand.

  2. Transform and map to D365 entities

    Your field mappings and transformation rules are applied in PowerShell, producing data shaped for the target Dynamics 365 data entity.

  3. Prevalidate and report issues in Excel

    Before anything is sent to Dynamics, the data is checked against the mappings. Problem records are written back into Excel with the issues highlighted, so they are corrected by the person who understands the data rather than diagnosed from an import log after a failure.

  4. Build the D365 data package

    The package file that the Data Management Framework expects is generated for you, including the Excel templates for each entity.

  5. Upload and start the import job

    The package is delivered to your Dynamics 365 environment and the import batch job is queued automatically.

  6. Monitor the batch job to completion

    Job status is polled until every job reaches a final state, so nobody sits refreshing the Data Management workspace late in the evening waiting to find out whether a load succeeded.

Why teams choose it

Built for the parts of a migration that actually hurt

Simple, fast and inexpensive

It replaces weeks of manual data preparation and failed load cycles at a fraction of the cost of enterprise data migration suites, with no per-record metering and no middleware tier to maintain.

You own and can modify the code

The PowerShell source is yours. Adapt it to your entities, your naming conventions and your release process, and keep using it indefinitely.

Data issues surface early

Prevalidation moves data quality problems to the start of the process, where they are cheap, instead of go-live weekend, where they are not.

Productive in an afternoon

There are no agents to deploy and no platform to stand up. Most teams complete a real migration run within one to two hours of installing it.

FAQ

Questions we get asked about D365 data migration

How long does a D365 data migration take with this tool?
Most teams are running their first real load within one to two hours of installing the library. The run itself depends on your volumes and your D365 environment, since the import is executed by Dynamics 365 as a batch job. The tool removes the manual work around that job rather than changing how fast Dynamics processes records.
How is this different from the Data Management Framework already in D365?
The Data Management Framework is what actually performs the import. It expects you to prepare the file, build the package, upload it, start the job and then watch it. D365 Data Migrator automates that whole sequence from PowerShell, adds prevalidation before anything reaches Dynamics, and polls the batch job until it reports a final status.
What happens when the source data has problems?
Prevalidation runs before the package is built. Records that would fail are written back into Excel with the problem highlighted, so a functional consultant can correct them in a familiar tool instead of reading through an import error log after a failed run.
Do we get the source code, and can we change it?
Yes. The product ships as PowerShell source. You can read it, modify it, extend it and fold it into your own release process. Nothing is obfuscated or licence-locked at runtime.
Which versions of Dynamics 365 does it support?
It targets Dynamics 365 Finance and Operations environments that expose the standard data management endpoints. Tell us your environment and version when you book a demo and we will confirm compatibility before you commit to anything.
Does it work for repeated loads, or only the initial migration?
Both. Because a run is a single PowerShell command, the same configuration can be scheduled or re-run for ongoing interfaces and top-up loads, not just the one-off go-live migration.

See it run against a realistic data set

Thirty minutes, screen shared. Bring your entity list and we will talk through how the load would work in your environment.

Book a demo