Exporting and importing a flow
Move a finished form between sites, keep a copy before a rebuild, or hand one to a colleague — as a JSON file.
- Intermediate
- 4 min read
- Applies to 2.0
Exporting
Open the flow and use Export. You get a JSON file holding the field definitions, their validation rules, their storage settings, and the layout — everything the builder knows about that flow.
The Export and Import buttons above the field list.
Export before a rebuild. It costs nothing, and it is the only undo the builder has.
Importing
Import, then choose the file. The imported schema replaces what the flow currently holds — it is not merged in alongside it.
Import replaces. Export the current flow first if there is anything in it you would miss.
Moving between sites
Export from one site, import on the other. Two things do not travel:
- The member data. A schema is a description of a form, not its answers. Members on the destination site have whatever they had before, under whatever meta keys already existed there.
- The page. A flow is attached to a WordPress page, and the imported schema attaches to whichever page the destination site has assigned to that flow. Assign the pages first, then import.
Check the storage keys after an import. A flow that wrote to
acme_membership_number on the old site will write to the same key on the new
one, which is right if both sites mean the same thing by it and wrong if they do
not.
Keeping the file
The export is plain JSON. It reads well enough to diff, so keeping successive exports in version control alongside your theme is a reasonable way to see what changed and when — something the builder itself does not record.
Something missing or out of date? Tell support.