Confluence Server to Confluence Cloud

Overview

An administrator's journey when migrating apps from server to cloud includes determining which apps provide an easy transition to cloud and only later work on the more advanced apps. See diagram below for help on this journey.

Direct Migration

(tick) Migration from Linking for Confluence Server to Cloud is supported

  Click here to expand...

Migration Path

Original Platform

Target Platform

Available App Migration Path

License Migration

Notes/Consideration

Server/DC

Cloud

Migration Path is available

Needed

  • Understand the feature differences (see below) between the application for Confluence server and Confluence cloud.

  • Allocate time for a test migration to understand the steps required to migrate data and complete re-configuration.

  • This guide assumes you have successfully migrated your  Confluence Server data into Confluence Cloud, per  Atlassian's instructions (CCMA).  More Atlassian resources are available here.

Feature Differences


Migration Focus Area

Feature

Platform


Server

Cloud

Versioning/License Version Support

Minimum migratable Version : 5.4.3

Migrate to Redirection for Confluence using steps at Migration Path
License Available through both Atlassian Marketplace and ServiceRocket Marketplace. Available through Atlassian Marketplace only. Monthly subscriptions are the default option, however, discounted annual subscriptions are available upon request to our Atlassian Sales team.

Integration with other macros

Linking macros allows

  • Integration with other macros.
  • Support of nested macros which means Linking macros can easily be nested and integrated with other Confluence native macros or any third-party macros
  • Integration with Scaffolding macro

Linking macros in cloud have the following limitations:

Macro Differences Overview

Server Macros 

Cloud Macros 

Macros availability

  • Only some macros in  are available in Cloud

  • Look out for icons highlighting how the data will be migrated.
    • (tick)  Available 
    • (error) – Unavailable

    • (warning) – Partially available

  • Migration for the following Linking macro works out of the box

  • For macros that are migrated but are unsupported, the following applies:

    • You may see an "unknown macro" where the macros were originally positioned in the documents

  • Find details of each migratable macro below and the differences in terms of behavior once migrated to Cloud

Macro Differences Breakdown

Macro name

Parameters unavailable in Cloud have been marked (error)

Key Differences

Server

Cloud

Add Page 

Supported macro parameters

  • Name
  • Link Text
  • Source
  • Source Type
  • Live Template (error)
  • Prefix
  • Postfix
  • Parent
  • Labels
  • Tip (error)
  • Allow Rename (error)

Supported macro parameters

  • Name
  • Link Text
  • Source
  • Source Type
  • Prefix
  • Postfix
  • Parent
  • Labels


(info) Notes about Cloud migration

  • While functionality is the same, Prefix and Postfix parameters accept different values in server and cloud.
  • You may need to re-write the values for these parameters after migrating to Cloud. Check here for more information about what values that Cloud accepts.

Add Page via Form

Supported macro parameters

  • Link Text
  • Button Text
  • Source
  • Source Type
  • Live Template  (error)
  • Prefix
  • Postfix
  • Parent
  • Labels
  • Tip (error)
  • Allow Rename (error)
  • Name Field Width (error)

Supported macro parameters

  • Link Text
  • Button Text
  • Field hint
  • Source
  • Source Type
  • Prefix
  • Postfix
  • Parent
  • Labels


(info) Notes about Cloud migration

  • While functionality is the same, Prefix and Postfix parameters accept different values in server and cloud.
  • You may need to re-write the values for these parameters after migrating to Cloud. Check here for more information about what values that Cloud accepts.

Incoming Links

Supported macro parameters 

  • Page (error) 
  • Spaces 
  • Display Mode (error) 
  • Separator (error)  
  • Bullet Style 
  • Maximum Results (error)
  • Display Excerpt 
  • Content Types (error)
  • Scope (error)
  • Labels (error)

Supported macro parameters

  • Spaces
  • Bullet Style
  • Display Excerpts

Outgoing Links

Can't find what you need?

Send us an e-mail at apps.support@servicerocket.com for assistance.

Which server feature would you like to see in Cloud? Please feel free to take our ongoing survey and we will prioritize accordingly.



Key steps

  • Upgrade Linking macro to at least version 5.4.3 and or above
  • Understand the macro differences and feature differences between Linking for Confluence Server and Confluence Cloud. 
  • Perform the migration using Confluence Cloud Migration Tool or through Space Exports.
  • Check and re-configure your Linking data in Confluence Cloud.

(tick) Migration from Redirection for Confluence Server to Cloud is supported

  Click here to expand...

Migration Path

Original Platform

Target Platform

Available App Migration Path

License Migration

Notes/Consideration

Server/DC

Cloud

Migration Path is available

Needed

  • Understand the feature difference (see below) between the application for Confluence Server and Confluence Cloud.

  • Allocate time for a test migration to understand the steps required to migrate data and complete re-configuration.

  • This guide assumes you have successfully migrated your  Confluence Server data into Confluence Cloud, per  Atlassian's instructions (CCMA). More Atlassian resources are available here.

Feature Differences


Migration Focus Area

Feature

Platform


Server

Cloud

Versioning/License Version Support

Min migratable Version : 5.3.2

Migrate to Redirection for Confluence using steps at Migration Path
License Available through both Atlassian Marketplace and ServiceRocket Marketplace. Available through Atlassian Marketplace only. Monthly subscriptions are the default option, however, discounted annual subscriptions are available upon request to our Atlassian Sales team.
Confluence Differences


Integration with other macros

Redirection application allows

  • Integration with other macros.
  • Support of nested macros which means Redirection macros can easily be nested and integrated with other Confluence native macros or any third-party macros

Redirection application in cloud have the following limitations:

  • Does not support nested macros which means Redirection macros cannot be placed in a nested container (such as inside an expand macro, etc.)
  • Due to the above, integration with other macros may be difficult.

Macro Differences Overview

Server Macros 

Cloud Macros 

Macros availability

Only some macros in Redirection for Confluence are available in Cloud:

  • Look out for icons highlighting how the data will be migrated.
    • (tick)  Available 
    • (error) – Unavailable

    • (warning) – Partially available

  • Macros that are migratable 

    • Migration for Redirect macro works out of the box.

  • For macros that are migrated but are unsupported, the following applies:

    • You may see an "unknown macro" where the macros were originally positioned in the documents.

  • Find details of each migratable macro below and the differences in terms of behavior once migrated to Cloud.

Macro Differences Breakdown

Macro Name

Key Differences

Server

Cloud

Redirect

Supported macro parameters

  • Visible
  • Location
  • Delay

Supported macro parameters

  • Visible
  • Location
  • Delay
  • Confluence Attachment

(warning) Notes about Cloud migration and Cloud behavior

  • Redirecting to a Confluence attachment is available on both server and cloud.
  • However, the location of the attachment is specified differently
    • Uses Location parameter on server
    • Uses Confluence Attachment parameter on cloud
  • Migrating users will need to amend this before getting Redirection macro to work
  • Blocked by browsers
    • On the Cloud platform, some browsers (e.g., Chrome) may attempt to block the redirect. If this happens, you will need to click the Pop-up Blocked icon in the address bar and configure the browser to always allow redirects for your Confluence site.
  • Redirection notice
    • Due to Atlassian's security policies, there will always be a popup about "Redirection Notice"
    • Just click Allow for the Redirect macro to continue.





Key steps

  • Upgrade Redirection macro to at least version 5.3.2 and or above
  • Understand the macro differences and feature differences between Redirection for Confluence Server and Confluence Cloud. 
  • Perform the migration using Confluence Cloud Migration Tool or through Space Exports.
  • Check and re-configure your Redirection data in Confluence Cloud.

(tick) Migration from Visibility for Confluence Server to Cloud is supported

  Click here to expand...

Migration Path

Original Platform

Target Platform

Available App Migration Path

License Migration

Notes/Consideration

Server/DC

Cloud

Migration Path is available

Needed

  • Understand the feature difference (see below) between the application for Confluence Server and Confluence Cloud.

  • Allocate time for a test migration to understand the steps required to migrate data and complete re-configuration.

  • This guide assumes you have successfully migrated your  Confluence Server data into Confluence Cloud, per  Atlassian's instructions (CCMA). More Atlassian resources are available here.

Feature Differences

Migration Focus Area

Feature

Platform


Server

Cloud

Versioning/License Version Support

Min migratable Version : 4.2.2

Migrate to Visibility for Confluence using steps at Migration Path
License Available through both Atlassian Marketplace and ServiceRocket Marketplace. Available through Atlassian Marketplace only. Monthly subscriptions are the default option; however, discounted annual subscriptions are available upon request to our Atlassian Sales team.
Confluence Differences Integration with other macros

Visibility for Confluence server allows

  • Integration with other macros.
  • Support of nested macros which means Visibility macros can easily be nested and integrated with other Confluence native macros or any third-party macros

Visibility for Confluence cloud has the following Confluence Cloud limitations:

  • Does not support nested macros.
    • Visibility macros cannot be placed in a container (such as inside an expand macro, etc.)
    • Cannot place a container inside Visibility macros (such as inserting an Expand macro, etc.)
  • Due to the above, integration with other macros may be difficult.

Macro Differences Overview

Server Macros 

Cloud Macros 

Macros availability

All macros in Visibility for Confluence are available in Cloud:

  • Look out for icons highlighting how the data will be migrated.
    • (tick)  Available 
    • (error) – Unavailable

    • (warning) – Partially available

  • All macros are migratable to Cloud


  • Find details of each migratable macro below and the differences in terms of behavior once migrated to Cloud.

Macro Differences Breakdown

Macro Name

Key Differences

Server

Cloud

Supported macro parameters

  • Match Using (tick)
  • Users (tick)
  • Special Usernames
  • User Groups (tick)
  • Space Permissions
  • Content Types
  • Display Types
  • Current Space
  • Action Types
  • Labels
  • HTTP Headers
  • Scope
  • Trim

Supported macro parameters

  • Match Using
  • Users
  • User Groups

(warning) Notes about Cloud migration and Cloud behavior

  • While the functions of these parameters do not have any output and the values are ignored in Cloud, all migrated data will be retained. Some of the parameters may be coming to Cloud in future releases.

Which server feature would you like to see in Cloud? Please feel free to take our ongoing survey and we will prioritize accordingly.



Key steps

  • Upgrade Visibility macro to at least version 4.2.2 and or above
  • Understand the macro differences and feature differences between Visibility for Confluence Server and Confluence Cloud. 
  • Perform the migration using Confluence Cloud Migration Tool or through Space Exports.
  • Check and re-configure your Visibility data in Confluence Cloud.

Advanced Migration

(tick) Migration from Composition Tabs for Confluence for both Data Center & Server to Cloud is supported

  Click here to expand...

Migration Path

Original Platform

Target Platform

Available App Migration Path

License Migration

Notes/Consideration

Server/DC

Cloud

Migration Path is available

Needed

  • Understand the feature differences (see below) between the application for Confluence Server and Confluence Cloud.

  • Allocate time for a test migration to understand the steps required to migrate data and complete re-configuration.

  • This guide assumes you have successfully migrated your Confluence Server data into Confluence Cloud, per Atlassian's instructions (CCMA).  More Atlassian resources are available here.

Feature Differences


Migration Focus Area

Feature

Platform


Server

Cloud

Versioning/License Version Support

Minimum migratable Version : 5.14.1

Migrate to Composition Tabs Cloud using steps at Migration Path.
License Available through both Atlassian Marketplace and ServiceRocket Marketplace. Available through Atlassian Marketplace only. Monthly subscriptions are the default option, however, discounted annual subscriptions are available upon request to our Atlassian Sales team.
Confluence Differences


Integration with other macros

Composition Tabs allows

  • Integration with other macros.
  • Support of nested macros, which means Composition Tabs macros can easily be nested and integrated with other Confluence native macros or any third-party macros

Composition Tabs macros in cloud have the following limitations:

  • Does not support nested macros, which means Composition Tabs macros cannot be placed in a nested container (such as inside an expand macro, etc.)
  • Due to the above, integration with other macro may be difficult.

Macro Differences Overview

Server Macros 

Cloud Macros 

Macros availability

  • Only some macros in  are available in Cloud

  • Look out for icons highlighting how the data will be migrated.
    • (tick)  Available 
    • (error) – Unavailable

    • (warning) – Partially available

  • Migration for the following Composition Tabs macros is possible

    • Migration for Showcase macros works out of the box.
    • Deck of Cards & Card can be migrated after performing the mandatory pre-migration steps
      • These will be converted to Tab Group & Tab (Legacy Editor) macros first
      • Then you can choose to convert to Tabs (New Editor) at a later point
    • Other Composition macros not available in Cloud can still be migrated without data loss, however, the below conditions apply:
      • You may see a blank space where the macros were originally positioned in the documents
      • While these macros do not have any output and the values are ignored in Cloud, all data will be retained. Some of the macros will be coming to Cloud in future releases.
  • Find details of each migratable macro below and the differences in terms of behavior once migrated to cloud

Macro Differences Breakdown

Supported Server Macro

Cloud Macro (Or closest equivalent ) 

Key Differences

Server

Cloud

Deck of Cards and Cards

  • In Server, Tabbed content is available by calling the Cards macro nested inside Deck of Cards. 
  • Content of each tab will be added inside each Card macro

(warning) Notes about Cloud migration

Tabs, Tab Group and Tab

Showcase 


Showcase

Parameters available:

  • Title
  • Description
  • Image URL
  • Button Text
  • Button Link

Parameters available:

  • Title
  • Description
  • Image
  • Emoji
  • Button Text
  • Button
  • Badge

(warning) Notes about Cloud migration

A number of parameters have different names in the Cloud version, but they work the same way as the Server version parameters, Server parameter names will be automatically converted to Cloud parameter names during migration.




Key steps

  • Upgrade Composition tabs to version 5.14.
  • Understand the macro differences and feature differences between Composition Tabs for Confluence Server and Confluence Cloud. 
  • Perform the pre-migration steps for your tabbed content.
  • Perform the migration using the Confluence Cloud Migration Tool or through Space Exports.
  • Confirm that migration was successful and tabbed content is appearing on Confluence Cloud.

(tick) Migration from Scaffolding for Confluence Server Server to Cloud is supported

  Click here to expand...

Migration Path

Original Platform

Target Platform

Available App Migration Path

License Migration

Notes/Consideration

Server/DC

Cloud

Migration Path is available

Needed

  • Understand the  feature difference (see below) between the application for Confluence Server and Confluence Cloud.

  • Allocate time for a test migration to understand the steps required to migrate data and complete re-configuration.

  • This guide assumes you have successfully migrated your  Confluence Server data into Confluence Cloud, per  Atlassian's instructions (CCMA) .  More Atlassian resources are available  here.

Feature Differences


Migration Focus Area

Feature

Platform


Server

Cloud

Versioning/License Version Support

Min migratable Version : 8.25.0

Migrate to Scaffolding cloud using steps at Migration Path
License Available through both Atlassian Marketplace and ServiceRocket Marketplace. Available through Atlassian Marketplace only. Monthly subscriptions are the default option, however, discounted annual subscriptions are available upon request to our Atlassian Sales team.
Access/Security Authentication Type Authentication will be based on your current setup Confluence Cloud protects your data with encryption in transit and at rest and provides administrative controls to enforce organization-wide protection such as SAML SSO, enforced 2FA, and SCIM. (Click the link to understand how Atlassian helps with security and encryption angles in Confluence Cloud)
Confluence Differences


Structure editing: 

Calling Field macros

Field macros are called directly on a page.
Some macros interact with each other and have to be nested inside other macros

Field macros are called after adding a Field Group macro on a page. You build the structure of the page inside this macro by choosing the Field macros from the left-hand panel and drag-and-dropping them down to the Editing area

Content editing:

Filling up the forms

Clicking "Edit Content" will pop-up a separate Scaffolding Edit Content editor.
Depending on the Scaffolding field macro type, editing values can be done on this directly, or on a separate popup editor area.

Clicking Edit Content will change the Page View to become an editable area. 


Scaffolding settings

Scaffolding includes an administrator setting, which allows Confluence administrators to set the default setting for the Edit Contents mode.

All limit settings are handled by the app internally. No further configuration is needed in Cloud.

Previous Scaffolding XML versions

Scaffolding allows users with the proper permissions to view Scaffolding data history on a page that contains Scaffolding metadata. Users may compare versions or restore older versions using this feature.

All changes made to pages with Scaffolding macros will be recorded in Page History, be it Scaffolding structure or data changes. Users are able to restore page data to an earlier version through the Confluence Page History.

(warning)  Due to the feature difference between Server and Cloud, only the current version of Scaffolding data will be migrated to Cloud. 
Integration with other macros

Since Field macros are called directly on a page as macros, this means that users can add any other Confluence macros inside this page along Scaffolding macros.

Confluence server supports nested macros as well which means Scaffolding macros can easily be nested and integrated with other Confluence macros.


  Example of how Scaffolding macros are nested with other macros...


Scaffolding supports integration with most reporting macros/apps like Page Property Report macros (Native Confluence macros) and Reporting (ServiceRocket app)

Field Group macro is a standalone macro that reveals a separate editor where you can build your page structure. While this editor supports most Confluence page functions, it does not support other complex macros and third party macros

Confluence Cloud currently does not support nested macro (See CONFCLOUD-68323) which means integration with other apps by way of nesting will be limited.

(warning)  Due to this limitation, pages and templates that contain Scaffolding macros nested with other macros (such as the one highlighted in the Server column on the left side) will fail to be migrated to Cloud. We suggest simplifying the page structure and removing any complex third party macros in the page/template before performing the migration to Cloud. Feel free to contact our support team to get further advice about this.

Currently, Scaffolding Cloud does not support integration with reporting apps such as Page Property Report macros. 


  Availability of Reporting for Confluence Cloud....

We're rebuilding the app for Cloud with better experience and functionality. Sign up through survey if you wish to participate in Beta releases.

Macro Differences Overview

Server Macros 

Cloud Macros ((warning) Naming conventions have been changed to suit new macro behavior)

We have simplified our cloud Scaffolding application to focus on some key macros. This means that data migrated will be handled totally differently in Cloud. Review and understand the following: 

  • Look out for icons highlighting how the data will be migrated.
    • (error)  – Unavailable

    • (warning)  – Partially available

  • We suggest you thoroughly test all the main data that you are migrating, keeping in mind which category they fall into. Include this as a part of the pre-migration tests.

  • For macros that are migrated but are unsupported, the following applies
    • Overall unsupported Macro
      • You may see a blank space where the macros were originally positioned in the documents
    • Unsupported Macro parameters
      • Migration will contain the data.
      • Your parameter values are available in the Content Properties
      • The function of those parameters is not available
      • The macros will behave differently in View & Edit content mode 
        • For example, if you have a page with Number Data with Decimal & MinValue set, that data in cloud will lose its Decimal value on View content mode. Upon Edit content mode, there will be no min.value set
  • Find details of each migratable macro below and the differences in terms of behaviour once migrated to cloud


Macro Differences Breakdown

Supported Server Macro

Cloud Macro (Or closest equivalent ) 

Key Differences

Server

Cloud

Attachment Options

Creates a set of list options linking to the attachments on the specified content. Must be contained inside a  List Data macro.

Files list

Accepts  content, include and exclude as filter criteria for the attachments

Accepts page location: The location of the page to search the attachment on

Content Options

Generates a set of options linking to Confluence content (e.g. pages, blog posts, etc).

May be filtered in several ways. Must be contained inside a  List Data macro.

Content List

Accepts space, parent ancestor, labels etc as filter criteria for the content to be displayed as option.

Accepts space as filter criteria for the content to be displayed as option.

Date Data

Allows editing of dates with a date picker pop-up menu, or via keying in directly into the fixed format field.

Date


Accepts minDate, maxDate & Display format as Date field criteria.

Accepts no parameter

Group Data

Allows data to be grouped within a named data set.

Field Group

Acts as a bucket of Field macros to be easily referred to later. Field name is required.

Acts as the main macro to do Structure editing. Field group name is required.

List Data

Allows selection of one or more options from a specific list.

Must contain option-generating sub-macros (e.g.  List OptionContent Options,  User Options,  Attachment Options or  Label Options).

Available as a combination of 

  • Define output to be a dropdown list. Requires other Field macros to work
  • Dropdown settings are defined here such as Required, Allow multiple, Separator, etc.
  • All dropdown macros are called individually depending on their function
  • Allow Multiple and Required setting are set in each individual macros
(warning) Unsupported server scenarios upon migrations.
  • List data that contains multiple types of options.
  • In Cloud, the type of options is its own separate macros and therefore cannot be combined. 

  • If this scenario happens, only the topmost option will be migrated. In this example, only User Options will be migrated to Cloud.

List Option

Generates a single, simple, list option.

Must be contained inside a  List Data  macro.

Custom List

  • Accepts text value in the dropdown options, can be modified to output other rich text formats such as Status or Emojis.
  • Have sorting mechanism


Accepts custom Texts (that may contain emoji) or Statuses as value and output of the dropdown list.

Live Template 

Live Templates use either Confluence Global templates, Space templates or even other regular Confluence pages as templates.

Live Template
  • Accepts Page, Space or Global Templates, and Scaffolding Blueprint as templates
  • Location of pages are assigned manually with the following format (SPACEKEY:Page_Title)
  • Accepts Page, Space or Global Templates, and any Confluence Blueprint as templates
  • Location of Page/Template/Blueprint is chosen from a dropdown field. Space name and Page name field are separated

    (warning) Unsupported server scenarios upon migrations.

Find Limitations at Limitation for Live Template in Confluence Cloud

  Click here to expand for more details...

Summary

Confluence server supports the Live template macro with various Template types.

However, the Live template macro in Cloud supports different types of template types. Therefore migration of Live Template may be limited

This document highlights the limitations and differences.

Environment

  • Confluence Cloud

  • Scaffolding Forms and Templates for Confluence Cloud

Cause

Due to differences of the macros and limitations in Cloud, Live Template macros in Cloud can only accept some of the template types used in Live Template macros in Server.

Resolution

Template Type Server Cloud Notes about Server - Cloud migration
Page

(tick)

(tick)

Can be migrated automatically

Space Template (tick)

(tick)

Can be migrated automatically

Global Template (tick)

(tick)

(warning) Due to CCMA limitations, Server Global template can't be automatically migrated to Cloud. All Global Template have to be copied to Space template manually before the migration. Read more about the steps here.

Confluence Blueprint (error) (tick)
Scaffolding Blueprint (tick) (error)

Scaffolding Blueprint is not supported in Cloud and will not be migrated to Cloud




Number Data

Allows editing of numbers in either a text box or a list item.

Number

Accepts decimal, minValue, maxValue, format display, etc as filter criteria for the number value.


Does not have further criteria for the number value.

Table Data

Allows dynamic addition or deletion of rows in a table.

Table

Accepts initialRows and order as parameters for the Table data.


Does not take any further parameters

(warning) Unsupported server scenarios upon migrations.
  • Nesting Table data does not work in Cloud. 
    • In server the following table appears as a nested table 

    • Confluence Cloud does not support nested macro related functions.

    • If this scenario happens, the data inside the table will not be migrated. I.e Agenda, Notes, Status, and Actions column will not be migrated.


Text Data

Allows editing of free text data. 

Short Text, Paragraph
  • Accepts area, line, or password as Type, and richtext, text, etc as the content type
  • Accepts language, minLength, maxLength, etc as parameters for the Text data

Text input is divided into Short Text and Paragraph. Paragraph macro accepts rich text while Short Text accepts the shorter length of texts

  • Text data: Accepts Placeholder to help users input their data
  • Paragraph: Does not take any further parameter
  • Migrating Text data with type Area will be migrated as Paragraph while type Line and Password will be migrated as Text Data
(warning) Unsupported server scenarios upon migrations.
  • Text data with type Password will be migrated as Short Text macro and will not have masked view on page view

  • Rich Text content is only partially accepted
    • Find limitations at Limitations of Rich Text content of Text Data Macro (Server) migration to Paragraph Macro (Cloud)

        Please click to find more complete details

      Summary

      Confluence server supports the Text Data macro which converts to Confluence cloud Short TextParagraph. However the Paragraph macro in cloud's support of rich text migrating from server is limited. This document highlights the limitations.

      Environment

      All Confluence versions that can support CCMA(Confluence Cloud Migration Assistant)

      Cause

      Due to differences of the macros and limitation in Cloud, Paragraph macro (Text data equivalent in the Cloud) can only accept some of the rich text content features.

      Resolution

      Paragraph
      • Look out for icons highlighting limitation of the rich text data migration if any at table below.
        • (tick) - Available
        • (error) – Unavailable

        • (warning) – Partially available

      Feature

      Available

      Fonts
      • Normal text
      • Heading 1, 2, 3, 4, 5, 6
      • Bold, italic, underline
      • Strikethrough
      • Code
      • Superscript, subscript
      (tick)
      Text alignment (tick)

      Text colour

      (tick)
      Lists
      • Bullet
      • Numbered
      (tick)
      Action item (tick)
      Link (tick)
      Files & images

      (error) SCAF-I-126 GATHERING INTEREST

      Mention

      (error)

      Emoji 

      (warning) Partially Available:

      • Bit emoji (tick)
      • Confluence specific emoji (error)
      Expand (error)
      Table (tick)
      Layouts (tick)
      Quote (tick)
      Code snippet (tick)

      Panel

      • Info
      • Note
      • Success
      • Warning
      • Error
      (tick)
      Decision (tick)
      Divider (tick)
      Date (tick)
      Status (tick)



User Options

Creates a set of list options linking to users matching the filter options. Must be contained inside a  List Data macro.

User List

Accepts groups, spaces, users etc to scope the list of users as options

Accepts user groups to scope the list of users as options



Key steps

  • Upgraded Scaffolding to version 8.25.0 or above.
  • Prepared the Scaffolding data and templates in Server.
  • Performed the migration using the EAP version of Confluence Cloud Migration tool.
  • Checked and re-configured your Scaffolding data in Confluence Cloud.

Manual Migration

(error) Migration from Connector for Salesforce & Confluence Server & Data Center Server to Cloud is not auto-migratable to Cloud. Learn more about a manual migration method.

  Click here to expand...

Migration Path

Original Platform

Target Platform

Available App Migration Path

License Migration

Notes/Consideration

Server/Data Center

Cloud

Not Applicable

Needed

  • Understand the feature differences between the application for Confluence Server(DC) and Confluence Cloud.

  • Allocate time for a test migration to understand the steps required to migrate data and complete re-configuration.

  • This guide assumes you have successfully migrated your Confluence Server data into Confluence Cloud, per Atlassian's instructions (CCMA).  More Atlassian resources are available here.

Feature Differences

Migration Focus Area

Feature

Platform


Server

Cloud

Versioning/License Version Support

No migratable version

App data cannot be automatically migrated to Cloud. Learn more about a manual migration method.
License Available through both Atlassian Marketplace and ServiceRocket Marketplace. Available through Atlassian Marketplace only. Monthly subscriptions are the default option, however, discounted annual subscriptions are available upon request to our Atlassian Sales team.
Confluence Differences


Setting up the connection to Salesforce

You will need to set up the connection to the Salesforce site on the Confluence side. You will need to provide Salesforce URL, login, and password directly in this menu.

  • Only allow one connection to a single Salesforce site.
  • This app supports SSO.

You will set up the connection on Confluence, but Confluence will redirect you to the Salesforce login page for authorization.

  • Allows more than one connection to multiple Salesforce sites.
  • SSO will be managed by Confluence Cloud. Read more about this here.
Integration with other macros

Confluence server supports nested macros as well, which means Salesforce connector macros can easily be nested and integrated with other Confluence macros.

Salesforce connector server supports integration with Reporting (ServiceRocket app) through its macros Salesforce Reporter and SOQL Reporter 

Confluence Cloud does not support nested macros, which means integration with other apps by way of nesting will be limited.

Currently, Salesforce Connector Cloud does not support integration with reporting apps such as Page Property Report macros. 

  Availability of Reporting for Confluence Cloud

We're rebuilding the app for Cloud with better experience and functionality. Sign up through survey if you wish to participate in Beta releases.

Macro Differences Overview Server Macros 

Cloud Macros 

This table signifies the difference between Server/Data Center app and the Cloud version. While the function of server macros is available in Cloud, they are not directly migratable.
Displaying Salesforce object in a card format

Depending on the Salesforce object, Confluence users will choose between Salesforce Account or Salesforce Contact macro to add to the page. 

Confluence users can add any type of Salesforce Object (e.g. Salesforce Account, Contact, Opportunities, etc.) into a page, as long as they know the Object URL using the Object macro.

Displaying Salesforce data is a table format

Use Salesforce Entity to displays a list of Salesforce entities in a table format

Use Table macro to display a list of Salesforce entities in a table format

  • Salesforce Search function is available to help you craft a SOQL to be added in this Table macro.
Other Highlights

These server macros are not yet available in Cloud

These are additional features available in Cloud




Currently, ServiceRocket does not have any migration path for this app due to the differences in data storage and configuration between the two platforms. We provide a manual method instead to move data over:

  • Understand the feature differences between Connector for Salesforce & Confluence server and cloud.
  • Have an idea of what data that you would like to bring to Cloud.
  • Understand the options that you have to bring these data to Cloud.
  • Configure your Salesforce Confluence Cloud connector.


(error) Migration from Security and Encryption for Confluence Server  Server to Cloud is not auto-migratable to Cloud. Learn more about a manual migration method.

  Click here to expand...

Migration Path

Original Platform

Target Platform

Available App Migration Path

License Migration

Notes/Consideration

Server/Data Center

Cloud

Not Applicable

Needed

  • Understand the feature differences between the application for Confluence Server(DC) and Confluence Cloud.

    • (warning) The macro names differs between Server and Cloud
  • Allocate time for a test migration to understand the steps required to migrate data and complete re-configuration.

  • This guide assumes you have successfully migrated your Confluence Server data into Confluence Cloud, per Atlassian's instructions (CCMA).  More Atlassian resources are available here.


Feature Differences

Migration Focus Area

Feature

Platform


Server

Cloud

Versioning/License Version Support

No migratable version

App is not auto-migratable to Cloud. Learn more about a manual migration method.
License Available through both Atlassian Marketplace and ServiceRocket Marketplace. Available through Atlassian Marketplace only. Monthly subscriptions are the default option, however, discounted annual subscriptions are available upon request to our Atlassian Sales team.
Confluence Differences


Creating a new Secured macro

Macros are created by calling the Secure macro on a confluence page

Macros are created by calling the Secret macro on a confluence page

Decrypting the Secured macro

Approved access users need to re-enter their Confluence password to decrypt

Approved access users can click "decrypt" button to immediately access the secured content

Other functions

An access log of each macro

After decrypting the macro, approved access users can also view the access log

Centralized view of all secrets on a space

As a space administrator, you can see what secrets are stored in the space, the last time they were updated and which pages do they belong to.

Centralized audit log of all macros on a space

As a space administrator, you can use the audit logs to run audit reports, review access to secrets, find out any unintended access, detect suspicious activities and provide supporting evidence of your organization's security compliance.

Macro Differences Overview Server Macros 

Cloud Macros 

This table signifies the difference between Server/Data Center app and the Cloud version. While the function of server macros is available in Cloud, they are not directly migratable.

Secure

Encrypts text for secure sharing of sensitive information on Confluence Server pages.

Secret 

Encrypts text for secure sharing of sensitive information on Confluence Cloud pages.




Currently, ServiceRocket does not have any migration path for this app, due to security implications and the common security-related use cases for this app. We provide a manual method instead to move data over:

  • Understand the Feature differences between Security & Encryption for Confluence Server and Cloud
  • Have an idea & be able to gather all the app data that you would like to bring to Cloud
  • Understand the options that you have to bring these data to Cloud