nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Did you have Early access program cloud to cloud jira migration experience.

Vera Valshonok_yp6w8e

Hi All,

I am planning on going with the migration using Early access program for Cloud to cloud migrations, There are some points I am not sure about in order to start with migration such as field schemes, workflows and fields on the destination site to be influenced by the migration while its all active projects with the customers.

Can you share your experience if you already did such a migration recently, please? What were the places you had to fix after the migration and working with customers how much of a downtime is needed approximately for the migration.

Accepted answers

Kris Dewachter

Hi @Vera Valshonok ,

I recently did a cloud-to-cloud migration. It was a simple migration of only 1 Jira project.

The migration is pretty straightforward. All schemes, workflows, etc .... are automatically migrated.

However, you need to investigate before the migration if the workflows, schemes, custom fields already exist in your destination site. If so, they might get overwritten (not sure if the migration assistant will warn you about this).

There is no downtime involved as both source and destination site remain active. You need to beware offcourse of changes made to the tickets in the source site, during the migration.

Migration time depends on the amount of projects, issues, ...

Best regards,

Kris

All comments

Kris Dewachter

Hi @Vera Valshonok ,

I recently did a cloud-to-cloud migration. It was a simple migration of only 1 Jira project.

The migration is pretty straightforward. All schemes, workflows, etc .... are automatically migrated.

There is no downtime involved as both source and destination site remain active. You need to beware offcourse of changes made to the tickets in the source site, during the migration.

Migration time depends on the amount of projects, issues, ...

Best regards,

Kris

Vera Valshonok_yp6w8e

I need to move only one project to begin with as well. I am worried about the part of things to be overwritten as it can seriously influence work process with other customers on the destination site. How did you check that?

Kris Dewachter

If possible, keep your workflows, scheme's, etc .... for the project you are going to migrate, separate from the existing projects on your destination site. Make sure they have unique names. In that case, there should be no interference.

After the migration, you can always change your project settings on the new environment in a more controlled way.

Vera Valshonok_yp6w8e

Thank you!

So basically, I should check on the same named workflows, schemes, custom fields ( so there won;t be duplications) and check all during the downtime after the migration in order for the customers not to be influenced.I Right?

Also I see that not all the fields from existent tickets are migrating. It meanings they are custom fields and I would need to create them in advance before the migrations?

Do you know how can I make sure these fields stay not to loose the info in the opened ticket while the migration or will i have to add these custom fields to the request type form and then manually edit info into them (checking the info on the source site?)

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-service-management-cloud

jira-service-management