Perplexity Collection Cannot Be Renamed After Migration: Fix

You migrated your Perplexity account or transferred collections between workspaces. Now when you try to rename a collection, the option is grayed out or the name reverts to the original. This happens because collection ownership metadata does not fully transfer during migration. This article explains why the rename lock occurs and provides two reliable methods to fix it.

Why Perplexity Blocks Renaming After Migration

Perplexity stores a collection’s owner ID and creation workspace in its internal database. When you migrate a collection from one workspace to another, the owner ID field may still point to the original workspace. The rename feature checks this field: if the current user is not the original owner, the rename control is disabled.

This is not a bug. Perplexity designed this behavior to prevent accidental renaming of shared collections by non-owners. However, after a migration where you are the intended new owner, the permission flag does not update automatically.

The fix requires either forcing a permission refresh or recreating the collection under your own identity. Both methods are explained below.

Steps to Regain Rename Access on a Migrated Collection

Try Method 1 first. If the rename option remains unavailable, move to Method 2.

Method 1: Edit the Collection Name Directly

1. Open the migrated collection
   Navigate to your library and click the collection that will not rename.
2. Click the three-dot menu
   Next to the collection name at the top of the page, click the More icon (three horizontal dots).
3. Select Edit Name
   From the dropdown menu, choose the Edit Name option. If this option is grayed out, proceed to Method 2.
4. Type the new name and press Enter
   Enter the desired collection name. Press Enter or click outside the text field to save. The name should update immediately.

Method 2: Export and Re-import as a New Collection

This method creates a brand new collection under your ownership, preserving all threads and allowing a custom name.

1. Export the collection
   Open the collection. Click the three-dot menu and select Export. Choose the JSON format. The file downloads to your computer.
2. Delete the original collection
   In the same menu, select Delete Collection. Confirm the deletion. This removes the locked collection from your library.
3. Create a new collection with your desired name
   Click New Collection in the left sidebar. Type the name you want and click Create.
4. Import the exported file
   Open the new empty collection. Click the three-dot menu and select Import. Choose the JSON file you exported in step 1. Perplexity imports all threads into the new collection.
5. Verify the rename option
   Click the three-dot menu again. The Edit Name option should now be active. You can rename the collection at any time.

If Rename Still Fails After Applying the Main Fix

Edit Name Option Is Present but Does Not Save

This usually indicates a sync delay. Log out of your Perplexity account, clear your browser cache, and log back in. Then repeat Method 1. If the name still reverts, use Method 2.

Collection Disappears After Deletion and Re-import

You may have deleted the collection before exporting. If you have no backup, check your Trash folder in Perplexity. Collections stay in Trash for 30 days. Restore the collection, export it, then delete and re-import as described in Method 2.

Multiple Collections Show the Same Rename Lock

If you migrated several collections at once, the owner ID field is likely incorrect for all of them. Repeat Method 2 for each collection. To avoid this in future migrations, ask your workspace admin to transfer ownership explicitly before migrating.

Item	Method 1: Direct Edit	Method 2: Export and Re-import
Time required	30 seconds	3 to 5 minutes per collection
Requires internet	Yes	Yes
Preserves thread history	Yes	Yes
Works when Edit Name is grayed out	No	Yes
Resets owner permissions	No	Yes
Best for	Single collection with active edit option	Multiple locked collections or persistent failures

You can now rename any migrated Perplexity collection using either the direct edit or the export and re-import method. If you manage multiple workspaces, ask your admin to transfer collection ownership before migration to prevent this issue entirely. For advanced users, the export JSON file contains an owner_id field that can be manually edited with a text editor before re-importing, though this requires careful handling of the file structure.