Import a Logical Forms form export under Logical Forms → Tools → Import. Form files create new forms. They do not replace an existing form with the same name or import submitted entries.
Before importing
Use a JSON file produced by the Logical Forms form exporter. Install compatible Core, Pro and required add-ons on the destination first. Import does not convert other plugins' form formats.
The upload limit is 1 MB, or the website's lower upload limit. A file must be a readable .json configuration with a supported format and schema. Save the original export so you can inspect it if the destination rejects it.
Upload and review
- Open Tools → Import.
- Choose the form configuration JSON file and select Import.
- Read the Review forms screen and select the forms you want to create.
- Resolve any required Page destinations and review warnings.
- Use the final import control to create the selected forms.
The form review itself does not create entries, execute notifications or download images. Its field count and warnings help identify whether the destination can use the configuration.
Resolve dependencies and resources
| Setting | What it does |
|---|---|
| Unavailable field or action type | Enable the compatible provider on the destination or revise the source form and export again. That form is blocked while a required type is unavailable. |
| Unresolved Page confirmation | Choose an appropriate published destination page in the review. An unrelated page with the same numeric ID is not sufficient. |
| Missing images | Images are not downloaded. Labels and values can remain, but you need to choose replacement images on the destination. |
| CAPTCHA configuration | Configure and test the destination site's keys. The form export does not supply global credentials. |
| Explicit URLs and recipients | Review them after import. They remain as configured; import does not infer a new inbox or replace arbitrary HTML links. |
Read the result
Each imported form is an independent creation with a new form ID. Field and action identities inside its configuration are retained so conditions and mappings can remain connected. An exported active status is not a substitute for reviewing the destination before sharing its page.
Read the created and failed results before repeating an import. Successful earlier copies can remain even if a later form fails; the whole file is not rolled back as one transaction. Repeating a successful import can create another copy.
Check the imported form
Open Build and Settings, review its status, questions, notification recipients, confirmation destinations, images and integrations. Save any corrections. Embed its new shortcode and test the destination workflow.
For copying the separate website-wide preferences, read site settings transfer. Its import behavior differs: a settings file is applied directly rather than going through form review.
