Skip to content

Migration process

This section outlines the plan to transition customers to the Xcelerator ecosystem and changes required to be made by application builders.

Insights Hub applications are transitioned to Xcelerator in multiple iterations. After migration, tenant users can access applications through siemens.app URLs only. Access attempts through mindsphere.io are redirected to siemens.app.

Applications hosted on siemens.app can invoke other platform services (for example, Asset Management and Time Series) only through siemens.app domains.

A customer tenant is transitioned only when all applications used by that tenant are compatible with the Xcelerator platform.

Impact of the Migration Approach

As the customer tenants are migrated in batches, the same application can be used by both migrated and non-migrated tenants.

  • Web applications detect the invocation context and invoke backend APIs through either mindsphere.io or siemens.app, based on the URL used by the user. For browser-based API calls, the respective gateway injects the correct token.
  • Backend services may receive requests through either gateway. Token structure and tenant identifier vary by gateway request. Therefore, OAuth-based authorization logic supports both token types. For token details, refer to Dual Token Awareness.
  • Applications that associate customer data with tenant identifiers have to support both identifier formats (current 8-character identifier and new 10-digit identifier). Services can handle tenant identifier changes in two ways:
    1. Mapping-based method (recommended) : Maintain the mapping of existing tenant ID to new tenant ID inside the service. Use the map to resolve existing tenant IDs when requests arrive with new identifiers. This keeps data associated with current tenant IDs during transition. After all tenants are transitioned, IDs can be replaced in one operation. Developers can download tenant ID mappings from the "Migration Assistant" Insights Hub app provisioned to developer tenants. This is the recommended approach.
    2. Migration-window method : Migrate the tenant data resources during a short migration window when a tenant is moved to Xcelerator. In this model, application builders participate in weekend migration operations. Builders are informed about tenants and migration order, and have to update the migration status, including rollback support.

High-level process

Phase 1

  1. Application builders download the tenant mapping information.
  2. Refactor application to work with Xcelerator services.
  3. Validate the application against a test tenant available in Xcelerator.
  4. Communicate the application readiness and migration method.

Phase 2 (optional)

This phase is applicable only if the application is designed to migrate the data.

  1. Insights Hub team will communicate the subset of tenants to be migrated on a specific day.
  2. Be available on the migration days to perform the data migration.
  3. Migrate customer data as per the provided order.
  4. Report the migration status.

Communication channel with Application Teams

Overview

A single interface enables streamlined communication with custom application development teams throughout the migration process. This interface provides application builders with a dedicated page to track refactoring progress, update migration status, and manage tenant mappings effectively.

For this purpose, Developer tenants are provisioned with this new application "Migration Assistant". This application is accessible through Insights Hub launchpad.

Application Provisioning and Workflow

1.Migration Readiness Tracking

The system provisions a dedicated application that enables migration readiness tracking for application providers. This application displays a comprehensive list of all applications associated with the provider. Following application refactoring to Xcelerator IAM, providers have to:

  • Update the application status to Ready for migration.
  • Refresh the application page to reflect current status.

This is done by selecting "Yes" and save the changes in the "Actions" column. homepage-migration

2.Tenant Mapping Visibility

The Tenant mapping section in Migration Assistant displays the list of user tenants (of your application) with the old tenant ID and new tenant ID. You can download the tenant mapping information in CSV format by clicking "Download CSV". This information can be used by your application to map Xcelerator tenant ID to the existing Insights Hub (IH) tenant ID.

3.Migration Status Management

After Insights Hub initiates tenant migration based on the Ready for migration status, providers can:

  • Access relevant tenants within the provisioned application.
  • Update the Migration status for each tenant accordingly.

4.Migration Completion Reporting

Upon completing data migration for a specific application and tenant, providers have to update the Migration status within the provisioned application. The status has to be designated as either:

  • Success - Indicates successful migration completion.
  • Failed - Reflects unsuccessful migration.

Application builders, once migration is initiated, need to update the status in the "tenant data migration status".

third party app

5.Traffic Redirection

Following successful tenant data migration, IH redirects traffic for migrated tenants and their associated applications from the IH gateway to the Xcelerator gateway.

6.Failure Handling Procedures

When data migration fails, traffic for the affected application and tenant continues routing through the IH gateway. Under these conditions:

  • Application functionality may be impacted.
  • Performance may not meet expected standards until migration completes successfully.
Last update: May 20, 2026

Except where otherwise noted, content on this site is licensed under the Development License Agreement.