No. Your applications, credentials, and your users’ access to your applications are unaffected. You will only lose access to the Developer Portal itself. You won’t be able to register new applications, change settings, or view your data until you migrate to Home Connect login.

No. The people using your application are not part of this migration. Their accounts, tokens, and sessions will remain unchanged, and they won’t be asked to sign in again.

No. Your integration, endpoints, credentials, and OAuth flow will remain the same. Nothing needs to be redeployed.

No. Your client ID and client secret will remain unchanged. If you rotate a secret later, it will work the same way as it does today.

Only the information needed to sign you in, such as your email address and authentication details. Your applications, credentials, and portal activity will remain in the Developer Portal and won’t be shared with other Home Connect services.

No. This is the same login you use for the Home Connect app. If you already have one, you’ll connect it during migration instead of creating another account. If you don’t, you’ll create one as part of the process. There’s nothing to set up in advance.

Only a few minutes. You can complete it in one sitting. If you stop halfway, your account will remain unchanged until you finish.

Yes. You can also switch to a different email address during migration. Either way, your applications will remain linked to your account.

That’s fine. The email addresses don’t have to match. During migration, you can choose which email address to use for the Developer Portal. Either way, your applications will remain linked to your account.

Migrate each one separately. They can be connected to different Home Connect logins, or you can consolidate them. Contact support if you want to merge your accounts.

We’ll never ask for your password, client secret, or any other credentials by email. If an email looks suspicious, don’t click any of its links. Instead, come to this page directly and start the migration from here.

No changes were applied, and your account remains unaffected. Sign in with your current Developer Portal credentials to continue the migration process.

No changes were applied, and your account remains unaffected. Sign in with your current Developer Portal credentials to start the migration process again.

Check your spam folder first. If your Home Connect login uses a different email address, make sure you’re checking the inbox for the address registered in the Developer Portal. If the email still hasn’t arrived after 10 minutes, request it again.

Creating a Home Connect login and connecting it to your Developer Portal account are two separate steps. If you stopped after creating the login, sign in again and choose “Connect existing Home Connect login.” You won’t need to create another one.

Contact support before continuing. We can disconnect it and allow you to migrate using the correct login. Don’t start another migration in the meantime.

If you’re already signed in, check whether you have full access to the Developer Portal - for example, whether you can manage your application settings. If you do, your migration is complete.

No. Once your account is connected to your Home Connect login, this becomes the way you sign in. You can still change the email address and security settings associated with your login at any time.

No. The option to switch to Home Connect login is currently available only for Individual and Community accounts and will become available for Corporate accounts later.

Your account won’t be deleted, and your applications will continue to work. You’ll still be able to sign in and use some Developer Portal features, but you’ll need to switch to Home Connect login to regain full access.

Their account is most likely Individual or Community, while yours is Corporate. Corporate account holders will need to switch to Home Connect login themselves in Phase 2. You don’t need to do anything until then.

A Home Connect login belongs to one person, so an account using a shared mailbox cannot be migrated as it is. Decide who should own the account, then migrate it using that person’s Home Connect login. The rest of the team will retain access as members. If no one can access the shared mailbox anymore, contact support so we can verify ownership.

Contact support before the deadline for your phase. We’ll verify that your company owns the account and transfer ownership so you can migrate without losing any applications.

To make the process quicker:

• Confirm who currently owns the account and who should own it after the migration,
• Check that every team member’s email address is up to date,
• Decide who should take over applications owned by people who have left the company,
• Contact us now if you need corporate SSO.