Skip to main content
Level 2
September 29, 2026
Question

Decisioning Migration API

  • September 29, 2026
  • 1 reply
  • 13 views

Have you used that API?
My Prod and Dev are not 1:1 so I am expecting problem. I assume as a first step do the POC: 

Prod Offer Decisioning → Dev Decisioning for one specific Decision Scope
Do you recommend creating all the profile attributes, audiences etc on Dev and then map prod → dev?

Any advices? 

1 reply

AmitVishwakarma
Community Advisor
Community Advisor
September 29, 2026

Hi ​@Dex 666 
The first thing I'd clarify is what you mean by "Offer Decisioning." If Prod is using legacy Decision Management/Offer Library and Dev is using the newer Decisioning capability, the Decisioning Migration API is designed for that legacy-to-new migration. It is not a general-purpose copy tool for moving already-native Decisioning objects from Prod to Dev https://experienceleague.adobe.com/en/docs/journey-optimizer/using/decisioning/experience-decisioning/migrate-to-decisioning/decisioning-migration-api

For a POC, I'd run dependency analysis first, then prepare the specific target-sandbox dependencies it identifies. The API's cross-sandbox prerequisites include profile attributes that exist in Dev or have mappings, target segments that already exist and are mapped from source IDs to target namespace/IDs, identity mapping, and a target Experience Event dataset attached to an Edge-enabled datastream. The API does not create or edit the profile attributes or segments for you. So I would not bulk-create every Prod attribute or audience in Dev first—create or map only the dependencies required for the pilot.https://experienceleague.adobe.com/en/docs/journey-optimizer/using/decisioning/experience-decisioning/migrate-to-decisioning/decisioning-migration-api

One scope caveat: the API documents decision-level migration using a list of decision IDs; it does not document a separate decisionScope selector. A legacy Decision Management decision scope maps to a Selection Strategy, Decision Policy, and Campaign. If the source decision contains multiple scopes, I would verify the migration behavior for that case rather than assume one scope can be migrated independently.

If both Prod and Dev already use native Decisioning, use Sandbox Tooling/package export-import instead. Its guidance says the destination needs the relevant profile attributes, custom Offer Attributes field group, and context schemas; decision items must be added to the package manually and copied before related objects https://experienceleague.adobe.com/en/docs/journey-optimizer/using/connect-systems/sandbox/copy-objects-to-sandbox

 

Amit Vishwakarma - Adobe Commerce Champion 2025 | 17x Adobe certified | 6x Adobe SME