ChatGPT Business account locked after migrating Google account to Google Workspace

ChatGPT Support
1

Hello everyone,

I need help with an authentication issue after migrating my company Google account to Google Workspace.

My ChatGPT account is associated with:

This account is part of a ChatGPT Business workspace. Before the migration, the same email was used as a Google account. After moving the domain/account to Google Workspace, I can no longer access ChatGPT.

When I try to sign in with Google, I get the following error:

“You tried signing in as “lxxxx@lixxxx.com” via Google, which is not the authentication method you used during sign up. Try again using the authentication method you used during sign up.”

Request ID:
8d8ecec1-79e9-48d1-81fe-522904ff63be

I also tried logging in with email/password, but the login flow does not

image
image932×1060 47 KB

even reach the password step. It seems completely blocked.

The Google Workspace account is active and working for Google services, but ChatGPT no longer accepts the login.

I have already contacted OpenAI Support, but I am posting here to see if anyone has experienced the same issue after migrating from an unmanaged Google account to Google Workspace.

My main concern is recovering access to the existing ChatGPT Business account/workspace, not creating a new account.

Has anyone solved this kind of Google identity / authentication method mismatch issue after a Workspace migration?

4

Thanks for flagging this @leandro-ligmee

Yeah, this sounds like it may be related to the Google Workspace migration causing an authentication-method mismatch on the account.

As you mentioned, you’ve already contacted Support - could you share the support ticket number here?

Once I have that, I can help investigate further.

~ Smith

5

hi, the case number is 10122595.

Thank you

6

Thanks for sharing the ticket number!

I'll pick this up from the support side and work with you there to get it sorted out. To keep things organized and avoid duplicate updates, I'll go ahead and close this community thread.

We'll continue the conversation through the support ticket from here on out.

~ Smith