Environment migration
- Paul Pingaud (Deactivated)
- Miguel Correa Calvo
Configuration is done and tested in non-production environments, and when ready, it can be easily deployed into production or some other environment thanks to the migration tool.
The migration tool allows exporting configurations from one environment and importing them into another, making it possible to easily deploy your configuration.
Only configuration are migrated, as they are traversal to different environments. Master data is not migrated, as population is done by the data flows of each environment.
Entity migration table
| Migratable |
|---|---|
Configurations | Yes |
Stock | No. Needs to be populated through import flows |
Buffers | No. Needs to be populated through import flows |
Items | No. Needs to be populated through import flows |
Orders | No. Needs to be populated through import flows |
Stock locations | No. Needs to be populated through import flows |
Webhooks | No. Needs to be populated through import flows |
Users | No. Needs to be populated through import flows |
The process
Migrating between environments is easy.
Go the migration tool in the environment you want to export from
Select configurations you want to export
Download the export file
Go to the migration tool in the environment you want to import to
Drag and drop or browse the export file and trigger the import.
