Migration Overview and General Procedure

Migrating CloudBlue Commerce to Azure cloud gives both providers and their customers such key benefits of managed PaaS solutions as faster time-to-market and lower operational and maintenance costs.

Migration Scenarios

General Migration Procedure

Prerequisites:

  • Azure cloud infrastructure is set up. For instructions, please refer to Deploying CloudBlue Commerce to Azure Cloud.

    Important: When deploying the Azure cloud target nodes for DNS hosting, make sure they have the same names as the corresponding on-premise source nodes.

  • A site-to-site open VPN connection is set up between the deployed Azure cloud infrastructure and your on-premise CloudBlue Commerce deployment.

    Note: An open VPN connection will allow the Operations management node to manage the migrated service nodes in Azure while the platform nodes are being migrated; this will minimize the system downtime.

Migration:

To migrate your on-premise CloudBlue Commerce installation to the Azure cloud infrastructure:

  1. Migrate service nodes (the Frontnet zone) one by one.
  2. Migrate APS Application Endpoints.
  3. Migrate the CloudBlue Commerce platform (the Backnet and DBnet zones).

Supported System Configurations

This migration solution supports the migration of:

  • CloudBlue Commerce versions 7.4, 8.0, 8.2, 8.3.
  • CloudBlue Commerce Platform core components: OSS, BSS, UI, Branding, DNS, Online Stores, APS endpoints.
  • CloudBlue Commerce cloud modules and services: Office 365, Azure, WebHosting Plesk.

Non-Supported Configurations

This migration solution does not support the migration of traditional hosting modules: Linux Shared Hosting, Windows Shared Hosting, WebHosting Linux (NG), Qmail, Blackberry, Hosted Exchange, SharePoint, Lync, VPS Hosting.