# Migrating in different namespaces?

**URL:** <https://forum.ansible.com/t/migrating-in-different-namespaces/6045>\
**Category:** Get Help\
**Tags:** awx-operator, awx, kubernetes\
**Created:** [May 28, 2024, 8:22pm UTC](https://forum.ansible.com/t/migrating-in-different-namespaces/6045 "2024-05-28T20:22:45Z")\
**Posts on this page:** 1\
**Showing post:** 12

<div class="post-metadata">

**Author:** ![Denney-tech](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/denney-tech/32/1556_2.png) [@Denney-tech](https://forum.ansible.com/u/Denney-tech)\
**Post date:** [June 10, 2024, 8:31pm UTC](https://forum.ansible.com/t/migrating-in-different-namespaces/6045/12 "2024-06-10T20:31:43Z")

</div>

_Apparently_, the migrations assume that the old config secret must refer to a managed instance, even though specifying a current config secret (without anything else) implies an unmanaged instance. I apologize, I didn’t think it worked like that.

What I think you can do instead, is migrate the data yourself directly from crunchy to cnpg, and then spin up a new awx-cnpg instance with only the secrets it needs for the cnpg database (i.e. leave out `old_postgres_configuration_secret`). I have a detailed post relating to migrating data between two pods for a botched upgrade. You’ll have to fiddle with the targeted hosts, username, and passwords, but I think it should work. I had the luxury of being able to use the environment variables and re-using the same credentials between hosts.

> [@ATTENTION - do NOT upgrade to AWX operator to 2.13.0](http://forum.ansible.com/t/attention-do-not-upgrade-to-awx-operator-to-2-13-0/4363/8):
>
> Well I had a fun day today. I had problems with upgrading from 2.12.1 to 2.13.1, but not necessarily because of a bug, but more of an oversight. I had set postgres\_image: to the redhat sclorg image, which was still pinned to 13 after the operator upgrade. This led to the operator creating the new postgresql-15 statefulset using the postgresql-13 image, performing the pg\_dump/pg\_restore successfully and leaving me with a new operator on a new but old db. Thankfully I had taking a volume snapsho…

---

_[View the full topic](https://forum.ansible.com/t/migrating-in-different-namespaces/6045)._
