Sparki Docs

Form Import and Export

Move form setups between portals, projects, and review environments.

Form I/O

Use import and export to reuse a proven form without rebuilding it by hand.

Export gives you a portable form file. Import creates a new editable draft that still needs a human review before customers use it.

When to Use It

Form import and export is useful when a team wants to reuse an intake, qualification, bidding, or document-collection process across portals, projects, or review environments.

Good use cases:

  1. Copy a working pre-validation flow to a similar project.
  2. Share a standard intake form with another portal.
  3. Review a form setup outside the builder before changing the live version.
  4. Keep a backup of a complex form before making larger edits.

Export

Open the form and use the export action when it is available for your plan and role. The export file should represent the form structure: title, description, steps, questions, content blocks, options, conditions, endings, and translations that belong to the form.

Export is a configuration snapshot, not a customer-data export. Customer answers stay in Inbox and customer timelines as Answer interactions.

Import

Import creates a new form draft from the exported file. Review the draft before publishing it:

  1. Check the title and description.
  2. Open every step and question.
  3. Confirm required fields, options, and conditions.
  4. Check every ending and project-related action.
  5. Review translations in the languages enabled for the portal.
  6. Save and test the customer flow from portal or plugin before sharing it.
Form question and content types

Imported forms use the same builder blocks as normal forms, bidding questions, and pre-validation questions.

Project-Specific Review

Project links and appointment endings need extra attention after import. A form file can describe the intended action, but the new portal or project may not have the same project, agenda, bidding setup, payment setup, or document-upload feature enabled.

If an imported ending points to a project action, select the correct project again and confirm the action is still valid. If the form belongs to pre-validation or bidding, test it from the project page where customers will actually use it.

Safety Checks

Treat import like copying a template, not publishing a finished production flow. A good import review checks:

  1. No required question is missing customer-facing text.
  2. Conditional questions still make sense with the imported options.
  3. Fallback endings are clear.
  4. Translations are present for the customer languages you expose.
  5. File upload questions are only used when document uploads are enabled for the portal.
  6. The imported form is inactive until someone confirms it is ready.

Plan and Role Notes

Form import and export are Pro and Custom capabilities. Members need form editing access to import, export, or publish form changes. For normal CSV exports of dashboard lists, see Data Export.

On this page