HubSpot CRM for JiraHubSpot CRM for Jira
Try For Free

Migrating from Connect to Forge

HubSpot for Jira has moved to Atlassian Forge, Atlassian's hosted app platform. Forge runs the app inside Atlassian's own infrastructure, which improves security, performance and reliability.

The upgrade is performed by a Jira administrator and takes a few minutes. Your linked HubSpot records, permissions and field mappings carry over automatically.

Who performs the upgrade

Only a Jira administrator can upgrade the app. If you are not an administrator, you will see a notice asking you to contact one. Your linked HubSpot records are not affected while you wait.

What carries over automatically

The migration copies your existing configuration from the Connect version to the Forge version:

  • The HubSpot connection, including the connected portal

  • View permissions: groups, spaces, internal comment settings and the selected view fields

  • Write permissions: the groups allowed to create or update, and the editable field lists

  • Field mappings between HubSpot properties and Jira fields

  • Links between HubSpot records and Jira work items

  • Automation rules

In most cases no reconfiguration is needed after the upgrade.

What does not carry over

Audit log history is not migrated. Audit log entries recorded by the previous version stay with that version and do not appear in the Forge app's Audit Log. The Forge Audit Log begins recording from the moment the migration completes.

If you need to retain the earlier history for compliance or reporting, export or record it before you upgrade.

Features that changed

Auto-display HubSpot panel has been removed. The previous version had a setting under Synchronize Data that let administrators choose Jira spaces in which the HubSpot panel opened automatically on every work item.

In the Forge version, users open the panel from the work item themselves: use the button row under the work item title, select View app actions, then HubSpot CRM. There is no per-space auto-open setting to configure or migrate.

Before you upgrade

The migration carries configuration across automatically, but recording your current setup gives you a reference to check against afterwards. Note the following from the existing app:

  1. The connected HubSpot portal name and Hub ID

  2. The Jira spaces available for the HubSpot integration

  3. View permission settings, including groups and selected fields

  4. Write permission settings, including editable fields

  5. Field mapping configuration for each object type

  6. Any automation rules, and whether each is active or paused

  7. Audit log entries you need to keep, since these are not migrated

Running the migration

  1. Install or upgrade to the Forge version of HubSpot for Jira. The migration starts automatically on installation and on upgrade.

  2. Wait for the migration to finish. The admin configuration page becomes available while data is still being copied.

  3. Refresh the admin configuration page once the migration completes to see the final state.

After the migration

Confirm that the app is working as expected before removing anything:

  1. Open the admin configuration and check that the HubSpot connection is present and the portal is correct.

  2. Compare view and write permissions against the settings you recorded.

  3. Check that field mappings are intact for each object type.

  4. Open a work item that had linked HubSpot records and confirm the links are still there.

  5. Check your automation rules, including whether each is still in the state you expect.

The app may show onboarding prompts after the migration suggesting configuration steps. Because your configuration has already been carried over, these are prompts rather than required actions. Review them against your recorded settings and dismiss the ones that do not apply.

Re-running the migration

The migration runs once. If the app is uninstalled and reinstalled, the admin configuration reports that the data was already migrated rather than importing it a second time. This prevents duplicate records. Contact resolution support if you need the data imported again.