How to Migrate Extension Fields to the Main App

We are committed to the Forge platform for “External Data for Jira Fields” and have closed the functionality gap in the main app that required the Extension App.

Since existing Extension Fields cannot be copied automatically, use this guide to complete your transition from the Extension App.

Migrated fields will be new custom fields, allowing you to migrate or test without disrupting production. After migration, switch to the new fields.

Before you start

  • Identify all Extension Fields to migrate. In “Field Configuration,” look for fields with type:

    • Extension Search

    • Extension Search External

    • Extension Info Panel

    • Extension Asset Field

  • Understand dependencies among Extension Fields before starting.

Step 1 - Create new Custom Fields

Use Jira UI “Settings > Work items > Fields” or the App section “Manage Jira Fields

For each field to migrate, select “+ Add Custom Field” and choose the correct Field Type

Extension Field


Main App Field

External Data Extension - Search Field

extension-search-field

->

External Data - Search Field

search-field

External Data Extension - Search Field (Multiple Choice)

extension-search-field-multi

->

External Data - Search Field (Multiple Choice)

search-field-multi

External Data Extension - Info Panel

extension-info-panel

->

External Data - Info Panel

info-panel

External Data Extension - Asset Field

extension-asset-field

->

External Data - Asset Field

asset-field

Step 2 - Duplicate field configurations

In the “Field Configuration” section, for each existing extension field configuration:

  1. Create a new field configuration by selecting the Duplicate icon.

Screenshot 2026-07-21 at 14.25.04.png
  1. Verify that customfield references in Context Filter and Data source Variables remain valid. This is crucial if the field depends on another Extension Field.

  1. Change the Target Jira Field to the new field from Step 1

Step 3 - Data action

Screenshot 2026-07-21 at 10.11.29.png


In the “Actions” section, for each extension field:

  1. Create a new data action “+ Add New Action”.

  2. Select Extension Field Migration

  3. Select Extension Field Configuration, the field configuration to copy values from.

  4. Select Main Field Configuration, the field configuration to copy values to.

  5. Use a JQL Query like “project=DEMO” and verify with Test JQL

  6. Save.

When Extension Fields have dependencies, create a Data Action for each parent field before running the data action for its child fields. The dependency mapping derives from existing data actions.

Remove any test data actions that might disrupt the field mapping from extension fields to main app fields.

Screenshot 2026-07-21 at 15.00.46.png