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; } } }

Migration of an Service Desk Project with Insight CMDB

Marco Göhl

Hello Community,

We have the challenge to migrate a Jira Service Desk project including Insight CMDB from one Jira instance to another (Server to Server).
In the target instance there are already Insight Object Schemas and some Service Desk projects.
Is there somewhere something like a migration path?
So what do you have to do first and then secondly the...
I have already migrated the CMDB object schema and found that all the IDs (object schema id, object type id, object type attribute ids) are different from those in the source, which means that a number of scripts will no longer work for us.
I suspect similar problems will arise with the custom_field_ids.

Since we have little or no experience with this, I'll place my question here.

Thanks for sharing your experiences!

Accepted answers

Laurens Coppens

Marco,

There are apps like project configurator or configuration manager that allows you to copy projects, including custom fields, WF's, ... that preserve the ID's.

As you said, insight import doesn't keep the id's so scripts might need modification, be sure to also check the custom field configuration that has references to insight objects.

Hope this helps,

Laurens

Kristian Walker _Adaptavist_

Hi Marco,

I can confirm that as Laurens has said above that Project Configurator can be used to migrate projects between instances however, I can confirm that Project Configurator does not officially support the Insight add on so we cannot guarantee if this will be able to migrate the insight data and configuration as expected and you can see a full list of the plugins which are supported here.

Also, I can confirm the way fields is migrated is by there name and type as documented here and not by ID as

It is common in any migration that you will need to update anywhere where fields are referenced by ID's in scripts or filters etc as those ID's used could already be used so Jira itself will give the fields new ID's when they are migrated into the new instance and so I would advise updating your scripts to reference the fields by name if possible otherwise you will need to manually update these after your migration.

I hope this information helps.

Regards,

Kristian

All comments

Laurens Coppens

Marco,

There are apps like project configurator or configuration manager that allows you to copy projects, including custom fields, WF's, ... that preserve the ID's.

As you said, insight import doesn't keep the id's so scripts might need modification, be sure to also check the custom field configuration that has references to insight objects.

Hope this helps,

Laurens

Kristian Walker _Adaptavist_

Hi Marco,

Also, I can confirm the way fields is migrated is by there name and type as documented here and not by ID as

I hope this information helps.

Regards,

Kristian

Laurens Coppens

Hey Kristian,

In my experience, when i use Project Configurator it preservers my CF ID's, so either i've been lucky so far, or i'm blind

In terms of insight data, i believe you need to reconfigure the fields, and data preservation is hard as the CF will contain the insight key, and that key is not preserved when doing an export import of an insight object schema.

So its very logic that you can't support or at least guaranty insight fields transfers.

Kristian Walker _Adaptavist_

Hi Laurens,

I can confirm that Project Configurator exports the fields by there name and the type and the Jira API's which are used to import the configuration is what assigns the field its ID.

If the same ID is available then Jira will reuse this but we cannot always guarantee that this the case and this why we always recommend referencing fields by there name as a best practice.

As for insight as mentioned above, we can only guarantee how the configuration for the plugins we support will be migrated, this, however, does not mean the configuration won't be migrated with PC but we would advise testing this to see if it will be migrated as expected as we cannot guarantee this.

Regards,

Kristian

Marco Göhl

Hi Laurens,

thank for your reply.
I'm aware of the configuration manager and that it will migrate also insight custom fields. But what happend with the custom field ids?

Welcome!

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

Quick Links

Find more posts tagged with

server

migration

jira-service-desk

jira-software

jira-software-server

insight