One click migration from old plunk to new plunk

[niyonx]

Is your feature request related to a problem?

Yes. Plunk has moved from the previous Plunk version to the newer Plunk experience, but there does not appear to be a clear one-click migration path for existing paid-service users.

Existing users may already have important production data in the previous version, including users, projects, API keys, contacts, events, templates, campaigns, automations, and email history. Without a guided migration, upgrading feels risky because it is unclear what data will carry over, what may change, and whether API keys or sending/tracking behavior will keep working.

Describe the solution you'd like

Add a guided one-click migration flow from the previous Plunk version to the new Plunk version.

Ideally, the migration would:

• Detect existing accounts/projects on the previous Plunk version
• Preserve users, projects, project memberships, API keys, contacts, events, templates, campaigns, automations, and email history where possible
• Preserve sending domains and sender settings where possible
• Explain any breaking changes before migration
• Show a clear preflight checklist before proceeding
• Create a backup or recovery point before migration
• Allow rollback or support-assisted recovery if migration fails
• Provide post-migration verification checks for login, API auth, project keys, sending, tracking, contacts, and campaigns

Alternatives or workarounds

The current workaround is to manually recreate the account/project setup in the new Plunk version and manually move over any necessary data.

That is risky and time-consuming because:

• API keys may change
• Contacts, events, templates, campaigns, or automations may not transfer cleanly
• Sending domains and sender settings may need to be reverified or reconfigured
• Production integrations may break during the transition
• It is unclear which parts of the previous account state are compatible with the new version

Another workaround is to continue using the previous version, but that leaves existing users unable to confidently move to the newer Plunk experience.

Additional context

This request is for existing paid-service users on the previous Plunk version who want to migrate to the new Plunk version without manually rebuilding their setup or risking production email/API disruption.

Relevant docs:

https://docs.useplunk.com/

API docs:

https://docs.useplunk.com/api-reference/overview

[driaug]

99% of users from the old managed version of Plunk have already migrated away. The self-hosted version is provided as-is according to the license.

Here is my reasoning:

• The move will remain manual since it does not make sense to implement this for a handful of customers
• Your domain will automatically verify in the new version of Plunk
• The only part that safely carries over between the old and new Plunk are your contacts. You can export these and import them in the new version including all data
• Other parts do not carry over cleanly as the new Plunk is far more extensive (segments, workflows). A one-click migration would carry over bad patterns of the old Plunk into the new Plunk. This is a good time to reconsider how you have set up your emails.