# Best practice arranged by migration phase
## Assess Phase
### Operational excellence pillar
+ [MIG-OPS-BP-1.1 Your migration plan must be informed by and reflect technology, processes and business](assess-ops.md#MIG-OPS-bp-1.1-your-migration-plan-must-be-informed-by-and-reflect-technology-processes-and-business)
### Security pillar
+ [MIG-SEC-BP-1.1 Understand the security credentials needed by the discovery tool](assess-sec.md#mig-sec-bp-1.1-understand-the-security-credentials-needed-by-the-discovery-tool)
+ [MIG-SEC-BP-1.2 Understand how the discovery tool works](assess-sec.md#mig-sec-bp-1.2-understand-how-the-discovery-tool-works)
+ [MIG-SEC-BP-1.3 Understand the discovery tool's data security and apply appropriate controls](assess-sec.md#mig-sec-bp-1.3-understand-the-discovery-tools-data-security-and-apply-appropriate-controls)
+ [MIG-SEC-BP-2.1 Perform a tools mapping exercise](assess-sec.md#mig-sec-bp-2.1-perform-a-tools-mapping-exercise)
+ [MIG-SEC-BP-3.1 Understand, establish, and implement compliance framework](assess-sec.md#mig-sec-bp-3.1-understand-establish-and-implement-compliance-framework)
### Reliability pillar
+ [MIG-REL-BP-1.1: Define SLAs across all applications or environments (like production, development, or test) and confirm them with your business team](assess-rel.md#mig-rel-bp-1.1-define-slas-across-all-applications-or-environments)
+ [MIG-REL-BP-1.2: Define and automate runbooks and communicate them to your teams](assess-rel.md#mig-rel-bp-1.2-define-and-automate-runbooks-and-communicate-them-to-your-teams)
+ [MIG-REL-BP-1.3: Map AWS Global Infrastructure to your business SLAs before migrations starts](assess-rel.md#mig-rel-bp-1.3-map-global-infrastructure-to-your-business-slas-before-migrations-starts)
+ [MIG-REL-BP-1.4: Select tools to monitor SLAs and notify you in case thresholds are exceeded](assess-rel.md#mig-rel-bp-1.4-select-tools-to-monitor-slas-and-notify-you-in-case-thresholds-are-exceeded)
+ [MIG-REL-BP-2.1: Keep your business impact analysis up-to-date](assess-rel.md#mig-rel-bp-2.1-keep-your-business-impact-analysis-up-to-date)
+ [MIG-REL-BP-2.2: Update the risk assessment for the type of disaster events covered by your BCP](assess-rel.md#mig-rel-bp-2.2-update-the-risk-assessment-for-the-type-of-disaster-events-covered-by-your-bcp)
+ [MIG-REL-BP-2.3: Define the recovery point objective (RPO) and recovery time objective (RTO) targets](assess-rel.md#mig-rel-bp-2.3-define-the-recovery-point-objective-rpo-and-recovery-time-objective-rto-targets)
+ [MIG-REL-BP-2.4: Select a disaster recovery strategy based on cloud best practices](assess-rel.md#mig-rel-bp-2.4-select-a-disaster-recovery-strategy-based-on-cloud-best-practices)
+ [MIG-REL-BP-3.1: Estimate the required maintenance window](assess-rel.md#mig-rel-bp-3.1-estimate-the-required-maintenance-window)
+ [MIG-REL-BP-3.2: Test the migration window and impact](assess-rel.md#mig-rel-bp-3.2-test-the-migration-window-and-impact)
+ [MIG-REL-BP-3.3: Plan for failure](assess-rel.md#mig-rel-bp-3.3-plan-for-failure)
### Performance efficiency pillar
+ [MIG-PERF-BP-1.1: Understand the performance characteristics of your current infrastructure to select the best performant optimized cloud infrastructure](assess-perf.md#mig-perf-bp-1.1-understand-the-performance-characteristics-of-your-current-infrastructure)
+ [MIG-PERF-BP-2.1: Evaluate operating systems and versions that are running in your environment](assess-perf.md#mig-perf-bp-2.1-evaluate-operating-systems-and-versions-that-are-running-in-your-environment)
+ [MIG-PERF-BP-3.1: Evaluate the different methods to migrate data and select the one best for you use case: online mode, offline mode, or hybrid approach](assess-perf.md#mig-perf-bp-3.1-evaluate-different-methods-to-migrate-data)
+ [MIG-PERF-BP-4.1: Select the storage solution based on the characteristics of your workloads](assess-perf.md#mig-perf-bp-4.1-select-the-storage-solution-based-on-the-characteristics-of-your-workloads)
+ [MIG-PERF-BP-4.2: Choose the optimal storage solutions for specialized workloads, such as SAP and VMware cloud on AWS](assess-perf.md#mig-perf-bp-4.2-choose-the-optimal-storage-solutions-for-specialized-workloads)
+ [MIG-PERF-BP-4.3: Evaluate the different storage tiers at prices to meet your migrated workload's performance](assess-perf.md#mig-perf-bp-4.3-evaluate-the-different-storage-tiers-at-prices-to-meet-your-migrated-workloads-performance)
+ [MIG-PERF-BP-5.1: Establish a reliable network connectivity from on-premises to AWS to ensure performance](assess-perf.md#mig-perf-bp-5.1-establish-a-reliable-network-connectivity-from-on-premises-to-cloud-to-ensure-performance)
+ [MIG-PERF-BP-5.2: Assure that network performance is not impacted by external factors](assess-perf.md#mig-perf-bp-5.2-assure-that-network-performance-is-not-impacted-by-external-factors)
### Cost optimization pillar
+ [MIG-COST-BP-1.1: Thoroughly assess existing infrastructure usage and application dependencies prior to migration](assess-cost.md#mig-cost-bp-1.1-thoroughly-assess-existing-infrastructure-usage-and-application-dependencies-prior-to-migration)
+ [MIG-COST-BP-1.2: Leverage AWS programs and workshops designed to remove common blockers and accelerate migrations](assess-cost.md#mig-cost-bp-1.2-leverage-programs-and-workshops-designed-to-remove-common-blockers-and-accelerate-migrations)
### Sustainability pillar
+ [MIG-SUS-BP-1.1: Include sustainability considerations as part of your migration business case and preliminary assessments](assess-sus.md#mig-sus-bp-1.1-include-sustainability-considerations)
+ [MIG-SUS-BP-2.1: Choose a Region for the workloads you plan to migrate based on your business requirements and your sustainability goals](assess-sus.md#mig-sus-bp-2.1-choose-a-region-for-the-workloads-you-plan-to-migrate-based-on-your-business-requirements-and-your-sustainability-goals)
## Mobilize Phase
### Operational excellence pillar
+ [MIG-OPS-BP-2.1 Define and measure key performance indicators (KPIs) which can be shared with all teams involved in the migration](mobilize-ops.md#MIG-OPS-bp-2.1-define-and-measure-key-performance-indicators)
+ [MIG-OPS-BP-3.1 Invest time and effort to ensure the required migration and operations skills are captured, skills gaps identified, and training plans are implemented and managed](mobilize-ops.md#MIG-OPS-bp-3.1-invest-time-and-effort)
+ [MIG-OPS-BP-4.1 Build a comprehensive resource model for your migration that reflects the demands of the migration as well as the regular activities](mobilize-ops.md#MIG-OPS-bp-4.1-build-a-comprehensive-resource-model)
+ [MIG-OPS-BP-5.1 Build a Cloud Center of Excellence (CCoE) team within your organization as part of your migration planning](mobilize-ops.md#MIG-OPS-bp-5.1)
+ [MIG-OPS-BP-6.1 Define Cloud Operations Strategy: understand your current operating model, processes and tools, and explore how to implement them efficiently, securely and reliably in the cloud to create your cloud operations strategy](mobilize-ops.md#MIG-OPS-bp-6.1-define-cloud-operations-strategy)
+ [MIG-OPS-BP-6.2 Align AWS operational requirements with your existing tools and identify any gaps](mobilize-ops.md#MIG-OPS-bp-6.2-align-operational-requirements-with-your-existing-tools-and-identify-any-gaps)
+ [MIG-OPS-BP-6.3 Regularly test your operations in the cloud](mobilize-ops.md#MIG-OPS-bp-6.3-regularly-test-your-operations-in-cloud)
+ [MIG-OPS-BP-7.1 Calculate your potential migration velocity using both technical and non-technical perspectives (like network bandwidth, team availability, volume of changes, and change freezes)](mobilize-ops.md#MIG-OPS-bp-7.1-calculate-your-potential-migration-velocity)
### Security pillar
+ [MIG-SEC-BP-4.1 Implement strong identity and least privilege principles](mobilize-sec.md#mig-sec-bp-4.1-implement-strong-identity-and-least-privilege-principles)
+ [MIG-SEC-BP-5.1 Implement AWS multi-account structure](mobilize-sec.md#mig-sec-bp-5.1-implement-multi-account-structure)
+ [MIG-SEC-BP-6.1 Establish secure connectivity to AWS ](mobilize-sec.md#mig-sec-bp-6.1-establish-secure-connectivity)
+ [MIG-SEC-BP-6.2: Establish network security controls ](mobilize-sec.md#mig-sec-bp-6.2-establish-network-security-controls)
+ [MIG-SEC-BP-7.1 Establish security controls for protecting data at rest](mobilize-sec.md#mig-sec-bp-7.1-establish-security-controls-for-protecting-data-at-rest)
+ [MIG-SEC-BP-8.1: Establish application layer security controls](mobilize-sec.md#mig-sec-bp-8.1-establish-application-layer-security-controls)
+ [MIG-SEC-BP-8.2: Optimize application security with AWS Application Migration Service](mobilize-sec.md#mig-sec-bp-8.2-optimize-application-security)
+ [MIG-SEC-BP-9.1: Establish a data backup and restore strategy](mobilize-sec.md#mig-sec-bp-9.1-establish-a-data-backup-and-restore-strategy)
+ [MIG-SEC-BP-9.2: Establish a Disaster recovery plan](mobilize-sec.md#mig-sec-bp-9.2-establish-a-disaster-recovery-plan)
+ [MIG-SEC-BP-10.1: Validate and use AWS native monitoring tools.](mobilize-sec.md#mig-sec-bp-10.1-validate-and-use-monitoring-tools)
+ [MIG-SEC-BP-10.2: Explore cloud native AWS partner monitoring tools](mobilize-sec.md#mig-sec-bp-10.2-explore-cloud-native-partner-monitoring-tools)
+ [MIG-SEC-BP-11.1: Perform third-party integration due diligence](mobilize-sec.md#mig-sec-bp-11.1-perform-third-party-integration-due-diligence)
### Reliability pillar
+ [MIG-REL-BP-4.1: Be aware of service quotas and constraints for migration services](mobilize-rel.md#mig-rel-bp-4.1-be-aware-of-service-quotas-and-constraints-for-migration-services)
+ [MIG-REL-BP-4.2: Estimate the impact of new workloads on existing service quotas across accounts and Regions](mobilize-rel.md#mig-rel-bp-4.2-estimate-the-impact-of-new-workloads-on-existing-service-quotas-across-accounts-and-regions)
+ [MIG-REL-BP-4.3: Be aware of unchangeable service quotas and how you determine which accounts or VPCs workloads use](mobilize-rel.md#mig-rel-bp-4.3-be-aware-of-unchangeable-service-quotas-and-how-you-determine-which-accounts-or-vpcs-workloads-use)
+ [MIG-REL-BP-5.1: Provide sufficient bandwidth for normal and traffic from data replication](mobilize-rel.md#mig-rel-bp-5.1-provide-sufficient-bandwidth-for-normal-and-traffic-from-data-replication)
+ [MIG-REL-BP-5.2: Assure that links and equipment to on-premises are highly available](mobilize-rel.md#mig-rel-bp-5.2)
+ [MIG-REL-BP-5.3: Verify that your network design enables communication between on-premises and cloud networks](mobilize-rel.md#mig-rel-bp-5.3-verify-that-your-network-design-enables-communication-between-on-premises-and-cloud-networks)
+ [MIG-REL-BP-5.4: Use an IP scheme that allows for sufficient growth within cloud workloads and burst auto-scaling](mobilize-rel.md#mig-rel-bp-5.4-use-an-ip-scheme-that-allows-for-sufficient-growth-within-cloud-workloads-and-burst-auto-scaling)
+ [MIG-REL-BP-5.5: Complete a reliable DNS design that enables resolutions to existing domains, plus new domains in AWS](mobilize-rel.md#mig-rel-bp-5.5-complete-a-reliable-dns-design-that-enables-resolutions-to-existing-domains)
+ [MIG-REL-BP-5.6: Test network performance prior to migration](mobilize-rel.md#mig-rel-bp-5.6-test-network-performance-prior-to-migration)
+ [MIG-REL-BP-5.7: Test network component failure](mobilize-rel.md#mig-rel-bp-5.7-test-network-component-failure)
+ [MIG-REL-BP-6.1: Identify and back up all data that needs to be backed up, or reproduce the data from sources](mobilize-rel.md#mig-rel-bp-6.1-identify-and-back-up-all-data-that-needs-to-be-backed-up-or-reproduce-the-data-from-sources)
+ [MIG-REL-BP-7.1: Deploy the workload to multiple locations](mobilize-rel.md#mig-rel-bp-7.1-deploy-the-workload-to-multiple-locations)
### Performance efficiency pillar
+ [MIG-PERF-BP-6.1: Identify a migration strategy for your network components (DNS, IP addressing, and DHCP) migration](assess-perf.md#mig-perf-bp-6.1-identify-a-migration-strategy-for-your-network-components-dns-ip-addressing-and-dhcp-migration)
+ [MIG-PERF-BP-7.1: Identify the right CloudWatch metrics to capture or detect anomaly and identify performance blockers for shared services](mobilize-perf.md#mig-perf-bp-7.1-identify-the-right-cloudwatch-metrics-to-capture-or-detect-anomaly-and-identify-performance-blockers-for-shared-services)
+ [MIG-PERF-BP-7.2: Select the best performing cloud infrastructure that can scale for additional workloads in future without any performance impact](mobilize-perf.md#mig-perf-bp-7.2-select-the-best-performing-cloud-infrastructure)
+ [MIG-PERF-BP-7.3: Reduce the blast radius for performance impact into a single account](mobilize-perf.md#mig-perf-bp-7.3-reduce-the-blast-radius-for-performance-impact-into-a-single-account)
+ [MIG-PERF-BP-7.4: Benchmark existing workloads for performance](mobilize-perf.md#mig-perf-bp-7.4-benchmark-existing-workloads-for-performance)
### Cost optimization pillar
+ [MIG-COST-BP-2.1: Leverage existing tools to automate your migration](mobilize-cost.md#mig-cost-bp-2.1-leverage-existing-tools-to-automate-your-migration)
+ [MIG-COST-BP-2.2: Minimize the number of applications and the amount of data that is migrated](mobilize-cost.md#mig-cost-bp-2.2-minimize-the-number-of-applications-and-the-amount-of-data-that-is-migrated)
+ [MIG-COST-BP-2.3: Right-size your replication servers to prevent bottlenecks without over-provisioning](mobilize-cost.md#mig-cost-bp-2.3-right-size-your-replication-servers-to-prevent-bottlenecks-without-over-provisioning)
+ [MIG-COST-BP-3.1: Plan and set up cost and usage governance of AWS resources with help of IAM policies](mobilize-cost.md#mig-cost-bp-3.1-plan-and-set-up-cost-and-usage-governance-of-resources)
+ [MIG-COST-BP-3.2: Define a cost allocation strategy that meets your organizations specific financial management process](mobilize-cost.md#mig-cost-bp-3.2-define-a-cost-allocation-strategy-that-meets-your-organizations-specific-financial-management-process)
+ [MIG-COST-BP-3.3: Design a strategy to monitor, track and analyze your AWS cost and usage as you move resources to AWS](mobilize-cost.md#mig-cost-bp-3.3-design-a-strategy-to-monitor-track-and-analyze-your-cost-and-usage-as-you-move-resources)
### Sustainability pillar
+ [MIG-SUS-BP-3.1: Focus on efficiency across all aspects of infrastructure](mobilize-sus.md#mig-sus-bp-3.1-focus-on-efficiency-across-all-aspects-of-infrastructure)
+ [MIG-SUS-BP-4.1: Adopt metrics that can signal the sustainability of your application](mobilize-sus.md#mig-sus-bp-4.1-adopt-metrics-that-can-signal-the-sustainability-of-your-application)
+ [MIG-SUS-BP-4.2: Include sustainability metrics in the application portfolio analysis to drive migration and modernization initiatives](mobilize-sus.md#mig-sus-bp-4.2-include-sustainability-metrics-in-the-application-portfolio-analysis-to-drive-migration-and-modernization-initiatives)
+ [MIG-SUS-BP-5.1: Implement efficient workload design by leveraging the underlying infrastructure.](mobilize-sus.md#mig-sus-bp-5.1-implement-efficient-workload-design-by-leveraging-the-underlying-infrastructure)
+ [MIG-SUS-BP-6.1: Identify environments and workloads that can be consolidated or retired](mobilize-sus.md#mig-sus-bp-6.1-identify-environments-and-workloads-that-can-be-consolidated-or-retired)
+ [MIG-SUS-BP-6.2: Identify workloads that can use efficient software and architecture patterns to maintain consistent high utilization of deployed resources](mobilize-sus.md#mig-sus-bp-6.2-identify-workloads-that-can-use-efficient-software-and-architecture-patterns)
+ [MIG-SUS-BP-6.3: Analyze your data access patterns and data lifecycle processes, and evaluate how you can become more efficient and sustainable in your data management](mobilize-sus.md#mig-sus-bp-6.3-analyze-your-data-access-patterns-and-data-lifecycle-processes)
+ [MIG-SUS-BP-6.4: Understand and influence business requirements, and optimize areas of code to reach your sustainability goals](mobilize-sus.md#mig-sus-bp-6.4-understand-and-influence-business-requirements-and-optimize-areas-of-code-to-reach-your-sustainability-goals)
## Migrate Phase
### Operational excellence pillar
+ [MIG-OPS-BP-8.1 Ensure you have a testing strategy in place](migrate-ops.md#MIG-OPS-bp-8.1-ensure-you-have-a-testing-strategy-in-place)
+ [MIG-OPS-BP-9.1 Determine if your current CI/CD pipeline works on AWS](migrate-ops.md#MIG-OPS-bp-9.1-determine-if-your-current-cicd-pipeline-works-on-the-cloud)
+ [MIG-OPS-BP-9.2 Provision resources through infrastructure as code (IaC) templates](migrate-ops.md#MIG-OPS-bp-9.2-provision-resources-through-infrastructure-as-code-iac-templates)
### Security pillar
+ [MIG-SEC-BP-12.1: Understand the data security and compliance ](migrate-sec.md#mig-sec-bp-12.1-understand-the-data-security-and-compliance)
+ [MIG-SEC-BP-13.1: Understand AWS service capabilities for event detection and investigation](migrate-sec.md#mig-sec-bp-13.1-understand-capabilities-for-event-detection-and-investigation)
+ [MIG-SEC-BP-14.1: Understand AWS best practices for incident response](migrate-sec.md#mig-sec-bp-14.1-understand-best-practices-for-incident-response)
+ [MIG-SEC-BP-15.1: Protect your network resources](migrate-sec.md#mig-sec-bp-15.1-protect-your-network-resources)
+ [MIG-SEC-BP-16.1: Manage authentication for applications and databases](migrate-sec.md#mig-sec-bp-16.1-manage-authentication-for-applications-and-databases)
### Reliability pillar
+ [MIG-REL-BP-8.1 Before the cut-over, test HA and FT for the migrated workloads, and perform a DR dry-run after the migration](migrate-rel.md#mig-rel-bp-8.1-before-the-cut-over-test-ha-and-ft-for-the-migrated-workloads-and-perform-a-dr-dry-run-after-the-migration)
### Performance efficiency pillar
+ [MIG-PERF-BP-8.1: Perform stress and user acceptance tests on migrated workloads before the actual cutover.](migrate-perf.md#mig-perf-bp-8.1-perform-stress-and-user-acceptance-tests-on-migrated-workloads-before-the-actual-cutover)
+ [MIG-PERF-BP-8.2: Review and implement the lessons learned from previous migration waves](migrate-perf.md#mig-perf-bp-8.2-review-and-implement-the-lessons-learned-from-previous-migration-waves)
+ [MIG-PERF-BP-8.3: Perform a Well-Architected Framework Review on each iteration of the migrated workload.](migrate-perf.md#mig-perf-bp-8.3-perform-a-well-architected-framework-review-on-each-iteration-of-the-migrated-workload)
+ [MIG-PERF-BP-9.1: Generate alarm-based notifications for metric's threshold breach](migrate-perf.md#mig-perf-bp-9.1-generate-alarm-based-notifications-for-metrics-threshold-breach)
+ [MIG-PERF-BP-9.2: Determine the need for a real-time or a near real-time monitoring solution](migrate-perf.md#mig-perf-bp-9.2-determine-the-need-for-a-real-time-or-a-near-real-time-monitoring-solution)
+ [MIG-PERF-BP-9.3: Implement CloudWatch or a Quicksight dashboard as a single pane view for visualizing all metrics](migrate-perf.md#mig-perf-bp-9.3)
+ [MIG-PERF-BP-9.4: Set up automated testing for your application metrics](migrate-perf.md#mig-perf-bp-9.4-set-up-automated-testing-for-your-application-metrics)
+ [MIG-PERF-BP-9.5: Re-evaluate your compute usage with AWS Trusted Advisor, AWS Compute Optimizer, or partner tools](migrate-perf.md#mig-perf-bp-9.5-re-evaluate-your-compute-usage)
### Cost optimization pillar
+ [MIG-COST-BP-4.1: Create a deliberate metrics strategy to help demystify cloud economics](migrate-cost.md#mig-cost-bp-4.1-create-a-deliberate-metrics-strategy-to-help-demystify-cloud-economics)
+ [MIG-COST-BP-4.2: Monitor spend and limit unintended or unnecessary costs with budgeting and forecasting tools](migrate-cost.md#mig-cost-bp-4.2-monitor-spend-and-limit-unintended-or-unnecessary-costs-with-budgeting-and-forecasting-tools)
+ [MIG-COST-BP-4.3: Use AWS Cost Anomaly Detection in Cost Explorer to quickly improve cost controls](migrate-cost.md#mig-cost-bp-4.3-use-cost-anomaly-detection-to-quickly-improve-cost-controls)
+ [MIG-COST-BP-4.4: Use dashboards that provide pre-built visualizations to help you get a detailed view of your AWS usage and costs as you move resources to AWS](migrate-cost.md#mig-cost-bp-4.4)
+ [MIG-COST-BP-5.1: Leverage the right purchase options and scalable architecture for your workloads](migrate-cost.md#mig-cost-bp-5.1-leverage-the-right-purchase-options-and-scalable-architecture-for-your-workloads)
+ [MIG-COST-BP-5.2: Identify resources during migration that are likely candidates for cost optimizations later](migrate-cost.md#mig-cost-bp-5.2-identify-resources-during-migration-that-are-likely-candidates-for-cost-optimizations-later)
+ [MIG-COST-BP-6.1: Use automation to re-evaluate your compute usage periodically](migrate-cost.md#mig-cost-bp-6.1-use-automation-to-re-evaluate-your-compute-usage-periodically)
+ [MIG-COST-BP-7.1: Create a plan early to optimize after the initial migration](migrate-cost.md#mig-cost-bp-7.1-create-a-plan-early-to-optimize-after-the-initial-migration)
### Sustainability pillar
+ [MIG-SUS-BP-7.1: Implement data management practices](migrate-sus.md#mig-sus-bp-7.1-implement-data-management-practices)
+ [MIG-SUS-BP-8.1: Adopt methods that can reduce interim resource consumption during the migration](migrate-sus.md#mig-sus-bp-8.1-adopt-methods-that-can-reduce-interim-resource-consumption-during-the-migration)