Importing configuration items to the target environment

You can load the migration file into the target environment by downloading the file from the OpenPages® repository or by importing a saved file from your local client.
The import process automatically validates the configuration items before performing the import to ensure that the items are complete and any object dependencies are in the migration file or in the target environment before the items are imported. The validation process verifies that:
  • The XML file is a well-formed ObjectManager loader file.
  • The metadata attributes are valid, according to the OpenPages validation rules.
  • All dependent items that a particular item requires are present in either in the migration file or in the target system.
  • Special characters are validated if the Special Character Validation setting is true (see Settings that apply to environment migration).

You can also run the validation process separately from the import. See Validating a migration file.

To avoid validation errors, review the information on dependent items that must be manually created and/or moved to the target environment. For details, see Items that are not migrated. For example, if you select a filter for import, ensure that all objects, field groups, and fields that are used by the filter are either included in the migration file or already in the target system.

You must have the ImportConfiguration application permission. You must also have read and write access to the Migration Documents folder. For information, see Types of application permissions and Managing system files and folders.

Important: The environment migration import process might periodically enable System Admin Mode (SAM), preventing users from making and saving changes (see Enabling and disabling System Admin Mode). To avoid errors in the imported data and other issues, migrate data during off-hours or when the target environment is not being used.