# Next steps
<a name="next-steps"></a>

We recommend that you consider the following next steps:
+ [Learn how organizations use Teradata Vantage](https://www.teradata.com/Customers) to connect and analyze data across their entire ecosystems, including data lakes, object stores, and cloud services.
+ Identify the migration workloads in your on-premises environments or other cloud environments. Then, review your [deployment options](https://www.teradata.com/Cloud/Deployment-Options) and identify your destination environment. For more information, see [Teradata Vantage on AWS](https://www.teradata.com/Cloud/AWS) on the Teradata website.
+ Choose either a rehost (that is, lift and shift) or replatform (that is, make some workload changes) migration strategy. For more information, see [Lift-and-shift Cloud Migration](https://www.teradata.com/insights/data-analytics/lift-and-shift-migration) and [A Guide to Cloud Migration](https://www.teradata.com/insights/data-architecture/cloud-migration-guide) on the Teradata website.
+ Assess the costs of running Teradata VantageCloud on AWS. For more information, see [Teradata VantageCloud Pricing](https://www.teradata.com/Cloud/Pricing) on the Teradata website.
+ Make sure that you meet all the prerequisites for a migration based on the [Prerequisites](introduction.md#prereq) section of this guide.

**Note**  
Teradata makes a commercially reasonable effort to make Teradata Vantage available on AWS all day, every day. Teradata targets a service-level agreement (SLA) of 99.9 percent (excluding planned downtime), measured monthly. For operating model and services options, see [Teradata Vantage on AWS](https://www.teradata.com/Cloud/AWS) on the Teradata website.