Migrate from Formaloo to HubSpot

Formaloo records in bases tracking people (with name, email, phone, job title fields) map directly to HubSpot Contacts. Each record becomes one Contact. We match on email address for deduplication. Records without email land in HubSpot as Contacts with email set to null and flagged for manual review.

Formaloo records in bases tracking organizations (company name, domain, industry, employee count) map to HubSpot Companies. We map the Formaloo company name field to HubSpot's Company Name property and domain to the Website property. Multi-word company names are preserved as-is.

Formaloo bases containing deal-like records (deal name, amount, close date, status) map to HubSpot Deals. We identify deal-type bases by the presence of currency fields and status/choice fields. The deal name maps to Deal Name, amount to Amount, and the status field values map to your HubSpot pipeline stage values via value mapping.

Formaloo bases tracking support requests, tickets, or case records map to HubSpot Tickets. Subject, description, priority, and status fields map to HubSpot Ticket properties. HubSpot Ticket pipeline stages are configured in your destination portal before migration. We also map any custom fields related to ticket categorization, resolution timestamps, and internal notes to ensure your support history carries over completely.

Formaloo bases representing custom business entities (projects, subscriptions, certifications) that don't map to HubSpot's standard Contact/Company/Deal/Ticket objects require HubSpot custom objects. We create the custom object and its custom properties in HubSpot, then map records accordingly. Custom object associations to standard objects use HubSpot's association API.

Formaloo's relational fields linking records in one base to another map to HubSpot associations or custom lookup properties. For contact-to-company relationships we use HubSpot's primary company association. For custom object links we create custom association types or store the related record's HubSpot ID in a custom property.

Formaloo records store creation timestamps and modification timestamps. HubSpot's native Createdate and lastmodifieddate reflect migration time, not original record creation. We preserve the original Formaloo timestamps in custom datetime fields (e.g., Original_Created_Date__c) for reporting continuity. This approach maintains your historical data integrity and ensures that time-based reports and analytics reflect the actual customer journey from the original Formaloo system.

Formaloo records may have an assigned user or owner field with an email address. We resolve these emails against your HubSpot user list. Matched users become the Deal Owner or Contact owner. Unmatched owners are flagged before migration — your team either creates HubSpot users first or assigns records to a fallback owner.

Formaloo file attachment fields (images, PDFs, documents) are downloaded and re-uploaded to HubSpot's file manager. Each file becomes a HubSpot File record, and the link is stored on the parent record (Contact, Company, Deal, or custom object). Files over 25MB are flagged for manual handling.

Formaloo choice-type fields (single select, multi select) map to HubSpot pick-list properties if the number of values is manageable. If Formaloo has open-ended text choices, we map to HubSpot single-line text. Multi-select in Formaloo maps to HubSpot's text property storing comma-separated values, since HubSpot has no native multi-select for Contact properties.