Important information for migrating between platforms
Since the origins of the Cloud and Server/Data Center versions of Confluence are the same, the underlying REST API platform that the CLI depends on is largely the same, including the same underlying constructs and concepts. The same Confluence CLI client supports both Cloud and Server/Data Center instances. The interface definition and abstraction are identical. We intend to maintain this level of compatibility as much as possible in the future as well.
The CLI supports a wide range of Confluence Server releases, and that means that there may be release-specific differences as Confluence and CLI support improves over time.
We do this in an upward-compatible way to protect customers' investments in scripts as we add new actions, parameters, and output. For example, an action may only work successfully when used against an instance of Confluence 6.0 or above. This is handled with the appropriate error messages and documentation. Cloud is treated similarly.
There may be actions or capabilities that are only available on Cloud or specific releases of Server or Data Center. The vast majority of functions are the same. However, there are some cases where there are differences, and those differences may change depending on the Confluence Server version.
Specific differences
Authorization and user management-related actions:
There are underlying differences in the available information and actions that can be completed.
Specifically, Cloud uses Atlassian ID, which is significantly different from standard Confluence Server user management. Also, Cloud supports and recommends using Atlassian API tokens in place of passwords. Using the CLI requires users to generate the appropriate key for their Atlassian ID.Add and remove application link actions only apply to Server.
Migration planning
You can approach migration in a similar way to an application upgrade:
Plan for some validation testing. Update your scripts for the server address and authorization changes. Review your scripts and automation documentation to understand areas of that can be affected by specific differences listed above.
Customers can have scripts using the add or store page, or similar, with wiki or storage format page content. That content may contain macros that are not available on the target instance. That content should be reviewed and updated where needed.
Differences in Confluence storage formats may also cause issues. However, the storage format is usually upward compatible.
We have no configuration or other data that needs to be migrated between instances.