# Deploy archival settings

**URL:** <https://forums.pega.com/t/deploy-archival-settings/8280>\
**Category:** General\
**Tags:** 8-8-5, team-lead, 23-1-3, installation-and-deployment, system-administration, case-management\
**Created:** [September 16, 2024, 3:10pm UTC](https://forums.pega.com/t/deploy-archival-settings/8280 "2024-09-16T15:10:20Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![RodrigoA17233239](https://avatars.discourse-cdn.com/v4/letter/r/cdc98d/32.png) [@RodrigoA17233239](https://forums.pega.com/u/RodrigoA17233239)\
**Post date:** [September 16, 2024, 3:10pm UTC](https://forums.pega.com/t/deploy-archival-settings/8280/1 "2024-09-16T15:10:20Z")

</div>

**What is the best practice to deploy case archival configuration?**

Deploying case type’s the pyDefault seems not enough.

Achival configrations were made in DEV env and a product was created with case type’s pyDefault.

In STG, no archival config was there after the deploy.

* * *

We also tried to send the Data-Retention-Policy associated instance, but the is listed but couldn’t be open.

There are a thew more instances from other classes related to archival…but it doesn’t look like it should be done this way? We are on cloud w/ Pega 23.

---

<div class="post-metadata">

**Author:** ![MarijeSchillern](https://yyz2.discourse-cdn.com/pega/user_avatar/forums.pega.com/marijeschillern/32/23321_2.png) [@MarijeSchillern](https://forums.pega.com/u/MarijeSchillern)\
**Post date:** [October 7, 2024, 7:36pm UTC](https://forums.pega.com/t/deploy-archival-settings/8280/2 "2024-10-07T19:36:09Z")

</div>

@RodrigoA17233239 please log a support incident via the msp and provide the INC id here so that we can help track it.