DAM Migration from Box to AEMaaCS | Community
Skip to main content
A
ayyappavenkatesh
Level 2
March 10, 2026
Question

DAM Migration from Box to AEMaaCS

  • March 10, 2026
  • 4 replies
  • 19 views

I’m looking for suggestions and practical approaches followed by anyone or to follow for the migration of binary from Box to AEMaaCS? I know one way, which is Box(~15TB) → AWS/Azure/GCP → AEMaaCS but apart from that, I’m looking for more or less direct migration from Box to AEMaaCS! are there any native Box tools that support this or anything from Adobe itself by any chance(couldn’t figure it so far but in case if I miss)

4 replies

arunpatidar
Community Advisor
arunpatidarCommunity Advisor
Community Advisor
March 10, 2026

Hi ​@ayyappavenkatesh 
You can check 

 

Arun Patidar
Vishal_Anand
Vishal_Anand
Level 5
March 10, 2026

​@ayyappavenkatesh You can rely on OOTB options provided by AEM instead of relying on external storage. 

As pointed by Arun, you can refer to this response here: https://experienceleaguecommunities.adobe.com/adobe%2Dexperience%2Dmanager%2Dsites%2D8/move%2Dassets%2Dfrom%2Dbox%2Dto%2Daem%2D25924?postid=325114#post325114

AmitVishwakarma
Community Advisor
AmitVishwakarmaCommunity Advisor
Community Advisor
March 11, 2026

Hi ​@ayyappavenkatesh 

Today there is no native, supported "Box -> AEM as a Cloud Service" migration connector.

AEM's Bulk Import only supports these sources: Azure, AWS, Google Cloud, Dropbox, OneDrive – Box is not on the list.

Because of that, for a ~15 TB migration the recommended, fully supported approach is:

  1. Stage from Box into a supported cloud store
    • Use Box tools (Shuttle, API, CLI, or export) to dump your content into S3, Azure Blob, GCS, Dropbox, or OneDrive.
  2. Use AEM Assets Bulk Import to pull into AEMaaCS
    • Configure Bulk Import in AEM Assets (Admin or Assets view) to point at that bucket/container.
    • This is the pattern Adobe documents for large migrations from non‑AEM sources and is proven at multi‑TB scale

If you absolutely must avoid intermediate storage, the only alternative is custom code, not OOTB:

  • Build a small service that:
    • Reads binaries + metadata from Box via the Box API.
    • Uploads into AEMaaCS via the direct binary upload HTTP APIs (or the aem-upload Node.js library), which are designed for large, client‑side uploads
Amit Vishwakarma - Adobe Commerce Champion 2025 | 16x Adobe certified | 4x Adobe SME
PGURUKRISHNA
PGURUKRISHNA
Level 4
March 11, 2026

Hey ​@ayyappavenkatesh 

Box Setup:

  1. Create Box App at https://app.box.com/developers/console

  2. Choose "Custom App" → "OAuth 2.0 with JWT"

  3. Generate Developer Token (valid 60 mins) or implement OAuth flow

AEM Setup:

  1. Create service user with DAM write permissions

  2. Use technical account credentials for AEMaaCS

Run Migration

mvn clean compile exec:java -Dexec.mainClass="com.wknd.migration.BoxToAEMDirectMigrator"
Terms & ConditionsAccessibility statement

Loading footer...