Migrate from Formaloo to Pipedrive

Each Formaloo Form becomes a field-mapping configuration rather than a destination object. We export the full field structure (field label, field type, required flag, choice options) and pre-create matching Pipedrive custom fields on the People and Organization objects. Text fields map to Text type, email to Email type, phone to Phone type, date to Date type, choice fields to Picklist or Multi-select, rating to Numeric or Star Rating. The form definition itself (logic, styling, layout) is documented as a text summary because Pipedrive has no form-builder object equivalent.

Individual Form Responses containing contact data (name, email, phone, address) map to Pipedrive People. We use the responder's email address as the dedupe key. If the Form Response includes company information, we resolve it to an Organization before the Person insert so that the OrganizationId lookup is satisfied at insert time. Timestamps (created_at, updated_at) migrate as Pipedrive open_answered_date and last_contacted_date fields.

Form Responses that contain company data (organization name, domain, industry, employee count) map to Pipedrive Organizations. We use organization name as the dedupe key. If multiple Forms track the same company via Formaloo's relational Database reference, we consolidate into a single Organization record and link all associated People. Organization address fields map to Pipedrive's address compound field.

Formaloo's relational Database links multiple Forms via reference fields. We export the Database structure as a set of related tables, identify the primary key on each Form Response, and resolve cross-form references using Pipedrive's REST API during migration. A reference from a Contact Form to a Company Form becomes an OrganizationId on the Person record. We flag circular or broken references during the mapping audit and surface them to the customer before import.

Formaloo file upload field values are exported as URLs or as base64-encoded binary data. We download uploaded files from Formaloo's storage and upload them to Pipedrive's document store, linking each file to the corresponding Person, Organization, or Deal via the deal_id, person_id, or org_id parameters in Pipedrive's Files API. File names and original upload timestamps are preserved in the file metadata.

Formaloo signature fields (available on paid plans) contain e-signature image data or links. Pipedrive does not have a native e-signature field. We migrate signature images as file attachments linked to the Person or Organization, and document the presence of the original signature in a custom text field signature_source__c so the customer's admin can evaluate DocuSign or PandaDoc integration for future e-signature workflows.

Formaloo calculation fields evaluate formulas at form submission time and store a numeric result. Pipedrive has no formula field equivalent. We migrate the calculated numeric result as a custom Pipedrive field of Numeric type, with the original calculation formula documented in a companion text field calculation_formula__c. The customer's admin decides whether to rebuild calculation logic in Pipedrive Workflows or a third-party formula tool.

Formaloo choice fields (single-select and multi-select) map to Pipedrive Picklist and Multi-select Picklist field types. We export the choice option labels and use them to populate the Pipedrive field's option list. If the customer uses Formaloo's conditional logic to show or hide choice options based on prior answers, we document this as a conditional-field note for manual Pipedrive rebuild.

Formaloo Workspace and Folder structure is organizational, not a CRM object. We export the folder hierarchy as a dot-separated path string and create Pipedrive Tags from the folder names (e.g., workspace_name.folder_name.subfolder). Tags attach to Person, Organization, or Deal records so that the original Formaloo folder context is recoverable in Pipedrive search. Workspace access permissions map to Pipedrive Teams and are documented as a permission matrix for the customer's admin to apply.

Formaloo does not have a native engagement timeline. If the customer's use case treats each Form Response as a sales touchpoint (e.g., a lead intake form submission), we create a Pipedrive Activity of type Email with the Form Response body as the activity body and the submission timestamp as the ActivityDate. This preserves the sequence of interactions in Pipedrive's timeline view. For simple data collection forms without sales context, timestamps migrate as custom date fields on the Person record instead.

Formaloo conditional logic, field visibility rules, and conditional calculation formulas are UI-defined and not exported as structured data. We provide a written inventory of every Form's logic configuration, including trigger conditions, visible fields, hidden fields, and calculation expressions, formatted for the customer's admin to rebuild in Pipedrive Workflows. This document is a deliverable, not an automated migration.

Formaloo integrations (Google Sheets two-way sync, Wix, Pabbly webhooks) are platform-specific and do not transfer to Pipedrive. We document each active integration, its trigger events, and its destination, and recommend the equivalent Pipedrive integration or Zapier connection. Google Sheets sync, for example, is replaced by Pipedrive's native Google Workspace integration or Zapier's Pipedrive triggers.