Transition Guide

In July 2025, Nordic Semiconductor acquired Memfault. As a result, we are integrating both platforms into a unified experience. This means that certain functionality like Security Services, Location Services, and Device Management are now available alongside Memfault's Device Observability, Debugging, and over-the-air (OTA) update offerings. Once fully integrated, the new nRF Cloud experience will be an end-to-end cloud solution for Nordic Semiconductor customers across all stages of their development and production product lifecycles.

Much is changing to provide you with a better experience. As we integrate systems, update documentation, and deliver new capabilities, we are evolving to support you. Most features have been migrated as of October 2026. For features that have not yet been migrated, existing users can access them using the Legacy App button in the left navigation menu. Features available in the new nRF Cloud platform will not be available in legacy nRF Cloud.

If you are a new user, we do not recommend using functionality in the legacy nRF Cloud experience. Review the current docs or reach out to us in DevZone if you have questions.

We are working to fully deprecate the legacy nRF Cloud UI by December 31, 2026.

Platform changes

Login and password reset

You can continue to sign up and log in from nrfcloud.com, where you can sign up for the new nRF Cloud experience.

New or Existing myNordic User

myNordic users will not have access to the legacy nRF Cloud. myNordic login has been updated to only allow for the new nRF Cloud experience. If you need to use the legacy features during the transition, you must sign out, re-register at nrfcloud.com using the same email address used for myNordic. This will create a new nRF Cloud account and link it to your existing account.

Email + Password

We have unified the email and password login. Only legacy nRF Cloud customers who signed up for a legacy account or sign up for a new nRF Cloud account will have access to the legacy nRF Cloud UI.

Getting started

Inviting and managing users: Organization admins can invite new users. Go to Admin > Invites and enter the names and email addresses of the users. Go to Admin > Users to adjust permissions or remove users.

Projects: Currently, the new nRF Cloud experience only supports a single project per organization.

See Getting started for more information.

Security Services

Identity Services and Provisioning Services have been consolidated into Device Onboarding. Adding a device in the new nRF Cloud experience both claims and onboards it, so you no longer need to configure auto-onboarding rules.

For nRF9151 and nRF9161 devices, no firmware or SDK changes are required. You continue to use the identity attestation token returned by AT%ATTESTTOKEN. Bulk onboarding now uses an organization auth token (OAT), organization- and project-scoped API URLs, and a CSV containing each device ID and attestation token. Devices are initially assigned to the default cohort.

Legacy claiming is no longer available in the legacy nRF Cloud UI but remains available via the API. For more details, examples and troubleshooting, see Secure Device Onboarding. Device Onboarding also supports the nRF93M1. Deleting a device in the new nRF Cloud experience also unclaims it, replacing the two separate operations in legacy nRF Cloud. To remove a device from the fleet while retaining its claim, deactivate it instead.

Location Services

nRF Cloud offers Location Services for A-GNSS (Assisted Global Navigation Satellite System) and P-GNSS (Predicted GNSS) for select Nordic modems, as well as Wi-Fi, Single Cell, Multi-Cell, and Groundfix support. You can access these through nRF Cloud via device-to-cloud or cloud-to-cloud.

You must use an Organization Auth Token. To set up an Organization Auth Token, go to the Location Services section of nRF Cloud, or go to Admin > Manage Organization Auth Tokens. If you have existing integrations using a service or evaluation token, see Location Services for the migration steps.

Firmware over-the-air (FOTA) updates

nRF Cloud has unified the legacy nRF Cloud firmware over-the-air (FOTA) update experience. You do not need to make firmware or Software Development Kit (SDK) changes to manage this transition. The update is backward compatible for nRF Cloud customers while providing enhanced functionality to monitor releases, compare versions and deploy secure and scalable updates with controlled releases. You now create Releases and Deployments instead of bundles and jobs; see New FOTA Experience for what to set up before your first update.

Device fleet and management

All devices now appear in the new nRF Cloud experience, giving you the ability to onboard the nRF91 Series and the nRF93M1, and to rename or manage devices.

nRF Cloud no longer supports managing devices via Groups, a legacy nRF Cloud feature. To work with the new nRF Cloud experience's FOTA, you manage devices via Cohorts, which allows each device to be in a single cohort.

Billing and service usage summary

Billing continues to be powered by the nRF Cloud experience. No changes are required. Go to Admin > Billing to manage your plan, upgrade, or update billing details. This opens the nRF Cloud billing experience in a new tab.

Account management

Account admins can add users and create teams by going to Settings > Admin and managing user permissions. Only admins can perform certain functions, such as creating Organization Auth Tokens, adding or removing users, and setting account-level permissions for features like in-app AI. For details on user roles and permissions, please see User Management and Access Control: Teams and Roles.

APIs

We are consolidating our APIs to be available under one umbrella. Documentation and web applications will be updated as part of this process.

Documentation

All documentation continues to be available at docs.nrfcloud.com. We are updating, revising, and removing content as needed to reflect the new nRF Cloud experience.

Message Routing Service

The Message Routing Service is now available in the new nRF Cloud experience under Data Ingestion > Message Routing, where Organization Admins can create, verify, test, and manage destinations and review their recent delivery activity. It is available on all plans; Developer-plan organizations can have one destination. Destinations are shared across the organization and are managed from its default project.

Existing destinations carry over unchanged, and the legacy nRF Cloud experience continues to work as before. No data migration is required. See Transitioning Message Routing for a mapping of existing features to the new experience.

Device Shadow

Device Shadow is now available from a device's Device Shadow tab in the new nRF Cloud experience. Existing shadow data appears automatically, and device MQTT and CoAP integrations continue to work without firmware changes.

See Device Shadow to work with shadows in the new experience. If you use the legacy web app or REST API, see Transitioning Device Shadow for a workflow comparison and API migration guidance.

MQTT protocol support

MQTT (Message Queuing Telemetry Transport) functionality remains supported for existing customers. We are prioritizing CoAP (Constrained Application Protocol) support to provide cellular modem customers with a power- and bandwidth-optimized device-to-cloud solution.

Frequently asked questions

Will APIs be changing?

Yes. We are updating the APIs to use Organization Auth Tokens and will deprecate the Legacy nRF Cloud "Team" API Keys. Some APIs will be fully deprecated, and others will have new endpoints. For example, GET https://api.nrfcloud.com/v1/devices will become GET https://api.nrfcloud.com/v1/organizations/{orgSlug}/projects/{projectSlug}/devices. When this begins, we will publish a full Transition Guide and work with impacted customers. You can begin using any APIs listed in the Memfault API Documentation.

Will pricing change?

No. Pricing for existing customers will not change. You can review pricing on the Pricing page.

Are there quotas or limits on the number of devices I can connect?

If you are on a Developer plan, the device limit remains at 10, and your usage now includes observability features to try. On the Pro plan, there are no device limits.

What happens to my old data in nRF Cloud?

No data is being deleted as part of this integration. We are changing the way you access and manage your data in nRF Cloud.

Do I need to make firmware changes or update my SDK version?

Our focus is on maintaining backward compatibility to minimize the chance of requiring firmware or SDK updates. If this becomes necessary, we will work with customers to support them through a transition period.

Who do I contact for support?

Contact Nordic Semiconductor support on the DevZone community forum.

What about ordering IMEIs?

We will continue to link to the legacy nRF Cloud experience from the new nRF Cloud experience to purchase International Mobile Equipment Identity (IMEI) numbers for the nRF9161 or list IMEIs for the nRF9160, nRF9161, and nRF9151. You can also continue to use the IMEI APIs.

Why does a + Create Project option appear in my menu if I cannot create a second project?

Currently, the new nRF Cloud experience only supports a single project setup. We are working to enable customers to create additional projects.

Why is A-GNSS and P-GNSS only available for select modems?

A-GNSS and P-GNSS support specific Nordic cellular modems only.

Can I add a Bluetooth device that is not supported in device onboarding?

Yes. All Nordic chips are supported in nRF Cloud. You can continue to use them with the Memfault SDK built into nRF Connect SDK.