Setup Data Export and Import Using an Offering or a Functional Area

You may choose to export and import setup data of an entire offering, or limit the processes to one of its functional areas.

This method is a simplified export and import process, which doesn't require understanding complexities of data dependencies and setup tasks.

By Offering

You typically export and import an entire offering when you migrate setup data of the offering to the target environment for the first time. Setup data related to all enabled functional areas and features of the offering is exported and imported.

By Functional Area

When setup data specific to a functional area changes over time, you might decide to export and import only the affected functional area. This helps to limit export and import of setup data to a smaller range and therefore, migration processes take less time to complete than that of the entire offering.

If you select a specific functional area to export, only the setup data related to that functional area and its enabled features is exported and imported.

Note: You must ensure that all prerequisite setup data needed by the setup data of the exported functional area is available in the target environment before you start import. Otherwise, the import process might fail.

Same Levels of Export and Import

You must start the import process from the same offering or the functional area that was used to create the configuration package file you want to import. Otherwise, you receive an error message until you upload the correct configuration package file. All setup data in the configuration package file is imported irrespective of whether or not the corresponding functional areas or features are enabled in the target environment.

Setup Data Comparison

You can compare setup data of an offering or functional area in an exported configuration package file with that of the same offering or functional area in an environment. Setup data comparison is integrated with the import process as an option to compare and analyze which setup data is imported. Alternatively, you can also use setup data comparison independent of an import process. For example, to compare how the setup data of an environment has changed over a certain period, you can start the comparison outside of an import process.