Connector for Salesforce and Confluence Feature Differences

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. This is covered in detail in the table below. 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
Migration Focus Area	Feature	Server	Cloud
Versioning/License	Version Support	No migratable version	App data cannot be automatically migrated to Cloud. Learn more about a manual migration method.
Versioning/License	License	Available through Atlassian 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.
Confluence Differences	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		Salesforce Account Salesforce Contact Depending on the Salesforce object, Confluence users will choose between Salesforce Account or Salesforce Contact macro to add to the page.	Object macro 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		Salesforce Entity Use Salesforce Entity to display a list of Salesforce entities in a table format	Table macro Use Table macro to display a list of Salesforce entities in a table format A 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 Salesforce Reporter SOQL Reporter Vcard Link	These are additional features available in Cloud Salesforce Search Associating a Case with a Confluence Page

Migration Path

Feature Differences

Cloud