Perplexity does not provide account-data transfer that merges two histories into one. You can choose a primary account for future work and retain reference copies of material you are entitled to keep, but that is not a native account merge. Moving eligible paid access is a separate decision.
Official guidance checked October 14, 2026. The earlier JSON collection export/import and email-renaming workflow was incorrect.
Inventory both accounts before changing either
Open each account separately and record its registered email, sign-in method, paid plan and billing provider. Use separate browser profiles or carefully check the active account before any operation. Give the accounts clear labels in your notes, such as “work email, existing history” and “personal email, new account.”
Then identify what matters: particular threads, project or collection material, instructions, uploaded files, shared access, or a subscription. Perplexity’s account-management guide says data transfer is unsupported. Do not assume that a similar project name in each account means the underlying content has merged.
Choose a primary account based on long-term access and permitted use, not only on which currently has Pro. For workplace content, follow the organization’s ownership and retention rules before moving a copy to a personal account.
Keep reference copies without claiming a native migration
For important material you own, use the sharing, copy, or download controls actually offered for that item. Preserve source links and context where available, and open the saved result to check it. Do not rely on an undocumented whole-account JSON export followed by a Collections Import command.
Use a short inventory to verify each item:
- Original account and item title.
- What you need to retain and whether you are authorized to copy it.
- Where the reference copy is saved.
- Whether text, attachments and source links were checked.
- Any dependency on access to the original account.
Pasting an old answer into a new chat creates new content; it does not restore the original conversation state or prove that every citation and attachment moved. Likewise, making a private thread public is not a safe default migration method. Keep the original account available while you verify what you still need.
Resolve subscriptions independently of the content
Consult the subscription-transfer walkthrough before canceling. Standard eligible web plans have a transfer route, while store, educational, organizational and promotional plans have different constraints. Changing an invoice contact email does not rename a Perplexity login.
If both accounts are paid, ask the relevant seller to clarify your options. Do not assume two remaining terms can be combined or that a second purchase will automatically be refunded. Keep receipts and cancellation confirmations separate for each account.
If you choose to stop renewal, follow the correct billing-channel instructions. Verify the scheduled end date. Account deletion does not cancel billing and should not be included as an automatic cleanup step.
Finish with a verified primary account, not a deletion shortcut
Sign in to the intended primary account and check its email, plan and newly created working structure. Confirm your reference copies outside the old account. Record any missing material instead of declaring the consolidation complete because the subscription now works.
Keeping the old account for reference is different from continuing to pay for it. Consider deletion only as a separate, deliberate decision after access, billing and retention needs have been resolved. Do not delete it to “free up” an email for an unsupported rename.
For lost original access, follow Perplexity’s account-access guidance. Do not promise that support can merge histories or recover inaccessible content merely because you have proof of payment.
Glad it helped. Take a short break with a game:
Sorry about that. Search for the exact error message, or look for a tool that checks your device: