Contact Forms Core
Build as many forms as you need, place them on any page, get each message by email and keep it in the admin, with any files the visitor sent. Checked on the server, with spam traps built in.
Not open yet No card
Description
Build as many forms as you need, place them on any page, get each message by email and keep it in the admin, with any files the visitor sent. Checked on the server, with spam traps built in.
What it does
- Form builder
- Email routing
- File upload
- CAPTCHA hook
- Validation
- Multi-form
Stands in for
Contact Form 7.
These are other companies' products, named only to say what job this module does. WebHD is not affiliated with them.
What comes across
What this module brings over from the plugin a site used before, and what it leaves behind. Each import ends with a report that names anything it could not carry.
- From Contact Form 7
- Comes across: Each form's name and its fields: labels, types, which are required, the choices of drop-downs, radio buttons and checkboxes, file upload fields with their size limit and kinds, plus the send button's wording, and its email settings: who it emails (plain addresses), the subject with answers in it, the visitor's acknowledgement (subject and text) and the thank-you message.
- Does not: CF7's own notification body (here each message lists every answer), answer tags inside the acknowledgement, its other messages (errors), file size limits above 8 MB and file kinds this site does not take, quiz and CAPTCHA tags, and the [contact-form-7] shortcodes in your pages, which you replace with a Form block.
- Not yet verified against a live export: this importer has only been tested on sample files we wrote from the documented format.
- From WPForms Lite
- Comes across: Each form's name, fields, required marks and choices, file upload fields, the send button's wording, the confirmation message, and the notification address (a plain email address) and subject (without smart tags).
- Does not: Stored entries and their files, conditional logic, payment fields, page breaks, and the [wpforms] shortcodes in your pages, which you replace with a Form block.
- Not yet verified against a live export: this importer has only been tested on sample files we wrote from the documented format.
- From Fluent Forms
- Comes across: Each form's fields (name and address parts become separate fields), required marks, choices, help text, file upload fields, the send button, the thank-you message or a redirect to a path on this site, plain notification addresses with the subject, the visitor's confirmation email, and whether entries were kept.
- Does not: Stored entries and their files, conditional logic, and the shortcodes in your pages, which you replace with a Form block. Also email wording with placeholders, conditional email routing, CAPTCHA fields (Spam Protection guards forms here), country lists, steps and payment fields.
- Not yet verified against a live export: this importer has only been tested on sample files we wrote from the documented format.
- From Ninja Forms
- Comes across: Each exported form's fields in their order, required marks, choices, help text, the send button, the success message, a redirect to a path on this site, plain notification addresses with the subject, the visitor's confirmation email, and whether submissions were stored.
- Does not: Stored entries and their files, conditional logic, and the shortcodes in your pages, which you replace with a Form block. Also state and country lists (they become text boxes), CAPTCHA and anti-spam fields, password fields, add-on actions such as Mailchimp, and payments.
- Not yet verified against a live export: this importer has only been tested on sample files we wrote from the documented format.
- From Everest Forms
- Comes across: Each form's fields in builder order, required marks, choices, help text, file and image upload fields, the privacy consent box, the send button, the success message, an outside-link redirect when it is a path on this site, plain notification addresses with the subject, the visitor's confirmation email, and whether entries were kept.
- Does not: Stored entries and their files, conditional logic, and the shortcodes in your pages, which you replace with a Form block. Also redirects to a WordPress page (set its path again), ratings, payment fields and styles.
- Not yet verified against a live export: this importer has only been tested on sample files we wrote from the documented format.
- From MW WP Form
- Comes across: Each form's fields from its [mwform_…] tags with their labels, choices and required marks, the send button, the completion message, the completion page when it is a path on this site, the admin address and subject, the automatic reply, and whether entries were kept in the database.
- Does not: Stored entries and their files, conditional logic, and the shortcodes in your pages, which you replace with a Form block. Also the check-your-answers screen (forms here send in one step), separate input and confirmation page addresses, CC and BCC addresses, hidden and password fields.
- Not yet verified against a live export: this importer has only been tested on sample files we wrote from the documented format.
- From FormLayer
- Comes across: Each form's fields, required marks, choices, help text, the terms box, the send button, the thank-you message or a redirect to a path on this site, the notification address and subject, and the visitor's confirmation email.
- Does not: Stored entries and their files, conditional logic, and the shortcodes in your pages, which you replace with a Form block. Also star ratings, CAPTCHA fields (Spam Protection guards forms here) and custom styles.
- Not yet verified against a live export: this importer has only been tested on sample files we wrote from the documented format.
- From Redirection for Contact Form 7
- Comes across: The page each Contact Form 7 form went to after sending, set on the form of the same name already imported here, when it is a page in the export or a path on this site.
- Does not: Redirects to other websites, delays, opening in a new tab, passing answers on in the address, stored leads, and the plugin's other actions (sending to an API, running scripts).
- Not yet verified against a live export: this importer has only been tested on sample files we wrote from the documented format.
Using a plugin that is not named here? It is built for your site On The Fly. How that works
Changelog
1.5.0 November 19, 2026
Contact Forms 1.5.0: Contact Form 7 forms bring their email settings: who they email, the subject with answers in it, the visitor's acknowledgement and the thank-you message. WPForms forms bring their notification subject.
1.4.0 November 19, 2026
Contact Forms 1.4.0: a page builder import can now ask for a form an old page held to be made here; Page Builder's Divi and Elementor importers use it, so an imported contact form arrives as a working form when Contact Forms is active.
1.3.1 November 18, 2026
Contact Forms Core 1.3.1: its importers that read a WordPress export now name the WordPress plugins they import from, so a site connected through Migrate → “Connect your WordPress” is offered them only when the old site uses one of those plugins. Nothing else changed. Needs Core 0.1.40.
1.3.0 November 17, 2026
Contact Forms Core 1.3.0 (needs Core 0.1.29): a Contact Form 7 shortcode on a page or post becomes a placed Form block, whether the forms or the content are imported first, including the short code newer versions of the plugin write. A shortcode inside other text is left for a person.
1.2.0 November 17, 2026
Contact Forms Core 1.2.0: imports forms from Fluent Forms, Ninja Forms, Everest Forms, MW WP Form and FormLayer: fields with their labels, choices, help text and required marks, the send button, the thank-you message or a redirect to a path on this site, plain notification addresses and their subject (field references are rewritten), the visitor's confirmation email, and whether messages were kept. A new Redirection for Contact Form 7 importer sets the page each already-imported Contact Form 7 form goes to after sending. CAPTCHA fields, payments, conditional logic, placeholders in email wording and outside redirects are named in the report.
1.1.0 November 17, 2026
Contact Forms: a file upload field (documents, pictures or both, up to three files of 8 MB), kept private and downloadable only by staff, and old messages and their files are cleared on a schedule you set.
1.0.0 November 16, 2026
Contact Forms Core: build any number of forms, place them on pages, get each message by email and keep it in the admin. Server-side checks, spam trap, send limit and a hook for CAPTCHA modules. Imports from Contact Form 7 and WPForms.
Get Contact Forms Core when WebHD opens
One form on the home page: your WordPress address, then your email.
No card Takes a minute No fake scan