How to help the Admin to choose the right setup?

[Matthias Leipert]

Hi folks,

i'm a german native, so i would describe my english as ok, so please do not mind any errors, i hope it is understandable.

i have some experience with Confluence (Data Canter and Cloud), but i am now in a new company and only a user of confluence right now. i am already trying to get space-admin rights (to some of the spaces) to restructure our spaces to a more useful combined space (of course with the correct authorization rights).

Our confluence got migrated from data center to cloud and has now of course some new features and possibilities, where i think our general admin is not aware of, but i would like to use them.

How can i help my admin to take the right steps to activate those features? are there any helpful guides to "what to do after migration?" or something like that?

I already found posts like this: Solved: Migrating from On-Prem to Cloud: What do you wish ... (which are fairly new and don't have much contents right now. but i think i stressed the search quit a bit, without finding what i am looking for.

So i decided to ask here.

[Marc -Devoteam-]

Hi @Matthias Leipert 

What features would you like to have enabled in the new Cloud instance?

[Matthias Leipert]

Some features, like third-party-addons are weird, cause we having slack activated, but are using teams, so i think that should be changed,

but the admin didn't have time at the migration to check this, so i am checking the marketplace for suitable things.

but since i don't have any admin rights in the old instance, i don't know which addons were active.

macros are also an point to check. rovo is not really configured.

i would like to use some basic features, like correct connection to our jira instance. also  a connection for confluence as knowledge base for our ticketing.

[Marc -Devoteam-]

Hi @Matthias Leipert 

Slack integration to be activated or used is a default in the system.

You can use MS Teams, but no by default.

You will at least have admin permissions on the products Jira and Confluence, your admin needs to provide them to you

For apps, this should have been noticed on doing the migrations, as this is part of the check before migrating to Cloud.

For ootb macros, related in migration to DC and Cloud, you can see here what would happen, learn-which-macros-are-being-removed 

Set-up-your-knowledge-base-with-confluence 

[Viswanathan Ramachandran]

Hi @Matthias Leipert 

Welcome to the community. 

See post-migration-phase and Confluence-cloud-site-details 

It is a lot there, but you will be there. 

Strategic Steps for Your Admin

1. Audit App & Feature Entitlements: Verify your subscription tier (Standard, Premium, or Enterprise), as features like AI, Automation limits and Analytics depend on the plan level.
2. Review Permissions : Now you will have organisation admin, site admins, app admins and space admins.
3. Set Up Default Page & Space Templates: Make high-value templates (such as project charters, databases, and decision logs) visible globally.
4. Fix Legacy Links & Macros: Run the built-in Atlassian post-migration link converter to repair broken cross-space links and replace deprecated Data Center macros with Cloud equivalents. See Fix links after the migration 
5. Run a Cloud What's New Session: Host a brief video demo with team leads to boost adoption.

Have you had a chance to test and play around in the sandbox? 

[Matthias Leipert]

Thanks for the Links to the support-pages!

i will inform my admin about that.

Unfortunately i don't have a sandbox to play with.

Macros is an open point, i have to check this.

I think adoption is not a problem right now, cause the usage is ok, in my opinion, but we will do an internal communication, once the spaces our team provides will be combined and checked. Templates are already updated for the space i would like to administrate.

We have some technical issues with the access to the confluence cloud instance, but these are network related issues we created ourself. 

[Sami Shaik]

Hello @Matthias Leipert , good list. Adding to @Marc -Devoteam-  and @Viswanathan Ramachandran pointers, three things that change your next steps:

1. You do have a sandbox. Your post is tagged Premium, and a Confluence sandbox is included on Premium (one per production site). Your org admin creates it in Atlassian Administration under Apps, then Sandboxes, and can copy production data into it. Test Teams, Rovo and the space restructure there first. Ask for this before anything else.

2. The old app list is recoverable without DC admin rights. The Cloud Migration Assistant produced an app assessment during migration; whoever ran it has it. On the Cloud side, Atlassian Administration, Apps shows what is installed today. Compare the two.

3. Split your list by who can act:

• You (once you hold the space Admin role): space restructure, templates.
• Product or org admin: install the Microsoft Teams integration app (Slack is built in, Teams is not), activate and review Rovo in Atlassian Administration (it is included in your plan), link a Confluence space as knowledge base from the JSM project settings.

One check for the Jira link: same Cloud site means already connected; separate sites means the admin sets up an application link.