# Key requests migration SaaS

**URL:** <https://community.dynatrace.com/t/key-requests-migration-saas/43855>\
**Category:** Upgrade To Saas\
**Tags:** key-requests, upgrade-to-saas\
**Created:** [January 26, 2024, 2:00pm UTC](https://community.dynatrace.com/t/key-requests-migration-saas/43855 "2024-01-26T14:00:06Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![arild\_palencia3](https://avatars.discourse-cdn.com/v4/letter/a/4491bb/32.png) [@arild\_palencia3](https://community.dynatrace.com/u/arild_palencia3)\
**Post date:** [January 26, 2024, 2:00pm UTC](https://community.dynatrace.com/t/key-requests-migration-saas/43855/1 "2024-01-26T14:00:06Z")

</div>

Hi!  
We are migrating from DT Managed to SaaS. Anyone knows what happens to the marked key requests during the config migration? We are using the oneagent re-route option.

Regards  
Arild

---

<div class="post-metadata">

**Author:** ![dannemca](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/dannemca/32/7215_2.png) [@dannemca](https://community.dynatrace.com/u/dannemca)\
**Post date:** [January 26, 2024, 2:55pm UTC](https://community.dynatrace.com/t/key-requests-migration-saas/43855/2 "2024-01-26T14:55:39Z")

</div>

Your key requests will not be migrated, since they are part of Services entities and they will also be “new entities” in your SaaS.

> **[Data migration - Plan deployment upgrade](https://docs.dynatrace.com/managed/upgrade/up-plan#data-migration)**
>
> During the Plan phase you collect requirements, adjust to differences, create a scope, and decide on the approach to upgrading to SaaS. The Plan phase should result in a detailed plan for performing the upgrade to SaaS deployment and a well-prepared...

You can use [Monaco](https://docs.dynatrace.com/managed/manage/configuration-as-code#upgrade-from-managed-to-saas-deployment), or play with [APIs](https://docs.dynatrace.com/docs/dynatrace-api/environment-api/settings/objects/put-object) to make sure the same requests will be marked as Key Request in your SaaS env.

Example, you can list (get) all the current key requests you currently have in your Managed env, schemaid: builtin:settings.subscriptions.service, and then post it, for each service (objectid) once they are ready in SaaS env.

---

<div class="post-metadata">

**Author:** ![Eric\_Yu](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/eric_yu/32/20360_2.png) [@Eric\_Yu](https://community.dynatrace.com/u/Eric_Yu)\
**Post date:** [January 26, 2024, 2:58pm UTC](https://community.dynatrace.com/t/key-requests-migration-saas/43855/3 "2024-01-26T14:58:45Z")

</div>

While migrating configurations, KeyRequests are associated to a specific Service ID. So, when re-routing the OneAgent traffic you’ll have to check if the new Service ID on SaaS is the same one as the one in Managed (not likely).

 ![Eric_Yu_1-1706279882647.png](https://global.discourse-cdn.com/dynatrace/original/3X/d/0/d00700a8dba2228ca068a1463ebd71e02f71d85b.png)

 ![Eric_Yu_0-1706279833723.png](https://global.discourse-cdn.com/dynatrace/original/2X/3/395e10e69ed8be53262e6589fda57ecb3bbbefa8.png)

If is not the same ID, you can either reconfigure KeyRequests for each service through the UI or, better, modify the scope (serviceId or objectId) during the migration of your Key Requests configuration (either [Monaco](https://docs.dynatrace.com/managed/shortlink/configuration-as-code) or API).

> **[Monitor key requests in Services Classic](https://docs.dynatrace.com/docs/observe/application-observability/services-classic/services-page/monitor-key-requests)**
>
> Discover how to closely monitor requests that are critical to your business.

> **[Settings API - GET a schema](https://docs.dynatrace.com/docs/dynatrace-api/environment-api/settings/schemas/get-schema)**
>
> View a settings schema via the Dynatrace API.

---

<div class="post-metadata">

**Author:** ![dcryans](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/dcryans/32/14318_2.png) [@dcryans](https://community.dynatrace.com/u/dcryans)\
**Post date:** [February 13, 2024, 7:35pm UTC](https://community.dynatrace.com/t/key-requests-migration-saas/43855/4 "2024-02-13T19:35:54Z")

</div>

Hi,

Often, service IDs will be the same in both tenants because of the algorithm that creates the ID.

But you are right, IDs may and will change during a migration  
If you do not want to bother manually matching thousands of IDs across tenants, you may be interested in trying the Config Manager:

> **[Migrate configuration](https://docs.dynatrace.com/managed/upgrade/up-execute-upgrade/up-migrate-cfg#config-manager)**
>
> Migrate your Dynatrace Managed environment configuration using Monaco.

The config manager will match every type entity IDs using their properties (name, ip address, etc.), but also topology (relationships). Then they will be automatically replaced in your configs.

---

<div class="post-metadata">

**Author:** ![sa\_gopalm](https://avatars.discourse-cdn.com/v4/letter/s/c5a1d2/32.png) [@sa\_gopalm](https://community.dynatrace.com/u/sa_gopalm)\
**Post date:** [July 24, 2025, 7:16am UTC](https://community.dynatrace.com/t/key-requests-migration-saas/43855/5 "2025-07-24T07:16:08Z")

</div>

$headers = New-Object “System.Collections.Generic.Dictionary[[String],[String]]”  
$headers.Add(“Authorization”, “Api-Token dt0c01.xxxxxxxxxxx”)  
$headers.Add(“Content-Type”, “application/json”)

$body = @"  
[  
{  
`“schemaId`”: `“builtin:settings.subscriptions.service`”,  
`“scope`”: `“SERVICE-B75 ****** `”,  
`“value`”: {  
`“keyRequestNames`”: [  
`“getReservatio`”  
]  
}  
}  
]

"@

$response = Invoke-RestMethod ‘https://{environmentid}.live.dynatrace.com/api/v2/settings/objects’ -Method ‘POST’ -Headers $headers -Body $body  
$response | ConvertTo-Json

This will make a request to key request via api call

---

<div class="post-metadata">

**Author:** ![erh\_inetum](https://avatars.discourse-cdn.com/v4/letter/e/48db29/32.png) [@erh\_inetum](https://community.dynatrace.com/u/erh_inetum)\
**Post date:** [August 21, 2026, 7:27am UTC](https://community.dynatrace.com/t/key-requests-migration-saas/43855/6 "2026-08-21T07:27:36Z")

</div>

hi&nbsp;[@arild\_palencia3](https://community.dynatrace.com/user/30869)&nbsp;,

You can migrate key web request with SaaS Upgrade Assistant.

You can find your key web requests in “builtinsettings.subscriptions.service” config type

 ![erh_inetum_1-1787297212806.png](https://global.discourse-cdn.com/dynatrace/original/2X/0/09ee6c0cf736ceee0ea7a4cf181ca1582306edc8.png)

Hope it helps.

Regards,

Elena.
