Migrate from Server/DC

Migration Assistant App doesn’t support Forge apps which are developed using the latest Atlassian cloud development framework. For this reason, progress for WorklogPRO will remain at 0%. But our server app will create some “.json” files as explained below. Give it some time to create these files.

During the migration process from server/DC to cloud, worklogs are automatically transferred by Jira itself. If you don’t need worklog attributes and account values for old worklogs, you don’t need to include WorklogPRO in the migration process. Jira will migrate worklogs anyway and they will be available for the Cloud version of WorklogPRO. If you also want to migrate worklog attributes and account values for old worklogs, it's necessary to manually migrate worklog attributes and accounts and associate them with the imported worklogs.

But this migration is different than usual migration in migration asistant. You need the start the migration as usual in the migration assistant, but you need to use our custom steps to complete the migration. The Migration Assistant generates six files located in the {JIRA_HOME}/export/worklogpro folder to facilitate this process. These files include attribute definitions, account definitions, worklog attribute values, worklog account values, worklog mappings, and project mappings. You'll need to select the correct file using buttons labeled appropriately.

During the import, if an attribute or account with the same name doesn't exist in your Jira cloud instance, the relevant attributes and accounts are created. If they do exist, matching is done through the existing account/attribute. After the migration, you'll find the created attributes and accounts listed in a table. Any errors caused by missing worklogs or incomplete information in the uploaded files can be viewed in the "Errors" tab of this table.