One-Click Migration
From WP Mail SMTP, Fluent SMTP, or Easy WP SMTP Free & Pro
One-Click Migration: what it does
Switching SMTP plugins usually means copying settings across by hand and hoping nothing was missed. NimblyMail’s setup wizard detects WP Mail SMTP, Fluent SMTP, and Easy WP SMTP, imports their settings in one click, and reports anything it could not map rather than dropping it silently. Migrating from Fluent SMTP recovers the most: NimblyMail decrypts Fluent SMTP’s own encrypted credentials, so SMTP passwords and API keys transfer intact. Both plugins can stay active during cutover, and the whole process is multisite-aware.
What you get with One-Click Migration
True one-click import
Host, port, encryption, credentials, from-name and from-address — imported automatically.
Nothing disappears quietly
Any field that cannot be mapped is listed with the reason, so you know exactly what to re-enter.
Zero-downtime cutover
Both plugins stay active while you verify; NimblyMail takes over wp_mail() only when ready.
Multisite-aware
Network installs import per-site settings and apply network defaults where sites haven't configured their own.
Three steps, zero babysitting
Install NimblyMail
The wizard detects WP Mail SMTP, Fluent SMTP, or Easy WP SMTP on activation.
Click import
Settings and API keys transfer, with a list of anything skipped. The old plugin stays active as a safety net.
Verify and finish
Send a test email, run the deliverability audit, then deactivate the old plugin when satisfied.
One-Click Migration questions, answered
Yes, once. OAuth tokens are issued against a single application's redirect URI, so they cannot be transferred between plugins — any tool claiming otherwise is describing something that does not work. Your client ID and secret do import, so reconnecting is a single click on the consent screen rather than a fresh setup.
None. Both plugins can stay active during cutover; NimblyMail only assumes wp_mail() when you confirm. Verify delivery with a test email and audit before deactivating the old plugin.
Yes. The importer is multisite-aware: it imports per-site settings, respects network defaults, and flags sites that had custom configurations.