...
For now, migration of configuration needs to be done by manually adding configuration in JEMH Cloud.
We have been adding some config section-exports in JEMH, (e.g. image blacklisting) but as yet have not added the import aspect to JEMHC.
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.
...
Inbound/Outbound mail server connectivity isn’t within JEMH for Server/DC, in JEMHC, we have reimplemented re-implemented all inbound/outbound mail server connectivity functionality. For example, JEMHC has OAuth authorization support, which requires specific admin actions to support, that cannot be migrated.
...