Rewst to n8n form migration checklist
A migration checklist for MSPs rebuilding Rewst forms in FormNode while moving workflow execution to n8n.
A Rewst to n8n form migration checklist should inventory every source form field, dynamic option source, organization variable, conditional rule, approval step, payload mapping, and workflow trigger before rebuilding the form layer in FormNode and the workflow logic in n8n.
Verify these before publishing.
Export or document the source form
Capture fields, labels, field names, conditions, dynamic options, and workflow trigger expectations.
Classify dynamic fields
Mark each option list as static, integration-backed, workflow-generated, or organization-variable based.
Map organization context
Decide where customer, tenant, PSA, RMM, and Microsoft 365 IDs will live in FormNode.
Rebuild option endpoints
Create read-only n8n webhooks for dynamic dropdowns that need live data.
Rebuild approvals explicitly
Do not assume approval behavior transfers automatically from the old workflow.
Compare payloads
Submit test data and compare the new FormNode+n8n payload to the old workflow requirements.
Migrate one form at a time
Start with onboarding, ticket intake, approvals, or license requests before broader migration.
- A Rewst-generated option list has no replacement n8n endpoint.
- Organization variables are not mapped before publishing.
- Conditional fields are dropped without confirming they are no longer needed.
- The new n8n workflow expects field names that differ from the rebuilt form.
- The migration tries to replace the whole automation platform in one pass.
Can I migrate Rewst forms without sharing workflows?
Yes. You can document field structure, dynamic option behavior, and payload expectations without publishing reusable workflow exports.
What is the first Rewst form to migrate?
Start with a high-value but bounded workflow such as Microsoft 365 onboarding, ticket intake, license requests, or customer approvals.