What to Check After Importing a Converted WordPress Form

April 16, 2026

So you've converted your form with FormPorter, imported it into your new plugin, and it's sitting there in your form list looking pretty. Before you embed it on a page and call it done, there are a few things worth a quick check. Most of this takes under five minutes. But skipping it can mean a broken form on a live site, and nobody wants that email from a client.

Submit a test entry

This is the big one. Preview the form, fill it out with test data, and submit it. Check that the confirmation message shows up. Check that the notification email arrives. Check that the entry appears in the form submissions. If all three of those work, you're in great shape.

Check your notification emails

FormPorter carries over your notification settings, including the "to" address, subject line, and message body. But email templates work differently across plugins. Gravity Forms uses merge tags like {all_fields}. WPForms uses {all_fields} too but with different formatting. Ninja Forms uses {all_fields_table}. Make sure the notification email you receive actually includes the form data and isn't just sending a blank template.

Also double-check the "from" and "reply-to" addresses. Some plugins default to the WordPress admin email. Others use whatever was set in the source form. If your notification is coming from "wordpress@yourdomain.com" instead of "info@yourdomain.com," that's a quick fix in the notification settings.

Verify required fields

Open the form in the builder and spot-check a few fields to make sure the required toggle is set correctly. FormPorter maps the required setting from every source plugin, but it's the kind of thing that's easy to overlook and embarrassing to miss. Submit the form with empty required fields and make sure the validation fires.

Review dropdown and radio choices

If your form has select dropdowns, radio buttons, or checkbox groups, open one in the builder and make sure all the options came through. Check both the label (what the user sees) and the value (what gets saved). Some plugins handle these differently, and occasionally a choice might get the label and value swapped.

Rebuild conditional logic

If your original form had show/hide logic or conditional fields, those didn't convert. Every plugin implements conditional logic differently, and there's no universal translation between them (yet). FormPorter warns you about this during conversion, but this is where you'll spend the most manual time if your form was complex. Open your original form in the old plugin for reference and rebuild the rules one by one in the new plugin.

Reconnect integrations

Payment gateways (Stripe, PayPal), email marketing connections (Mailchimp, ActiveCampaign), CRM integrations, Zapier hooks. None of these transfer between plugins because they're all plugin-specific configurations tied to API keys and accounts. If your form connected to any external service, you'll need to set those up fresh in the new plugin.

Update the embed

Don't forget the obvious one. Your old form was embedded on a page using the old plugin's shortcode or block. You need to replace that with the new plugin's shortcode or block. If you skip this step, you'll deactivate the old plugin and suddenly have a broken shortcode showing on a live page.

Keep the old plugin installed (temporarily)

Don't deactivate your old form plugin right away. Keep it around for a few days until you've confirmed everything works. That way you still have the original form as a reference if you need to check a setting or rebuild a conditional logic rule. Once you're confident the new form is working correctly, then you can safely deactivate and remove the old plugin.