Migration mappings do not stay constant. What partners should know about this?

This post outlines some scenarios where a mapping can change over time.

Mappings provide information about how the App migration platform identifies data in cloud that was migrated from server. You can retrieve the mapping for a specific namespace by making a query to the App migration platform from either the server side or the cloud side of your app. Mappings are linked between the server and cloud site, regardless of how many migrations or transfers are completed.

All mappings have lifespan associated with it. After the end of lifespan of namespace mappings, they are not accessible. The table below lists the lifespan of each namespace mappings .

Namespace Lifespan
identity:* 14 days
confluence:* 2 years
jira:* 2 years

Mappings do not stay constant throughout their lifespan. Cloud IDs can change when an entity is deleted and re-migrated at cloud site.

Examples

Following example describes the get mappings in pages endpoint result you would get when a Jira issue was migrated using JCMA.

Request
curl --request GET 'https://your-site.atlassian.net/rest/atlassian-connect/1/migration/mapping/{transferId}/page?namespace=jira:issue' \
--header 'Accept: application/json'
Result after first migration
{
    "meta": {
        "pageSize": 5000,
        "hasNext": false,
        "lastEntity": null
    },
    "items": {
        "10000": "10152"
    }
}
Result after deleting and re-migrating the project
{   "meta": {
        "pageSize": 5000,
        "hasNext": false,
        "lastEntity": null
    },
    "items": {
        "10000": "10153"
   }
}

Following example describes the get mappings by keys endpoint result you would get when a Jira issue was migrated using JCMA.

curl --request POST 'https://your-site.atlassian.net/rest/atlassian-connect/1/migration/mapping/{transferId}/find?namespace=jira:issue' \
--header 'Accept: application/json' \
--header 'Content-Type: application/json' \
--data-raw '["10000"]'
Result after first migration
{
    "10000": "10152"
}
Result after deleting and re-migrating the project
{
    "10000": "10153"
}

Complete list of namespace mappings provided by app migration platform is listed at following page:

https://developer.atlassian.com/platform/app-migration/mappings/#mappings-namespaces-and-entities

1 Like