SitecoreAI Connector
Migrating from XP/XM Connector to SitecoreAI Connector
Field Type Mapping (XP/XM -> SitecoreAI)

Field Type Mapping (XP/XM -> SitecoreAI)

Use this as your primary template migration reference.

Core Model Change

In XP/XM, teams commonly used multiple DAM-specific field types such as:

  • General Link [DAM]
  • Image [DAM, Single asset]
  • Image [DAM, Multi asset]
  • Image [DAM, Single file]
  • Video [DAM]
  • File [DAM]

In SitecoreAI, migration targets one connector field type:

  • Field type: Plugin
  • Source value: pub-acdcf8ff-54f9-4269-977a-c4be5b8fde10
  • Source meaning: Bynder DAM Connector for SitecoreAI public Marketplace App ID
  • Configuration location: Field value (typically on __Standard Values)
  • Configuration parameters: optional mode (defaults to SingleSelectFile), optional assetTypes, optional defaultSearchTerm, optional hideLimitedUse, and future parameters
  • Full parameter reference: Plugin Field Options

Mapping Table

XP/XM field typeSitecoreAI field typeModeAsset types
General Link [DAM]Plugin (bd_BynderBaseSingleSelect)SingleSelectall or ['document']
Image [DAM, Single asset]Plugin (bd_BynderBaseImage)SingleSelect['image']
Image [DAM, Multi asset]Plugin (bd_BynderBaseMultiSelect)MultiSelectall or ['image']
Image [DAM, Single file]Plugin (bd_BynderBaseSingleFile)SingleSelectFileall
Video [DAM]Plugin (bd_BynderBaseVideo)SingleSelect['video']
File [DAM]Plugin (bd_BynderBaseSingleFile / bd_BynderBaseSingleSelect)SingleSelectFile or SingleSelectall or ['document']

Notes:

  • Prefer pre-delivered base templates for faster migrations.
  • Use custom Plugin fields when exact legacy field naming must be preserved.
  • Set assetTypes explicitly when strict media filtering is required.

See Also