Migrating a Subscription to Another Service Template

This chapter is about migrating your subscriptions to another service template.

Important: If your CloudBlue Commerce installation is used with Billing, the procedure of switching the service template can be performed only in Billing. In that case, refer to the Billing documentation for the detailed instructions.

As described in the previous topic, a subscription can be upgraded or downgraded by changing the resource set or limits of the resources in the service template the subscription is based on. In this topic, we describe how the subscription can be migrated to another service template.

By subscription migration, we mean the switching of the service template the subscription is based on.

Important: This process requires a lot of attention, because a misconfiguration can lead to loss of functionality used by customers.

In general, we suppose that such migration is targeted to provide your resellers and customers with new features that the destination service template contains.

The safest migration conditions are when the target service template contains all the resources of the source service template, the corresponding limits are the same or greater, and the activation parameter values are the same. The easiest way to ensure this is by using a clone of the source service template for the target service template.

  1. Locate the subscription you want to migrate in the Operations > Subscriptions.
  2. Click the subscription's name. On the General tab, find the service template this subscription belongs to.
  3. Click the name of that service template.
  4. On the General tab, click Create a Copy.
  5. The copy of the service template will be created immediately with the name "Copy of service template #N". You can change its name by editing the parameters on the General tab.
  6. Deactivate the service template by clicking the corresponding button on the General tab.
  7. Open the Resources tab and click Add New Resources. Select the necessary resources and click Submit to save them.
  8. Activate the service template by clicking the corresponding button on the General tab.
  9. Go back to the subscription you wish to migrate to the newly created service template and click Change Service Template.
  10. Using the drop-down list, select the new service template and click Submit.

After several minutes, refresh the page. On the General tab, in the Service Template area in the Name field, you will find the name of the new service template the subscription is based on.

This operation can also be performed to downgrade the existing subscription. Below we describe the main factors that affect the results of the migration.

  • Resource Types. The availability of the necessary resource type in the destination service template directly influences the results you get. If you included the same resource type to the destination service template, the resources will be smoothly migrated. If the destination service template contains another resource type based on the same resource class, this resource will be migrated to the new resource type. If the destination service template does not have the resource type, which was in the source service template, this resource will be completely unprovided, meaning that if there were already objects created by the customer (the resource is used), they will disappear without the possibility of being restored.
  • Limits and usage. Each resource type in the source service template has a limit on its usage by the customer. You can set the same limits on resources in the destination service template or increase them. The migration will happen without any consequences for the subscriber. But if you set the lesser limits on the same resources, the migration will fail. See "Allow overuse".
  • Allow overuse. At System > Settings > System Properties in the Core group, there is a parameter called Allow resources overuse during subscription migration. If this property is enabled, you can downgrade any subscription with overuse. In that case, in CCP > Home > Resource Usage, the overuse of resources will be displayed. If the property is disabled, the downgrade will fail in this situation. If the limits on the target subscription are set to the zero for some of the services, they will be unprovided regardless of this system property value.
  • Activation Parameters. If the activation parameters of the destination service template differ from those of the source service template, they will be rewritten. However, most of the activation parameters affect only the provisioning of the subscription, so switching to the service template with different values of activation parameters will not have any effect. There are only a few exceptions; see the service-specific sections below.

Below are some examples of the migration scenarios:

Scenario Subscription Before Migration

Destination Service Template

Subscription After Migration

All resource types are presented in the destination service template with the same activation parameters as in the source service template. The limits on the existing resource types are increased.

A new resource types is added.

  • Resource type "A"

    • Limit – 10
    • Usage – 5
    • Activation parameters "A, B, C"

  • Resource type "B"

    • Limit – 5
    • Usage – 2
    • Activation parameters "A, B, C"

  • Resource type "A"

    • Limit – 20
    • Activation parameters "A, B, C"

  • Resource type "B"

    • Limit – 10
    • Activation parameters "A, B, C"

  • Resource type "C"

    • Limit – 3
    • Activation parameters "A, B, C"

  • Resource type "A"

    • Limit – 20
    • Usage – 5
    • Activation parameters "A, B, C"

  • Resource type "B"

    • Limit – 10
    • Usage – 2
    • Activation parameters "A, B, C"

  • Resource type "C"

    • Limit – 3
    • Usage – 0
    • Activation parameters "A, B, C"

All resource types are presented in the destination service template with the same activation parameters as in the source service template. The limit is decreased below the usage level, and the “allow overuse” parameter is switched on.

  • Resource type "A"

    • Limit – 10
    • Usage – 5
    • Activation parameters "A, B, C"

  • Resource type "B"

    • Limit – 5
    • Usage – 2
    • Activation parameters "A, B, C"

  • Resource type "A"

    • Limit – 3
    • Activation parameters "A, B, C"

  • Resource type "B"

    • Limit – 5
    • Activation parameters "A, B, C"

  • Resource type "A"

    • Limit – 3
    • Usage – 3
    • Overuse – 2
    • Activation parameters "A, B, C"

  • Resource type "B"

    • Limit – 5
    • Usage – 2
    • Activation parameters "A, B, C"

All resource types are presented in the destination service template with the same activation parameters as in the source service template. The limit is decreased below the usage level, and the “allow overuse” parameter is switched off.

  • Resource type "A"

    • Limit – 10
    • Usage – 5
    • Activation parameters "A, B, C"

  • Resource type "B"

    • Limit – 5
    • Usage – 2
    • Activation parameters "A, B, C"

  • Resource type "A"

    • Limit – 3
    • Activation parameters "A, B, C"

  • Resource type "B"

    • Limit – 5
    • Activation parameters "A, B, C"

Error. The scenario is not supported.

All resource types are presented in the destination service template with the same activation parameters as in the source service template. The limits are set to zero. The status of the "allow overuse" parameter does not matter.

  • Resource type "A"

    • Limit – 10
    • Usage – 5
    • Activation parameters "A, B, C"

  • Resource type "B"

    • Limit – 5
    • Usage – 2
    • Activation parameters "A, B, C"

  • Resource type "A"

    • Limit – 0
    • Activation parameters "A, B, C"

  • Resource type "B"

    • Limit – 0
    • Activation parameters "A, B, C"

  • Resource type "A"

    • Limit – 0
    • Usage – 0 (services are unprovided)
    • Activation parameters "A, B, C"

  • Resource type "B"

    • Limit – 0
    • Usage – 0 (services are unprovided)
    • Activation parameters "A, B, C"

One of the resource types is not present in the destination service template.

  • Resource type "A"

    • Limit – 10
    • Usage – 5
    • Activation parameters "A, B, C"

  • Resource type "B"

    • Limit – 5
    • Usage – 2
    • Activation parameters "A, B, C"

  • Resource type "A"

    • Limit – 10
    • Activation parameters "A, B, C"

  • Resource type "A"

    • Limit – 10
    • Usage – 5
    • Activation parameters "A, B, C"
  • Resource type "B" – unprovided

One of the resource types is not present in the destination service template but there is another resource type in the destination service template that is based on the same resource class.

  • Resource type "A" (resource class "A")

    • Limit – 10
    • Usage – 5
    • Activation parameters "A, B, C"

  • Resource type "B"

    • Limit – 5
    • Usage – 2
    • Activation parameters "A, B, C"

  • Resource type "C" (resource class "A")

    • Limit – 10
    • Activation parameters "A, B, C"

  • Resource type "B"

    • Limit – 5
    • Activation parameters "A, B, C"

  • Resource type "C" (resource class "A")

    • Limit – 10
    • Usage – 5
    • Activation parameters "A, B, C"

  • Resource type "B"

    • Limit – 5
    • Usage – 2
    • Activation parameters "A, B, C"

All resource types are presented in the destination service template but activation parameters differ.

  • Resource type "A"

    • Limit – 10
    • Usage – 5
    • Activation parameters "A, B, C"

  • Resource type "B"

    • Limit – 5
    • Usage – 2
    • Activation parameters "A, B, C"

  • Resource type "A"

    • Limit – 10
    • Activation parameters "D, E, F"

  • Resource type "B"

    • Limit – 5
    • Activation parameters "D, E, F"

  • Resource type "A"

    • Limit – 10
    • Usage – 5
    • Activation parameters "D, E, F"

  • Resource type "B"

    • Limit – 5
    • Usage – 2
    • Activation parameters "D, E, F"

© 2025 Ingram Micro, Inc. All Rights Reserved. Privacy Policy, Terms of Use and Legal

CloudBlue, an Ingram Micro business, uses cookies to improve the usability of our site. By continuing to use this site and/or logging in you are accepting the use of these cookies. For more information, visit our Privacy Policy.
I accept