Selecting the appropriate discovery tool for your cloud migration

{"value":"Cloud migrations invariably require the coordination of multiple stakeholders, such as business and technical teams, partners, and third-party providers. As a stakeholder, understanding your portfolio is crucial to determine which workloads to migrate, and their requirements and interdependencies. But manually gathering these insights can be a daunting task. You can inform your decision by provisioning a discovery tool.\n\nGiven the variety of choices available, choosing the appropriate discovery tool for your use case can also be challenging. In this blog post, we explain a proven three-step technique to successfully filter and prioritize a list of discovery tools based on the essential features needed for your business.\n\n\n\nFigure 1. Steps to determine your migration discovery tool\n\n#### **Step 1: Review**\nReview the outcomes that your migration journey should deliver. These will drive your discovery requirements and baseline the features needed. Compare the baseline features with existing tools within your organization such as Configuration Management Databases (CMDBs) or Application Performance Management (APM) tooling. By the end of this Review step, you should establish if your in-house tools are sufficient for your objectives. Here is a list of [ questions to support your migration analysis.](https://docs.aws.amazon.com/prescriptive-guidance/latest/migration-portfolio-discovery/data-collection.html#decide_how_gather).\n\nYou may need to collect high-level data or complete datasets depending on your stage in the [migration process](https://aws.amazon.com/cloud-migration/how-to-migrate/). You may be exploring migration costs to assess the lift-and-shift migration threshold of a benefit program such as [ Amazon Web Services Migration Acceleration Program (MAP)](https://aws.amazon.com/migration-acceleration-program/). In this case, you probably only need a snapshot of your on-premises environment with a list of servers, their configurations, and attached licenses. You may be evaluating the [ Total Cost of Ownership (TCO)](Total Cost of Ownership (TCO)) between your on-premises infrastructure and an elastic deployment model on the cloud. In this case, you’ll want to be able to estimate the cost of a right-sized cloud infrastructure. For that, you will want to run a discovery tool for the duration of a business cycle.\n\nFinally, to decide how and when applications are going to migrate, you will need a complete and accurate dataset with the application and database features to be migrated. This must include network dependencies, non-functional requirements (NFRs), disaster recovery (DR) plans, and third-party licensing terms and conditions (T&C).\n\nConclude this step by baselining the features that you require in the discovery tool.\n\n#### **Step 2: Refine**\nThis step is an elimination process. One of the resources you can use to compile a list of candidate discovery tools is the [Discovery migration tool comparison](https://aws.amazon.com/prescriptive-guidance/migration-tools/migration-discovery-tools/) page. Filter and sort the list using the following criteria categories:\n\n1. Core features\n2. Common features\n3. Special features\n4. Tool provisioning\n5. Operation\n\nBy the end of this step, you should have a prioritized list of the discovery tools that optimally match your requirements.\n\n##### *Core features*\nFollowing are the basic set of features that you should expect from any discovery tool. Analysis of the data captured by these features will support your high-level business case.\n\n- **Automatic inventory collection**. Reports on the infrastructure profile, such as CPU family, CPU cores, memory size, disk size and speed, and operating system.\n- **Utilization**. Shows peak and average utilization of CPU, memory, and disk.\n- **Network storage discovery**. Detects and profiles network shares from network-attached storage (NAS).\n- **Software**. Identifies running processes and installed software, pinpointing database engines and their versions.\n- **Network scanning**. Scans network subnets to discover unknown infrastructure assets.\n##### *Common features*\nHere are some common features of discovery tools. With this data, you will be able to create a more detailed TCO analysis and migration plan.\n\n- **Lift-and-shift cost estimation**. Maps a recommended target Amazon Web Services infrastructure for the rehost of the source infrastructure, and calculates the Amazon Web Services cost.\n- **Target sizing recommendation**. Maps and calculates the cost for alternative target Amazon Web Services infrastructures based on the peak and average utilization.\n- **TCO analysis**. Provides a cost comparison between current on-premises cost and projected Amazon Web Services cost.\n- **Dependency mapping**. Collects network connection information and builds inbound and outbound dependency maps of the servers and running applications. Infers applications from groups of infrastructure resources based on communication patterns.\n- **Application prioritization**. Assigns weight or relevance to application and infrastructure attributes to create prioritization criteria for migration.\n- **Wave planning**. Recommends groups of applications and the ability to create migration wave plans.\n\n##### *Special features*\nSpecial features map to less common requirements, or to a specific set of the workloads you want to migrate. For example, you may require your tools to collect database dependency information if databases form a significant part of your workloads. If you have strict regulatory compliance to follow (HIPAA, GDPR), you’ll need tools that comply with these regulations. Other examples are:\n\n- **Licensing analysis**. Provides optimization recommendations for Microsoft SQL Server and Oracle systems in rehosting and replatforming scenarios.\n- Enterprise platforms. Includes the ability to collect details from proprietary operating systems like AIX and Solaris, or infrastructure such as AS/400 and mainframe.\n\nWhen evaluating each feature, consider how much of your environment it applies to, and how important it is for the overall objective. It’s a good practice to deprioritize rather than completely eliminating tools that don’t provide a specific feature.\n\n##### *Provisioning*\nOnce you run through the minimum, common, and special feature requirements, further refine the tool list by evaluating the challenges associated with the provisioning process of each tool. For example, consider aspects like data residency and the cost model. Read [Evaluating the need for discovery tooling ](https://docs.aws.amazon.com/prescriptive-guidance/latest/application-portfolio-assessment-guide/understanding-initial-assessment-data-requirements.html#discovery-tooling) for a detailed list of provisioning criteria.\n\n##### *Operations*\nFinally, refine your tool list further by evaluating the requirements to operate the tool. This includes considerations like the running cost and the support model.\n\n#### **Step 3: Select**\nAt this stage, you should have a shortlist of preferred discovery tools, with only one or two tools remaining for final evaluation.\n\nAll of these shortlisted tools should fulfill your requirements. You can further refine your selection by choosing the tool that best fits your priorities. For example, if only two tools remain in your shortlist and ease of installation and operation are paramount, then select the tool with the highest levels of deployment automation. If cost is your main constraint, then select the least expensive tool to acquire and operate.\n\n#### **Conclusion**\nTools from Amazon Web Services and [Amazon Web Services Partners](https://aws.amazon.com/partners/) can help accelerate your migration to the Amazon Web Services Cloud. To select the relevant discovery tool for your specific use case, we recommend the following proven three-step approach:\n\n- **Review –** Start by reviewing existing in-house capabilities, tools, and data sources. By the end of this step, you should establish if your in-house tools are sufficient for your cloud migration objectives.\n- **Refine –** Narrow down a list of candidate discovery tools by filtering and prioritizing them based on the requirements from the previous step.\n- **Select –** Filter the final list of suitable discovery tools by selecting the tool that best addresses your priorities.\n\n\n\n**David Ninnis**\nDavid is a Senior Manager leading a team of Migration and Modernization Specialist Solutions Architects. With 25+ years of enterprise IT experience, David drives change at all organizational layers, and is passionate about diving deep with customers to architect creative solutions to some of the most complex challenges in cloud computing. David collects acrylic blocks holding the last processor retired from large corporate datacenters after migration. He’s coming for yours...\n\n\n\n**Ashish Ameta**\nAshish is a Senior Architect at Amazon Web Services Professional Services. He helps customers to build a foundation for cloud Migration and Modernization that is scalable and aligns with their business strategy. He works with enterprise architects and business leaders to devise and implement a holistic cloud migration/modernization approach that encompasses people, process, and technology.\n\n\n\n**Jorge Fonseca**\nJorge is a Senior Solutions Architect and entrepreneur with 20+ years in IT, holding 13 Amazon Web Services certifications, 2 master degrees in Computer Science and Enterprise Management, and multiple Agile Management certifications. At Amazon Web Services, he drives customers through their cloud journeys by converting complex challenges into actionable roadmaps for both technical and business audiences. Jorge is also an SME for migration and modernization, travel and hospitality, chaos engineering, and emotional intelligence.","render":"<p>Cloud migrations invariably require the coordination of multiple stakeholders, such as business and technical teams, partners, and third-party providers. As a stakeholder, understanding your portfolio is crucial to determine which workloads to migrate, and their requirements and interdependencies. But manually gathering these insights can be a daunting task. You can inform your decision by provisioning a discovery tool.</p>\n<p>Given the variety of choices available, choosing the appropriate discovery tool for your use case can also be challenging. In this blog post, we explain a proven three-step technique to successfully filter and prioritize a list of discovery tools based on the essential features needed for your business.</p>\n<p><img src=\\"https://dev-media.amazoncloud.cn/53ba15c5cb57475ca9e010fcf3ac3686_image.png\\" alt=\\"image.png\\" /></p>\n<p>Figure 1. Steps to determine your migration discovery tool</p>\n<h4><a id=\\"Step_1_Review_8\\"></a><strong>Step 1: Review</strong></h4>\\n<p>Review the outcomes that your migration journey should deliver. These will drive your discovery requirements and baseline the features needed. Compare the baseline features with existing tools within your organization such as Configuration Management Databases (CMDBs) or Application Performance Management (APM) tooling. By the end of this Review step, you should establish if your in-house tools are sufficient for your objectives. Here is a list of <a href=\\"https://docs.aws.amazon.com/prescriptive-guidance/latest/migration-portfolio-discovery/data-collection.html#decide_how_gather\\" target=\\"_blank\\"> questions to support your migration analysis.</a>.</p>\\n<p>You may need to collect high-level data or complete datasets depending on your stage in the <a href=\\"https://aws.amazon.com/cloud-migration/how-to-migrate/\\" target=\\"_blank\\">migration process</a>. You may be exploring migration costs to assess the lift-and-shift migration threshold of a benefit program such as <a href=\\"https://aws.amazon.com/migration-acceleration-program/\\" target=\\"_blank\\"> Amazon Web Services Migration Acceleration Program (MAP)</a>. In this case, you probably only need a snapshot of your on-premises environment with a list of servers, their configurations, and attached licenses. You may be evaluating the [ Total Cost of Ownership (TCO)](Total Cost of Ownership (TCO)) between your on-premises infrastructure and an elastic deployment model on the cloud. In this case, you’ll want to be able to estimate the cost of a right-sized cloud infrastructure. For that, you will want to run a discovery tool for the duration of a business cycle.</p>\\n<p>Finally, to decide how and when applications are going to migrate, you will need a complete and accurate dataset with the application and database features to be migrated. This must include network dependencies, non-functional requirements (NFRs), disaster recovery (DR) plans, and third-party licensing terms and conditions (T&amp;C).</p>\n<p>Conclude this step by baselining the features that you require in the discovery tool.</p>\n<h4><a id=\\"Step_2_Refine_17\\"></a><strong>Step 2: Refine</strong></h4>\\n<p>This step is an elimination process. One of the resources you can use to compile a list of candidate discovery tools is the <a href=\\"https://aws.amazon.com/prescriptive-guidance/migration-tools/migration-discovery-tools/\\" target=\\"_blank\\">Discovery migration tool comparison</a> page. Filter and sort the list using the following criteria categories:</p>\\n<ol>\\n<li>Core features</li>\n<li>Common features</li>\n<li>Special features</li>\n<li>Tool provisioning</li>\n<li>Operation</li>\n</ol>\\n<p>By the end of this step, you should have a prioritized list of the discovery tools that optimally match your requirements.</p>\n<h5><a id=\\"Core_features_28\\"></a><em>Core features</em></h5>\\n<p>Following are the basic set of features that you should expect from any discovery tool. Analysis of the data captured by these features will support your high-level business case.</p>\n<ul>\\n<li><strong>Automatic inventory collection</strong>. Reports on the infrastructure profile, such as CPU family, CPU cores, memory size, disk size and speed, and operating system.</li>\\n<li><strong>Utilization</strong>. Shows peak and average utilization of CPU, memory, and disk.</li>\\n<li><strong>Network storage discovery</strong>. Detects and profiles network shares from network-attached storage (NAS).</li>\\n<li><strong>Software</strong>. Identifies running processes and installed software, pinpointing database engines and their versions.</li>\\n<li><strong>Network scanning</strong>. Scans network subnets to discover unknown infrastructure assets.</li>\\n</ul>\n<h5><a id=\\"Common_features_36\\"></a><em>Common features</em></h5>\\n<p>Here are some common features of discovery tools. With this data, you will be able to create a more detailed TCO analysis and migration plan.</p>\n<ul>\\n<li><strong>Lift-and-shift cost estimation</strong>. Maps a recommended target Amazon Web Services infrastructure for the rehost of the source infrastructure, and calculates the Amazon Web Services cost.</li>\\n<li><strong>Target sizing recommendation</strong>. Maps and calculates the cost for alternative target Amazon Web Services infrastructures based on the peak and average utilization.</li>\\n<li><strong>TCO analysis</strong>. Provides a cost comparison between current on-premises cost and projected Amazon Web Services cost.</li>\\n<li><strong>Dependency mapping</strong>. Collects network connection information and builds inbound and outbound dependency maps of the servers and running applications. Infers applications from groups of infrastructure resources based on communication patterns.</li>\\n<li><strong>Application prioritization</strong>. Assigns weight or relevance to application and infrastructure attributes to create prioritization criteria for migration.</li>\\n<li><strong>Wave planning</strong>. Recommends groups of applications and the ability to create migration wave plans.</li>\\n</ul>\n<h5><a id=\\"Special_features_46\\"></a><em>Special features</em></h5>\\n<p>Special features map to less common requirements, or to a specific set of the workloads you want to migrate. For example, you may require your tools to collect database dependency information if databases form a significant part of your workloads. If you have strict regulatory compliance to follow (HIPAA, GDPR), you’ll need tools that comply with these regulations. Other examples are:</p>\n<ul>\\n<li><strong>Licensing analysis</strong>. Provides optimization recommendations for Microsoft SQL Server and Oracle systems in rehosting and replatforming scenarios.</li>\\n<li>Enterprise platforms. Includes the ability to collect details from proprietary operating systems like AIX and Solaris, or infrastructure such as AS/400 and mainframe.</li>\n</ul>\\n<p>When evaluating each feature, consider how much of your environment it applies to, and how important it is for the overall objective. It’s a good practice to deprioritize rather than completely eliminating tools that don’t provide a specific feature.</p>\n<h5><a id=\\"Provisioning_54\\"></a><em>Provisioning</em></h5>\\n<p>Once you run through the minimum, common, and special feature requirements, further refine the tool list by evaluating the challenges associated with the provisioning process of each tool. For example, consider aspects like data residency and the cost model. Read <a href=\\"https://docs.aws.amazon.com/prescriptive-guidance/latest/application-portfolio-assessment-guide/understanding-initial-assessment-data-requirements.html#discovery-tooling\\" target=\\"_blank\\">Evaluating the need for discovery tooling </a> for a detailed list of provisioning criteria.</p>\\n<h5><a id=\\"Operations_57\\"></a><em>Operations</em></h5>\\n<p>Finally, refine your tool list further by evaluating the requirements to operate the tool. This includes considerations like the running cost and the support model.</p>\n<h4><a id=\\"Step_3_Select_60\\"></a><strong>Step 3: Select</strong></h4>\\n<p>At this stage, you should have a shortlist of preferred discovery tools, with only one or two tools remaining for final evaluation.</p>\n<p>All of these shortlisted tools should fulfill your requirements. You can further refine your selection by choosing the tool that best fits your priorities. For example, if only two tools remain in your shortlist and ease of installation and operation are paramount, then select the tool with the highest levels of deployment automation. If cost is your main constraint, then select the least expensive tool to acquire and operate.</p>\n<h4><a id=\\"Conclusion_65\\"></a><strong>Conclusion</strong></h4>\\n<p>Tools from Amazon Web Services and <a href=\\"https://aws.amazon.com/partners/\\" target=\\"_blank\\">Amazon Web Services Partners</a> can help accelerate your migration to the Amazon Web Services Cloud. To select the relevant discovery tool for your specific use case, we recommend the following proven three-step approach:</p>\\n<ul>\\n<li><strong>Review –</strong> Start by reviewing existing in-house capabilities, tools, and data sources. By the end of this step, you should establish if your in-house tools are sufficient for your cloud migration objectives.</li>\\n<li><strong>Refine –</strong> Narrow down a list of candidate discovery tools by filtering and prioritizing them based on the requirements from the previous step.</li>\\n<li><strong>Select –</strong> Filter the final list of suitable discovery tools by selecting the tool that best addresses your priorities.</li>\\n</ul>\n<p><img src=\\"https://dev-media.amazoncloud.cn/41b066a232064953b26150c75c141b78_image.png\\" alt=\\"image.png\\" /></p>\n<p><strong>David Ninnis</strong><br />\\nDavid is a Senior Manager leading a team of Migration and Modernization Specialist Solutions Architects. With 25+ years of enterprise IT experience, David drives change at all organizational layers, and is passionate about diving deep with customers to architect creative solutions to some of the most complex challenges in cloud computing. David collects acrylic blocks holding the last processor retired from large corporate datacenters after migration. He’s coming for yours…</p>\n<p><img src=\\"https://dev-media.amazoncloud.cn/1524b87fa8fc4355b9e18ba2f018dff9_image.png\\" alt=\\"image.png\\" /></p>\n<p><strong>Ashish Ameta</strong><br />\\nAshish is a Senior Architect at Amazon Web Services Professional Services. He helps customers to build a foundation for cloud Migration and Modernization that is scalable and aligns with their business strategy. He works with enterprise architects and business leaders to devise and implement a holistic cloud migration/modernization approach that encompasses people, process, and technology.</p>\n<p><img src=\\"https://dev-media.amazoncloud.cn/bcbc63dacda643d387883624fbff6f38_image.png\\" alt=\\"image.png\\" /></p>\n<p><strong>Jorge Fonseca</strong><br />\\nJorge is a Senior Solutions Architect and entrepreneur with 20+ years in IT, holding 13 Amazon Web Services certifications, 2 master degrees in Computer Science and Enterprise Management, and multiple Agile Management certifications. At Amazon Web Services, he drives customers through their cloud journeys by converting complex challenges into actionable roadmaps for both technical and business audiences. Jorge is also an SME for migration and modernization, travel and hospitality, chaos engineering, and emotional intelligence.</p>\n"}