Migrate from Formaloo to Nutshell

Each Formaloo Form is treated as a structured table. For forms collecting person-level data (name, email, phone, company), each Response row maps to a Nutshell Contact. For forms collecting organization-level data, each Response row maps to a Nutshell Company. The Form definition (field structure, field labels) is preserved as a text summary in a custom field formaloo_form_id__c for audit. If multiple Forms collect contact information, the responses are merged into a single Contact record per submitter using email as the dedupe key.

Individual Form Responses map to Nutshell Contact or Company records with field-by-field transformation. Formaloo field types (text, email, phone, date, number, choice) map to Nutshell standard fields (Email, Phone, Mobile, Birthday, Date of Birth, Postal Code, Description). Formaloo choice fields map to Nutshell custom picklist fields created during schema design. Each Response's submitted_at timestamp maps to Contact Created Date or a custom formaloo_submitted_at__c field to preserve the original submission time.

Formaloo's relational database layer links multiple Forms via reference fields. We export the database structure as a set of related tables, then flatten cross-record references into Nutshell custom fields. For example, a Formaloo reference field linking a Contact Form to a Project Form becomes a custom text field project_name__c or a Tag on the Contact record. Many-to-many relationships are decomposed into Tags on the Contact. The customer selects the flattening strategy during scoping based on the number of related records.

Formaloo file upload fields attached to form responses migrate as Nutshell Notes with the file attached via the File (ContentDocument) model. We extract the file from Formaloo's export or API response, upload it to Nutshell as an Attachment or ContentDocument, and link it to the parent Contact or Company record. File names are preserved in the Note body for searchability.

If the customer used Formaloo's email notification feature to send confirmation emails to form submitters, those email events are not separately stored in Formaloo's export and do not produce individual EmailMessage records in Nutshell. The submission timestamp is preserved as a Contact or Note field. If the customer used Formaloo's two-way email feature to receive email replies to form notifications, those replies do not migrate; we document this limitation and recommend setting up Nutshell email templates as the replacement communication method.

Formaloo's conditional logic rules, field visibility conditions, and calculation formulas are UI-defined automation that does not export as structured data. We document each Form's logic configuration as a written summary (field name, trigger condition, action) and deliver it alongside the migration. Nutshell's Automations use a different trigger-and-action model; the customer's admin uses the logic inventory to rebuild equivalent rules in Nutshell Automations post-migration.

Formaloo signature fields are only available on paid plans. If the customer's source plan included signature fields, we export the signature image as a PNG or PDF file and attach it to the corresponding Nutshell Contact record as a Note or ContentDocument. Nutshell does not have a native e-signature field; for legally binding signature use cases, we recommend a separate e-signature tool such as DocuSign or PandaDoc as the replacement workflow.

Formaloo Workspaces map to Nutshell Teams for organizational assignment. Formaloo folder paths map to Nutshell Tags so that folder structure is recoverable as tag labels (e.g., tag: Lead/Inquiry/2025). We extract the full folder path from each Form and Response and decompose it into the most granular applicable label.