These pages will be centered on Projectrak's integration into the Jira Cloud Migration Assistant, and how to migrate from Projectrak Server/Datacenter to Cloud.

In this section you will find the following information:

Useful information before migrating Projectrak

Please, check Migration troubleshoot to learn about common problems.

Requirements

To carry out the migration process from the Data Center to Cloud, there are a series of requirements and recommendations regarding the Data Center version:

Minimum version: 8.4.0
Recommended version: 8.7.7

Warm up

Before starting, we would like for you to read through Projectrak's features that will be migrated from Jira Server/Datacenter to Cloud.

Data we will migrate

Fields
Layouts and its project association
Current project fields values
Permission schemes:
- In Server/DC: "Projectrak: view project field values" - In Cloud: "Projectrak: View project values".
- In Server/DC: "Projectrak: edit project field values" - In Cloud: "Projectrak: Edit project values".
- In Server/DC: "Projectrak: associate layouts to projects" - In Cloud: "Projectrak: Switch layout".

Data we won't migrate

Fields:
- Script fields
- Group fields
- List fields of external data source
Field options
- Project field mapped to Jira fields
- Dependencies of list fields
- Visibility restrictions.
History of project fields' value
Default layouts
Saved filter
Scheduled subscriptions
Watched projects
Gadgets configuration
Project fields conditions, post functions, and validations in issue workflows
"Projectrak Administrator" permission.
Permission schemes:
- Projectrak: watch project

Incremental migration process

It is important to note that the migration process for Projectrak is conducted in an incremental manner. The characteristics of this incremental approach are as follows:

One-time Migration for Fields and Layouts: The fields and layouts of Projectrak will be migrated only once. Any subsequent migrations following an initial migration will only migrate those fields or layouts not already present in the Cloud instance. This will be determined by checking their names.
- How do Projectrak fields behave on migrations?
- How are Projectrak layouts migrated?
Single Migration for Project Field Values: The values of project fields will be migrated only once, with the aim of preventing the update of any information that has already been migrated to the Cloud.

Users can perform phased migrations and continue working on their already migrated projects without worrying about their information being overwritten in future migrations, ensuring data integrity and operational continuity for users and their projects.

How to Re-Migrate Project Values

If a project has been previously migrated but there's a need to re-migrate its values, the user must first delete the specific project from their Cloud instance. After this step, a new migration can be initiated, during which Jira and Projectrak will restore the values from the Data Center instance. This process ensures that the latest project data is accurately reflected in the Cloud environment.

Migration process

Before starting the migration, Atlassian suggests going through a checklist that will ensure the data is ready to migrate. Here is the Jira pre-migration checklist.

Like any other process, migration from Datacenter/Server to Cloud will pass through different stages and steps. If you have decided to migrate your information through the Jira Cloud migration assistant, this documentation page will carry you through the entire process: Use the Jira migration Cloud Assistant to migrate.

In the following paragraphs, we will explain how to migrate Project information, taking into account that we have already migrated Projects and users to the Cloud instance.

Prerequisites

Installing Jira Cloud Migration assistant in your Datacenter/Server instance.
Assess Projectrak before migrating:

We suggest you select Assess your apps, on the Migration Assistant home screen. Here you can read about it, too.

When on the assess your apps screen you will see 5 columns that will provide info about your apps:

User-installed Apps: This will let you know what apps are installed on your server instance.
Status: where you will decide whether the app is needed or not in your Cloud instance, and therefore migrate it.
Exists in Cloud: this will show you if the App exists in the Cloud, and if it does, it will show a link to the App's feature parity documentation page.
Can be migrated: see if the app can be correctly migrated to Cloud, and if it is possible, it will show a link to the migration path.
Notes: here you can write notes for yourself or your colleagues to keep in mind during migration.

Focusing on Projectrak, the following image is the one you should expect to see:

Also, as a complementary exercise, we strongly suggest you go through these 4 points.

Validate the Projectrak Project fields that fulfill a business need.
Analyze the functionality that can provide those business needs.
Compare the features that will be available in Jira Cloud. (Link to parity)
Implement those fields that have been chosen and test to achieve the closest results.

Now, we can carry on with the following:

Plan the steps to take before executing the Jira Cloud Migration assistant.
Go ahead with the plan.

Step 1: Prepare your apps

Select Prepare your apps, on the Migration Assistant home screen, which will take you to the Connect to Cloud screen.

There are 3 main tasks you will perform at this stage:

Connect to your cloud site: here you will choose the destination Cloud site. You may have one prepared already, sign up for a Free plan or Set up a free trial
Install your apps: here you will select “Install app” for Projectrak in your cloud site, which will allow you to read the support and privacy policy. (This is in case the app is not installed in your destination Cloud site. You won’t be able to move on unless you have passed the Assess your Apps screen first).
Agree to app migration:

Atlassian also suggests the following:

When an app migration is performed, the migration moves the data from each server app to its cloud version on your cloud site. The Marketplace Partner (vendor) that built each app has created a migration pathway to move the data.

During this process, the Marketplace Partner will be performing the app data migration, not Atlassian. Because of this, you need to review and agree to each Marketplace Partner agreement so they can access your data to migrate it.

To complete the assessment flow, you must provide consent and agree to app migration for each app.

On the ‘Agree to app migration’ screen:

Select View policy for each app that shows as requiring your consent.
This opens a card that:
1. lists all the types of data the Marketplace Partner (vendor) will have access to, such as read core data or read user data.
2. links to the Atlassian Marketplace Terms of Use, the Marketplace Partners Privacy Policy, and the Marketplace Partners Terms of Use. We strongly recommend you read this for each app you migrate.
Select Confirm on this card.
When you have performed the above action for all applicable apps, select Done to return to the ‘Migration Assistant home’ screen.

You can find more detailed information about this on Introduction to third-party migration agreement.

It’s important to know the following:

Only an app with an automated migration path needs you to agree to the migration.
If you agree to third-party migration, you can revoke your agreement at any time.
If you don’t agree to third-party migration, that app cannot be migrated using the Jira Cloud Migration Assistant.
If a Marketplace Partner updates an app, you will need to agree to the migration again.
After you agree to app migration, you can still select Revoke agreement. This will remove your agreement to third-party data migration. To agree again, click View policy and re-confirm your agreement.

The Done button will be disabled if you have not done the following:

assigned a status to each app (on the Assess your apps screen)
installed apps needed in the cloud (on the Install your apps screen)
viewed and agreed to the policy for each app (on the Agree to app migration)

Step 2: Migrate your data.

The following key steps will allow you to set up and run your migration from Server/Datacenter to cloud:

Connect to your cloud site
Choose your migration options
Check for errors
Review your migration
Migrate

More info

In each section, we will focus on Projectrak’s app data migration. If you need more information, please refer to the Atlassian Support page: Use the Jira Cloud Migration Assistant to migrate, or in case you need further assistance with Projectrak, please reach out to us through our Customer Support portal or at help@deiser.com

Begin migrating your data:

1. Select Migrate your data in the Migration Assistant home

2. In the Migration dashboard, select.

3. Review the information shown on this screen and select Connect to Cloud.

Connect to the Cloud site

Name your migration in the field presented.
In the Choose your destination cloud site field, choose the cloud site you would like to migrate to.

Choose to migrate all data at once or Choose what to migrate (in this case we will choose what to migrate so we can migrate Projectrak)

4. Now, you should be able to choose what to migrate.

Choose migration options:

You will be able to migrate everything at the same time, but as we mentioned before, we’ll focus on Projectrak right now, and you can do this by selecting Projectrak in the Apps option.
Here, you won’t be able to select just one App, so please, select All. When the selection has been made, you’ll be taken back to “Choose your migration options” and continue with the migration.

Here you will be able to see the information which Projectrak will let you migrate. It is always a good idea to re-check our Feature Parity between Server/Datacenter and Cloud page to have an idea of what to expect.

Check for errors

Here, a list of checks will be run (please refer to the Atlassian article above), and they will be all part of the four main groups to migrate:

App version
Users and groups
Projects
Apps

To understand the error messages a bit further, we strongly suggest referring to the migration article, but since we are focused on Projectrak, here are the errors you can be prompted with right here.

Message	Description
App assessment is incomplete	You will be taken back to the app assessment table. You should assign statuses to each of the apps in your assessment. Once the table is completed, rerunning the check will display a green tick.
Some apps marked as 'Needed in cloud' on your server are out of date	You will need to update your apps on server to a version that’s compatible for app migration. Contact your Marketplace Partner for information on app versions that are compatible for app migration.
You have not consented to app data migration	You need to consent to app migration on the ‘Agree’ screen.
Some 'Needed in cloud' apps are not installed on your cloud site	You need to install all the apps that you have chosen as ‘Needed in cloud’ on your cloud site. You can do this on the ‘Install’ screen.
Some apps marked as ‘Needed in cloud’ do not meet the migration success rate criteria	If you have selected apps marked as Stage 1 that have unknown or low migration success rates, you will be given the option to: remove the apps from the migration proceed to migrate with the selected Stage 1 apps

You can also decide to Continue and fix later, reviewing the errors after the migration is saved.

Review the migration

As a final step from setting the migration, you’ll see the following screen.

It is always helpful to review every step or download the pre-migration, post-migration, and error logs reports. You can do that in the Logs and Reports tab.

Manage and run your migration

After saving the migration, you’ll be able to follow it in the migration dashboard, where you can run the migration, follow its process and see if it has been successful or not.

Please, if you find that any features or cases are missing, please let us know through our Customer Support portal, and report an Improvement on the "I need this improvement" request type.

Browser not supported