How to Successfully Migrate off Google IoT Core

Welcome to the latest edition of The IoT Pulse - an exclusive collection of opinions, insights, and commentary from industry experts on key topics and questions in the world of #IoT , #AI , and #DigitalTransformation . Be sure to hit subscribe today so you don’t miss out on future editions!

It’s been ten months since Google announced the deprecation of Google IoT Core Services (“IoT Core”). For those who are not as familiar with IoT Core, it is a managed service by Google Cloud that enables organizations to securely connect, manage, and gather data from IoT devices, providing a centralized platform for IoT device communication, data processing, and analysis at scale – while also simplifying IoT device management and data ingestion and offering seamless integration with other Google Cloud services for advanced analytics and processing capabilities.

Now, the deprecation deadline is just ten weeks away. If existing IoT Core customers want to maintain the functionality and continuity of their IoT solutions, they must migrate off IoT Core before August 16, 2023.

We asked a Partner expert how small and large organizations have successfully migrated off Google IoT Core while avoiding disruption to their IoT solutions.

Justin Mikolay , SVP of Business Development at Leverege

At Leverege, we’ve helped companies around the world migrate from IoT Core. In the process, we’ve learned successful migrations require (1) timely completion; (2) minimal service interruption; (3) cost-effectiveness; (4) matching (or better) functionality; (5) scalability and futureproofing; and (6) maintained security of edge devices.?

?At this point, it’s too late to custom-build an IoT Core replacement. Instead, we recommend that organizations focus on finding a suitable technology partner that offers a replacement ready for implementation today.?

?When evaluating potential technology partners, consider if they offer similar pricing tiers, features, and performance as IoT Core, plus additional capabilities. Key capabilities include easy and secure device-cloud connection, device management, secure key pairs, supported protocols, and no-code message routing.

?Once your organization has selected a technology partner, migration involves four steps:??

1. Migrate registry data to the IoT Core replacement product;
2. Update firmware for all devices to integrate with the IoT Core replacement product;?
3. Update cloud infrastructure, if necessary; and
4. Test the enterprise IoT solution.?

?We’ve found updating firmware can be operationally intensive for large enterprises. If existing devices support Firmware Over the Air (FOTA), firmware updates can be done with relatively little overhead for devices in the field. Otherwise, each device will need a high-touch update to continue functioning as expected. If this applies to you, ensure you have a detailed operational plan in place now to manually update every device.?

?We recommend starting with a small group of test devices, validating new connections, and then migrating the remaining devices in your solutions. This can be done using available documentation, and it is often most efficient to migrate test devices during live, white-glove migration service calls between technical teams. Start the process today!?

1. A Step-by-Step Guide to Successfully Migrate from Google IoT Core by Leverege
2. 5 Reasons Why Google Cloud is (Still) the Best Cloud for IoT by Leverege

Keep the conversation going! Let us know if you have any further questions on how to navigate the deprecation of Google IoT Core Services in the comments below.?

Curious about how you or your company’s experts can be featured? Reach out to me at [email protected] or connect with me on LinkedIn: Ryan Chacon

Next week, we will be featuring experts from our Partner Community, including Libelium , the LoRa Alliance , and others who will discuss the role IoT plays in building #smartcities . So be sure to subscribe so you don’t miss it!

See you next week!