Migrating data from custom database before moving to Forge

Forge
1

Hi all,

We’re currently working on migrating our Atlassian Connect app to Forge, and we’re exploring how to best handle the migration of existing customer-specific data.

As part of the migration path, we’re considering using App Properties as an intermediate step — moving data from our own database into App Properties before eventually storing it in Forge.

We’re wondering if there is anyone else here who have gone through a similar process and could answer the following questions:

  1. Have you migrated data from a custom backend database to App Properties?
  2. What challenges or limitations did you encounter?
  3. Are there alternative or better strategies you would recommend for apps moving from Connect to Forge?

Any tips, examples, or lessons learned would be incredibly helpful.

Thanks in advance! :raising_hands:

2

Hey @PaulinaBuzderewicz,

If you’re planning to use KVS or ESS to store data like properties or configuration, you can use Forge Remote as an interim stepping stone to bringing that data into the Forge environment. If you use one of the Connect Frameworks, this will simplify this further, as it supports Forge Remotes out of the box.

A sample pathway to migrating data could look like:

  1. Listen for the Connect installation event which will not contain a Forge installationId
  2. Subscribe to the Forge installation event to your remote
  3. Utilise the remote token to interact with Forge Storage

With that said, this is one potential approach. As you’ve noted, an app migrated from Connect to Forge can continue to access the Connect app properties as long as the app.connect.key is aligned to the same app id. In this circumstance, you could then read this data in Forge and write it to Forge storage.

1 Like