Data migration from Connect app to Forge

Forge Adopting Forge from Connect
, , , ,
1

Hi community,

I’m currently migrating my existing Connect app to Forge, aiming to eventually run all functionality on Forge. My main challenge is migrating the data from the Connect app to the Forge app.

I’ve tried making API calls, but noticed that JWTs in Connect and Forge have different structures, which prevents me from using Connect JWTs to authenticate on Forge endpoints.

My main question is: what is the recommended way to transfer data from a Connect app to a Forge app? Are there any official or practical approaches to migrate existing instance data into Forge, considering JWT differences?

1 Like
2

Hi @MuhammetSnmez ,

The official Connect frameworks support both Connect and Forge auth. In Atlassian Connect for Node.js Express, for instance, you could have something like this (perhaps hit periodically via a Forge scheduled trigger):

app.get("/migrate", [addon.authenticateForge(), addon.associateConnect()], async (req, res) => {
  const dataToMigrate = addon.settings.get("data", req.context.clientKey);
  const forgeClient = addon.forgeHttpClientAsApp(req);
  // Then use the Forge Storage api with forgeClient to upload dataToMigrate
});