@Tei M. A bit of the opposite. Atlassian Govt Cloud (AGC) is a new product and the migration path is commonly from commercial dc or cloud into agc. As @Denise Ellis said, it's somewhat a niche and uncommon path to go the opposite way. Atlassian does not currently have any migration assistant products in the opposite direction, which means such a migration would involve some sort of a 3rd party tool ETL process over API. That likely means whatever configs and data that cannot be pulled out via API would need to be re-created through some other means. Provided newness of this product, Atlassian has some experience migrating in, and virtually none with migrating out.

I'm interested. Reach out on linkedin

Not all users have to be managed users, but having users managed via Okta allows certain automations around joining/leaving.

I've written an agent to help write scripts/speaking points for Jira Custom Onboarding. The intent is that it will read an onboarding template and can generate both the 500char summaries for onboarding, and the 5min video script. More info here: https://community.atlassian.com/forums/Jira-Cloud-Admins-articles/From-Zero-to-Scalable-Building-a-Custom-Jira-Onboarding/ba-p/3212524

@Tei M. my former org had both BambooHR and then Hibob. We had Okta, so users were added via Okta Workflow into Jira, JSM, Confluence groups. Did not have users as Asset Objects, but i wouldn't be surprised if the process was the same.