A PC equipped with advanced AI capabilities and Windows Copilot integration
Open the affected chat in Copilot on the web using the same personal account and sign-in method; if it fails there as well as on Android, report that specific conversation through the app because Microsoft does not provide a user-side repair or remigration control.
1. Determine whether the failure is Android-only
- Open the Copilot web app in a browser.
- Sign in using the exact same identity and method used before migration:
- Microsoft account, or
- Continue with Google, or
- Continue with Apple.
- Open Conversations and select Personalized Fasting Journal.
Microsoft states that eligible chats move automatically and should synchronize across devices. Personal and work/school histories remain separate, so check the account label or account switcher if both account types are configured.^1^ ^2^
- If it opens on the web: The conversation still exists, and the problem is limited to the Android client or its synchronization. Fully close and reopen the Android app, then retry. Also install any available Copilot update from Google Play.
- If it fails on the web with the same error: This is specific to that migrated conversation rather than the Android display alone. Proceed to reporting below.
- If an in-app migration message provides access to previous chats: Use that link while the remaining content finishes moving. Microsoft notes that migration time varies with the amount and type of content.^1^
2. Report the affected conversation
In Copilot:
- Select … in the upper-right corner.
- Select Send feedback.
- Select Report a problem.
- Include:
- The chat title: Personalized Fasting Journal
- The exact message: “We couldn't open this chat. Please try again later.”
- That all other chats migrated successfully
- Whether the chat also fails in the web client
- When the migration and failure began
- Android device model and OS version
- Copilot app version
- A screenshot of the error
These details let Microsoft distinguish an Android synchronization issue from a failure affecting the individual migrated conversation. The documented escalation route for persistent migration problems is Send feedback → Report a problem.^1^
Do not delete the chat while it remains visible in history. The available guidance does not document a way for users to restore or manually rerun migration for one conversation.
References