Migrate from Formaloo to Salesforce Sales Cloud

Formaloo form responses with no buyer qualification data map to Salesforce Lead. We extract each Form as a separate export, identify which form fields correspond to standard Lead fields (Name, Email, Phone, Company, Title), and map the remaining fields to custom Lead fields (custom field API name with __c suffix). The mapping is form-specific; we build a per-form field matrix during scoping.

Formaloo form responses from customer-facing forms (support intake, onboarding, renewal) where the submitter is an identified Contact map to Salesforce Contact. We require the customer to designate which Forms represent known customer records versus prospect leads during scoping. Contact records require a parent AccountId at insert time, so we create or match the Account first.

Formaloo forms that collect organizational data (company name, domain, industry, employee count) map to Salesforce Account. Multiple form responses from the same company (via email domain match or explicit company field) are de-duplicated and merged into a single Account record. We use the company domain as the primary Account dedupe key.

Formaloo forms used for specialized data collection (application intake, order tracking, project registration) that have no Salesforce standard object equivalent migrate to Salesforce Custom Objects. We pre-create the Custom Object schema (API name, fields, field types, picklist values) in the destination org before data import. Formaloo's Database layer forms that link multiple tables map to Custom Objects with explicit lookup fields pointing to the related Salesforce records.

Formaloo's Database layer connects Forms via reference fields, creating a relational graph of related records. We export the Database structure as a set of related tables, identify foreign-key equivalents (the reference field values linking Form A to Form B), and create Salesforce Custom Objects with Lookup fields that replicate the relationship. The lookup resolution happens at migration time by matching the reference field value to the target record's Salesforce ID.

Formaloo's 20+ field types (text, number, email, phone, date, file upload, signature, rating, calculation, choice, ranking, matrix, equation) map to typed Salesforce fields. Text to Text, Long Text Area, or Email depending on format. Number to Number with appropriate precision. Date to Date. File upload to ContentDocument linked via ContentDocumentLink. Signature to a custom Rich Text field or as a separate ContentDocument with e-signature metadata preserved. Choice fields map to Picklist or Multi-Select Picklist based on whether single or multiple selection.

Formaloo folders nested within Workspaces provide a hierarchical organizational layer. We export the folder path for each Form and Response and map folder names to Salesforce Tags on the migrated records. The customer chooses during scoping whether to use Salesforce native Tags or a custom multi-select picklist field that preserves the folder hierarchy as a delimited string (e.g., Sales/Qualified/Leads).

Formaloo Workspaces act as organizational containers analogous to business units or org hierarchies. We map Workspace membership to Salesforce Teams (Territory-based or Queue-based) or to hierarchical Account structures if the Workspaces represent customer segments rather than internal teams. The customer designates the Workspace mapping strategy during scoping.

Formaloo response timestamps (submission time, last edit time) migrate as Salesforce CreatedDate and LastModifiedDate where the API allows. Where Salesforce prevents direct CreatedDate writing, we store the original Formaloo timestamp in a custom field formaloo_created_date__c and note it in the handoff document for the customer's admin.

Formaloo file upload fields attach documents to form responses. We export the files, create Salesforce ContentVersion records, and link them via ContentDocumentLink to the parent Salesforce record (Lead, Contact, or Custom Object) using the Formaloo file path as the ContentDocument title. We do not migrate the original file URLs as Salesforce does not accept external URLs as document sources.

Formaloo folder-level access control and role-based permissions are exported as a permission matrix (user, folder, role). We map Formaloo roles to Salesforce Permission Sets or Permission Set Groups based on the equivalent access scope. Workspace-level access maps to Salesforce Teams membership. The customer reviews and approves the permission mapping before provisioning.

Formaloo conditional logic, field visibility rules, and calculation formulas are UI-defined automations that do not export as structured data. We document each form's logic configuration as a text summary (form name, field, condition, action) in the handoff inventory. The customer's admin or a Salesforce partner rebuilds the equivalent logic in Salesforce Flow post-migration. This is not included in the migration scope.