Overview

This article contains an overview of the migrations.

It is important to distinguish and understand the different types of migrations that can occur within the Emersion platform. It is quite easy to get them confused, or assume there is only one way to perform a migration, but it is a very important distinction to make because they function very differently. 



Package Subscription Migrations

In the past, these have sometimes been referred to as service migrations, however the use of the term has been dropped since service type migrations have been introduced to help avoid any confusion between the two.  They are very occasionally referred to as 'normal' migration. This stems from the fact that this type of migration that was developed first by Emersion.

This type of migration permits services to be migrated from from one package to another. 

Service types contained in the source and destination packages must be the same, although a services can be dropped when moving from a bundled package plan to an unbundled one. 

Package Plans are placed into a contract pool.  Migrations between plans in the same contract pool are permitted.  Migrations between plans in different contract pools are not permitted.  

Contracts are not migrated.

In the case of a break of contract, you cannot automatically waive upgrade, downgrade, or cross-grade fees.

Any bolt-ons and bolt-on add ons are not migrated with the service. 

Included Value Plans

When a mid cycle migration occurs and the user has not exceeded their included value:

  • the period will be shortened
  • unused portion of the any access fee is credited back
  • the usage allowance is also reduced if the plan is prorated.

When a mid cycle migration occurs and the service user has exceeded their included value:

  • they will be charged excess usage charges
  • under some circumstances, they can incur excess usage charges.

The activation portal is not used to activate services, since the service itself is not changed, only the plan the end user has subscribed to.

Package subscription migration showing the shortened package period before and after migrating.



Service Type Migrations

Rather than forcing you to break out of the contract and create a new one on the new subscription, service type migrations will permit the preservation of the contract and to carry it forward to the new subscription.

It is possible to waive contract break out, upgrade, downgrade and cross-grade fees.

Provides the ability to retain the included value and bolt-on allowances from the previous (source) plan, so the end user doesn't get charged excess as a consequence of migrating. 

If the user is already over their included value or bolt-on allowance at the time the migration is performed, they will still be charged excess in accordance with to the source package plan's settings. But these fees can be waived on a case-by-case basis.

The activation portal provides the ability for the end user to initiate the final stage of migration at a time of their choosing.

Take me to Service Type Migrations landing page.

Service type migration showing the shortened package period before and after migrating.