Hi Everyone, We are planning a Confluence Cloud-to-Cloud migration between two different Atlassian organizations. In the source Confluence instance, we have multiple spaces that contain Smart Links to pages in other Confluence spaces within the same source environment. If all these spaces are migrated to the target Confluence instance: * Will the Smart Links automatically point to the corresponding migrated pages in the target environment? * Do the links continue to reference the source URLs? * If link updates are required, what is the recommended approach for fixing Smart Links after migration? We're particularly interested in understanding how Smart Links between migrated Confluence pages/spaces are handled during a cross-organization migration. Thanks in advance for any guidance.

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

Smart Links Between Confluence Spaces in a Cloud-to-Cloud Migration

Likhita Biyyala

Hi Everyone,

We are planning a Confluence Cloud-to-Cloud migration between two different Atlassian organizations.

In the source Confluence instance, we have multiple spaces that contain Smart Links to pages in other Confluence spaces within the same source environment.

If all these spaces are migrated to the target Confluence instance:

Will the Smart Links automatically point to the corresponding migrated pages in the target environment?
Do the links continue to reference the source URLs?
If link updates are required, what is the recommended approach for fixing Smart Links after migration?

We're particularly interested in understanding how Smart Links between migrated Confluence pages/spaces are handled during a cross-organization migration.

Thanks in advance for any guidance.

Accepted answers

Abaho Katabarwa (Katabarwa Labs)

Hi @Likhita Biyyala, to confirm Tobi's suggestion: link fixing does cover cloud-to-cloud migrations, and it's the supported way to deal with this.

After a cloud-to-cloud migration, URLs that point at the old site (pasted links and Smart Links included) keep pointing at the old site, because the content now lives under a different URL. Atlassian's link-fixing tool, run from Atlassian Administration on the destination site after the migration, finds those links and rewrites them to the new site. Atlassian documents it here: https://support.atlassian.com/migration/docs/update-product-links-after-the-migration/

Two practical notes: run it per product (Confluence and Jira separately), and it lists what it will change before you confirm, so you can review the scope first. Doing a small test migration of one or two spaces and running link fixing on that is the quickest way to see how your Smart Links come out.

All comments

Tomislav Tobijas

Hi @Likhita Biyyala ,

I believe any/all absolute smart links and URLs will not be updated when using C2C migration. (That's the theory; haven't tested/noticed this before) 👈

Now, what you could do or try is the following:

Use link fixing in Atlassian Administration > I believe this would/should do the trick, but again, not entirely sure
What will work is if Atlassian Support performs an ADF fix/refresh on the backend side. You just need to raise a ticket 🎟️ and they should be able to help out or at least give you a list of pages that need to be updated.

You could also try Rovo to see if it gives you the list and can potentially update all references you're using (or have been using) across different pages.
This is, as well, more theoretical than proven to work, but still it could be worth a try 🤞

If you'll actually test this, I'm keen to hear the results.

Cheers,
Tobi

Abaho Katabarwa (Katabarwa Labs)

Hi @Likhita Biyyala, to confirm Tobi's suggestion: link fixing does cover cloud-to-cloud migrations, and it's the supported way to deal with this.

Likhita Biyyala

Hai @Abaho Katabarwa (Katabarwa Labs)

Thanks for the clarification. One of the follow-up questions: in our case, the migration is between two completely different Atlassian organizations

[ for example,

src.atlassaian.net → tar.atlassain.net].

Are there any prerequisites or configuration steps that need to be completed before running Link Fixing in the destination environment? For example, does Atlassian require any product links, site associations, or other setup to correctly identify and update the migrated smart Links? or any other Links in confluences which refers to src.atlassian.net?

Thanks for your guidance.

Kris Klima _K15t_

Hi @Likhita Biyyala

I guess restoring the whole Confluence site from a backup is not an option.

What you can do is to migrate individual spaces (or use a site-to-site space synchronization app - Space Sync for Confluence by Ricksoft, which useful if you cannot freeze multiple space at once and your work needs to continue).

Then, you can use a programmatic approach to replace the bits of smart links url or an app like Space Content Manager by Easyapps that allows search and replace.

Abaho Katabarwa (Katabarwa Labs)

Hi @Likhita Biyyala, good question, and the two-org detail matters. From Atlassian's link fixing docs, check these before the production run:

Timing. Links can only be updated for 2 weeks after a migration. After that, the migration data used to match old and new links is deleted, so run link fixing right after each migration wave, not at the end of the project.
Permissions and setup. The person running it must be an organization admin and an admin of the app whose links are being fixed, and the cloud apps and the destinations of the links need to be connected with app links. It lives in Atlassian Administration > Data management > Link fixing.
Org scope. The docs say: "You can only update links between cloud apps within one organization. If your apps are on multiple sites, but still within one org, this is supported." My reading is that this applies to the destination side, so your migrated Jira and Confluence should sit in the same destination org. Because your source is a different org, I would confirm that reading with Atlassian Support before you rely on it.

The small test migration is still the best check: run link fixing on it within the two weeks and see which src.atlassian.net links come out rewritten.

Update product links · Supported products and types of links

Welcome!

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

Quick Links

Find more posts tagged with

confluence-cloud

smart-links

cloud-to-cloud-migration