Introduction:
Cloud migration using Azure Storage Mover enables high‑volume data transfer from Amazon S3 into Azure Blob Storage as part of SAP on Azure modernization initiatives, including RISE and SAP HANA deployments. Azure Arc multicloud connectors provide control‑plane integration with AWS, allowing Azure to authenticate and discover S3 buckets and expose them as managed external resources.
Storage Mover then orchestrates the end‑to‑end data movement using S3 source and Blob target endpoints, supporting large‑scale migrations with telemetry, integrity validation, and incremental sync options. Migrated datasets land in Azure Blob Storage, where they can be consumed by SAP HANA, SAP Data Intelligence, SAP S/4Hana, BW/4Hana and downstream Azure analytics or backup workflows.
The process completes as the data lands in Azure Blob Storage, establishing a cloud‑native destination for ongoing analytics, applications, or archival needs. This guide outlines the essential prerequisites, service limits, and configuration steps required to implement migration with clarity and operational confidence.
End‑to‑End Migration with SAP Consumption Diagram:
The migration process begins with Amazon S3, which serves as source storage containing the files and folders you intend to transfer to Azure. Azure then connects securely to your AWS environment through the Azure Arc Multicloud Connector, which authenticates to AWS, discovers your S3 buckets, and exposes their inventory to Azure as part of its cross‑cloud control‑plane integration. Once connected, Azure Storage Mover a fully managed migration engine executes the data transfer using the configured S3 source endpoint and Azure Blob target endpoint.
Storage Mover supports large‑scale migrations of up to 500 million objects per job, provides incremental sync options, and offers detailed logging and job tracking for operational visibility. Once migrated datasets are staged in Azure Blob Storage, where they can be leveraged by SAP HANA, SAP Data Intelligence, SAP S/4HANA, BW/4HANA, and integrated Azure analytics or backup workflows. The cloud‑native destination that supports containers, lifecycle policies, and seamless integration with Azure analytics and application services such as Azure Synapse, Azure Data Factory, and AI workloads.
1) Prerequisites:
- An active Azure subscription with the required permissions to manage Azure Storage Mover and Azure Arc resources.
- An AWS account with access to the Amazon S3 bucket you plan to migrate.
- A destination Azure Storage account to receive the transferred data.
- An Azure Storage Mover resource already deployed in your Azure environment.
2) Service Limits:
- Supports up to 500 million objects per migration job.
- Allows a maximum of 10 concurrent migration jobs per subscription (higher limits available through support).
- Archived objects are not automatically rehydrated: Data in Deep Archive or Glacier must be restored before migration.
- Private networking is not supported: Secure data transfer is enforced using trusted Azure IP ranges.
3) Create Multicloud Connector for AWS:
- Use Azure Arc to connect AWS services to Azure, enabling discovery and data transfer operations.
- Steps include selecting subscription, region, AWS account ID, and adding Inventory and Storage Data Management solutions.
4) Configure Endpoints:
- AWS S3 Source Endpoint - Navigate to Storage Endpoints → Source endpoints → Add endpoint. Select the AWS S3 bucket from the multicloud connector.
- Azure Blob Storage Target Endpoint - Select your subscription, storage account, and blob container. Assign Storage Blob Data Contributor RBAC role.
5) Creating Migration Project & Job Definition:
- Create a migration project under Project Explorer.
- Add a Job Definition specifying source S3 endpoint and target Blob endpoint. Select migration mode: Mirror, Incremental, or Full copy.
6) Run & Monitor Migration Job:
- Start the job from the Job Properties pan.
- Monitor speed, progress %, and estimated completion time in Migration Overview. Review logs for warnings or transfer errors.
7) Post-Migration Validation:
- Verify data integrity and completeness.
- Conduct UAT testing.
- Enable incremental sync if needed.
- Optionally delete S3 bucket after migration is validated.
Conclusion:
The combined use of Azure Storage Mover and Azure Arc Multicloud Connector provides robust, scalable, and secure architecture for migrating data from Amazon S3 to Azure Blob Storage especially for SAP, RISE, and HANA modernization scenarios. By extending Azure’s control plane into AWS, Arc enables authenticated discovery of S3 buckets while Storage Mover orchestrates high‑throughput, policy‑driven data movement using defined source and target endpoints. With support for large object counts, telemetry, and sync capabilities, the solution ensures operational visibility and data integrity throughout the migration lifecycle. Once transferred, data lands in Azure Blob Storage, ready to integrate with SAP HANA, SAP Data Intelligence, SAP S/4HANA, BW/4HANA, and Azure-native analytics and AI services, establishing a high‑performance foundation for SAP workloads in the cloud.
Reference links:
Microsoft