Migrating from XP/XM Connector to SitecoreAI Connector
If you are currently using the 'Bynder DAM Connector for Sitecore XP/XM' on 'XM Cloud or SitecoreAI', use this guide to move from the XP/XM connector model to the SitecoreAI connector model with minimal disruption.
On XM Cloud/SitecoreAI, the current XP/XM connector is only supported in Content Editor (not in Pages).
It covers:
- Template and field-type migration
- Legacy value format migration (including XML-wrapped values)
- Component migration using the SitecoreAI SDK
- Template modeling decisions when you need both Sitecore media and Bynder media
When You Need This Guide
Use this page when you are moving from Sitecore XP/XM implementations that used Bynder DAM custom field types to SitecoreAI/XM Cloud implementations that use Plugin fields.
If you are currently using the XP/XM Connector on an XM Cloud setup, we strongly recommend migrating to the SitecoreAI Connector.
For setup fundamentals, see:
Common Pitfalls
- Treating old XP/XM field types as direct one-to-one UI controls in SitecoreAI.
- Forgetting to set mode/assetTypes on standard values for custom Plugin fields.
- Assuming all existing values are JSON objects (legacy XML-wrapped values may still exist).
- Using one field when business rules require both Sitecore-native and Bynder-managed asset selection.