| Include Page | ||||
|---|---|---|---|---|
|
Topics
| Table of Contents | |||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Quick Intro
tbd
Migration Options
tbd
Migration Steps
tbd
Features Parity
...
Though Atlassian believes in Cloud platform as an ultimate destination for its products and services there are clients that decided to stick to Data Center platform due to objective reasons.
They might have started with Cloud to realize they need Data Center. In some rare case there might be also a need for reverse migration from Cloud.
In Release Management Apps we support both Cloud and Data Center versions of the App with approx 80%+ feature parity between the two.
Here’re the link to Data Center ..
Caption | Link |
|---|---|
Marketplace Listing | |
Help Center | https://releasemanagement.atlassian.net/wiki/spaces/RM4J/overview |
Migration Options
Similar to https://releasemanagement.atlassian.net/wiki/spaces/RM4J/pages/1643544577/Migration+to+Cloud#Migration-Options there are 3 possible ways to engage & complete a migration project:
Manual to recreate boards on Data Center instance
Semi-automated by your engineering team and our support
With a help of Solution Partner that are either proficient in our Apps migrations and/or could be guided by us to execute.
Migration Steps
The below is an example on how migration strategy and steps might look like based on guidance we provided to one of the clients:
| View file | ||
|---|---|---|
|
Features Parity
Please navigate to the link below to have all the necessary insight about feature parity between Data Center and Cloud Apps:
...
| Include Page | ||||
|---|---|---|---|---|
|