Move data between environments
Data Migration copies records from one Dataverse or Dynamics 365 environment to another, for example from development to test, or from a configured sandbox into production. It is built for the reference and configuration data developers move all the time.
Choose a source and a target, then pick a table. Only columns that can be written are offered, and the primary key is always kept so records keep the same ID in both environments.
Control what moves
Narrow the source records with a FetchXML filter, then open Preview to see what will be sent before anything is written to the target.
Choose how records are written:
- Create adds records that do not exist in the target.
- Update overwrites records that already exist in the target with the same ID.
- Both creates or updates each record, an upsert.
Each migration runs as a job, and its status stays visible while you set up the next one.
When to use it
- Seeding a new environment with reference data.
- Keeping configuration tables in step across dev, test, and production.
- Copying a filtered set of records to reproduce a bug.
Data moves directly between your machine and your environments. Nothing passes through a third-party service.