Introducing Paymattic 4.6.22: Migrate from GiveWP to Paymattic, and More!

Hello Paymattic Lovers! We’re excited to announce something we’ve been working on for weeks.

Paymattic 4.6.22 is our biggest release for nonprofits and donation-driven sites yet. The headline is a full GiveWP-to-Paymattic migration engine, built to move your forms, donors, donations, subscriptions, and email notifications in one guided flow without losing a record.

What’s new in Paymattic 4.6.22

Without further ado, let’s dive in.

GiveWP to Paymattic migrator

Switching donation plugins has always been a risky, time-consuming project. Export a CSV here, import a script there, lose half your subscription data along the way, and then spend days reconciling what didn’t come through. That’s no longer the case.

Paymattic 4.6.22 ships a dedicated GiveWP to Paymattic Migrator, accessible directly from your WordPress Dashboard under the Paymattic menu. The migrator walks you through a step-by-step flow (pre-flight, migration, and report) and handles everything from donation forms to recurring subscriptions, donor records, custom fields (FFM), email notifications, and currency switcher settings.

The pre-flight scan runs before anything moves. It detects which GiveWP payment gateways you’re using, identifies features or gateways that don’t yet have a Paymattic equivalent, and surfaces a compatibility report so you can make informed decisions before committing. After migration, you get a detailed summary listing what migrated, what was skipped, and if you’re on Stripe, a reminder to update your webhook endpoint.

Every migration is scoped and reversible. If something doesn’t look right, rollback targets are cleanly isolated to your migration batch. No orphaned rows. No stale state.

Use cases:

• Nonprofits running GiveWP for recurring donor campaigns who want Paymattic’s broader gateway support and leaderboard features
• Agencies migrating client donation sites from GiveWP to Paymattic with minimal downtime
• Membership and event organizations whose GiveWP FFM fields capture critical donor metadata they can’t afford to lose
• Donation campaigns using GiveWP v3 campaigns that need form titles and campaign names preserved in Paymattic

Here’s how this plays out in practice: your GiveWP forms become active Paymattic forms the moment migration completes, matching their pre-migration published state, so donors can keep giving without interruption.

Improvements: Paymattic 4.6.22

Here, we made some notable improvements in this update.

Configurable permitted roles for user dashboard

Previously, the Paymattic User Dashboard was only accessible to built-in Paymattic roles. Sites with custom user roles, or those migrating from GiveWP, where donors hold the give_donor role, had no clean way to extend access without code.

Now you can configure permitted roles via the _wppayform_dashboard_permitted_roles option. Any role in that list gets full User Dashboard access, and migrated GiveWP donors automatically receive this grant on migration completion. No more workarounds.

Subscription cadence parity with GiveWP

GiveWP supports billing intervals that Paymattic didn’t previously preserve on import: quarterly, fortnightly, and half-yearly cycles. These are now mapped correctly during migration, including signup-fee semantics, so a donor on a $10/month plan with a one-time signup fee arrives in Paymattic exactly as they left GiveWP.

Form titles reflect GiveWP campaign names

GiveWP v3 organizes donations around campaigns. Migrated forms are now named “Form name (Campaign name)”, making it easy to identify which Paymattic form corresponds to which GiveWP campaign without cross-referencing anything.

Fixes: Paymattic 4.6.22

This release also ships a round of data-integrity fixes targeting the migration pipeline:

• Duplicate Stripe renewal rows – Stripe transactions with both pi_ and ch_ identifiers are now deduplicated correctly, so there are no double-entries after migration
• Orphaned subscription rows – Partial subscription migration failures now roll back cleanly, leaving no orphaned rows behind
• Form idempotency scope – The form idempotency check was incorrectly matching non-Paymattic post types, and is now scoped correctly
• Rollback scope – Rollback operations were not consistently scoped to their migration batch, and are now isolated per meta group
• Report fetch failure – A report fetch error was surfaced as a full migration failure in the UI, and is now handled gracefully with a specific error state
• Reset panel reactivity – The reset (danger-zone) panel toggle was not reactive, and now updates correctly on state change

Update Paymattic now!

Paymattic 4.6.22 is rolling out to all sites today. Head to your WordPress Dashboard → Plugins → Updates and click Update on Paymattic, or grab it directly from your paymattic.com account.

If you’re migrating from GiveWP, we recommend running the pre-flight scan on a staging copy first.

If you run into anything unexpected, our support team is one ticket away.