Migrate from Formaloo to HighLevel

Form Responses where the primary field is a person's name and email map to GoHighLevel Contact records. We export the Form's Response data via REST API or Excel, map each field to either a standard Contact field (First Name, Last Name, Email, Phone, Address) or a custom Contact custom field, and import via the GoHighLevel Contacts API. The Form's submission timestamp maps to the Contact's createdAt field. Deduplication is performed on email address before import.

Form Responses where the primary entity is an organization (company name, industry, employee count) map to GoHighLevel Account records. We treat this as a separate Form mapping pass after the Contact import. The Account Name maps directly; other fields map to Account custom fields. Account creation must precede the Contact import pass if the Form uses a reference field to associate a person with a company.

Formaloo's relational database links multiple Forms via reference fields. We identify the primary (parent) Form and import it first, then during the linked (child) Form import we resolve the reference field value against the imported parent records to populate the corresponding GoHighLevel Contact custom field or lookup. The foreign-key relationship does not translate to a native GoHighLevel object relationship because GHL does not support cross-object relational modeling at the Form level.

Formaloo field types (choice, rating, number, date, text, email, phone) map to GoHighLevel Contact custom fields. We create the custom field in GoHighLevel with the matching type (text, number, date, phone, picklist) before import, then map the Response value during the data load. Choice fields map to GoHighLevel picklist custom fields with the same options.

Formaloo signature fields hold e-signature image data. We export the signature as an image file and attach it to the GoHighLevel Contact record via the file attachment API. If the source plan was Free tier (which does not include signatures), we flag this as a data gap during scoping. The signature field is preserved as a reference note if the image cannot be extracted.

Formaloo file upload fields hold uploaded documents, images, or other attachments per Response. We export the file, store it with the corresponding record's identifier, and attach it to the GoHighLevel Contact or Opportunity record via the GoHighLevel file attachment API. Large file sets may require chunking to stay within attachment size limits.

Every Formaloo Form Response carries a createdAt timestamp. We preserve this as a custom field submission_date__c on the GoHighLevel Contact to maintain the original submission chronology, which is distinct from the GoHighLevel record creation date (the migration import date). This distinction matters for teams tracking customer tenure from first interaction.

Formaloo's folder hierarchy organizes Forms and Responses within Workspaces. We extract the folder path for each Form and apply GoHighLevel tags (e.g., folder_path_lead__c) to the migrated Contacts so that the original organizational context is recoverable. Tags are applied as part of the import pass, not as a separate operation.

Formaloo conditional logic, field visibility rules, 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 (which fields are conditional, what conditions trigger visibility, how calculations are derived) and deliver it alongside the migration. Your team uses this summary to rebuild the logic as GoHighLevel Workflows post-migration.

Formaloo calculation fields perform arithmetic or formula operations within a Form (sums, averages, conditional totals). These exist only within Formaloo's form engine and have no GoHighLevel equivalent as a stored field. We preserve the calculation logic in the logic inventory document delivered with migration data. The customer's admin rebuilds the logic as a GoHighLevel Workflow formula action or a custom field formula.