Follow Up Boss to HubSpot migration
Moving from Follow Up Boss to HubSpot means trading a real-estate-only CRM for HubSpot's full CRM, marketing, sales, and service platform under one account. We map every Follow Up Boss person, transaction, tag, and custom field — preserving original create dates and agent assignments — so your HubSpot instance launches with complete contact and deal history intact.
FlitStack AI migrates contacts, contact.lifecycle_stages, contact.hs_object_tag_ids, hubspot workflows and contact.hs_analytics_source_data2s from Follow Up Boss to HubSpot, with their history and the associations between records. Every field is mapped and validated, a sample run is checked with you before the full migration, and the whole move can be rolled back in one click. Typical timeline: 24–48 hours for under 10,000 records after field mapping is approved.

What moves from Follow Up Boss to HubSpot?
Follow Up Boss organizes leads around a Person object with stage, tags, sources, and Action Plans for automated follow-up sequences.
Read the full summary
HubSpot models contacts with lifecycle_stage, deal properties, and association labels on a unified CRM object graph. This migration carries your Follow Up Boss people, companies, transactions, and activity history into HubSpot contacts, companies, and deals with custom field parity. Action Plans — Follow Up Boss's core automation engine — do not migrate and must be rebuilt in HubSpot's workflow builder. Integrations such as MLS feeds, IDX portals, and lead-source connectors also require reconfiguration in HubSpot. We use Follow Up Boss's REST API for extraction, map all standard and custom fields, validate with a sample migration before committing the full run, and run a delta pickup window for in-flight changes during cutover. Our process includes a comprehensive inventory of your FUB data, a property creation checklist for HubSpot, owner resolution by email match, and a detailed export of Action Plan logic to guide the rebuild in HubSpot Workflows. We also capture transaction-level data, custom field definitions, and tag values to ensure a complete and accurate CRM instance in HubSpot.
Person → Contact
FUB's Person object maps directly to HubSpot Contact.
How it maps
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.
Person.stage → Contact.lifecycle_stage (or custom field)
FUB's single stage field has no direct HubSpot equivalent.
How it maps
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.
Tag → Contact.hs_object_tag_ids (custom property)
FUB supports multiple tags per person with unlimited tag creation.
How it maps
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.
Action Plan → HubSpot Workflow (manual rebuild required)
FUB Action Plans are the primary automation engine — they trigger emails, texts, task creation, and stage changes based on lead actions.
How it maps
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.
Source → Contact.hs_analytics_source_data2 (or custom property)
FUB tracks lead source (Zillow, Realtor.com, Referral, etc.) as a person property.
How it maps
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.
Transaction → Deal
FUB transactions map to HubSpot Deals with direct mappings for name, amount, stage, and close date.
How it maps
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.
- PersonContact1:1
- Person.stageContact.lifecycle_stagetransformed
- TagContact.hs_object_tag_idstransformed
- Action PlanHubSpot Workflowtransformed
- SourceContact.hs_analytics_source_data2transformed
- TransactionDeal1:1
+ 6 more in the mapping below
How Follow Up Boss and HubSpot differ
The differences that decide how each record is mapped. These are what a CSV export and a native importer don't resolve for you.
| Dimension | Follow Up Boss | HubSpot |
|---|---|---|
| Data model | FUB uses a Person object with stage, tags, and Action Plans as core constructs; transactions and leads are secondary. | HubSpot uses Contact with lifecycle_stage, Company, Deal (opportunity), and Ticket as separate CRM objects with associations. |
| Automation | Action Plans drive follow-up sequences, drip emails, and task creation automatically when leads enter a stage. | HubSpot Workflows and Sequences handle automation. FUB Action Plans must be exported and rebuilt manually. |
| Contact properties | FUB person properties use snake_case names such as stage, source, and background, with a flat property model. | HubSpot contact properties use snake_case but support a much larger property library including lifecycle_stage, hs_lead_status, and custom __c fields. |
| Marketing features | FUB focuses on lead management and calling/texting; email marketing and landing pages are limited compared to HubSpot. | HubSpot includes native email marketing, landing pages, live chat, and a full marketing hub requiring separate licensing. |
| Lifecycle representation | FUB's stage field represents a single lead progression path with no built-in historical stage-tracking timestamp. | HubSpot's lifecycle_stage field represents buyer journey stages with associated dates (e.g., contact_date, deal_stage_last_date) preserved during migration. |
| Phone and SMS | FUB provides integrated calling, two-way texting, and per-agent phone numbers as native platform features on most plans. | HubSpot calling requires a Sales Hub Professional+ seat; Twilio SMS must be reconnected via HubSpot's integrations post-migration. |
| Custom fields | FUB custom fields support types: text, date, number, and dropdown. Field name in API is stored in the name property. | HubSpot custom properties support identical types but require creation in HubSpot before import; dropdown values must be mapped individually. |
| Integration ecosystem | FUB's strength is lead-source integration (Zillow, Realtor.com, MLS, IDX websites) with over 200 third-party connections. | HubSpot's ecosystem includes 1,000+ integrations via App Marketplace, but MLS and IDX portal connections are not included natively. |
Follow Up Boss to HubSpot field mapping
The 30 most-used fields of 40 mapped for this pair. Custom fields are added from your own schema during scoping. Download the full mapping (CSV) ↓ or open it in the field mapping template.
-
firstnamePersonfirstnameContact -
lastnamePersonlastnameContact -
emails[0].valuePersonemailContact -
phones[0].value (primary)PersonphoneContact -
phones[1].value (mobile)PersonmobilephoneContact
| Follow Up Boss field | HubSpot field | Mapping | Note |
|---|---|---|---|
Person.firstname | Contact.firstname | direct | |
Person.lastname | Contact.lastname | direct | |
Person.emails[0].value | Contact.email | direct | |
Person.phones[0].value (primary) | Contact.phone | direct | |
Person.phones[1].value (mobile) | Contact.mobilephone | direct | |
Person.stage | Contact.lifecyclestage | value_mapping | FUB stage values map to HubSpot lifecycle_stage pick-list. Custom stage names require a custom field (FUB_Stage__c) if no HubSpot lifecycle value matches. |
Person.stage_updated | Contact.hs_lifecycle_stage_last_contacted_date | custom_field_required | FUB stage change timestamp preserved as HubSpot lifecycle date or custom datetime field FUB_Stage_Updated__c. |
Person.tags | Contact.hubspot_tag_ids | custom_field_required | FUB tags array joined by comma into HubSpot custom text property. Multi-select pick-list used if HubSpot edition supports it. |
Person.source | Contact.hs_analytics_source_data2 | custom_field_required | FUB lead source mapped to HubSpot original source field or custom property FUB_Source__c for full source attribution. |
Person.background | Contact.FUB_Background__c | custom_field_required | FUB background long-text field maps to custom long-text property on HubSpot contact preserving buyer criteria notes. |
Person.website | Contact.website | direct | |
Person.address.street | Contact.address | direct | |
Person.address.city | Contact.city | direct | |
Person.address.state | Contact.state | direct | |
Person.address.postal_code | Contact.zip | direct | |
Person.assigned_user_id | Contact.hubspot_owner_id | transformed | FUB agent ID resolved by email match to HubSpot user. Unmatched agents flagged and assigned to fallback owner; FUB_Agent_ID__c preserves original reference. |
Person.created_at | Contact.original_create_date | custom_field_required | HubSpot sets CreatedDate at migration time. Original FUB created_at preserved as custom datetime field for reporting continuity. |
Person.id | Contact.FUB_Person_ID__c | custom_field_required | FUB internal person ID stored for traceability, deduplication in future delta runs, and audit purposes. |
Company.name | Company.name | direct | |
Company.website | Company.domain | direct | |
Company.phone | Company.phone | direct | |
Company.address.street | Company.address | direct | |
Company.address.city | Company.city | direct | |
Company.address.state | Company.state | direct | |
Company.address.postal_code | Company.zip | direct | |
Company.id | Company.FUB_Company_ID__c | custom_field_required | FUB internal company ID stored for traceability and association verification during migration. |
Transaction.name | Deal.dealname | direct | |
Transaction.amount | Deal.amount | direct | |
Transaction.stage | Deal.dealstage | value_mapping | FUB transaction stage values mapped to HubSpot deal stage pick-list values. Custom stage names in FUB require value-by-value mapping before import. |
Transaction.close_date | Deal.closedate | direct |
What to watch for in a Follow Up Boss to HubSpot migration
The issues we plan around on this pair: limits and data-model gaps that the official import tools leave to you.
Action Plans have no HubSpot equivalent and must be rebuilt manually
Follow Up Boss Action Plans are the core automation engine — they trigger drip email sequences, SMS messages, task assignments, and stage changes when a lead enters or exits a stage.
How we handle it
HubSpot has no direct functional equivalent in its base CRM tier, and even in Sales Hub Professional, the trigger model differs significantly. We export full Action Plan definitions as a structured rebuild reference (step-by-step trigger logic, timing, and actions), but the rebuild itself must be performed by a HubSpot admin or partner using HubSpot Workflows and Sequences after migration completes.
FUB SMS and calling integrations do not carry over to HubSpot
FUB provides integrated two-way texting, per-agent phone numbers, call logging, and call recording as platform-native features included on most plans.
How we handle it
HubSpot's native calling requires a Sales Hub Professional or Enterprise seat with the calling add-on configured separately. Any Twilio-based SMS setup in FUB will not transfer — all SMS routing must be re-established via HubSpot's SMS integrations, Twilio connector, or a third-party tool post-migration. Teams relying heavily on FUB's built-in calling should budget for HubSpot's calling seat cost before committing to migration.
FUB pipeline stages do not map to HubSpot lifecycle_stage automatically
FUB's stage field represents the deal progression for a lead (New Lead, Contacted, Showing, Under Contract, Closed).
How we handle it
HubSpot's lifecycle_stage on a contact represents the buyer's journey from Subscriber through Customer. These are fundamentally different concepts — a contact's HubSpot lifecycle stage does not represent the same thing as a FUB stage. If you want to preserve FUB stage progression in HubSpot, we map it to a custom property (FUB_Stage__c) with the original stage names and transition timestamps. If you prefer to use HubSpot lifecycle stages, we map FUB stages to the closest HubSpot lifecycle values (e.g., FUB 'Contract' maps to HubSpot 'opportunity') but the behavioral history does not carry over in that case.
FUB tags-per-contact model requires custom field handling in HubSpot
FUB supports assigning multiple tags to a single person — a lead can simultaneously carry tags for Lead Source, Property Type, Budget Range, and Agent Assignment.
How we handle it
HubSpot's native contact properties are single-value by default, which means a contact cannot hold multiple tag values in a single field without a custom property. We join FUB tags into a comma-separated HubSpot custom text property, but this prevents native HubSpot filtering by individual tags without additional processing. Teams that rely heavily on FUB tag-based segmentation should plan for post-migration tag re-segmentation in HubSpot using lists and workflows.
FUB MLS and IDX integrations cannot be migrated and must be rebuilt from scratch
FUB's core value proposition for real estate teams is its native integration with MLS feeds, IDX website connectors, and real estate lead aggregators (Zillow, Realtor.com, BoomTown, etc.).
How we handle it
These integrations are authentication-based connections to third-party services, not CRM data objects, so they do not appear in a standard data export. All active lead-source integrations must be reconfigured in HubSpot's App Marketplace or rebuilt via Zapier. We document every active FUB integration during the discovery phase so your team has a complete checklist for rebuilding connections after migration.
How the migration runs
Inventory FUB objects and build the field mapping plan
We connect to your FUB account via API and extract a full data inventory: total person count, company count, transaction count, custom field definitions (type, label, choices for dropdowns), tag list, and active pipeline/stage configuration.
What this step covers
From this inventory we build a field mapping plan covering every standard and custom property. You review and approve the mapping before any data is extracted. We also document all active FUB integrations (MLS, IDX, lead sources) for the rebuild checklist.
Create HubSpot properties and configure the destination schema
Before data moves, your HubSpot admin (or our team) creates the custom properties identified in the mapping plan — custom text fields for FUB background and source, dropdown properties for FUB stage, and number/date fields for FUB custom fields.
What this step covers
We deliver a HubSpot property creation checklist so the schema is ready before the first test import runs. We also identify which HubSpot lifecycle stage values to use or whether a custom field approach is preferred based on your FUB stage complexity.
Run owner resolution and a sample migration with field-level diff
We resolve FUB agent assignments by matching agent email addresses against your HubSpot user list.
What this step covers
Unmatched agents are flagged before migration so your team can invite them to HubSpot or assign a fallback owner. A representative sample — typically 100–500 records spanning contacts, companies, deals, and activity history — migrates to a HubSpot sandbox or test account first. We generate a field-level diff comparing source values against destination values so you can verify stage mapping, tag handling, and owner resolution before the full run commits.
Execute full migration with delta-pickup and audit log
The full data migration runs against your live HubSpot account in dependency order: companies first (for contact lookups), then contacts, then deals associated to contacts, then activity history.
What this step covers
A delta-pickup window — typically 24–48 hours — captures any FUB records modified during the cutover period. Every operation is logged in an audit trail. One-click rollback is available if reconciliation identifies unexpected data divergence. After migration, we deliver an Action Plan export document and an integration rebuild checklist for your HubSpot admin.
Follow Up Boss - Connect
- Map
- Sample
- Migrate
- Verify
- Contacts48,210 / 48,210 Done
- Companies9,134 / 9,134 Done
- Deals6,377 / 11,920 In progress
- Before sample runRestore point 01Restore
- Before full migrationRestore point 02Restore
- After verificationRestore point 03Current
How long it takes, and what drives the quote
FlitStack AI pricing scales with record count, custom field volume, and data-model divergence between the two platforms. FUB databases with fewer than 5,000 contacts and fewer than 20 custom fields land in the lower range. Teams with high tag volume, multi-transaction records per person, or complex Action Plan logic requiring manual rebuild documentation push toward the upper range. The primary cost drivers are (1) total contact and transaction count requiring API pagination under FUB's rate limits, (2) number of custom field types needing HubSpot property creation, and (3) whether tags and sources require value-by-value mapping or can be imported as-is. Every quote is scoped with you; there is no self-serve pricing.
Get a quote for Follow Up Boss to HubSpot →Why teams move from Follow Up Boss to HubSpot
- FUB's tight Zillow ownership creates vendor-lock-in anxiety for real estate teams — especially after Zillow's 2021 iBuying exit and subsequent data-policy shifts that changed how FUB handles lead data. Teams want to consolidate on a platform with no real estate platform dependency and broader operational flexibility.
- FUB's native marketing automation for email campaigns, landing pages, and lead nurturing is materially weaker than HubSpot's integrated marketing hub. Teams frequently layer in Mailchimp or ActiveCampaign alongside FUB, adding cost and creating a fragmented stack that HubSpot can consolidate.
- Real estate teams scaling past five agents often need broader operational tooling — service hub, reporting depth, custom object extensibility — that FUB's real-estate-centric feature set doesn't provide without adding multiple paid integrations. As team size grows, the need for unified customer service, advanced analytics, and flexible data structures becomes critical, and HubSpot's platform delivers these capabilities natively, reducing the reliance on third-party add-ons.
- FUB charges per-seat and per-agent calling add-ons that compound as teams grow. HubSpot's free CRM tier gives teams a starting point without migration lock-in, and teams can migrate gradually rather than paying FUB pricing while rebuilding in HubSpot simultaneously. This cost structure allows teams to spread migration expenses over time, avoiding a large upfront investment while gradually expanding HubSpot usage as the team scales.
- When brokerage operations expand beyond a single CRM use case — combining lead management, back-office service, and marketing — FUB's scope becomes a constraint. HubSpot's platform handles all three functions under one account structure, reducing license overhead and simplifying vendor management. This consolidation allows teams to manage leads, service tickets, and marketing campaigns from a single dashboard, improving coordination and reducing the complexity of managing multiple subscriptions.
Questions, answered
Follow Up Boss to HubSpot migration questions
How long does a Follow Up Boss to HubSpot migration take?
Most FUB-to-HubSpot migrations complete in 24–48 hours of clock time for databases under 10,000 records once the field mapping is approved. Larger setups with 50,000+ records or complex multi-tag and custom-field configurations extend to 3–7 days. The longest phase is typically property creation and mapping review in HubSpot before data extraction begins. During this phase we also run owner resolution and prepare the delta-pickup window to capture any in-flight changes that occur while the initial migration runs.
Will my Follow Up Boss Action Plans migrate to HubSpot Workflows?
No. FlitStack AI migrates data and schema only — Action Plans, automated follow-up sequences, and drip campaign logic do not transfer. HubSpot Workflows and Sequences are the equivalent mechanisms but use a different trigger model. We export your Action Plan definitions as a structured rebuild reference with step-by-step trigger logic and timing so your HubSpot admin can recreate the automation sequence after migration.
What happens to my FUB transaction data in HubSpot?
FUB transactions (deals with amount, stage, and close date) migrate as HubSpot Deals associated to the corresponding contact. Multiple transactions per person in FUB create multiple HubSpot Deals. FUB transaction stage names are mapped to HubSpot deal stage pick-list values — if FUB uses custom stage names beyond New/Contacted/Showing/Contract/Closed, a value-by-value mapping is required before import to avoid import errors.
Can I migrate Follow Up Boss custom fields to HubSpot?
Yes. FUB custom fields (text, date, number, and dropdown types) map to HubSpot custom contact and deal properties. Dropdown fields require value-by-value mapping of FUB choices to HubSpot option labels. Text, number, and date fields map directly once the HubSpot property is created. We identify all custom fields during the discovery phase and include them in the property creation checklist delivered before migration runs.
Does the migration affect my FUB account during the cutover?
No. FlitStack AI uses scoped read access on your FUB account — your team continues working in FUB throughout the migration. A delta-pickup window (24–48 hours after the full migration run) captures any contacts, transactions, or activity history created or modified in FUB during the cutover window. At go-live your HubSpot instance reflects FUB's final state including any changes made during the transition period.
What happens to my FUB agent assignments and user ownership?
FUB agent assignments on people and transactions are resolved by matching the agent's FUB email address to their HubSpot user email. We run an owner resolution pass before migration: matched agents link to the correct HubSpot owner; any unmatched agents are flagged for your team to resolve. The original FUB agent ID is preserved as a custom property (FUB_Agent_ID__c) on each record for post-migration reassignment if needed.
Will my MLS, IDX, and lead-source integrations transfer to HubSpot?
No. FUB's integrations with MLS feeds, IDX websites, and real estate lead aggregators (Zillow, Realtor.com, etc.) are authentication-based third-party connections that exist outside the CRM data model. They do not appear in a standard data export and cannot be migrated. We document every active FUB integration during the discovery phase so your team has a complete rebuild checklist for HubSpot App Marketplace connections and Zapier setups.
How are FUB tags handled in HubSpot if a contact has multiple tags?
FUB supports multiple tags per contact; HubSpot's native contact properties are single-value by default. We join all FUB tags into a comma-separated custom text property on the HubSpot contact so no tag data is lost. Teams that rely heavily on FUB tag-based filtering should plan for post-migration tag re-segmentation in HubSpot using Lists and Workflows to replicate FUB's multi-tag segmentation logic.
Related migrations
HubSpot implementation
Set up HubSpot and migrate into it as one engagement.
See the service → Nutshell to HubSpotMapping · history · rollbackHousecall Pro to HubSpotMapping · history · rollbackConvertkit to HubSpotMapping · history · rollbackVinsolutions to HubSpotMapping · history · rollbackBitrix24 to HubSpotMapping · history · rollbackfolk to HubSpotMapping · history · rollback Follow Up Boss to HighLevelMapping · history · rollbackSources: official documentation
- Format import files — HubSpot Knowledge Base
- Create and edit custom objects — HubSpot Knowledge Base
- Import objects programmatically — HubSpot Knowledge Base
- Understand property field types in HubSpot
- Associate records on CRM objects — HubSpot Knowledge Base
- Integration throughput and limits — HubSpot Knowledge Base
- HubSpot Cloud Infrastructure and Data Hosting FAQ
Get a quote
Moving from Follow Up Boss to HubSpot?
Tell us roughly how many records and objects you have. We scope the mapping and the HubSpot setup with you, then send a quote.
Get a quote