Skip to main content
Adoption connects configuration that already exists in both the source and target. It records matching links for future sync previews without changing configuration data.

​
When to Use Adoption

Use adoption when:
  • the target was imported before organization sync tracking was available
  • corresponding entities were created manually in both environments
  • a sync preview reports Needs adoption or an ambiguous match
Adoption is not needed for entities created by a current import or a tracked organization duplication, because those workflows record their links automatically.

​
Match Classes

An ambiguous source can only be paired with a target from the same entity type and identity group. The same target cannot be selected for more than one source.

​
Review and Apply Adoption

  1. Load the source export file for the target organization and select Preview sync.
  2. When adoption candidates are present, open Adopt existing entities.
  3. Select Review adoption matches.
  4. Keep the appropriate exact matches selected.
  5. Review each probable match and select it only when the two entities represent the same configuration item.
  6. For ambiguous groups, choose the correct target for each source or use Leave unresolved.
  7. Select Adopt selected.
After adoption, the sync preview refreshes automatically.

​
What Happens to Existing Differences

Adoption does not choose a winner or copy values. If you adopt a probable match whose source and target content differs, the next sync preview reports that difference as a Conflict. Resolve it there by taking the source or keeping the target. This is intentional: because the two entities were created or changed before Azalt had a shared comparison point, the system cannot safely attribute the existing difference to only one side.