BMC Helix Cloud Migration service
The migration of BMC Helix services and/or tenant from an existing cloud service location to another involves several tasks in the following phases. After BMC completes the provisioning of your applicable environments, which typically include development, QA, and production environments and may include any additional environments in your subscription, the major tasks involved in the migration process include:
- Preparation and readiness
- Non-production migration
- Production migration
The datacenter migration will retain the version of your BMC Helix instance and there will be downtown required when migrating each environment. Please avoid making any changes to your non-production environments once the database copy and migration activity is in progress. The total duration of the move is typically 3-weeks, including a week of readiness and pre-check activities.
Licensing
The BMC Helix Cloud Migration service is available with the purchase of any of the following line items from your ordering document:
| License | Unit of Measurement | Service location |
| BMC Helix Cloud Migration | Each | Target datacenter service location mutually agreed with and approved by BMC |
With the "Each" unit of measurement, you are entitled to a one-time migration project under the scope of BMC Helix subscription services defined between the customer and BMC to a single, target datacenter service location.
Additional license terms
The following additional terms apply to the BMC Helix Cloud Migration service:
- The scope of BMC Helix services defined under each migration project must be feasible and supported by BMC
- In the event of migrations to multiple target service locations are required, the purchase of additional SKUs may be required
- Please notify BMC 30-days advanced notice for a datacenter migration request to ensure proper planning and scheduling
- The UAT and go-live dates are subject to change within reason, especially in regard to pending customer actions or inaction
- Licensing terms and conditions are as defined in the governing master agreement and take precedence over any published description from this site
Preparation and readiness
Please create a Support Case after purchasing the BMC Helix Cloud Migration service and include details of the migration and datacenter move being requested. Datacenter migrations are subject to a technical review by the BMC team.
| Customer actions | |
| 1. | You will receive a Datacenter Migration FAQ document from your migration Project Manager, please review and feel free to raise any questions at this time. |
| 2. | If you have allowlisted the BMC Helix public IPs in the past, please heck with your network team the firewall settings to update the BMC Helix public IP accordingly. |
| 3. | Please review the heads-up email notification containing your change window and datacenter details. You can coordinate with your Project Manager to change or confirm the change window, if required. |
| 4. | Please review the subprocessor email notification for the change in datacenter location and accept the notice to proceed with the migration. |
| 5. | Share the current Client Gateway configuration file to your migration Project Manager. |
| 6. | Ensure you are ready to configure the new Client Gateway and SAML file during the migration change window. |
| BMC actions | |
| 1. | Conduct a technical review of the migration. |
| 2. | Schedule and outline the migration plan for customer review and approval. |
| 3. | Check infrastructure readiness and make a copy of the database for migration to the destination datacenter location. |
Non-production migration
The duration of migration and post-migration activities are anticipated to be within 7-9 hours.
| Customer actions | |
| 1. | A CRQ (Change Request) will be generated for your reference. No further actions are required. |
| 2. | Your Project Manager will collaborate with you to configure Client Gateway and SAML authentication during the migration window on non-production environments. |
| 3. | Please perform UAT post-migration, including validation of all integrations, sanity checks on functionality, ensure the updated allowlist is in place for BMC Helix public IPs. |
| BMC actions | |
| 1. | Restore the source database copy in the destination datacenter location. |
| 2. | Deploy BMC Helix ITSM and underlying platform. |
| 3. | Deploy the rest of the applications including, but not limited to, Digital Workplace, Innovation Suite, etc. |
| 4. | Conduct post-migration activities and testing, then release the environments to customer for UAT. |
Production migration
The duration of migration and post-migration activities are anticipated to be within 7-9 hours.
| Customer actions | |
| 1. | A CRQ (Change Request) will be generated for your approval. |
| 2. | Your Project Manager will collaborate with you to configure Client Gateway and SAML authentication during the migration window on the production environment. |
| 3. | Please perform UAT post-migration, including validation of all integrations, sanity checks on functionality, ensure the updated allowlist is in place for BMC Helix public IPs. |
| BMC actions | |
| 1. | Restore the source database copy in the destination datacenter location. |
| 2. | Deploy BMC Helix ITSM and underlying platform. |
| 3. | Deploy the rest of the applications including, but not limited to, Digital Workplace, Innovation Suite, etc. |
| 4. | Conduct post-migration activities and testing, then release the environments to customer. |