Migrate from Follow Up Boss to HubSpot

FUB's Person object maps directly to HubSpot Contact. Standard properties (name, email, phone, address) transfer as-is. FUB's phones array must be decomposed into HubSpot's phone and mobilephone properties. FUB stage, tags, and source properties map to custom contact properties in HubSpot.

FUB's single stage field has no direct HubSpot equivalent. We map FUB stage values to HubSpot lifecycle_stage pick-list options or create a custom field (FUB_Stage__c) to preserve the original progression. If FUB uses custom stage names beyond New/Contacted/Showing/Contract/Closed, a custom field mapping is required before import.

FUB supports multiple tags per person with unlimited tag creation. HubSpot has no native multi-tag property on contacts. We create a custom text property and join all FUB tags with a delimiter, or use a multi-select pick-list if HubSpot edition supports it. Tag count and uniqueness determine which approach is recommended per migration plan.

FUB Action Plans are the primary automation engine — they trigger emails, texts, task creation, and stage changes based on lead actions. HubSpot Workflows are the equivalent mechanism but have a different trigger model. We export full Action Plan definitions as a structured rebuild reference so your HubSpot admin can recreate the logic in Workflows.

FUB tracks lead source (Zillow, Realtor.com, Referral, etc.) as a person property. HubSpot has multiple source tracking fields on contacts. We map the primary FUB source to HubSpot's original_source_data2 or create a custom property (FUB_Source__c) to preserve all historical source attribution.

FUB transactions map to HubSpot Deals with direct mappings for name, amount, stage, and close date. FUB supports multiple transactions per person; each becomes a separate Deal associated to the same contact in HubSpot. FUB's transaction-stage names may need value-mapping to HubSpot deal pipeline stage names.

FUB's Background field stores a long-text note for the most important contextual information about a person. We map this to a custom long-text property on the HubSpot contact (FUB_Background__c) to preserve the data. The Background field is a flat text field in FUB but can contain important buyer criteria and qualifying notes.

FUB action history — including call logs, sent emails, text messages, and meeting notes — migrates as HubSpot engagements. Calls and emails become Tasks with Type='Call' or 'Email'; meetings become Events. Original timestamps and assigned agent owners are preserved. Note: FUB's action metadata (e.g., call disposition, duration) becomes custom task properties in HubSpot.

FUB agent assignments on people and transactions map to HubSpot User owners by email match. We run an owner resolution pass before migration: matched emails link to HubSpot users; unmatched agents are flagged and assigned to a fallback HubSpot owner, with a custom property (FUB_Agent_ID__c) preserving the original agent reference for post-migration reassignment.

FUB's core differentiator is its integration with MLS systems, IDX websites, and real estate lead providers (Zillow, Realtor.com, BoomTown). These integrations are not part of the contact or transaction data model and do not migrate. We document every active FUB integration and provide a rebuild checklist for HubSpot App Marketplace connections and Zapier setups.

FUB supports four custom field types (text, date, number, dropdown) per person, company, and transaction. Each FUB custom field requires a corresponding HubSpot custom property to be created before import. Dropdown fields require value-by-value mapping of FUB choices to HubSpot options. Text and number fields map directly once the HubSpot property is created.

FUB people can be associated with a primary company. This maps to HubSpot's Company object. Company name, address, phone, and website transfer directly. Multiple FUB people linked to the same company create multiple HubSpot contacts all associated to the same HubSpot Company record.