Migrating from Thingsee IoT

If you are a Thingsee IoT customer, this section helps you migrate to Haltian IoT with minimal disruption. Your Thingsee devices continue to work. The migration happens at the cloud and application layer.

What Changes

Key Concept Changes

Beyond new tools and APIs, Haltian IoT introduces some fundamental changes to how the platform is structured.

Data Model

Thingsee uses a flat structure of installations and deployment groups. Haltian IoT offers a hierarchical data model:

Organization > Space > Zone > Device

• Organization is the top-level container (your company)
• Spaces represent physical locations (buildings, floors, areas)
• Zones are polygon areas within a space (meeting rooms, desks, parking slots). Zones can be used to group devices by location but are optional
• Devices can be installed on floors with GPS coordinate information

Spaces and zones are optional. You can also organize devices using metadata:

• Device name - free-form name
• External identifier - your own ID from another system
• Keywords - tags for grouping and filtering
• Notes - free-text annotations

For example, existing Thingsee deployment groups can be mapped to keywords (e.g. #dg-mygroup) to preserve your current grouping logic.

For full details, see Data Model.

Device Identity

Thingsee identifies devices by a TUID (Thingsee Unique Identifier). Haltian IoT assigns each device a UUID, which is the primary identifier across all APIs. For example, the MQTT stream publishes data using UUID only. The original TUID and other identifiers (such as Wirepas node address) are available as cross-references through the Service API.

For user-friendly device identification, Haltian IoT uses vendorId instead of TUID. The vendorId is printed on device QR codes and labels, and works for both Thingsee and third-party devices. We recommend using vendorId as your go-to human-readable identifier going forward.

For more details, see Device Identity.

Measurements

In Thingsee, sensor data arrives as a single JSON message containing a message header and one or more sensor readings grouped by message profile (e.g. environment profile, presence profile). Your application parses the message type and extracts the relevant fields.

In Haltian IoT, sensor data is split into individual measurement types. Each measurement is a separate, named data point (e.g. measurementAmbientTemperature, measurementOccupancyStatus, measurementBatteryPercentage). This means:

• You subscribe to or query specific measurement types instead of parsing message profiles
• Each measurement has its own timestamp and value
• Filtering, aggregation, and alerting can target individual measurements directly

Haltian IoT also offers a binary passthrough mode where you receive the unaltered raw message from sensors, allowing you to do message parsing yourself if preferred.

For a full list of available measurement types, see Measurement Types.

Roles and Access Control

Thingsee has basic user/admin roles. Haltian IoT introduces a full role-based access control (RBAC) model with granular permissions:

• System Admin - full platform access
• Organization Manager - manage organization settings and users
• Space Designer - configure spaces and zones
• Asset Installer - commission and manage devices in the field
• Data Viewer - read-only access to data and dashboards

For full details, see Roles and Access.

Migration Process

Migration from Thingsee to Haltian IoT is a gradual, low-risk process. Your Thingsee environment remains fully operational until you are ready to cut over.

%%{init: {'theme': 'base', 'themeVariables': {'primaryColor': '#F6FAFA', 'primaryTextColor': '#143633', 'primaryBorderColor': '#143633', 'lineColor': '#143633', 'secondaryColor': '#C7FDE6', 'tertiaryColor': '#73F9C1', 'clusterBkg': '#ffffff', 'clusterBorder': '#143633', 'edgeLabelBackground': '#ffffff'}}}%%
flowchart LR
    A["1. Planning"] --> B["2. Sample Mirror"] --> C["3. Pilot Switch\n(optional)"] --> D["4. Full Mirror"] --> E["5. Gateway Switch"]

1. Planning and Introduction

Haltian works with you to understand your current Thingsee setup: devices, integrations, data flows, and applications. If you are using custom cloud connectors on Thingsee, this phase includes discussion on how to replicate or replace them on Haltian IoT. Together we define the migration scope and timeline.

2. Sample Data Mirror

Haltian enables data mirroring from a selected subset of your devices. The same sensor data appears in both Thingsee and Haltian IoT simultaneously. This allows you to:

• Explore Haltian IoT APIs with real, live data from your own devices
• Build and test new integrations before committing to full migration
• Validate that data arrives correctly and matches expectations
• Learn the Service API for device configuration and management
• Evaluate Haltian Field and Haltian Studio if you use similar tools on Thingsee

Your Thingsee setup continues to work normally. Nothing changes for your existing integrations.

3. Pilot Gateway Switch (optional)

If you use device configuration or downlink commands through the Open Service API, this phase lets you validate that workflow on Haltian IoT before full migration. Haltian switches a selected group of gateways directly to Haltian IoT (same firmware update as the final phase). These devices are no longer mirrored but connected natively, allowing you to test:

• Device configuration via the Service API
• Downlink commands to sensors
• Full two-way communication through Haltian IoT

Note that devices moved in this phase will no longer report data to Thingsee. There is no Haltian IoT to Thingsee mirroring.

4. Full Data Mirror

Once you are satisfied with the sample data and your new integrations are ready, Haltian enables mirroring from all your devices. At this point:

• All device telemetry flows to both Thingsee and Haltian IoT
• You switch your production integrations to use Haltian IoT APIs
• Thingsee APIs can be closed once no longer needed

5. Gateway Firmware Switch

After everything is verified to work through Haltian IoT, Haltian pushes a firmware update to your gateway devices. The gateways switch their connection from Thingsee Operations Cloud directly to Haltian IoT. This eliminates the mirroring step. Data flows natively through Haltian IoT and the Thingsee installation can be fully decommissioned.

Guides

• MQTT Comparison - Side-by-side comparison of Thingsee vs Haltian IoT MQTT

Support

For migration planning and execution, contact support@haltian.com.