If the policy, or any related object in the archive already exists in the target instance of CentraSite, the existing object will be overwritten according to the conditions described in the CentraSite Administrator’s Guide.

To import a policy successfully, you must belong to a role that includes the Manage Design/Change-Time Policies permission. If the archive contains a system-wide policy or custom action templates, you must also belong to a role that has the Manage System-Wide Design/Change-Time Policies permission.

When the imported policy is added to the registry, the import process assigns the Organization, Lifecycle State, and Activation State properties to the imported policy as follows.

When an imported policy replaces (updates) an existing policy in the target registry, all of the policy's properties, except for its permission settings, are updated according to the policy object in the archive. This includes the policy's organizational scope, its lifecycle state, and its activation state (that is, whether the policy is active or inactive). If the referenced organization and/or lifecycle model does not already exist on the target registry, the import process will fail. Also, be aware that the import process will replace the policy on the target regardless of whether the target policy is currently active or inactive. Due to this behavior, you might want to import only new versions of a policy, and not use the import process to directly replace a version of a policy that already exists.

If the archive file contains a reference to an object that is not already present in the target registry or is not included in the archive file itself, the policy will not be imported.

If design/change-time policies exist for the events that the import process initiates (for example, the creation of a policy), those policies will be triggered.