

# Tagging key combinations
<a name="setting-up"></a>

To better help you find your tagging values, consider the following questions:


+ What AWS service will be the destination for your migration?
+ Where is the source of your migration (on-prem or already in AWS as Amazon EC2)?
+ Are your workloads in the specialized workload list such as SAP or Oracle workloads?



Use the tagging decision tree shown in the following diagram to help you assign the tag value for your migrated workloads. For a complete list of services that are included in MAP 2.0, see the MAP 2.0 Included Services list: **https://s3-us-west-2.amazonaws.com/map-2.0-customer-documentation/included-services/MAP\_Included\_Services\_List.pdf**. 

The following diagram shows the decision tree for selecting the appropriate tag value:

![Decision tree flowchart for selecting MAP 2.0 tag values based on migration source, destination, and workload type](https://docs.aws.amazon.com/MAP/latest/transform-userguide/images/MAP-tagging-flowchart.png)






**To get started**
+ Where are you migrating to?

  
  + **Services included in the Service list**
  + **SAP included in the Service list**
  + **Oracle included in the Service list**
  + **Database and analytics included in the Service list**: For more information, see [Database and analytics tags](DBA-tags.md).

  

**Note**  
Use lowercase letters for the `mig`, `sap`, and `oracle` prefixes. For more information about your PRM ID, see [PRM ID length](mpe-length.md).

## Services
<a name="setting-up-services"></a>

`mig{{PRM ID}}`

*Example: *`migra-abcdefg123456`

## SAP
<a name="setting-up-sap"></a>

`sap{{PRM ID}}`

*Example: *`sapra-abcdefg123456`

## Oracle
<a name="setting-up-oracle"></a>

`oracle{{PRM ID}}`

*Example: *`oraclera-abcdefg123456`