General Description of Subscription Transfer Procedure

Transferring of a customer subscription is performed by provider’s or reseller’s staff in the control panel:

  1. The vendor finds the customer account in PCP/RCP, selects the list of subscriptions to be moved (it can be all subscriptions) and the target customer account.
  2. In some cases the system will correct the list of subscriptions to account for linked subscriptions (the ones that cannot be moved without each other), and asks to confirm the new (expanded) list of subscriptions. The explanation why the list was expanded is displayed. The staff member confirms the selection.
  3. The system transfers the subscriptions and displays the success message. The target customer gets notification about the new subscription.

Data moved together (or preserved) with subscription

  1. Subscription data
    • Service status history
    • Resource limits in subscription
  2. Services
    • Domains
    • SSL certificates
    • Licenses
    • Linux Shared Hosting sites
    • Windows Shared Hosting sites
  3. Hosted data
    • IIS, Apache data
    • Database data
    • DNS hosting
    • Exchange 2013 data
    • MessageLabs, MX Logic, GlobalRelay data
    • Qmail data
    • Office 365 data
    • Hosted PBX data
    • VPSs, Cloud Infrastructure Automation VMs (we imply CI Hosting)
    • APS 1.x, APS 2.x apps
  4. Users
    • Service Users – both with restricted (per subscription) access and account-wide.

Data not moved with subscription

  1. Orders.
  2. AR Documents – memos, invoices, payments, etc.

  3. Staff members.

    Note: If a staff member has restricted access to a subset of services/subscriptions, it continues to be linked to them even when these subscriptions are transferred to another account. After the transfer, these subscriptions will not be displayed to the user (because they no longer belong to the same account), but will be linked in the database. This is made to avoid problems with a common logic in Operations: a staff member that doesn’t have any access restrictions "sees" all subscriptions of the account.

  4. Customer class defined by purchased plan. The customer class of the new customer account is not changed to that defined in the subscription’s plan.

Transferring subscriptions to AD-based services

Services based on Operations AD infrastructure (listed later in this section) do not depend on a customer account the subscription belongs to. User data is bound to AD users who correspond to Operations service users. Those AD users are linked to an OU (AD Organization Unit) that corresponds to a subscription. This OU has parent OU of a vendor (though vendor OUs are not used to store any CloudBlue Commerce data, except for provider's OU that has linked "technical" AD users that can manage the service but are not reflected in CloudBlue Commerce). Vendor's OU belongs to the root "Hosting" OU.

Thus moving subscriptions between customer accounts doesn't affect AD structure, unless the subscription being moved is marked as "shared". The latter means that the subscription can have shared service users attached users who manage several subscriptions. In CloudBlue Commerce 6.0 there is a restriction that an account can have only one shared subscription that includes services based on Operations AD. CloudBlue Commerce 6.0 doesn't support merging of shared subscriptions, thus if the target already has a shared subscriptions with an AD-based service (e.g. MS SharePoint), it will not be allowed to transfer a shared subscription with, e.g., MS Exchange into that account.

The list of services based on Operations AD:

  • Hosted Exchange
  • Microsoft SharePoint
  • Windows Shared Hosting

The following AD services do not support moving:

  • Microsoft Office Communication Server
  • Microsoft Dynamics CRM
  • CDI (Customer Directory Integration)

Billing and refunding of transferred subscription

  • Resource overusage for the whole billing period (including the part occurred under the source account) will be charged to the new account (for ABP) / not refunded (for BBP and BSP).
  • Generating the billing order (to reset resource overusage) is not supported.
  • Refunding the customer account for the rest of the pre-paid period is not supported.
  • For accounts billed “per account” (aka "consolidated invoicing”) a consolidated invoice doesn't get generated. Orders pending consolidation would be consolidated under the old customer account.

Applying discounts and promotions to transferred subscription

Discounts. A discount (by customer class and by customer account) initially applied to the subscription won’t be applied to consequent billing and renewal orders if the new customer is not eligible to that discount. Conversely, if a customer is eligible to a discount previous subscription owner wasn’t eligible to, the consequent orders get discounted under the new customer account.

Promotions. A promotion (by customer class, by parent plan, by promo code) initially applied to the subscription remains attached to the subscription only if the new customer is eligible to that promotion (all promotion conditions are met and per customer limit is not exceeded). Otherwise the promotion gets detached from the subscription leaving the price in the subscription intact, so next sync with the plan (on subscription renewal or manual sync) would change the price to that set in the plan (without promotion) unless it is fixed explicitly in the subscription.

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