DocumentationExperience Cloud KCS

Calculating disk space requirements for AEM as a Cloud Service migration using Content Transfer Tool

Last update: October 22, 2026

✨ This content is AI generated and could be inaccurate. Generative AI Terms

This article explains how to calculate the disk space required when migrating production content to Adobe Experience Manager as a Cloud Service using the Content Transfer Tool (CTT), ensuring a smooth migration process.

Description description

Environment

  • Adobe Experience Manager as a Cloud Service (all versions)
  • Migration from on-premise or AMS-hosted AEM to AEM as a Cloud Service
  • Content Transfer Tool (CTT) used for migration

Symptoms

  • Uncertainty about how to estimate disk space needed for migration packages and temporary files
  • Risk of migration failures or incomplete transfers due to insufficient disk space

Cause

The Content Transfer Tool requires sufficient disk space for both the source content and temporary working files. Underestimating disk requirements can result in migration failures or incomplete content transfer.

Resolution resolution

Follow the steps below to resolve the issue.

  1. On the source AEM instance, determine the size of the repository segment store (typically located at crx-quickstart/repository/segmentstore or a similar path).
  2. Use operating system commands to calculate the total size. For example, on Linux: du -sh /path/to/crx-quickstart/repository/segmentstore.
  3. Include any additional directories if custom content or binaries are stored outside the default paths.
  4. Allocate at least 2x the size of the content being migrated to accommodate temporary files created by the Content Transfer Tool. For example, if the content store is 100 GB, plan for at least 200 GB of available disk space.
  5. Before starting migration, verify that the host system has sufficient free disk space using OS utilities such as df -h on Linux.
  6. Ensure the target directory for temporary files is on a volume with adequate free space.
  7. During migration, periodically monitor disk usage to avoid unexpected failures due to insufficient space.
  8. If disk space runs low, pause the migration and free up space or expand the storage volume as needed.
  9. Refer to the official Content Transfer Tool documentation for additional best practices and requirements.
recommendation-more-help
experience-cloud-kcs-help-kbarticles