Import from Formwise Classic
Bring your Formwise Classic Smartforms and CoPilots into FormWise as draft Flows, and know what to review before publishing.
Import from Formwise Classic
If you built tools in Formwise Classic (the original app at app.formwise.ai), you can import them into your FormWise workspace instead of rebuilding them. Each Classic tool becomes a draft Flow that you review and publish.
Who can import
The importer is available to accounts that signed in with the same email as a Formwise Classic login. If your workspace was created without a Classic account, the option doesn't appear. Sign in with your Classic email to see it.
Where to find it
- Open Flows in the sidebar.
- Click New, then Import from Formwise Classic at the bottom of the picker.
- Your Classic tools are listed, grouped by Classic workspace. Search by name if you have many.
- Tick the tools you want, or use Select all ready, then click Import selected.
Select all ready leaves out tools that are already imported and tools that have nothing runnable (no prompt steps, or no prompt). You can still tick those by hand.
What migrates
| Classic | FormWise |
|---|---|
| Smartform | Form Flow: questions in the Start step, one Agent step per prompt step, in order |
| CoPilot | Chat Flow: one Agent step with the system prompt, plus the conversation starters and input placeholder |
| Question types | Short answer, email, phone, date, multiple choice, checkboxes. Multiline questions become short answer. The "user data source" picker becomes a file upload |
| Prompt variables | @answer tokens become the matching question variable; @Step_N becomes a reference to that step's output |
| Model | Mapped to the closest current model. Retired models (for example GPT-3.5) fall back to the workspace default |
| Web browsing and scraping | Kept per step |
| Hidden steps | Kept as "hide response from chat". If every step was hidden, the last one is shown so the Flow produces output |
| Webhook forwarding | A Send Webhook step with the same URL |
| Chat disclaimer | Kept when you had customised it in Classic |
What does not migrate
- Knowledge documents. Classic documents are not copied. Upload them to a Notebook in this workspace and attach it to the Flow.
- Themes, colours, and icons. Styling starts from your workspace defaults.
- Response history and credits pricing. Past runs stay in Classic; pricing is set in FormWise.
- Advanced model settings such as top-p, max tokens, and penalties. Only an explicitly set temperature carries over.
- Webhook payload shape. The Send Webhook step sends FormWise's payload, which differs from Classic's. Update the receiver (Make, Zapier, and so on) to read the new fields.
The import report
After importing, each tool shows one of:
- Imported: a draft Flow was created.
- Imported with warnings: created, with items to check. Expand the row to read them. Typical ones are knowledge documents that were not migrated, a retired model that was swapped, a prompt step that had no prompt and was skipped, or a prompt variable that no longer matches a question.
- Updated: you re-imported a tool and its existing draft was refreshed.
- Skipped: the tool was already imported. Use Re-import on its row to refresh the draft.
- Failed: something went wrong for that tool. Use Retry failed or import it again later.
Click Open draft to review a Flow. Nothing is published until you publish it.
Re-importing
Importing the same Classic tool again does not create a duplicate. By default it is skipped; Re-import on the row replaces the draft with the current Classic version. Any edits you made to the draft in FormWise are overwritten, so re-import before you start editing, not after.
Your Classic tools
Importing changes nothing in Formwise Classic. Your Classic tools, embeds, and links keep working exactly as before.