Hi all,
Docs for AGC/Isolated Cloud only cover Data Center → Cloud migration. Is a Commercial Cloud → AGC/Isolated Cloud path planned?
If it ever ships, a key problem: Forge installations of the same app get a different app key on Commercial Cloud vs. AGC vs. Isolated Cloud. That breaks anything keyed by app key:
1. Forge Storage (KVS, Forge SQL, Object Store) - does this data move with the site, or is it on each vendor to build their own export/import?
2. Issue properties used for JQL search - two failure modes depending on how the property key is built:
- Key includes the app key: issue migrates fine, but the property key no longer matches (different app key in the new cloud) → JQL search silently breaks until the app rewrites every property with the new key.
- Key is app-key-agnostic (same everywhere): the property key survives, but the app’s own backend data behind it may not have migrated → JQL can return stale/wrong matches until the app clears those properties.
Since the app key will necessarily differ between clouds, would Atlassian rewrite entity property keys automatically during migration (old key → new key), or expose an API/notice ahead of cutover so vendors can remediate properties themselves right after migration?
3. Custom fields - field key and schema key are also app-key-scoped. Would custom field definitions + values migrate at all (given the old key won’t match any app in the destination), get dropped, or get remapped to the new installation?
Any pre-GA / directional guidance from Atlassian would help us build the right safeguards ahead of time. Thanks!