SitecoreAI Connector
Migrating from XP/XM Connector to SitecoreAI Connector
Practical Migration Checklist

Practical Migration Checklist

Content Architect Checklist

  1. Audit XP/XM templates and DAM field usage.
  2. Map each field to a SitecoreAI Plugin target (mode + assetTypes).
  3. Choose pre-delivered base templates or custom Plugin fields.
  4. Configure __Standard Values for each migrated field.
  5. Validate authoring flows in Pages (single, multi, and filtered selection cases).

Developer Checklist

  1. Replace format-specific parsing with parseBynderField().
  2. Update renderers/components to support new field names and target modes.
  3. Define fallback behavior for dual-field (Sitecore + Bynder) models.
  4. Regression-test key templates and components with real content.
  5. Remove obsolete XP/XM-only parsing helpers once migration is complete.

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.

See Also

Template Modeling for Mixed Sitecore + Bynder ScenariosTroubleshooting