High-level migration overview
The following table shows a high-level overview of an OpenText TeamSite and Media Management migration to the AWS Cloud.
| Workload | Source workload | OpenText Customer Experience solutions: |
| Source environment | On premises or on another cloud provider. | |
| Migration | Migration strategy (7 Rs) |
Depending on your source environments, you can use the following migration strategies:
|
| Is this an upgrade in workload version? | No | |
| Is the source workload different from an independent software vendor (ISV) workload? | No | |
| Estimated migration duration | Depending on your source environment, a migration can take between two and three weeks. | |
| Estimated cost | Estimated cost of running ISV workloads on the AWS Cloud | A sample cost structure for three environments (development, QA-UAT, and production)
using ELB and a
DevOps toolset for development and deployment is available in this
estimate |
| Assumptions and prerequisites | Minimum and maximum system requirements | Check the compatibility matrix for your OpenText product version. This matrix is
available in the release notes on the OpenText
support portal |
| Service-level agreements (SLAs) | You can meet SLAs with a basic setup that uses ELB, AWS Lambda functions, and two Availability Zones. | |
| Licensing and operating model in the AWS account | For more information about your OpenText license agreement, contact your OpenText account manager. | |
| AWS services used in the AWS account |
