Migrating Confluence from Cloud to Data Center
Asked by LAXMI ABHINAV REDDY ARAE:

Hello,

We are planing on migrating Confluence from Cloud to Data Center and below are the questions I have:

1. Implications of restricted pages within page trees and best path to migration?
2. possible solutions for search engine optimization to promote specific pages based on query?
3. best path to migrate essential add-ons: including GitHub and Terms?
4. best path to archive, clean and prune content effectively?
5. best path to ensure macros and add-ons are smoothly transitioned?
6. best path to ensure smooth transition from fabric editor to on-prem?
7. identify potential impact of the migration that will have on collaborative editing?
8. kindly provide any best practices and suggestions for migration.

Thank you.


Answers:
author: Daniel Eads
body: Hi [@LAXMI ABHINAV REDDY ARAE](/t5/user/viewprofilepage/user-id/1696538) !

Generally it works a little easier for folks answering questions if you can use separate questions entirely here on Community to organize problems. I can see some of these have been split out a bit. I'll try to take a run through what you've got above!

1. [Answered by Brant in another question you posted](https://community.atlassian.com/t5/Confluence-questions/Re-Migrating-Confluence-from-Cloud-to-Data-Center/qaq-p/1654320/comment-id/205931#M205931)
2. Natively, Confluence Server / Data Center doesn't have any features to manage SEO. There are [some apps for Confluence Server](https://marketplace.atlassian.com/search?hosting=server&product=confluence&query=seo) which do this - none are currently certified to run in Confluence Data Center. I would suggest having a look at those apps and contact the app vendor if you'd be interested in using any of those apps in your Data Center instance.
3. I'm not familiar with any specific GitHub apps for Confluence Cloud - I see there are some third-party ones on the Marketplace and would suggest getting in touch with the vendor of whichever one you're using. We (Atlassian) do offer a Microsoft Teams connector in Confluence Cloud but don't offer an equivalent in Confluence Data Center. I would suggest checking out the Marketplace [for Data Center apps that work with Microsoft Teams](https://marketplace.atlassian.com/search?hosting=dataCenter&product=confluence&query=microsoft%20teams) .
4. We offer some cleanup tips [for Confluence in our official cleanup guides](https://confluence.atlassian.com/clean/clean-up-your-confluence-instance-1026047969.html) that should help.
5. Apps vary greatly depending on the app and vendor. You'll need to look at the documentation or work with the vendor for each of the apps you currently have in your Confluence Cloud site.
6. Your users might need to re-train themselves on the differences between the new editing experience in Cloud and the legacy editor used in Confluence Data Center. Any Cloud-specific macros are likely to not work properly in Data Center after you export from Cloud / import to Data Center. These will need to be corrected or removed on each page that contains them.
7. Confluence Data Center fully supports collaborative editing - you'll likely not notice a change in functionality.
8. I'd suggest looking at the [documentation for migrating from Cloud to Server](https://confluence.atlassian.com/confeval/other-atlassian-evaluator-resources/migrating-from-cloud-to-data-center) (the same information will be relevant for Data Center, although there will be extra considerations for setting the Data Center installation up correctly if you'll be using multiple nodes). This [shorter document also contains some Data Center specific guidance](https://confluence.atlassian.com/confeval/other-atlassian-evaluator-resources/migrating-from-cloud-to-data-center) . An Atlassian Solutions Partner will be helpful to you if you're running into trouble as well; many partners have handled complex migrations and can work with you to help your specific case to be a success.

Cheers,  
Daniel


Tags: cloud

confluence-cloud