AWS Quick Desktop: local-to-cloud migration marked complete, but local archive was not migrated

I use AWS Quick Desktop on macOS and subscribe using Google Workspace sign-in.

Cloud migration ran on a fresh Mac Mini installation before my existing local archive was available. It reports completion, but my historical chats, context, knowledge graph, and local files were not migrated.

My current working data is on the Mac Mini in a separate local recovery installation. My original MacBook Air dataset is now stale.

I need help safely migrating the current Mac Mini archive:

  1. Can support reset or rerun migration for my account?
  2. How can I select the correct local profile and verify that all supported data migrated?
  3. What is the private technical support channel for a paid subscriber using Google sign-in?

Preserving the working local archive is critical. Please provide a supported procedure that includes backup and recovery before any changes.

Hi @Javier_Vazquez,

Welcome to the Quick Community! I would definitely create a support ticket, since only they can see how the migration ran for your account. Before that, back up the Mac Mini archive. Fully quit Quick Desktop, then copy the whole ~/.quickwork/ folder to an external drive or a zipped copy. Each sign-in identity gets its own subfolder under profiles/, which is likely why your recovery installation and the fresh install are side by side. Don’t delete, rename or merge any profile folders, and avoid signing in or out on the Mac Mini until support has looked at it.

There’s currently no documented way to rerun the migration after it reports complete, or to pick which local profile it reads from. Someone ran into nearly the same issue in this thread, and it also ended up going to support. In your case, I would recommend mentioning that the migration ran on a fresh install before your archive was there, and that you’ve backed it up.

Hope this helps!