Configuration scenarios: loadconfiguration vs. saveconfiguration

The following scenarios show how configurations are moved between Business Central (BC), the local DataMigratePro installation and ZIP archives. All examples assume that the basic settings (tenant, endpoint, databases) have already been stored.

1. Configuration from BC to local (-t loadconfiguration)

  • Command: DataMigratePro -t loadconfiguration
  • Result: Loads configuration data from BC into the local environment. Included are migration, mapping, optional BC table/field as well as value mapping and value mapping value; the data is transferred in blocks via pagination.
  • Typical use: synchronize the starting point before changes are made locally.

2. Write the local configuration back to BC (-t saveconfiguration)

  • Command: DataMigratePro -t saveconfiguration
  • Result: Sends the locally maintained configuration tables to BC. Before the upload, the target tables in BC are emptied and then refilled chunk by chunk.
  • Important: the tables BC Field and BC Table are not written back in the process.

3. Export configuration from BC as ZIP (-t loadconfiguration -o ./path/to/zipfile.zip)

  • Command: DataMigratePro -t loadconfiguration -o ./ausgabe/configuration.zip
  • Result: saves the configuration loaded from BC as a ZIP archive with the individual JSON files instead of writing it directly into the local database.

4. Read the configuration locally from a ZIP (-t loadconfiguration -i ./path/to/zipfile.zip)

  • Command: DataMigratePro -t loadconfiguration -i ./pfad/zur/configuration.zip
  • Result: Imports a previously exported configuration ZIP locally without contacting BC (e.g. for offline reviews or tests).

5. Back up the local configuration as a ZIP (-t saveconfiguration -o ./path/to/zipfile.zip)

  • Command: DataMigratePro -t saveconfiguration -o ./ausgabe/configuration.zip
  • Result: creates a ZIP archive from the current local configuration that can later be uploaded to BC or versioned.

6. Load BC configuration from ZIP (-t saveconfiguration -i ./path/to/zipfile.zip)

  • Command: DataMigratePro -t saveconfiguration -i ./pfad/zur/configuration.zip
  • Result: uses a ZIP file as the source and sends its content to BC. Suitable for distributing tested configurations as packages.
Thomas Marquardt
About the author

Thomas Marquardt

Leads migration projects and is the lead developer of DataMigrate Pro. Over 20 years of Microsoft ERP.