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

issue migrating a confluence space that shares a keyt

Jorge Torres Montijano

I am unable to migrate a Confluence space to another Confluence instance because another space already has the same key. I have changed the keys in both spaces (from "name" to "Aname" and "Bname"), but the migration tool still shows the original name, causing a conflict I cannot resolve.

What can i do?

Accepted answers

Evgenii Isaenkov

Hi, @Jorge Torres Montijano

This is a known gotcha with the Cloud Migration Assistant. You can't just simply rename space and migrate another, with same name, that existed earlier. You need to delete space.
Or, you can change space key on source confluence, and export space with new key.

Also, the migration tool caches space keys at assessment time, so even after renaming them, it may still show the old key. Try running a fresh migration assessment after changing the keys, that forces the tool to re-scan. I assume, this is the root cause of your problems.

Atlassian documents the conflict resolution options here: https://support.atlassian.com/migration/docs/check-for-possible-data-conflicts-when-migrating-confluence/

All comments

Evgenii Isaenkov

Hi, @Jorge Torres Montijano

Jorge Torres Montijano

@Evgenii

I already did a fresh migration assessment several times after I changed the key in both spaces...But it never worked. And I can't delete space in the destination confluence instance because contains business data.

Marc Koppelaar

Hi @Jorge Torres Montijano

Keys are stored form the last 3 iterations I believe.

The only option is to delete the space and then from trash, then do the migration action.

If this is not possible, due to the fact that space is also required, then you can export the space from the source instance.

Unzip the file and in all fils in the zip file replace the spacekey and re-zip all files and then import.

Amaury Dengis

Hello,

I have the same problem. I changed the space key on the source. But even with new migration projects, the migration tool still sees the old key... These Atlassian migrations are exhausting...

Have you found a solution ?

Thank you

Jorge Torres Montijano

The only solution I found was deleting completely the space in the destination...

Welcome!

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

Quick Links

Find more posts tagged with

confluence

cloud

confluence-cloud

organization-administration

not%20applicable