Start here

Update the plugin or plan a migration

Replace the matched ZIPs without deleting data, and preserve the site’s sending identity.

Free and Pro6 min readVersion 1.0.10
01

Back up and identify your version

Pause campaigns and automations. Take a consistent database and files backup, including newsletter signing keys, suppression keys, mappings and receipts. Keep the old plugin files and rehearse on a separate nonproduction copy with its transport held. Never restore an older customer database after further sends have occurred.

Fresh installations use newsletterplatform-com Free 1.0.10, then newsletterplatform-com-pro 1.0.10 if purchased. The Pro companion requires Free 1.0.9 or later. Future replacement updates within these new folders use Upload/Replace, Free first, without uninstalling.

02

Move from newsletter-platform

The supported migration starts from the old newsletter-platform 1.0.8 pair. If you run 1.0.0–1.0.7 or a beta, contact support for the staged 1.0.8 bridge before proceeding. Earlier Pure Elixirs installations need a separately verified migration.

  1. Use a standard WordPress Administrator account with permission to activate plugins. Deactivate old Free and Pro, and let their running web requests and background jobs finish.
  2. Install and activate the renamed Free ZIP. Open Plugins → Newsletter data upgrade and complete its explicit, bounded steps. The plugin stays inert until migration finishes.
  3. Activate matching Pro only after Free’s migration completes. Do not uninstall or reactivate the old pair.

The legacy migration requires MySQL 8.0 or MariaDB 10.6 or newer and InnoDB options, posts, user metadata and newsletter tables. Busy work, conflicting records, unsupported storage or uncertain ownership stop the process. Existing multisite data requires coordinated migration; automatic migration is refused. Do not delete data or reset secrets to clear a refusal.

03

Replace the rejected 1.0.9 candidate

If you installed pluginsshop-newsletter-platform and its Pro companion, deactivate both and let their jobs finish. Activate newsletterplatform-com Free first, then matching Pro. Both names share the NEWSPL data namespace, so settings, content, signing keys and permissions are reused without a second migration.

Do not uninstall the previous candidate. Its uninstall setting can delete shared data. Never activate an earlier copy alongside the renamed pair. Existing saved signup blocks, shortcodes, design exports, checkout consent metadata and issued public endpoints remain supported.

04

Review links and resume safely

Already delivered emails and saved designs can point to images in an old plugin folder. Keep those static image assets available or arrange exact old-to-new asset redirects with your host before removing old files. The plugin cannot rewrite received emails or configure your web server.

Current links use dedicated newsletter keys and per-subscriber secrets, not WordPress authentication salts. Existing version-2 signatures and recorded version-1 verification receipts are preserved. Unrecorded tracked links from before 0.1.0-beta.9 cannot be safely reconstructed. Back up keys, receipts and mappings together.

Review contacts, suppressions, drafts, workflows, permissions and production identity in Settings → Delivery and site safety. Sending settings can be retained; inspect them before restoring scheduled work. Confirm one intended production sender. An identical production clone cannot be detected, so explicitly mark copies nonproduction. Imports and updates do not enroll historical contacts into welcomes.

Private manual account downloads supply Pro. Local Pro features need no initial licence activation or update token. Its optional signed updater requires a separately protected publisher configuration and authorized connection; automatic update service availability is not promised by manual downloads.