Migrate your Follow Up Boss data
Lead-centric real estate CRM that aggregates inbound leads from any source into a single inbox, then automates follow-up through Action Plans and smart tasks. Built for agents and teams who prioritise speed-to-contact over pipeline complexity.
In its favor
Why people choose Follow Up Boss
The signal that keeps Follow Up Boss on the shortlist. Sourced from G2, Capterra, and customer scoping calls.
Customers cite the rapid lead response as the primary draw—Follow Up Boss centralises all inbound leads into one inbox so agents can contact new prospects within minutes rather than juggling multiple provider portals.
The platform is praised for an intuitive interface that requires minimal training; real estate agents with limited technical experience can navigate Action Plans, Tasks, and Smart Lists without a dedicated admin.
Integration coverage with major real estate lead providers (Zillow, Realtor.com, BoomTown, etc.) is frequently mentioned as a differentiator over simpler CRMs, giving teams a single view across all advertising channels.
Action Plans enable automated drip email and SMS sequences that run without manual intervention, helping teams maintain consistent follow-up cadence at scale without hiring additional staff.
Customers appreciate the accountability features—daily task queues and team performance visibility—because they reduce the guesswork of who is following up with which lead.
Several customers note that Follow Up Boss has limited customisation compared to broader CRM platforms; there is no support for complex custom objects, conditional logic beyond Action Plans, or bespoke pipeline views.
The per-user pricing model becomes expensive for large teams, especially when comparing to flat-rate or unlimited-seat alternatives; customers with many part-time agents or transaction coordinators feel the seat cost adds up quickly.
Search and filter functionality is described as clunky—saved groups with filter presets are not available, making it tedious to toggle between different lead segments repeatedly.
A subset of reviews cite slow or inconsistent customer support during busy periods, with some customers reporting multi-day waits for non-urgent tickets.
Users moving to platforms like GoHighLevel or HubSpot cite wanting deeper SMS automation, more flexible pipelines, and built-in VoIP calling rather than relying on third-party integrations.
Reasons to switch
Why people leave Follow Up Boss
The recurring reasons buyers give for replacing Follow Up Boss. Presented as facts, not knocks.
Platform scorecard
Strengths, weaknesses, and where Follow Up Boss fits
Grades across six dimensions, plus a SWOT-style view of where the platform shines and where it falls short.
SWOT — strengths, weaknesses, and use-case fit
Strengths
Weaknesses
Where it works
Where it struggles
Pricing tiers
Follow Up Boss pricing overview
Follow Up Boss charges per user per month, starting at $69. Additional team members cost $17/month each. There are no long-term contracts or setup fees, and a 14-day free trial is available. AI features appear to be available on higher tiers or as an add-on.
Starter
Tier 1 of 3
$69/user/month
What's included
Need help selecting your CRM?
Book a free 30 minute consultationPricing is informational. FlitStack AI does not bill on Follow Up Boss's schedule — see our quote-based pricing →
What gets migrated
Follow Up Boss object support
Object-by-object support for Follow Up Boss migrations. Per-pair details surface during scoping.
People (Contacts)
Fully supportedPeople is the core object in Follow Up Boss. Every lead and client is a Person record with name, email, phone, stage, source, assigned user, tags, and a Background note. We migrate Person records 1:1 via API or CSV export, preserving all standard fields.
Custom Fields
Fully supportedFollow Up Boss supports text, date, number, and dropdown custom fields. The API exposes these via /customFields using the field name. We read the field definitions first, then map values by name so dropdown choices and recurring dates are handled correctly at import.
Action Plans
Mapping requiredAction Plans are automated drip sequences tied to a Person. They are not a standalone exportable object—they live as metadata on the Person. We export Action Plan names as a tag or custom property so the destination can rebuild equivalent automations.
Tasks
Mapping requiredFollow Up Boss generates tasks automatically from Action Plans and manually by users. Tasks include a due date, assignee, and status. We preserve task text and due dates as part of the event log; assignee mapping requires a user-to-user lookup between source and destination systems.
Tags
Fully supportedTags are a flat label system applied to People. They carry lead source, lead type, and workflow context. We export tags as a comma-separated list and map them to equivalent labels in the destination CRM.
Stages (Lead Lifecycle)
Fully supportedStages represent where a lead is in the lifecycle (e.g. New, Contacted, Qualified, Contract). The stage is a property on the Person record. We preserve the current stage as a field value and optionally replay stage-change events from the activity timeline.
Users (Team Members)
Mapping requiredUsers own records, tasks, and Action Plans. We map source Users to destination Users by email or name. If the destination has fewer seats, we route orphaned records to a default owner and flag this for the customer before migration.
Events / Activity Timeline
Mapping requiredThe event log records every email sent, call logged, note added, and stage change. Events are time-stamped and attributed to a User. We replay the full event log as a chronological activity feed in the destination, though some platforms collapse email events into a single thread.
Background Notes
Fully supportedThe Background field holds high-priority notes pinned to the top of a Person record (e.g. 'Pre-qual for 300k', 'On vacation until October'). We migrate this as a long-text custom field to preserve its prominence in the destination.
Sources
Mapping requiredSources track where a lead originated (website form, Zillow, Realtor.com, etc.). Source is a property on the Person record. We preserve the source string and map it to an equivalent source or tag in the destination.
| Object | Support | Notes |
|---|---|---|
| People (Contacts) | Fully supported | People is the core object in Follow Up Boss. Every lead and client is a Person record with name, email, phone, stage, source, assigned user, tags, and a Background note. We migrate Person records 1:1 via API or CSV export, preserving all standard fields. |
| Custom Fields | Fully supported | Follow Up Boss supports text, date, number, and dropdown custom fields. The API exposes these via /customFields using the field name. We read the field definitions first, then map values by name so dropdown choices and recurring dates are handled correctly at import. |
| Action Plans | Mapping required | Action Plans are automated drip sequences tied to a Person. They are not a standalone exportable object—they live as metadata on the Person. We export Action Plan names as a tag or custom property so the destination can rebuild equivalent automations. |
| Tasks | Mapping required | Follow Up Boss generates tasks automatically from Action Plans and manually by users. Tasks include a due date, assignee, and status. We preserve task text and due dates as part of the event log; assignee mapping requires a user-to-user lookup between source and destination systems. |
| Tags | Fully supported | Tags are a flat label system applied to People. They carry lead source, lead type, and workflow context. We export tags as a comma-separated list and map them to equivalent labels in the destination CRM. |
| Stages (Lead Lifecycle) | Fully supported | Stages represent where a lead is in the lifecycle (e.g. New, Contacted, Qualified, Contract). The stage is a property on the Person record. We preserve the current stage as a field value and optionally replay stage-change events from the activity timeline. |
| Users (Team Members) | Mapping required | Users own records, tasks, and Action Plans. We map source Users to destination Users by email or name. If the destination has fewer seats, we route orphaned records to a default owner and flag this for the customer before migration. |
| Events / Activity Timeline | Mapping required | The event log records every email sent, call logged, note added, and stage change. Events are time-stamped and attributed to a User. We replay the full event log as a chronological activity feed in the destination, though some platforms collapse email events into a single thread. |
| Background Notes | Fully supported | The Background field holds high-priority notes pinned to the top of a Person record (e.g. 'Pre-qual for 300k', 'On vacation until October'). We migrate this as a long-text custom field to preserve its prominence in the destination. |
| Sources | Mapping required | Sources track where a lead originated (website form, Zillow, Realtor.com, etc.). Source is a property on the Person record. We preserve the source string and map it to an equivalent source or tag in the destination. |
Gotchas
What to watch for in Follow Up Boss migrations
Issues we've hit on past Follow Up Boss migrations, tagged by severity. FlitStack AI handles every one — surfacing them up front because buyer engineering teams want to know.
API rate limits restrict bulk migration throughput
Action Plans are not a standalone exportable object
CSV export from the UI excludes unexposed columns unless explicitly requested
Dropdown custom field choices are locked once data exists in them
| Severity | Issue |
|---|---|
| Medium | API rate limits restrict bulk migration throughput |
| Medium | Action Plans are not a standalone exportable object |
| Low | CSV export from the UI excludes unexposed columns unless explicitly requested |
| Low | Dropdown custom field choices are locked once data exists in them |
Leaving Follow Up Boss?
Where Follow Up Boss customers move next
12 destinations Follow Up Boss can migrate to.
How a Follow Up Boss migration works
Four steps, Follow Up Boss-specific
Connect
API key via HTTP Basic Authentication over HTTPS. Each Follow Up Boss user has a unique API Key available from Admin → API; the key is sent as the username with a blank password. into Follow Up Boss. Scopes limited to read-only on the data we move.
Map
We translate Follow Up Boss-specific structures (custom fields, objects, value lists) to the destination's model.
Sample
Test with a 50–200 record subset to validate Follow Up Boss quirks before production.
Migrate
Full migration with Follow Up Boss rate-limit handling. Rollback available throughout.
FAQ
Follow Up Boss migration FAQ
Answers to the questions buyers ask most during Follow Up Boss migration scoping. Not seeing yours? Book a call.
Can't find your answer?
Walk through your Follow Up Boss migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationReady when you are
Migrate Follow Up Boss.
Without the rebuild.
Free scoping call with a migration engineer. Tell us about your Follow Up Boss setup and destination — written quote back within a business day.