Perplexity Collection Cannot Be Edited After Migration: Fix

You created a Collection in Perplexity, then migrated it to a new account or workspace. Now the Collection shows up, but you cannot rename it, add new sources, or delete items inside it. This problem happens because the migration process does not transfer ownership permissions for the Collection metadata. This article explains why the lock occurs and provides a step-by-step fix to regain editing control over your migrated Collections.

Why Migrated Collections Become Read-Only

When you migrate a Perplexity Collection from one account to another, the source URLs and descriptions transfer correctly. However, the internal permission flag that grants the new owner editing rights does not always update. This flag is stored in the Collection metadata as a user ID that matches the original creator. Perplexity migration tools copy the data but do not re-assign the owner ID to the new account. As a result, the Collection appears in your library but behaves like a shared Collection that only the original owner can modify.

The same issue occurs when you use the built-in workspace transfer feature inside a Pro or Enterprise plan. The workspace migration script transfers folder structure and sources but leaves the creator field pointing to the old account. Perplexity support has acknowledged this as a known limitation in the current migration pipeline.

How the Permission Flag Works

Every Collection has a hidden property called owner_id. This property is set when the Collection is first created. During migration, the system copies the owner_id value instead of generating a new one tied to the destination account. The Perplexity API then checks this owner_id against the current user’s ID. When they do not match, the API returns a 403 Forbidden response for any write operation. The user interface hides the edit buttons because the API denies the request.

Steps to Fix a Locked Migrated Collection

The following method restores editing ability without losing any saved sources. It works on the web app and the Windows or macOS desktop app.

1. Open the locked Collection
   Go to Perplexity and sign in with the account that received the migrated Collection. Navigate to Collections from the left sidebar. Click the Collection that shows the read-only state. You should see the list of sources but no Edit or Add buttons.
2. Copy all source URLs
   Click each source in the Collection. A panel opens showing the source title and URL. Copy the URL to a text file or a temporary note. Repeat for every source in the Collection. If the Collection has more than 20 sources, use the Export function described in step 5 instead.
3. Delete the locked Collection
   Click the three-dot menu next to the Collection name. Select Delete Collection. Confirm the deletion. This removes the orphaned permission flag from your account.
4. Create a new Collection
   Click the plus icon next to Collections in the sidebar. Give the new Collection the same name and description as the original. Click Create.
5. Add the copied sources
   Open the new Collection. Click Add Source. Paste each URL from your text file. Perplexity will fetch the page title and description automatically. After adding all sources, the Collection is fully editable because the new owner_id matches your account.

Alternative Fix Using JSON Export and Import

If the locked Collection contains more than 50 sources, manual copying is tedious. Use the JSON export method instead.

1. Export the locked Collection
   Open the locked Collection. Click the three-dot menu and select Export. A JSON file downloads to your computer. This file contains all source URLs, titles, and descriptions.
2. Delete the locked Collection
   Follow step 3 from the main fix above.
3. Import the JSON file
   Click the plus icon to create a new Collection. After naming it, click Import and select the JSON file you exported. Perplexity re-creates the Collection with your account as the owner. All sources appear with their original metadata.

If Perplexity Still Blocks Editing After the Main Fix

Collection Still Shows Read-Only After Re-creation

This happens when you attempted to rename the old Collection instead of deleting it. Perplexity stores a cache of the Collection metadata for 24 hours. Even after deleting and re-creating, the old permission flag may persist in the browser cache. Clear the browser cache for the Perplexity domain, then refresh the page. On the Windows app, sign out and sign back in.

Sources Duplicate After Re-adding

If you manually copy sources and also import the JSON file, you will see duplicate entries. Delete the duplicate Collection and start fresh. Use only one method — manual copy or JSON import — not both.

Workspace Migration Left Multiple Orphaned Collections

When you migrate an entire workspace, all Collections in that workspace become read-only. The fix is the same: export each Collection, delete it, and re-import. To speed up the process, use the workspace-level export feature. Go to Workspace Settings > Export All Collections. This downloads a ZIP file containing individual JSON files for every Collection. Delete all Collections in the workspace, then import each JSON file one by one.

Perplexity Free vs Pro: Collection Ownership After Migration

Item	Perplexity Free	Perplexity Pro
Maximum Collections	10 Collections	Unlimited Collections
JSON export available	No	Yes
Workspace migration	Not supported	Supported with known permission bug
Support ticket priority	Standard	Priority with dedicated migration specialist
Manual source copy workaround	Works for up to 10 Collections	Works but JSON import is faster for large Collections

Free users cannot export Collections as JSON. They must use the manual copy method. Pro users should always use JSON export to avoid losing metadata and to speed up the process. If you are a Pro user and the JSON export is missing from the menu, contact Perplexity support to have the feature enabled on your account.

After applying the fix, all migrated Collections will be fully editable. You can rename them, add new sources, remove outdated links, and reorganize the order. To prevent this issue in future migrations, always export each Collection as JSON before starting the migration process. Then delete the original Collections in the source account. When the migration completes, import the JSON files into the destination account. This workflow ensures the owner_id is set correctly from the start.