Cloud concept · Updated

Migration and data transfer - Migration and data transfer is the planned movement of applications and data between environments, including the methods, costs, and operational controls needed to complete that movement safely.

In short

Cloud migration combines workload placement, application changes, and data movement to achieve business and technical goals. Engineers must choose an appropriate migration strategy, maintain data consistency, and account for transfer charges that depend on traffic direction, network path, and location.

Cloud Concepts Hub →

6 key aspects of Migration and data transfer

Successful migration combines an appropriate adoption strategy with reliable data movement, explicit cost modeling, and tested operational controls.

01
Business-led adoption and readiness

Define measurable goals, assess application dependencies, and establish security and operational foundations before moving production workloads. Use pilots and migration waves to validate assumptions and limit the impact of failures.

02
Workload-specific migration strategies

Choose among rehost, replatform, refactor or rearchitect, repurchase, relocate, retain, and retire for each workload. Balance migration speed against compatibility, organizational readiness, and long-term maintenance.

03
Consistent database migration

Choose a one-time copy or an initial load followed by ongoing replication according to downtime requirements. Validate schema compatibility, data accuracy, replication lag, and application behavior before cutover.

04
Transfer-path cost awareness

Price traffic according to its direction, service, Region, Availability Zone, and network path. Free inbound transfer does not mean free ingestion, and traffic within a Region is not universally free.

05
Bandwidth and transfer-method planning

Estimate transfer duration from effective throughput and the rate of ongoing source changes. Select network or supported offline transfer methods that meet the schedule while protecting data in transit and at rest.

06
Controlled cutover and recovery

Use validation criteria, a defined write-freeze procedure where needed, and a tested rollback plan. Account for how new writes will be preserved if the application must return to its original environment.

Cloud services for Migration and data transfer

These services address different layers of migration rather than replacing one another. AWS Application Migration Service supports server rehosting, while AWS Database Migration Service moves supported database data, potentially into Amazon RDS. AWS DataSync transfers file and object datasets, with Amazon S3 available as a destination or staging location. AWS Direct Connect can provide dedicated connectivity for online migration and continuing hybrid traffic, but it does not perform the migration itself. Engineers must coordinate dependencies, permissions, validation, cutover, and rollback across these tools, and estimate tool usage, destination resources, and network charges separately.

AWS DataSyncAWS DataSync

Automates online movement of file and object data between supported storage locations, including on-premises storage and AWS storage services. Transfer verification and incremental copying help with initial migration and subsequent synchronization, but service, storage, request, and applicable network charges must still be included.

AWS Application Migration ServiceAWS Application Migration Service

Supports server rehosting by replicating supported source servers and launching them on Amazon EC2 for testing and cutover. It addresses server migration rather than database-engine conversion or application redesign.

AWS Direct ConnectAWS Direct Connect

Provides dedicated network connectivity between customer locations and AWS, which can support sustained migration traffic and hybrid operation. Connection capacity does not guarantee end-to-end application throughput, and port charges and applicable outbound transfer charges still apply.

Amazon RDSAmazon RDS

Provides managed relational database targets for supported migration scenarios. Moving a self-managed database to RDS can be a replatforming strategy, but teams must check engine versions, extensions, privileges, and operational differences.

Amazon S3Amazon S3

Provides object storage that can serve as a migration destination or staging area for exports and transferred files. Incoming internet data transfer is generally free, while storage, requests, retrieval for applicable storage classes, and outbound transfer can introduce separate charges.

Migration and data transfer exam questions

Real practice exam questions on Migration and data transfer, with the correct answer and its explanation. Answer them with every option in the exam simulator.

CLF-C02

During an application migration, a company stages 15 TB of data in an Amazon S3 Standard bucket. Amazon EC2 instances in several Availability Zones will read the data directly from the bucket. The bucket and all instances are in the same AWS Region. Access uses an S3 gateway VPC endpoint, with no NAT gateway or other network-processing service. Excluding compute, storage, and request charges, how should the company budget for these reads?

Show answerCORRECT ANSWER

Include no data transfer charges for the reads from S3 to EC2.

Data transfer between Amazon S3 and Amazon EC2 in the same AWS Region is free, even when the instances run in multiple Availability Zones. S3 gateway VPC endpoints also have no additional endpoint charge. Compute, storage, and request charges remain separate.

SAA-C03

A video production company is consolidating files from offices on several continents into one existing Amazon S3 bucket. Each office has a high-bandwidth internet connection, but offices far from the bucket's AWS Region experience poor upload throughput. The company wants uploads to enter the AWS network at a nearby edge location to improve long-distance transfer performance. Files must be uploaded directly to the existing bucket without intermediate buckets or company-managed proxy servers. Upload clients can be configured to use a different endpoint.

Which solution meets these requirements?

Show answerCORRECT ANSWER

Enable S3 Transfer Acceleration on the existing bucket and configure upload clients to use the bucket's s3-accelerate endpoint.

S3 Transfer Acceleration receives uploads through nearby AWS edge locations and optimizes the network path to the destination bucket. Clients must use the acceleration endpoint to take advantage of this path. No intermediate buckets or company-managed proxies are required.

Practice Migration and data transfer in a full exam

Questions on Migration and data transfer in each practice exam, with every answer option and an explanation for each:

Start a free practice exam

What is Migration and data transfer

3 min read

Migration moves applications, databases, and supporting resources from one environment to another, such as from an on-premises data center to a cloud platform. Data transfer is the movement of bytes that supports migration and ongoing operation. They are related but not identical: copying a database does not migrate application dependencies, permissions, monitoring, or operational responsibilities.

Cloud adoption starts with business goals and readiness assessment rather than copying servers immediately. Teams inventory workloads, map dependencies, identify regulatory requirements, and establish identity, networking, security, billing, and operational foundations. AWS describes adoption through the phases assess, mobilize, and migrate and modernize. Its Cloud Adoption Framework considers business, people, governance, platform, security, and operations. A practical approach uses a pilot followed by migration waves, grouping dependent applications to reduce disruption.

Migration strategies are commonly described as the seven Rs. Rehosting moves an application with minimal changes, while replatforming introduces targeted changes, such as moving a self-managed database to a managed database service. Refactoring or rearchitecting changes the application design more substantially. Repurchasing replaces an existing product, often with software as a service. Relocating moves an environment at the infrastructure or virtualization layer with minimal application changes. Retaining leaves a workload in its current environment, and retiring removes one that is no longer needed. The right choice depends on deadlines, licensing, compatibility, risk, and long-term operating costs; extensive modernization is not required for every migration.

Database migration requires both moving records and preserving application behavior. A homogeneous migration keeps the database engine type, while a heterogeneous migration changes engines and may require schema conversion, rewritten queries, and changes to stored procedures or data types. For a small database with an acceptable maintenance window, backup and restore or export and import may be sufficient. For a busy production system, an initial full load followed by change data capture can replicate ongoing changes while the source continues serving requests.

Replication reduces downtime but does not automatically eliminate it. For example, an order-processing application might replicate its source database to a managed target, validate records, briefly stop writes, wait for replication lag to clear, and then redirect connections. Teams must test compatibility, reconcile data, establish a rollback plan, and decide how to handle writes made after cutover. Replication also does not replace backups because unwanted changes can propagate to the target.

Transfer method depends on data volume, effective bandwidth, available time, security, and source capabilities. Online transfers can use internet connectivity or dedicated network connections. Offline transport can be appropriate when a supported physical-transfer option is available and network transfer would take too long. Estimate duration using actual achievable throughput, not just the advertised link speed, and allow for encryption, retries, small-file overhead, and continuing source changes.

Transfer pricing is directional and path-dependent. Incoming data transfer from the internet into AWS is generally free of data-transfer charges, but storage, requests, migration tools, and network processing can still cost money. Outgoing transfer to the internet is generally charged, subject to applicable allowances and service-specific exceptions. Cross-Region transfers generally incur charges, and replication can create recurring transfer costs as well as destination storage costs.

Within one Region, traffic is not automatically free. Same-Availability-Zone traffic using private addresses is often free for supported paths, whereas cross-Availability-Zone traffic commonly incurs charges, potentially on both sides. Service-specific exceptions apply, so identify the source, destination, Availability Zones, Regions, and network components before estimating costs. NAT gateways, private endpoints, and dedicated connections can add processing or connection charges independently of data-transfer pricing. A sound estimate includes the initial copy, ongoing synchronization, testing, backups, and normal traffic after migration.

Learn Migration and data transfer in lessons

3 short lessons on Migration and data transfer in 2 certification courses.

Open the lessons