Migrate from
Leaving Advanced Custom Fields (ACF)? Here is what carries over.
On Hostless Duck, Custom Fields Pro does the job of Advanced Custom Fields (ACF) and imports 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
Custom Fields Pro
Field groups for any content type, with nineteen kinds of field including repeaters, groups, pictures and links to other items; a screen to fill them in, an API to read and write them, and blocks that print them.
From Advanced Custom Fields (ACF)
- Carries over
- Field groups that apply to a content type which exists here, with their fields mapped kind for kind: text, text area, WYSIWYG (as text with bold, italic and links), number, range, true/false, select, radio, button group, checkbox, date, date-time and time pickers, email, URL, colour, image, file, post object, relationship, page link, repeater and group. Labels, names (as keys), instructions, required, choices, limits and starting values come too.
- Does not carry over
- Gallery, flexible content, clone, map, oEmbed, taxonomy, user, link and password fields; fields inside a repeater or group that are themselves a repeater, group, picture gallery or map; conditional logic; location rules other than content type (a warning says so); groups for options pages, users or terms.
From Advanced Custom Fields (ACF) values
- Carries over
- What was typed into ACF fields, read from a WordPress export's post meta, for items already on this site and fields already defined here (matched by key). Lists of ticked choices, dates, repeater rows, group values and links to other items in the same export are converted. Only fields still empty here are filled, and every value passes the field's checks.
- Does not carry over
- Pictures and files (WordPress stores the number of the file in its own library), links to items that are not in the export or not on this site, values that fail a field's checks, and HTML in rich text beyond bold, italic, code and links.
Not yet verified against a live export: this importer has only been tested on sample files we wrote from the documented format.
Each import ends with a report that names anything it could not carry.
The rest of the site
Advanced Custom Fields (ACF) 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 Custom Fields Pro
The small print
Advanced Custom Fields (ACF) 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 Advanced Custom Fields (ACF) 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.

