Migration FAQ

Do my Thingsee devices need hardware replacement?

No. Your existing Thingsee sensors and gateways continue to work on Haltian IoT. The migration happens at the cloud layer — gateways receive a firmware update that redirects their connection from Thingsee Operations Cloud to Haltian IoT. No physical device changes are needed.

For details, see Migration Process.

Will there be downtime during migration?

No. Each migration phase runs in parallel with your existing Thingsee setup. Data mirroring ensures your devices never stop reporting, and your current integrations keep working until you explicitly switch them over.

For details, see Migration Process.

What happens to my existing MQTT integration?

Your MQTT integration will need updates. The authentication method, topic structure, and payload format have all changed between Thingsee and Haltian IoT. However, you can build and test the new integration while your existing one continues to run.

For a side-by-side comparison, see MQTT Comparison. For the new API reference, see Stream API.

Can I run both platforms in parallel?

Yes. Data mirroring sends the same sensor data to both Thingsee and Haltian IoT simultaneously. You can develop and validate your new integrations against live data without any risk to your production system.

For details, see Sample Data Mirror.

How do I map Thingsee TUIDs to Haltian IoT UUIDs?

Use the Service API to query device mappings. Each device in Haltian IoT has a UUID as its primary identifier, but the original TUID and vendorId (printed on device labels) are available as cross-references.

For details, see Device Identity and Service API.

Do I need new certificates for MQTT?

No. Haltian IoT uses API key authentication (username/password) instead of client certificates. You no longer need to manage .pem and .key files. API keys are self-service via IoT Studio with a 90-day validity period.

For details, see MQTT Comparison — Authentication.

What about my historical data in Thingsee?

Historical data remains in Thingsee for the duration of your Thingsee contract. Haltian IoT begins collecting data from the moment mirroring is enabled. If you need historical data migrated, discuss this with Haltian during the planning phase.

How long does the migration take?

The timeline depends on deployment size and integration complexity, but typically takes weeks rather than months. The phased approach (sample mirror → full mirror → gateway switch) lets you control the pace and move to the next phase only when ready.

For details, see Migration Process.

Can I migrate only some devices first?

Yes. The sample data mirror phase lets you select a subset of devices for initial testing. You can validate everything works with a small group before enabling mirroring for your full deployment.

For details, see Sample Data Mirror.