...
This article is for customers considering migrating from JEMH for Jira Server/DC to JEMHC for CloudData Center to JEMH Cloud, also known as JEMHC.
Migration
...
assistance
There is currently no automated migration tool yet, primarily due to :
The content of each is just too different
As yet we don’t have some features in JEMHC (scripting)
Some features achieve the same goal but are done differently
Yes, of course its possible for an imported to be created, to take what it could from the Profile, we are still unsure of the value of this, versus the value of learning how to configure what is needed from scratch. We want to avoid ‘we imported our Profile and we don’t get the same result support tickets.differences in the data structure used for storing configuration.
For now, migration of configuration needs to be done by manually adding configuration in JEMH Cloud.
Things to consider
JEMH Server/DC is managed by you, the volume of email and the MB data volume that they comprise is down to your infrastructure to handle. In JEMHC, our infrastructure handles everything, in order to avoid becoming swamped, your JEMHC Subscription drives an allocation of a Capacity Plan based on the number of subscribed users, as your users increase, so does message volume and data capacity.
JEMHC capacity plans have gone up frequently, they are sufficient to solve most users capacity needs. If your are in an edge case of low-users, high message volume/high data capacity, JEMHC has options, through the purchase of DataPacks Data Packs (short term Message and Data increases) as well as 1y term Plan Upgrades to gain higher capacities normally attributed to a higher number of users. Both DataPacks Data Packs and Plan Upgrades are purchased out of band from Atlassian Marketplace as it has not yet matured to support such app-specific metrics . (see Licensing for details).
Related to message volume, JEMHC delivers its notification by BCC to limit the numbers of mails JEMHC needs to send through your mailservermail server. Switching this to TO will increase message volume.
...
New users start on a Starter Plan that is deliberately limited in capacity, this is to fail fast when problem scenarios occur (eg e.g. processing a POP mailbox where the ‘from now’ checkbox wasn’t set…)
...
What's missing?
Whilst there are many subtle differences between JEMH and JEMHC, given JEMHC is an entirely different implementation, the main functionality missing in JEMHC is Scripting support, which means there there is no Script Field Processor or Script Rules yet. This is a big feature to do for cloud and is something we hope to look at this year.
https://thepluginpeople.atlassian.net/browse/JEMHC-2171 : Enable a 'safe' scripting feature
...
What's different?
Profiles
JEMH Server/DC Profiles Profile exports are not currently compatible with JEMHCJEMH Cloud.
The structure of the JEMH Profile is very different from JEMHC, . JEMH Profiles still have a lot of top-level configuration whereas JEMHC was designed with lessons-learned from JEMH whereby Project Mappings in JEMHC are Profile top-level feature, containing the majority of all configuration, Rules also then provide a subset of the Project Mappings.
...
Inbound/Outbound mail server connectivity isn’t within JEMH for Server/DC, in JEMHC, we have reimplmented reimplemented all inbound/outbound mail server connectivity functionality, for . For example, JEMHC has OAuth authorization support, which requires specific admin actions to support, that cannot be migrated.
...
Customers with self-managed mail infrastructure likely have their own SSL certificate chains, these would have been imported into the JRE cacerts ca-certs file in your Server/DC Jira. As JEMHC is multi-tenant, we re-implemented this in the application, but could not easily automate a migration.
...
In JEMH Server/DC notifications are driven by IssueEvents issue events from within Jira, in Cloud these don’t exist. As JEMHC receives only a subset of webhook notification types, the Jira notification scheme ceases to be useful, . JEMHC re-imagines the requirements of notifications through Audiences (sourced from custom fields, and/or related to Jira User issue fields like reporter/assignee etc).
In JEMH Server/DC its possible to use regular expressions to match Project keys that should be handled through this particular Notification Mapping, in . In JEMHC, we avoid regular expressions and simplify things, enabling users to ‘pick’ all or nominated projects.
...
In JEMH Server/DC notification templates relate to events fired by Jira, these are not directly applicable in Cloud (we get a much coarser granularity of create/update/commented events), also the Server/DC templates inherit effectively from the host Jira application, they use Jira provided macros and cssCSS, these are not available in cloud, so we have had to rebuild from scratch, and make them specific to the JSON webhook data that Jira sends (for inclusion of data in the notification).
...
JEMH Server/DC templates and css CSS 'theme' content is not compatible with JEMHC.
In JEMH Server/DC the template/css CSS all tie into macros and other templates that are internal to Jira. JEMH templates ‘are’ Jira templates and only with Jira IssueEvent/TemplateIssue objects, in JEMHC we have reimplemented Themes from scratch that work with the cloud specific Webhooks (the equivalent of IssueEventsissue events).
Custom Macros
Its possible for custom templates to be taken from a Jira Server/DC instance and loaded into _JEMHC > Notifications > Templates > Custom Macros_, doing so will allow those templates to be available to all custom Theme templates you define.
...
JEMHC Server/DC support for Images uses static resources and specific helper methods in $jemhUtils to render image links. In JEMHC we simply this, providing markup in the UI against all uploaded images. Static resources in JEMH can be exported, as yet we don’t have an export all feature.
...
We don’t support migrating audit history from JEMH Server/DC to JEMHC, in Server/DC customer is able to retain unlimited volumes of data, in . In JEMHC (with customer opt-out) we can store the most recent 100 inbound and outbound messages for your diagnostic purposes.
...