...
Click Configure the migration.
Choose your preferred migration approach:
Automated updates – Check the box labeled Yes, update them to automatically update existing issue data. Note that this may can trigger automation rules or impact reports.
Manual configuration – Leave the box unchecked if you prefer to manage configurations manually.
Important
If you leave the box unchecked, all asset data stored in the old custom field will be lost when the External Assets Platform is shut down on . If you only have a small number of issues, you can update them manually. For a large number of issues, we strongly recommend bulk updating:
Use a Jira automation rule to transfer values from the old (external) asset custom field to the new one.
You can use a scripting tool such as ScriptRunner to streamline this process. If you need any assistance, contact our Support team.
Step 2: Data migration
The migration process automatically maps existing data from the deprecated custom field to the new one.
Process:
Select your migration path – The administrator needs to acknowledge the migration process to start the process.
Upgrade the application – Install the new Forge-based version of the app.
Migration begins automatically – When the admin upgrades to the Forge app, the migration starts automatically.
Monitor progress – Real-time updates will be displayed during the migration.
...