Bynder to AEM DAM : Feasibility, Best Practices & Challenges

​@sherinregi-1 ​@Sachin_Arora_ ​@Sudheer_Sundalam ​@diksha_mishra ​@RajaShankar ​@Ankur_Khare ​@ArpitVarshney ​@AsifChowdhury ​@Sanjay_Bangar Pulling you into this discussion to get your take, especially if there are best practices we should be thinking about. Thanks in advance for any input you can share.

Hi ​@avesh_narang 

I have found below thread from Achim Koch -

 covering this to be very comprehensive. 

Also this article covers some of the learnings involved in a large scale migration - https://medium.com/@bsaravanaprakash/how-we-migrated-a-million-assets-into-aem-cloud-service-dam-ef7eb74d30fa

Thanks
Narendra

Hi ​@avesh_narang 

Recommended approach

1. Extract from Bynder
   • Use Bynder API/export to pull:
     • Original binaries (images, videos, docs).
     • Metadata (JSON/CSV) for each asset.
   • Store in S3/Azure or a local file share.
2. Ingest into AEM
   • AEMaaCS: use Bulk Import from S3/Azure.
   • AEM 6.5: custom script or tool using Assets HTTP API / AssetManager to create assets and set metadata.
   • Turn off heavy workflows during bulk load, then run processing later on chosen folders.
3. Metadata mapping (Bynder -> AEM)
   • Design an AEM metadata model first.
   • Build a mapping table, e.g.:
     • Bynder name -> dc:title
     • Bynder description -> dc:description
     • Bynder brand/campaign -> AEM tags
     • Bynder asset id -> custom property, e.g. bynder:id (always keep this).
4. Versions, renditions, large files
   • Usually migrate latest version only; keep old Bynder version IDs in custom properties if needed.
   • Import originals, let AEM create renditions.
   • For big videos, ingest master files and let AEM/Dynamic Media handle derivatives; throttle batches.
5. ID mapping, redirects, validation
   • Keep an external mapping: bynderId, bynderUrl, aemPath, aemUrl.
   • During site/content migration, rewrite Bynder URLs to AEM URLs using this mapping.
   • Validate:
     • Asset counts & total size by type.
     • Sample metadata correctness.
     • Search and permissions for key user journeys.

Common pitfalls to watch

• Filenames with weird characters or super-long paths.
• Letting every workflow run during bulk loads (kills performance).
• Trying to copy Bynder permissions 1:1 instead of designing simpler AEM roles/folders.

Assets Migration Blueprint (Achim Koch, Adobe Developers Live) – end‑to‑end reference architecture (extraction, transform, CSV mapping, bulk import, clean‑up, validation). https://experienceleague.adobe.com/en/docs/events/adobe-developers-live-recordings/2024/nov2024/aem-assets/asset-migration-blueprint

AEMaaCS asset ingestion & bulk import (for Bynder exports on S3/Azure/GCS, etc.) https://experienceleague.adobe.com/en/docs/experience-manager-learn/cloud-service/migration/bulk-import

Bulk import assets using Assets view – UI‑driven variant of the same backend bulk import service. https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/assets/assets-view/bulk-import-assets-view