This impacts badly to our cloud migration strategy. 

https://getsupport.atlassian.com/browse/MOVE-1747709

At least document the format changes. Having a list of changed formats, for example the changes in the format of headers on outgoing webhooks
This makes it possible to write scripts to reformat rule json to the cloud format.
The error messages from the importer are not really helpful, because in the case of false headers formatting on outgoing webhooks, point to somewhere in the string, bud not to the real problem:

Server:

"headers": [{
                    "id": "_header_1615780177907",
                    "name": "Secret",
                    "value": {
                        "keyOrValue":"hhjksafvn838vflwrb845vtlocbo845ucbo45bco8u45cc49",
                        "secret": false
                    }
                }],

Cloud:

"headers": [{
                    "id": "_header_1615780177907",
                    "name": "Secret",
                    "value":"",
                    "keyOrValue": "hhjksafvn838vflwrb845vtlocbo845ucbo45bco8u45cc49",
                    "secret": false
                }],

 note here that "value":

changed to: "value":"",                     "keyOrValue": "hhjksafvn838vflwrb845vtlocbo845ucbo45bco8u45cc49",                     "secret": false

The errormessage from the importer points however to position 162 of the whole string (above is only the changed part shown), which is in the middle of the word 'description' of the json export and therefore not helpfull.

https://getsupport.atlassian.com/browse/MOVE-1736383

We are affected because this feature is not enabled in the migrator after more than 4 years hence we have to migrate the rules manually (not acceptable). I hope that in a near future your colleagues can benefit of this feature.

We will evaluate this track based on headcount and funding in FY24. 

When is FY24?

Server dies at the beginning of 2024 which means we have to complete migrations in 2023. Going to be pretty risky or error prone if the migration tools aren't there ...

Hi Everyone,

We appreciate your patience while we triage this issue internally. 

Currently, the Automation Platform team is ramping up priorities around scale and platform resiliency which means that we currently do not have the capacity to take on work for the Jira Cloud Migration Assistant at this time.

We will evaluate this track based on headcount and funding in FY24. 

Please continue to provide us with your valuable feedback.

Thank you,

Bec 
 

The automation team cannot take up work on Jira Cloud Migration Assistant at this time due to the bandwidth required and current priorities on enterprise scale and platform resiliency. We will evaluate this track based on headcount and funding in FY24. 

@Atlassian: Are there any plans to support this in the meantime?

Since Jira Automation is now also part of the DC offering, I assume more and more future migrations will have to deal with this.

This functionality would be a huge benefit to customers such as us. We have over 200 enabled automation rules and must manually update 60-75% of each post JSON import to the cloud. Elements such as custom field, owner, actor, project association, etc are all broken/orphaned during the manual export/import process. In total it's requiring over 8 hours of work to manually correct migrated automation rules, severely impacting our migration go-live timelines and introducing substantial risk of human error.