Migrate from Formaloo to Twenty CRM

Formaloo form responses that contain individual contact fields (name, email, phone, address, job title) map to Twenty CRM Person records. We extract the submitter metadata (email, name) and field-type-specific values from each response, then map them to Person fields using Twenty's standard field schema. The email field on Person becomes the dedupe key. Any submitter metadata with a company affiliation maps to a Company lookup on the Person record. Responses from forms that do not contain individual contact fields (e.g., survey aggregates or product feedback forms) are evaluated for custom object placement during scoping.

Formaloo form responses that contain organizational data (company name, domain, industry, employee count, address) map to Twenty CRM Company records. If a Formaloo form captures both individual contact fields and company fields in the same response, we split the response into a Person record and a Company record and create the Person-Company link via the workInformation relationship on the Person object.

If a Formaloo form was used as a lead capture or deal registration form with deal-value fields, stage fields, or expected-close-date fields, those responses map to Twenty CRM Opportunity records. Pipeline stage values from Formaloo choice fields map to Opportunity.stageName, and deal value fields map to Opportunity.amount. The Opportunity.Company map-link connects each Opportunity to a resolved Company record.

Formaloo's relational database layer links multiple Forms via reference fields. We export the Database structure as a set of related tables, identify which cross-form references represent parent-child relationships (1:N) and which represent N:N associations, then create Twenty CRM custom objects or lookup relationships accordingly. Reference field IDs from Formaloo are preserved as externalId values on the target records so that the lookup can be resolved during import rather than requiring a two-pass load.

Formaloo calculation fields and formula fields do not export as structured automation. We document each calculation field's formula logic as a text note and, where Twenty CRM supports formula fields on standard or custom objects, we recommend recreating it as a Twenty formula field with equivalent logic. The original Formaloo calculation value migrates as a static numeric or text field on the target record for historical accuracy.

Formaloo signature fields store e-signature image data or signature log records. We export the signature as a file attachment linked to the target Person or Company record in Twenty CRM via ContentDocument and ContentDocumentLink. The source Formaloo plan must include signature fields — we confirm this during scoping to avoid attempting to migrate a feature unavailable on the customer's current plan.

Formaloo file upload fields store uploaded documents as attachments on form responses. We export the file metadata (filename, size, content type, download URL if available via API) and the file content itself, then attach each file to the target Person, Company, or Opportunity record in Twenty CRM via the ContentDocumentLink table. Large file handling uses chunked upload to respect API size limits.

Formaloo choice fields, rating fields, and multi-select fields map to Twenty CRM custom fields with the corresponding field type (select for single-choice, multi-select for multi-choice, number for rating). We extract the Formaloo choice option labels and create matching picklist values in Twenty's custom field schema before import begins. Rating scales from Formaloo (1-5, 1-10) are mapped to numeric custom fields in Twenty.

Formaloo form definitions (field names, field types, field order, conditional logic visibility rules) are documented as a written schema inventory rather than migrated as executable configuration. The form structure informs the field mapping above. Conditional field visibility rules are documented as text notes for the customer's admin to implement in Twenty CRM after migration.

Formaloo Workspaces act as organizational containers for forms and responses. We map Workspace membership to Twenty CRM workspace tags and capture folder path hierarchies as a tag prefix convention (e.g., Sales / Leads / Q1) so that the organizational context from Formaloo is recoverable in Twenty's tag system. This is a structural mapping, not a 1:1 object import.

Formaloo integrations with Google Sheets, Wix, Pabbly, and webhooks are platform-specific and do not transfer to Twenty CRM. We document each active integration (connection type, trigger event, destination URL or sheet ID) as a written handoff inventory so the customer's admin can reconfigure equivalent integrations in Twenty CRM after migration.