With the Cloud Migration Assistants (available now for Jira and Confluence on Server and Data Center), customers now have a clear, step-by-step process for migrating users, spaces, projects, issues, and more from Server to Cloud. These apps server as the primary “bridge” to cloud, and help support the increased complexity and demand for cloud migration we’ve seen recently.
We’ve recently released an update to both the Jira Cloud Migration Assistant and Confluence Cloud Migration Assistant to help customers perform an App Assessment. App Assessment is a critical first step for customers migrating with apps.
But we’re not stopping there. We’re working on a platform to help Marketplace Vendors build migration paths from server to cloud that integrate with our tooling. And, the getting started docs are coming soon!
We’d like to hear from you how to best structure our documentation so you can get started and building quickly.
- I’d like to see the end to end experience in a single doc with clear instructions on which APIs are ready to use versus those that are ‘coming soon’.
- I’d like to only see docs containing APIs that are ready to use. APIs that are ‘coming soon’ should live in a separate document (i.e. a changelog).
- Neither of those options sound good to me.