Migrate from
Leaving WPForms? Here is what carries over.
On Hostless Duck, Contact Forms Core and Multi-Step & Conditional Forms do the job of WPForms and import its data. What comes across and what does not is listed below, exactly as each importer's own record states it.
What carries over, and what does not
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.
From WPForms Lite
- Carries over
- 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 carry over
- 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.
Multi-Step & Conditional Forms
Forms split into steps with a progress bar, questions and whole steps that appear only when earlier answers call for them, groups a visitor can repeat, and a private link to save and finish later.
- Carries over
- Each form's name and fields, page breaks as steps with their titles, required marks and choices, and show-when rules that use is, is not, contains, empty, not empty, greater than and less than.
- Does not carry over
- Hide-when rules and rules that use starts with, ends with or does not contain (those fields arrive always shown, and the report names them), stored entries, payment, file upload and repeater fields, and the [wpforms] shortcodes in your pages, which you replace with a Step form block.
From an export file: not yet verified against a live export. The file importer has only been tested on sample files we wrote from the documented format.
Through the site connection: tested 19 November 2026 on a test WordPress site with the free version of the plugin, not a customer's site.
Each import ends with a report that names anything it could not carry.
WPForms's settings, read from the site itself
A move reads your WordPress site through a read-only connection that you approve. In a test on 19 November 2026, WPForms's settings came across through that connection into the Contact Forms Core module. The test used the free version of the plugin on a test WordPress site, not a customer's site.
The rest of the site
WPForms is one part of a site. Hostless Duck reads a WordPress site through a connection you approve and brings content, pictures, menus, comments and many plugin settings, and reports plainly what it could not carry.
The site check reads your public pages once and lists the theme and plugins it can see, with what Hostless Duck has for each. A plugin with no replacement yet is built for your site On The Fly. How that works
The Library Effect. Built once. Every site after rides free. A part built for one site joins the library, so every plugin on your site is in the library, in the build queue, or not yet needed. Look up the others.
$0 is the cost to build, for every site after the first. Applying the part to your site is part of the move. A site on a different version or set-up of the same plugin can read Partial: a priced gap, never a rebuild.
Also replaced by Contact Forms Core and Multi-Step & Conditional Forms
The small print
WPForms is another company's product, named here only to say what Hostless Duck can import from and what does the same job. Hostless Duck is not affiliated with, endorsed by or sponsored by its makers, and uses none of their code, styles or wording.
Is WPForms the only thing your site runs on?
Give us your site's address and we read its public pages once: its theme, its plugins, and what Hostless Duck has for each. A real scan of your public pages, never a made-up result. No card.

