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

We recommend that you consider the following next steps:

1. [Learn how organizations use Teradata Vantage](https://www.teradata.com/Customers) to connect and analyze data across their entire ecosystem, including data lakes, object stores, and cloud services.

1. 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) in the Teradata documentation.

1. 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) in the Teradata documentation.

1. Assess the costs of running Teradata VantageCloud Enterprise on AWS. For more information, see [Teradata VantageCloud Pricing](https://www.teradata.com/Cloud/Pricing) in the Teradata documentation.

1. Make sure that you meet all the prerequisites for a migration based on the [Prerequisites](prerequisites.md) section of this guide. Teradata makes a commercially reasonable effort to make Teradata Vantage available on AWS systems 24/7/365. Teradata targets an SLA (excluding planned downtime) of 99.9 percent measured monthly. For operating model and services options, see [Teradata Vantage on AWS](https://www.teradata.com/Cloud/AWS) in the Teradata documentation.

1. Define your security requirements. For more information on security compliance, see [Cloud Data Security as-a-service](https://www.teradata.com/Cloud/Data-Security) in the Teradata documentation.