Confluence server to cloud migration FAQs
- What are the differences between Confluence Server and Confluence Cloud?
- Will the design and layout be different in Confluence Cloud?
- Can I switch back to the old look and feel once I'm in Confluence Cloud?
- Can I connect Confluence Cloud to my other Atlassian server products?
- Which apps are available for Confluence Cloud?
- What is the user limit in Confluence Cloud?
- How frequently will updates happen in Confluence Cloud?
- Will I be notified before updates are released in Confluence Cloud?
- How do I pick my site name (URL) for my Confluence Cloud site?
- How do I manage users in Confluence Cloud?
- How do I plan my migration?
- How long does migration take?
- How do you handle testing and staging?
- Depending on the migration strategy we pick, how much downtime should be expected?
- When is the best time to run a migration?
- What migrates over, and what doesn't?
- Does the migration overwrite my existing data and information on the Confluence Cloud site?
- What happens to my apps when I migrate?
- I have Confluence linked to other tools – what happens to my links when I migrate?
- What happens to my users when I migrate?
To understand the full complexity of migrating and plan your approach, start by creating your migration plan.
No. There's no additional fee to migrate from Atlassian's server to our cloud products.
You simply pay the standard fees for your Confluence Cloud subscription and any Confluence Cloud apps you install.
No. However, you may need to upgrade before starting your migration if you're on Confluence Server version 5.10.0 or earlier.
If you're on a version earlier than 5.10.0 and don't have active maintenance on your Confluence Server license to upgrade, you can:
- Sign up for a free server evaluation license from my.atlassian.com.
- Set up a new instance on the latest version of Confluence Server with that license.
- Import your Confluence Server instance into the new instance.
- Then migrate from your new, upgraded server instance to your Atlassian Cloud site using the Cloud Migration Assistant for Confluence.
Server evaluation licenses last for 30 days and can be extended to 90 days upon request.
You can track major changes that affect all users of Confluence Cloud in the Atlassian Cloud Documentation blog. This includes new features, bug fixes, and other changes across all Atlassian Cloud products.
Once you're a cloud admin, you'll have immediate access to our latest features and bug fixes.
Site Administrators have the highest administration privileges on an Atlassian Cloud site. The following permissions are currently available to site admins:
- All permissions assigned to the 'confluence-administrators' group for Confluence Server
- Access to user management (the ability to invite new users, create groups, assign users to groups, grant product access, etc.)
- Access to billing information
Atlassian Access provides IT administrators with enhanced security and administration across all Atlassian Cloud products.
It includes a global view of all Atlassian accounts in your organization and the ability to secure them with SAML single sign-on or mandatory two-step verification, user lifecycle management with SCIM provisioning, and priority support across your enterprise.
You can set up single sign-on and automatic user provisioning for your organization with Atlassian Access. All of Atlassian's supported identity providers offer connectors to your on-premises ADFS (LDAP). We support SAML SSO and user provisioning with SCIM for the following cloud identity providers:
- Azure AD
- Google Cloud (coming soon)
- Onelogin (SAML only)
- Centrify (SAML only)
Learn more about security best practices, including setting up SSO and provisioning for Atlassian Cloud.
Trust and security
Confluence Cloud sites implement the following security standards:
- SSL by default and are hosted on a secure hosting facility
Confluence Cloud sites adhere to the following standards and regulations:
- ISO/IEC 27001
- ISO/IEC 27018
- PCI DSS v3.2, SAQ A
- CSA CCM c3.0.1
For more information on Atlassian Cloud compliance and security, check out Trust at Atlassian.
Atlassian hosts data for Confluence Cloud in six different AWS regions: US (East and West), Europe (Germany and Ireland) and Asia Pacific (Sydney and Singapore).
Atlassian will optimize where customer data is located based on how it's accessed around the world. For example, if the majority of your users access your Confluence Cloud site from Europe, then their data will be migrated to Europe.
Learn more about our cloud hosting infrastructure.
Unlike Confluence Server, Confluence Cloud is sold as a subscription, not a perpetual license. You can pay either monthly or annually, with a discount for paying annually.
Check out Confluence Licensing to decide which payment schedule is best for your team and estimate your baseline costs. If you're planning on using apps from the Atlassian Marketplace in Confluence Cloud, remember to factor these into your cost considerations. The Atlassian Cloud pricing calculator can help you calculate your total monthly or annual cost including apps.
Note that your existing Confluence Server license and maintenance do not transfer to Confluence Cloud. These are two separate licenses and are paid for separately.
With Atlassian Cloud products, including Confluence Cloud, Atlassian handles the security, upgrades, hosting, mobility, support, and more for your sites.
Since the hardware, database and file systems running Confluence Cloud are maintained by Atlassian, your total cost of ownership may be lower with Confluence Cloud.
You can use the Atlassian Access pricing calculator to estimate your cost.
Atlassian Access is billed by the total number of unique users accessing any of the Atlassian Access supported Cloud products. You only pay once for each user, even if that user has access to multiple products.
Supported products include Confluence, the Jira Cloud family of products, Bitbucket, and coming soon, Trello.
No, your existing Confluence Server license and maintenance do not transfer to Confluence Cloud. These are two separate licenses, and are paid for separately.
Visit our differences in Confluence Cloud to learn more.
You can also compare Atlassian Cloud and Server to choose the right solution for you.
Yes. The design and layout are different across Confluence Server and Confluence Cloud.
We recommend trialing Confluence Cloud before migrating to get comfortable with the differences and identify any communications or training needed to help onboard your users.
No. The design and layout are not the same across Confluence Server and Confluence Cloud, and you cannot switch between the two.
We recommend trialing Confluence Cloud before migrating to get comfortable with the differences.
Yes, you can link to server products from cloud.
To see which of the apps you use are available in Confluence Cloud and discover new cloud apps, check the Atlassian Marketplace. Keep in mind while you're evaluating that Confluence Cloud may have some functionality that replaces the need for your server apps.
Note that some apps are only available for cloud, and some are only available for server. If an app you need isn't available for Confluence Cloud, reach out to the app developer to request availability in Confluence Cloud or discuss your migration options.
You may also have custom apps that you've built in Confluence Server. If that's the case, you can recreate your custom app using our cloud APIs.
For additional assistance migrating app data, you can visit our Atlassian Partners page to find one who can help with your migration.
Each Confluence Cloud site supports up to 5000 users.
We regularly deploy updates to all of the Atlassian Cloud products, including Confluence Cloud. Major changes are announced weekly in the Atlassian Cloud Documentation blog. This includes new features, bug fixes, and other changes.
No. Because updates are deployed regularly, Site Administrators aren't notified of upcoming changes. We recommend following the Atlassian Cloud Documentation blog to keep up with changes and find out what's new in Confluence Cloud.
Site names are chosen for an entire Atlassian Cloud site at the time you sign up for your first Atlassian Cloud product – for example, when you first sign up for Jira Software Cloud or Confluence Cloud.
The format for the site name is https://example.atlassian.net, where example is a unique character string that you specify.
There are a few things to be aware of when choosing your site name:
- Your unique character string must be at least three characters.
- It can only contain letters, numbers, and hyphens.
- Hyphens can't be the first or last character.
You manage users and groups across all products you've subscribed to on an Atlassian Cloud site, including Confluence Cloud, from the Users and Groups pages of the site administration. See Managing users and groups for more.
You can also create an organization for your company from your site. With an organization, you can view and manage all Atlassian account users at your company with your verified domains.
Through Atlassian Access, you can set up SAML single sign-on and configure automatic user and group provisioning from your identity provider, like Okta or Azure AD.
If you use G Suite, you can automatically sync users from your G Suite directory to your Atlassian Cloud site and your users will log in with their G Suite accounts.
Check out our Confluence Server to Cloud migration planning guide for step-by-step instructions on how to plan and execute your migration.
No two migrations are exactly alike. Depending on the amount of planning, change management, and the complexity of your migration, the entire process could be a matter of days or months.
The best way to determine this is to plan your migration in advance and execute a test migration.
Based on the complexity of the data and migration, our support team can help you conduct a test migration, during which we'll help you prepare and create a migration plan.
These test runs help ensure there is minimal impact to your business processes during your live migration and will help your admins and project owners work out the steps and timeline required.
No two migrations are exactly alike. We recommend running a test migration to assess your plan and how long your migration will take, including any expected downtime.
We recommend scheduling your migration at night, over a weekend, or another downtime to reduce the impact on your users.
When you migrate, you can choose to import:
- Site data, including spaces, pages and attachments.
- Users and groups.
The following is not imported:
Global settings and permissions: These will need to be configured manually in your cloud site.
Third-party apps: You'll need to work with the app vendors to migrate or re-install your apps in Confluence Cloud after migrating.
Application links: If you plan to use Atlassian server products in conjunction with your Confluence Cloud site, you can create two-way links between your cloud and server products. If this applies to you, you can set these up after migrating.
Passwords: Users will need to reset their passwords in Confluence Cloud after migrating.
User avatars: Users will need to update their avatars at id.atlassian.com after migrating.
No. If you migrate using the Cloud Migration Assistant for Confluence, it will only add data, not overwrite it.
Third-party apps, including any custom built apps or integrations you may have, are not migrated when you move from Confluence Server to Confluence Cloud.
After migrating, you will need to re-install any compatible apps or work with the app vendor to migrate any relevant data.
For more information on migrating apps, refer to the Confluence Server to Cloud migration planning guide.
Links within the Application Links section in Confluence Server will not be migrated. After migrating, you'll need to set these up in your Confluence Cloud site.
There's currently no option to do a partial user migration using the Cloud Migration Assistant for Confluence. This means that if you choose to import them, all of your users and groups will be migrated together. You can learn more about user and group migration in our documentation.
Once migrated, you'll need to send an invitation or the link to your new site to your users so they can start using it. They will not be automatically invited. After you invite them, they'll also need to reset their passwords and avatars.
While we do not offer professional services for migrations, our support team can help you plan your migration.
For help with a full end to end migration, we also have a wide network of partners globally that are experienced in Atlassian migrations. Visit our Atlassian Partners page to find one who can help with your migration.
Our migrations support team can help with technical questions or issues related to your migration.