Document Center

All Products

Document Center

IoT Platform:Feature usage after migration

Last Updated:Jun 16, 2026

After products and devices are migrated from a public instance to an Enterprise instance, some features require reconfiguration or behave differently. This topic covers feature-specific usage notes.

Background information

For more information about instance migration, see Must-reads before you start.

For more information about the features of IoT Platform, see Features.

Device connection

Feature	Description
Device-side SDK	The device-side SDK automatically connects to the Enterprise instance. No changes are required.
Device security authentication	Supports one-device-one-secret and one-product-one-secret pre-registration authentication.
NB-IoT device	Migration of devices that use the NB-IoT network protocol is not supported.

Device management

Feature	Description
TSL model	Migrated product data does not need to be modified. You can add or modify the configuration as needed. Note The legacy public instance retains the original data. To prevent errors, manually delete the data after the migration is complete and your services run as expected.
Data parsing
Tags	Add tags again in the Enterprise instance.
Device groups	Add groups again in the Enterprise instance. Note The devices are still displayed in the original groups of the legacy public instance. An error is reported when you perform operations on these devices. Delete the groups that correspond to the migrated devices.
Advanced search	You can retrieve data that has been migrated to the destination Enterprise instance.
Device tasks	Create product-related tasks again in the Enterprise instance.
Device shadow	You can continue to use the device shadow caching mechanism.
File management	You can view files uploaded by devices in the destination Enterprise instance.
NTP service	You can continue to use the NTP service in the Enterprise instance to obtain the server-side time when it cannot be retrieved in real time.
Gateway sub-devices	Sub-devices can connect to IoT Platform only if the topology does not change during migration. Otherwise, an error occurs when sub-devices connect to IoT Platform.
Device distribution	For globally distributed devices, an error occurs when a device establishes a connection after the instance migration is successful.

Message communication

Feature	Description
Server-side subscription	You can use the migrated subscription settings and forwarding rules. You can also add or modify server-side subscriptions and data forwarding rules. Warning If you configured AMQP server-side subscriptions, configure a new AMQP client SDK. If you use server-side subscriptions or data forwarding for cloud APIs, also modify the request parameters of the related APIs. For example, the RuleId parameter of the GetRule operation. For more information, see Developer guide.
Data forwarding
Scene orchestration	Create scene orchestration rules again in the Enterprise instance.
RRPC communication	When you call communication APIs such as RRpc and PubBroadcast, you must pass the Enterprise instance ID.
Broadcast communication

Monitoring and O&M

Feature	Description
Real-time monitoring	Metrics for devices, messages, TSL models, and the rules engine change as the migration progresses. Monitor device connections and message communication in real time to verify they work as expected. During migration, business data shifts from the source public instance to the destination Enterprise Edition instance, causing metrics to decrease in the source and increase in the destination. If an alert rule on the public instance monitors for value drops, the migration may trigger an alert. We recommend that you disable or adjust the alert rule to match your business requirements. For more information, see Configure alert rules.
O&M dashboard
Online debugging	Send instructions to migrated devices from the Enterprise instance to debug device-side features.
Device emulator	In the public instance, shut down the device emulators for the devices to be migrated. Then, restart the device emulators in the Enterprise instance.
Simple Log Service	Simple Log Service in the Enterprise instance cannot query historical data.
OTA update	To ensure that devices can receive over-the-air (OTA) updates, add OTA update tasks again in the Enterprise instance.
Remote Configuration	Perform remote configuration again in the Enterprise instance.
Alert Center	Configure alert information again in the Enterprise instance.
Secure Tunnel	To ensure remote access to devices, create device secure tunnels again in the Enterprise instance.

Developer guide

Cloud API calls:

When you call the relevant service APIs, modify the request parameters to include the Enterprise instance ID.

The cloud APIs Pub, RRpc, InvokeThingService, and SetDeviceProperty are compatible with the Enterprise instance ID. You can submit a ticket to request this feature to reduce server-side modifications.

Warning
When you use a cloud SDK with an Enterprise instance, you must include the instance ID in your API calls. Otherwise, the calls fail and affect your services. For information about the required modifications, see Preparations before migration.
AMQP client connection:

If you configured AMQP server-side subscriptions or data forwarding to AMQP by using the rules engine, you must update the AMQP client SDK. Copy the new Enterprise instance ID and access domain name to configure a new AMQP client. After the grayscale migration, copy and update the consumer group ID, and then start the new AMQP client.

Warning
If you have configured AMQP server-side subscriptions, you must run an AMQP client for both the public instance and the destination Enterprise instance. This ensures that an AMQP client is available on both instances to receive data and prevents data loss.