Contact Form 7 Enters Feature Freeze. You Don't Need to Switch. AI Can Fill the Gaps.

At WordCamp Asia 2026 in February, Takayuki Miyoshi (三好剛平), the author of Contact Form 7 (CF7), announced that the plugin will enter feature freeze. He is shifting focus to a successor project, Contactable.io, targeted for 2028. This is not "end of life." This article walks through what the announcement actually means for site owners and lays out a third option that isn't "switch plugins."

What Was Actually Announced

The official position is:

No new features will be added going forward (feature freeze)
Bug fixes and security updates will continue
After 17 years and 150M+ downloads of maintaining CF7, the author is stepping back and focusing on a successor project, Contactable.io, targeting a 2028 release

In other words, CF7 isn't dying. It's being declared feature-complete. A 17-year-old WordPress plugin has entered stable-maintenance phase. That's the accurate framing.

How This Differs From the MW WP Form Precedent

Anyone who used MW WP Form before its full discontinuation in 2023 will recognize the anxiety pattern. When that plugin was abandoned:

Security issues that surfaced later went unpatched — no one was left to fix them
WordPress core updates eventually broke compatibility — no one was left to ship fixes
Site owners scrambled for migration paths months too late

CF7's feature freeze is qualitatively different.

Aspect	MW WP Form (2023-)	CF7 (2026-)
New feature development	None	None
Bug fixes	None	Continued
Security updates	None	Continued
WordPress core compatibility	Not guaranteed	Maintained
Active maintainer	None	Miyoshi continues

CF7 has entered something closer to the ideal software lifecycle phase: "we won't add to it, but we will keep it working." That's a feature, not a failure.

You Don't Need to Rush to Migrate

Some sites are spinning this as "CF7 is dead, switch now!" Multiple WordPress-focused outlets (Edel Hearts, kontaworks) have independently concluded the opposite: no immediate action is needed.

Question	Reality
Can I keep using it on existing sites?	Yes. Nothing changes.
Will security vulnerabilities be patched?	Yes. Updates will ship.
Will it stay compatible with future WordPress versions?	Yes. Compatibility is maintained.
Will it get fancy new features?	No — but it never really had those anyway.

When Should You Migrate, vs. Stay?

Kontaworks frames the decision well: "Is this form directly tied to revenue?"

Stay on CF7 if:

The form is an "inquiry endpoint" — that's all you need
You get a handful to a few dozen submissions per month
A 1% improvement in completion rate wouldn't move revenue (typical corporate "Contact Us" form)

Consider migration if:

The form sits directly on a landing page and drives conversions
You need a step-form / branching-logic flow for sign-ups
CRM / marketing-automation integration is foundational, not optional
Polishing the form UX itself materially grows revenue

The split is essentially: "Is the form part of your acquisition machinery, or just a reception desk?" If it's the latter, CF7 is still entirely fine.

The Hidden Costs of Switching

The "just in case, let's move to a different plugin" instinct is understandable, but here's what migration actually costs:

Rebuilding every form — Each plugin has its own form-tag syntax. Porting is manual work.
Redoing your CSS/HTML customizations — Theme-side styling tied to CF7 will mostly stop working.
Rewriting mail templates — Merge-tag syntax differs.
Finding replacements for CF7 add-ons (Flamingo, CF7 Skins, etc.) — You lose the surrounding ecosystem.
Reconfiguring Google Analytics conversion triggers — The wpcf7mailsent event has no exact equivalent in other plugins.
Re-testing every form — QA time across the entire site.

And the plugin you migrate to might enter its own EOL phase someday — that's exactly what happened to MW WP Form users. Migration should be a last resort.

What Are People Actually Struggling With on CF7?

In practice, the pain points around CF7 are not about "missing features." They are about operational headaches:

Cold sales outreach floods the inbox
"Form-submitted" conversions in Google Analytics get polluted by spam, breaking attribution
Real customer inquiries get buried under "Hello, we offer SEO services" emails
Akismet doesn't help much — human-written B2B sales pitches sail right through
reCAPTCHA / Cloudflare Turnstile filter bots, but humans writing cold outreach get through every layer

None of these get fixed by switching form plugins. They aren't form-plugin problems. They are classification problems.

A Third Option: Keep CF7, Add an AI Classifier Layer

Instead of replacing CF7, you can stack an AI classification layer on top of it.

The form layer stays the same (still CF7, zero migration cost)
An AI reads each submission and decides whether it's a real inquiry or sales outreach
Sales outreach gets a [Sales] prefix in the mail subject, so Gmail filters can quietly hide them
Google Analytics only counts real inquiries as conversions
The classifier plugin develops and maintains itself separately, so the overall stack keeps evolving even while CF7 stays frozen

This is exactly the design behind YomuForm. It hooks into wpcf7_before_send_mail, reads the submission, classifies it via your choice of Anthropic Claude, OpenAI GPT, or Google Gemini, and injects the verdict into the receipt mail's subject and body. It does not modify CF7 form definitions or mail templates.

Categories YomuForm Ships With

1. Lead              - real pre-sales inquiry with revenue potential
2. Sales             - boilerplate cold outreach
3. Recruitment       - recruiting / staffing pitches
4. Partnership / BD  - OEM, reseller, or business-development proposals
5. Scam / Phishing
6. Competitor Research

A typical setup: get an instant email for Lead and Partnership categories, while Sales, Recruitment, Competitor, and Scam stay silently in the log, never touching your inbox.

Pricing

Free (forever): CF7 integration, 6-category classification, 1 email notification, last 100 classifications stored, BYOK (bring your own API key). Distributed on the WordPress.org plugin directory.
Plus (¥9,800 / one-time payment): Multi-channel notifications (Slack / Discord / Chatwork / Webhook), category CRUD, CSV export, 1,000-entry log retention.
Pro (¥980/month or ¥9,800/year): HubSpot / Pipedrive auto-integration, GA4 Measurement Protocol server-side events, GTM dataLayer push, 5,000-entry log retention.

You bring your own Anthropic / OpenAI / Google API key (BYOK). Classification traffic never passes through YomuForm's servers. Form bodies go directly from your WordPress site to your chosen AI provider.

What About Contactable.io in 2028?

Miyoshi's next-generation project, Contactable.io, is targeting a 2028 release. It's expected to align with the headless / decoupled WordPress architecture, making forms easier to embed from React, Vue, and other modern frontends.

That's still about two years out. In the meantime:

CF7 keeps working (feature freeze + security updates)
If you need new capabilities, add them externally rather than waiting for CF7 to ship them (AI classification is one example)
When Contactable.io ships in 2028, re-evaluate then

There is little reason to rush a major migration today.

Summary

Your Situation	Recommendation
Happy with CF7's form features	Keep using CF7. No need to migrate.
Drowning in sales spam	CF7 + AI classifier to clean up the inbox.
Google Analytics conversion data is unreliable	CF7 + AI classifier to filter out fake conversions.
The form itself is a revenue funnel (LP / step form)	Migration is worth considering — but plan it carefully.

CF7 entering feature freeze is not bad news. It just means we now have a stable, no-more-changes form engine to layer modern AI classification on top of. This is fundamentally different from the MW WP Form situation — CF7 is being maintained, not abandoned.

YomuForm's Free version is available on WordPress.org. If you're tired of sorting sales emails by hand, give it a try — it doesn't cost anything to find out if it works for you.