Case Study: IoT Platform Migration from PaaS to ESP RainMaker

Companies with successful IoT products frequently outgrow their initial Internet of Things architecture. Whether dealing with a homegrown solution that does not scale or a third-party Platform-as-a-Service (PaaS) that restricts feature development, migrating to a custom solution is often required to advance the product. This was the case for a leading smart home brand when it approached us about an IoT platform migration: its existing platform failed to deliver the operational control and agility required.

Tasked with migrating the client’s connected devices from a restrictive PaaS IoT platform to a custom solution utilizing ESP RainMaker, our IoT engineering experts developed a comprehensive migration strategy and executed the implementation. The resulting solution provides the client with the flexibility they need going forward, along with full ownership of their cloud environment and IoT data.

The Technical Challenges of IoT Platform Migration

Migrating from the PaaS IoT platform to a custom RainMaker solution was driven by the need for control over feature implementation, user data, and system quality. Our client’s mobile app struggled with a 2.8-star rating, and lengthy response times from the platform provider hampered their ability to deploy improvements. Most critically, the company lacked the autonomy to customize its customer-facing applications and infrastructure.

While not a complete standalone solution, RainMaker provides a foundational architecture that greatly lowers development costs. RainMaker expects brands to differentiate their unique IoT products through custom implementation, typically handled by the brand internally or an outsourced engineering team like Cardinal Peak.

The PaaS solution’s infrastructure also posed technical challenges including:

• The platform’s proprietary communication protocols meant every device had to be reconfigured to operate on RainMaker.
• The transition required a secure method to authenticate authorized devices with the new cloud infrastructure.
• Thousands of devices were already fielded, requiring a seamless over-the-air (OTA) update to complete the migration without bricking hardware.

Given these limitations and escalating costs, the status quo was clearly unsustainable. Cardinal Peak designed, tested and implemented a remote IoT migration to efficiently and securely execute the transition.

Engineering the Shift with a Proven IoT Migration Approach

A seamless migration demanded that our engineers develop custom software to facilitate the transition from the PaaS to the AWS-hosted RainMaker environment. Our solution centered on deploying RainMaker within the client’s AWS environment, granting them full ownership of their cloud infrastructure and data pipeline.

The first step was decoding the existing firmware across the system’s multi-tier hardware architecture. Our team studied the source code and documentation to understand data processing and adapt the system to RainMaker’s framework. Specifically, we developed and managed the firmware for the main hub—powered by an ESP32 (WROOM 32E or 32UE) processor handling Wi-Fi cloud connectivity and Bluetooth-enabled mobile app provisioning during initial setup. We also adapted the firmware for the peripheral dispersal units utilizing STM32 F060 microcontrollers, ensuring secure and reliable inter-device communication with the main hub.

Next, we migrated the existing databases, moving historical data from the PaaS solution into an Amazon S3 bucket where scripts pulled it into a database for processing. We replicated a more efficient data architecture by integrating DynamoDB directly. Instead of routing data through S3, this new approach allowed the system to fetch data instantly via API calls, reducing latency and eliminating unnecessary processing overhead. We created an additional database mapping PaaS-specific metadata to RainMaker metadata, such as Node IDs.

Our team developed a precise sequence to execute the migration from the PaaS platform and initiate communication with RainMaker:

• Deploy an OTA update containing migration instructions through the existing platform.
• Implement a secure MQTT-based trigger system to initiate the transition.
• Transfer device certificates through a custom temporary MQTT-based migration proxy, managing the secure transfer of approximately 10,000 device certificates before switching to the new cloud.
• Implement a hashing mechanism to prevent unauthorized access. Devices generate a hashed signature validated by the cloud, ensuring only authenticated devices communicate.
• Establish secure communication with RainMaker using AWS IoT Core.
• Complete the transition with final firmware updates through RainMaker’s native OTA capability.

IoT Platform Migration from PaaS to a Custom ESP RainMaker Solution

Leveraging AWS’s serverless infrastructure, we designed the system to scale while maintaining optimal performance. The migration framework demonstrates how a well-architected migration strategy can eliminate platform lock-in, streamline updates and put IoT brands in complete control of their cloud infrastructure.

For this project, our client chose a two-prong approach. While all new and future products connect to the RainMaker solution for flexibility and control, previously deployed units remain on the PaaS platform. Our engineering team demonstrated the feasibility of a full migration, but the customer made the business decision to let legacy products age out.

Measurable Results of the IoT Platform Migration

This project demonstrates the significant technical and business benefits of migrating IoT products to a custom device management solution using ESP RainMaker:

Companies do not need to remain tethered to IoT platforms that limit their product roadmaps. With careful planning and technical expertise, you can transition to solutions offering superior architectural control.

Connect with our IoT Engineering Experts

Are you evaluating an IoT platform migration? Schedule an expert consultation with Cardinal Peak. Our embedded and cloud engineers will evaluate your product requirements, identify technical risks, and provide a detailed Rough Order of Magnitude (ROM) to accurately estimate your budget and timeline.