Upstream ticket:
https://pagure.io/freeipa/issue/3656

Given that the bz is about migration from on OS to other or one env to other, I linked it to RFE] FreeIPA-to-FreeIPA migration as an additional user story.

This BZ has been evaluated multiple times over the last several years and we assessed that it is a valuable request to keep in the backlog and address it at some point in future. Time showed that we did not have such capacity, nor have it now nor will have in the foreseeable future. In such a situation keeping it in the backlog is misleading and setting the wrong expectation that we will be able to address it. Unfortunately we will not. To reflect this we are closing this BZ. If you disagree with the decision please reopen or open a new support case and create a new BZ. However this does not guarantee that the request will not be closed during the triage as we are currently applying much more rigor to what we actually can accomplish in the foreseeable future. Contributions and collaboration in the upstream community and CentOS Stream is always welcome!
Thank you for understanding
Red Hat Enterprise Linux Identity Management Team

Is there a possibility to just have a DOC (or even "napkin notes" of how to manually export/import things that might be important like DNS, etc?  I get not having the time to create tools but any DOCs on manually doing it would basically be the same thing and if I have a command set I cat create ansible code that I think might be able to do this or at least be a starting point others might be able to build on for a tool to do this.

What I am using to try this is a IDM platform I saved as an image where the KRA certs were deleted so the fix would be basically export what is important, build new, import important parts.

Having done extensive HIGHLY looped/parameterized "AI" like data driven code my plan would be a 2 module approach.  First run a "scraper" module that extracts all needed info out of IDM into a formatted data file (yml).  Then the data file can be altered (like if switching domains, etc) and using true/false switch changes to import or not import data.  Then you run the import module to run all the commands against the new IDM system to then import what is needed.

I'd leave it to someone else to create a ncurses or ui system to walk through modding the data file to import just what is needed, etc.  Possibly the import playbook could be made to be called by a install playbook as well so once you do export and mod the rest (install new then import) is seamless.

We already have Backup and restore solution:
https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/planning_identity_management/backing-up-and-restoring-idm_planning-dns-and-host-names

Migration, from FreeIPA to IdM -- this is quite complicated problem. One of the aspects are the certificates which needs to be regenerated properly. In general, we are not talking only about data to be migrated, we are talking about data which are related to security. So, this type of migration should be properly adopt by IdM, then there could be ansible role for it.

The needinfo request[s] on this closed bug have been removed as they have been unresolved for 500 days