Link copied to clipboard!
Group 16: Migration & Transfer
Data movement and hybrid connectivity: DataSync, Migration Hub, DMS, Storage Gateway, Transfer Family.
Migration Principle: Select migration strategy based on data volume, downtime tolerance, and connectivity requirements.
Services & Roles
DataSync
Online data transfer between on-premises and AWS storage services.
- One-time & recurring sync
- EFS, S3, FSx targets
- Data validation
Migration Hub
Central tracking and orchestration of application migrations.
- Migration tracking
- Discovery tools
- Partner integrations
DMS
Database migration with minimal downtime and schema conversion.
- Homogeneous migrations
- Heterogeneous migrations
- Continuous replication
Storage Gateway
Hybrid cloud storage with on-premises cache and AWS backend.
- File Gateway
- Volume Gateway
- Tape Gateway
Transfer Family
Managed file transfer protocols (SFTP, FTPS, FTP) with S3/EFS.
- Protocol support
- Identity providers
- Compliance features
Key Differences
| Dimension | DataSync | Migration Hub | DMS | Storage Gateway | Transfer Family |
|---|---|---|---|---|---|
| Data Type | Files & objects | Applications | Databases | Hybrid storage | File transfers |
| Transfer Mode | Scheduled sync | Migration tracking | Real-time replication | Hybrid access | Protocol-based |
| Downtime | Minimal (incremental) | Varies by tool | Near-zero | None (hybrid) | None |
| Use Case | Data migration | App migration | Database migration | Hybrid storage | File exchange |
| Complexity | Low (file sync) | High (orchestration) | Medium (DB schemas) | Medium (hybrid setup) | Low (protocol bridge) |
Selection Model
0–10 sliders weight migration requirements, data types, and operational constraints.
Score_DataSync = 0.32*C_fileMigration + 0.26*C_scheduledTransfer + 0.18*C_dataValidation + 0.12*C_incrementalSync + 0.08*C_storageTargets + 0.04*C_bandwidthOptimization
Score_MigrationHub = 0.30*C_applicationMigration + 0.26*C_migrationTracking + 0.18*C_discoveryTools + 0.12*C_partnerIntegration + 0.08*C_migrationPlanning + 0.06*C_portfolioAssessment
Score_DMS = 0.34*C_databaseMigration + 0.28*C_minimalDowntime + 0.16*C_schemaConversion + 0.12*C_continuousReplication + 0.06*C_dataTransformation + 0.04*C_changeDataCapture
Score_StorageGateway = 0.32*C_hybridStorage + 0.26*C_onPremisesCache + 0.18*C_cloudBackend + 0.12*C_protocolSupport + 0.08*C_localAccess + 0.04*C_cloudIntegration
Score_TransferFamily = 0.34*C_protocolTransfer + 0.28*C_managedFileTransfer + 0.16*C_identityIntegration + 0.12*C_complianceFeatures + 0.06*C_workflowAutomation + 0.04*C_auditLogging
DataSync {{vm.scores.datasync|number:2}}
Migration Hub {{vm.scores.migrationhub|number:2}}
DMS {{vm.scores.dms|number:2}}
Storage Gateway {{vm.scores.storagegateway|number:2}}
Transfer Family {{vm.scores.transferfamily|number:2}}
Primary Emphasis: {{vm.recommended.name}} ({{vm.recommended.score|number:2}})
Heuristics
- High C_fileMigration + C_scheduledTransfer → DataSync for file synchronization.
- Strong C_applicationMigration + C_migrationTracking → Migration Hub for complex migrations.
- High C_databaseMigration + C_minimalDowntime → DMS for database transfers.
- C_hybridStorage + C_onPremisesCache → Storage Gateway for hybrid scenarios.
- C_protocolTransfer + C_managedFileTransfer → Transfer Family for B2B exchanges.
Anti-Patterns
- Using DataSync for database migration (use DMS instead).
- Using Transfer Family for large-scale data migration (use DataSync).
- Using DMS for file system migration (use DataSync).
- Complex application migration without Migration Hub (tracking overhead).
Summary
Choose DataSync for files, DMS for databases, Migration Hub for applications, Storage Gateway for hybrid, Transfer Family for protocols.