Export and import forms safely with Drecha Forms Free

What form portability includes

Drecha Forms Free can export one form definition as a versioned JSON file and import that definition as a new draft. Use it to copy a form between sites, keep a reviewable configuration backup, or create a variant without rebuilding every field.

The export contains the form title and validated schema. It does not contain entries, uploaded files, delivery history, licenses, or site configuration. Integration secrets and URL-like secret fields are blanked recursively before the file is created.

Export a form

1. In WordPress, open Drecha Forms > Tools.
2. Under Export a form, choose the form.
3. Select Export JSON.
4. Save the downloaded file in a protected location.

The filename is based on the form title and ends with drecha-forms.json. The payload identifies itself as Drecha Forms format version 1 and includes an export timestamp.

Import the form as a draft

1. Open Drecha Forms > Tools on the destination site.
2. Under Import a form, choose the JSON file. The upload limit is 1 MB.
3. Select Import draft.
4. Return to Forms and open the newly created draft.
5. Review every field, confirmation, notification, conditional rule, calculation, and integration setting.
6. Re-enter any required destination-specific secret or endpoint, send a test, and publish only after review.

Import never overwrites an existing form. It assigns a new internal identifier and keeps the result unpublished. When the exported title is unavailable, the fallback title is Imported form.

Understand validation and edition boundaries

The importer accepts JSON only, limits nesting depth, requires the Drecha Forms marker and supported format version, then sends the schema through the current field and feature registry. Malformed JSON, unsupported versions, unknown structures, and invalid field settings are rejected before a form is created.

The portability workflow itself is Free. A file can contain settings for Pro capabilities that existed on its source site, but only currently installed and entitled implementations can execute those capabilities. Free rendering and editing remain available; premium data must not be treated as an active integration merely because it appears in a transferred definition.

Practical example

To move a contact form from staging to production:

1. Export the reviewed staging form.
2. Import it on production as a draft.
3. Confirm email recipients use production addresses.
4. Reconnect any Pro provider or webhook because secrets were removed.
5. Submit a harmless test entry and verify storage, confirmation, and accepted mail or integration logs.
6. Publish and embed the new production form.

Troubleshooting

• File too large: confirm it is a single form-definition JSON file smaller than 1 MB, not a ZIP or entry export.
• Invalid JSON: export again from Drecha Forms instead of editing the file in a word processor.
• Unsupported format version: update the destination Free plugin, then retry. Do not manually change the version number.
• Import succeeds but an integration fails: reconnect it and restore destination-specific configuration; secret values are deliberately omitted.
• Need entries: use the separate Entries CSV export. Form JSON does not transfer submissions and CSV cannot recreate a form definition.

Continue with Build, edit, and publish a form and Understand submissions and manage entries after the imported draft has been reviewed.