Transfer data between Power Platform environments
A Power Platform solution moves the schema (tables, columns, forms, apps, flows) but never the rows, so reference and configuration data must be migrated separately. Immediate fix: use the Configuration Migration Tool — define a schema of the tables/columns to export, export to a zip, then import into the target environment. For larger or recurring transfers, use Dataflows with alternate keys defined on the tables so rows upsert instead of duplicating on each run. The pac CLI, Excel import, or XrmToolBox also work for one-off or automated transfers. Never migrate transactional or user data between environments — only configuration/reference data — and keep alternate keys consistent so re-running a transfer stays idempotent.
Schema vs data
A solution carries the structure (tables, columns, forms, apps, flows) but not the records. Reference and configuration data (lookups, settings, seed rows) must be migrated separately.
Do NOT migrate transactional or user data (real records created by users) between environments — only configuration/reference data.
Configuration Migration Tool (CMT)
- 1Use the Configuration Migration Tool to define a schema of the tables/columns to export, export the data to a zip, then import into the target environment.
- 2It is the go-to for moving curated reference data dev → test → prod in a repeatable way.
Dataflows (with alternate keys)
- 1For larger or recurring transfers, use Dataflows to read from the source and upsert into the target.
- 2Define alternate keys on your tables so rows upsert (match-and-update) instead of duplicating on each run.
Other options
The pac CLI can export/import solutions and data for automation. For one-off or small sets, Excel import or a manual export works. XrmToolBox offers helpers for bulk operations.
Whatever the tool, keep alternate keys consistent so re-running a transfer is idempotent and never creates duplicates.