Object dependencies for data migration

To migrate data, we must ensure that you include all the dependencies of the migrated object.

A dependency is generally an individual object referenced by a parent or root object that is required on a target system to successfully import the parent. To protect the integrity of the data throughout the migration process, the import and export tasks automatically detect and include exported object dependencies.


Full exports compared to partial exports

Export everything through the use of Export All saves all of the data that is supported by Export All in the system. If you export individual items with a partial export, we might not actually export all of the dependencies needed for the object to function. A partial export saves only those dependencies that are needed to create the object that is saved. For example, we might export a provisioning policy that includes an automatic account creation function. The identity policy needed to create the user ID is not exported as a dependency of the provisioning policy. The identity policy is not required for the creation of the provisioning policy object. However, it might be required for the purpose that you intend for your provisioning policy. If that is the case, export and import the dependency as a separate object.


Policies

Identity policies and password policies are not exported when a provisioning policy is exported. We must explicitly export these policies as part of the export process.

An identity, password, or provisioning policy role and service objects are not exported by default. To export these items, you must manually add them to the export list.


Services

If a service is exported, the service owner information is also exported. The dn is appropriately set if a person exists with the same name on the target system.


Role relationships

If a role that has a senior or junior role relationship is exported, then the relationship is also exported. The related role itself is not exported as a dependency.

If the dependent role exists on the target system, then the role relationship is created. Otherwise, it is not created. Role relationships are never deleted during import.


Export multiple objects

Export multiple objects over a period of time might result in saving variations of mutually shared dependencies that change over the course of the daily activity of the system. Keep the possibility of variations in mind as you plan your export strategy.


Dependencies and parent objects

Removal of a parent object is allowed. However, when a parent object is removed, the import and export tasks automatically remove all of its dependencies from the export list.

Parent object Dependencies
  • Identity policy
  • Lifecycle rule
  • Lifecycle operation
Object profile
  • Identity policy
  • Lifecycle rule
  • Lifecycle operation
  • Password policy
  • Provisioning policy
  • Service
  • Service selection policy
  • Workflow
Service profile
Organizational role
Service
  • Lifecycle rule
Lifecycle operation

Parent topic: Data import and export