Follow Up Boss to HighLevel migration
Moving from Follow Up Boss to HighLevel consolidates your CRM, marketing automation, and client management into one platform. FlitStack AI maps every contact, deal, company, and custom field from Follow Up Boss into HighLevel's Opportunities and Contacts — preserving your pipeline stage history and original create dates so your new HighLevel reporting reflects the full state of your real estate business from day one.
FlitStack AI migrates contacts, companies, opportunities, pipeline stages and tags from Follow Up Boss to HighLevel, 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: 48–72 hours for under 25,000 records.

What moves from Follow Up Boss to HighLevel?
Follow Up Boss structures real estate lead data around People (contacts), Deals, and Stages within a lead-centric pipeline model.
Read the full summary
HighLevel uses a similar Contacts + Opportunities structure but adds Pipelines with multiple stages, a built-in Workflows engine, and an agency-friendly sub-account architecture. The migration carries all standard records (People, Companies, Deals, Stages, Tags, Tasks, Notes) into their HighLevel equivalents, while FlitStack flags Action Plans, Smart List filters, and integrated lead-source configurations for manual rebuild in HighLevel's Workflow builder. We use Follow Up Boss's API export (with CSV backup validation) and HighLevel's bulk contact import endpoint with custom field mapping. During the migration, we preserve create timestamps, owner assignments, and stage transition history so reporting continuity is maintained. The main structural difference teams encounter post-migration is that Follow Up Boss's real-estate-native lead scoring and lead-source attribution logic requires recreation using HighLevel's Tags and custom fields, and automation sequences must be manually rebuilt using the exported Action Plan definitions.
Person / People → Contact
Follow Up Boss People records map directly to HighLevel Contacts.
How it maps
Name, email, phone, address, and all standard fields transfer as-is. Primary company link in Follow Up Boss attaches to the corresponding HighLevel Company record. Owner/User assignment resolves by email match against HighLevel users.
Company → Company
Follow Up Boss Companies map 1:1 to HighLevel Companies.
How it maps
Company name, domain, address, and industry fields transfer directly. Parent/child company hierarchy in Follow Up Boss maps to HighLevel's Company hierarchy field. Multi-company associations on a Person collapse to primary Company with additional associations stored as Tags.
Deal → Opportunity
Follow Up Boss Deals map to HighLevel Opportunities.
How it maps
Deal name, value/amount, expected close date, and assigned Person link transfer directly. The destination Opportunity is associated with the mapped Contact. Note that a single Follow Up Boss Deal maps to one Opportunity — deals without a Contact association link to a placeholder in HighLevel.
Stage / Status → Pipeline Stage
Follow Up Boss stages (Lead, Active, Pending, Sold, Dead) become named Stages within a HighLevel Pipeline.
How it maps
Teams running one pipeline map to one Pipeline in HighLevel; teams with separate buyer/seller flows create multiple Pipelines. Stage transition timestamps in Follow Up Boss are preserved as custom datetime fields in HighLevel for reporting continuity.
Tag → Tag
Tags migrate directly — Follow Up Boss Tags appear as HighLevel Tags on the Contact record.
How it maps
Tag names and tag assignments per Person/Deal transfer as-is, preserving the exact spelling and case. HighLevel's tag model supports unlimited tags per contact, matching Follow Up Boss behavior. Multi-value tags on a single record are split into individual Tag entries in HighLevel. Tag metadata such as color coding or creation timestamps does not transfer as HighLevel Tags lack these properties.
Action Plan → Workflow (manual rebuild)
Follow Up Boss Action Plans do not have a direct equivalent in HighLevel.
How it maps
FlitStack exports Action Plan definitions (triggers, steps, delay logic, message templates) as a structured JSON reference document. Your team rebuilds these in HighLevel's Workflow builder — we provide the exported definitions and a mapping guide so no step is forgotten.
- PersonContact1:1
- CompanyCompany1:1
- DealOpportunity1:1
- StagePipeline Stagetransformed
- TagTag1:1
- Action PlanWorkflowtransformed
+ 8 more in the mapping below
How Follow Up Boss and HighLevel 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 | HighLevel |
|---|---|---|
| Primary CRM object | Follow Up Boss uses People as the central record; Deals attach to People via Stage/Status | HighLevel uses Contacts as the central record; Opportunities attach via pipeline stages |
| Pipeline model | Follow Up Boss stages (Lead, Active, Pending, Sold, Dead) are per-lead status labels | HighLevel uses named Pipelines with customizable Stage rows; one Contact can have multiple Opportunities |
| Automation engine | Follow Up Boss Action Plans are trigger-based sequences; stored as XML/JSON config in account | HighLevel Workflows are visual flowchart automations; triggers, conditions, and actions built in the UI |
| Lead attribution | Follow Up Boss Smart Lists filter by source, stage transition time, and days-since-contact | HighLevel uses Tags and custom filters; attribution logic rebuilt using Tags + Workflow triggers |
| Reporting depth | Follow Up Boss reports focus on agent response time, lead-to-appointment rates, and deal velocity | HighLevel reporting covers pipeline value, conversion rates, and workflow performance across multiple sub-accounts |
| Contact limit model | Follow Up Boss pricing tiers by user count; contact volume does not trigger billing | HighLevel Starter at $97/mo includes unlimited contacts; cost driven by sub-account count and usage add-ons |
| Phone/telephony | Follow Up Boss integrates with third-party phone providers; lead phone numbers stored as standard text fields | HighLevel includes built-in LC Phone System; phone numbers can be provisioned directly within the platform |
Follow Up Boss to HighLevel field mapping
The 30 most-used fields of 45 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.
-
firstNamePersonFirst NameContact -
lastNamePersonLast NameContact -
emailPersonEmailContact -
phonePersonPhoneContact -
cellPhonePersonMobileContact
| Follow Up Boss field | HighLevel field | Mapping | Note |
|---|---|---|---|
Person.firstName | Contact.First Name | direct | |
Person.lastName | Contact.Last Name | direct | |
Person.email | Contact.Email | direct | |
Person.phone | Contact.Phone | direct | |
Person.cellPhone | Contact.Mobile | direct | |
Person.address | Contact.Address | direct | |
Person.city | Contact.City | direct | |
Person.state | Contact.State | direct | |
Person.zip | Contact.Postal Code | direct | |
Person.source | Contact.Lead Source Tag | transformed | Lead source value from Follow Up Boss becomes a Tag in HighLevel (e.g., tag: 'Source: Zillow') and optionally a custom field for reporting. |
Person.stage | Opportunity.Pipeline Stage | value_mapping | Follow Up Boss stage labels map to HighLevel pipeline stage names. Each stage value is mapped individually in the migration plan. |
Person.assignedTo | Contact.Assigned To (user) | transformed | Owner/User resolved by email match against HighLevel users. Unmatched owners flagged for assignment to a fallback user. |
Person.createdAt | Contact.Created At | direct | |
Person.updatedAt | Contact.Updated At | direct | |
Person.lastContactedAt | Contact.Last Activity Date | direct | |
Person.tags | Contact.Tags | direct | Tags transfer as-is. Multiple tags on one Person create multiple Tag entries in HighLevel. |
Person.background | Contact.Background (custom field) | custom_field_required | Follow Up Boss Background notes field migrates to a HighLevel custom text field. |
Person.timeframeToMove | Contact.Timeframe_to_Move__c (custom) | custom_field_required | Timeframe to Move (Follow Up Boss) becomes a custom date or text field in HighLevel preserving the range value and set date. |
Person.zillowLeadId | Contact.Source_System_ID__c (custom) | custom_field_required | Follow Up Boss internal ID stored for traceability and delta-run de-duplication. |
Company.name | Company.Name | direct | |
Company.domain | Company.Website | direct | |
Company.address | Company.Address | direct | |
Company.phone | Company.Phone | direct | |
Company.industry | Company.Industry | direct | |
Deal.name | Opportunity.Name | direct | |
Deal.value | Opportunity.Value | direct | |
Deal.stage | Opportunity.Stage | value_mapping | Deal stage maps to the corresponding HighLevel Pipeline Stage. Value mapping defined per stage name in the migration plan. |
Deal.expectedCloseDate | Opportunity.Close Date | direct | |
Deal.createdAt | Opportunity.Created At | direct | |
Deal.ownerId | Opportunity.Assigned To | transformed | Owner resolved by email match to HighLevel user. Unmatched owners flagged before migration. |
What to watch for in a Follow Up Boss to HighLevel 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 native equivalent in HighLevel — they must be rebuilt manually
Follow Up Boss Action Plans are trigger-based sequences (email, SMS, task creation, stage change) stored as account-level configuration.
How we handle it
HighLevel has no Action Plan import tool — these automations do not carry over in a data migration. FlitStack exports your Action Plan definitions as a structured JSON reference document listing every trigger, step, delay, and message template. Your team rebuilds them in HighLevel's Workflow builder using that reference. This is the most time-intensive part of a Follow Up Boss migration and should be scoped separately from the data migration.
Smart List filter logic requires manual translation to Tags and custom field filters
Follow Up Boss Smart Lists let you segment leads by stage transition timestamps, days since last contact, lead source, and property type interest.
How we handle it
HighLevel's filtering model uses Tags on Contacts plus custom field conditions on Opportunities — there is no Smart List object. FlitStack exports Smart List definitions and maps the filter logic to a recommended HighLevel tag schema and Opportunity custom field setup. Because Smart Lists are query-based and HighLevel tags are label-based, the segmentation behavior will differ: Smart List real-time updates become manual Tag management in HighLevel.
Follow Up Boss API rate limits constrain export window and require sliding-window throttling
Follow Up Boss enforces API rate limits based on a sliding 10-second window (default limit: 200 requests per 10 seconds per API key context).
How we handle it
Large datasets (50,000+ contacts) require multiple API key rotations or a request increase approval from Follow Up Boss support. FlitStack manages this by implementing a sliding-window throttler that stays within the limit, with automatic retry on 429 responses and a Retry-After header follower. If your account requires a rate limit increase, we flag this during the planning phase and can assist with the outreach to Follow Up Boss support.
HighLevel has no native Zillow integration — imported leads lose their Zillow attribution context
Follow Up Boss has deep Zillow integration: leads imported from Zillow carry attribution metadata (Zillow agent ID, property ID, lead type) that Follow Up Boss displays in the lead profile.
How we handle it
HighLevel does not have a native Zillow integration. FlitStack preserves Zillow attribution data as custom fields on the Contact record, but HighLevel's native UI will not surface this context automatically. If your team relies on Zillow attribution for agent performance tracking or lead-source ROI, you will need to use HighLevel's Tags and custom fields to recreate that reporting layer.
Follow Up Boss Zillow data-sharing concerns may affect how quickly you need to migrate
After Zillow's acquisition of Follow Up Boss in November 2023, real estate professionals have raised concerns on Reddit and Facebook groups about what happens to their lead data under Zillow's data-sharing policies.
How we handle it
Follow Up Boss's Terms of Service and privacy policy now reference Zillow data-sharing arrangements. If your brokerage has strict data-sovereignty requirements or client confidentiality obligations, this is a compliance consideration. FlitStack migration runs use scoped read access — we read your data to migrate it but do not retain a copy after the migration completes. You can request a data-deletion confirmation from Follow Up Boss after export if needed.
How the migration runs
Audit Follow Up Boss data and map Action Plan + Smart List definitions
Before any data moves, FlitStack runs a full audit of your Follow Up Boss account: contact volume, deal count, company count, tag inventory, custom field list, and stage configuration.
What this step covers
We simultaneously document your Action Plan definitions and Smart List filter logic. This gives us the exact record counts and schema complexity needed to confirm pricing and timeline, and it produces the Action Plan JSON export and Smart List mapping reference that your team uses for the manual automation rebuild.
Create HighLevel custom fields, pipelines, and stage setup
HighLevel's custom fields and pipeline stages must exist before data lands, otherwise the bulk import will reject unmapped values.
What this step covers
FlitStack generates a HighLevel setup plan based on your Follow Up Boss custom field list and stage configuration: we specify the exact custom field names, types, and dropdown choices to create, plus the pipeline and stage names to set up in HighLevel. Your team creates these in HighLevel before the test migration runs. We provide step-by-step instructions for each setup action.
Run sample migration with field-level diff on 100–500 records
A representative slice of your Follow Up Boss data (contacts, companies, deals, tasks, notes) migrates first.
What this step covers
FlitStack generates a field-level diff report comparing source values to destination values for every mapped field. You verify that stage labels map correctly, owner resolution works for your team, custom field values transfer completely, and Tags attach to the right records. The diff report is your sign-off gate — no full migration runs until you confirm the sample results.
Full migration run with delta-pickup window
Once the sample is approved, FlitStack runs the full migration against your HighLevel account.
What this step covers
The migration runs against live data; your team continues working in Follow Up Boss throughout. A delta-pickup window (24–48 hours) after the initial run captures any records created or modified in Follow Up Boss during the migration window so HighLevel reflects your final state at cutover. FlitStack's audit log records every operation — record count, source ID, destination ID, and field values for each migrated row.
Post-migration reconciliation and rollback validation
After the delta pickup closes, FlitStack generates a reconciliation report comparing Follow Up Boss record counts and field values against HighLevel.
What this step covers
You verify key metrics: total contacts, total deals, pipeline stage distribution, owner assignment rate, and custom field completeness. If reconciliation reveals discrepancies, one-click rollback reverts the HighLevel import and we re-run. We also deliver the Action Plan JSON export and Smart List mapping guide to your team for the automation rebuild phase.
Follow Up Boss
HighLevel - 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
A quote scales with record count, custom field volume, and pipeline complexity on the destination side. Follow Up Boss setups with >15 custom fields or multiple deal stages fall into the upper range because field-level mapping requires type-aware translation (dropdown values, date formats, numeric ranges). Teams migrating from Follow Up Boss Enterprise tiers with integrated lead-source configurations pay more because Smart List filter logic must be translated into HighLevel Tag-and-filter equivalents. The delta-pickup window (24–48 hours) is included in all standard migrations; expedited timelines add a premium. Every quote is scoped with you; there is no self-serve pricing.
Get a quote for Follow Up Boss to HighLevel →Why teams move from Follow Up Boss to HighLevel
- Follow Up Boss was acquired by Zillow Group in November 2023 for up to $500 million. Reddit threads in r/realtors and r/gohighlevel show agents concerned about Zillow gaining access to their proprietary lead data, conversations, and contact histories — with fears that data could eventually flow to Zillow Premier Agents. Migrating to HighLevel lets teams maintain full control of their lead database independent of any Zillow data-sharing arrangement.
- HighLevel's all-in-one platform includes funnels, landing pages, email/SMS marketing, reputation management, and a white-label option — features that Follow Up Boss charges extra for through third-party integrations. Real estate teams generating their own leads report that consolidating onto HighLevel eliminates $50–$200/month in addon costs while gaining native automation capabilities.
- HighLevel's flat-rate pricing model ($97–$497/month) covers unlimited contacts, whereas Follow Up Boss pricing scales by user count and third-party integrations. Agents running high lead volumes report that HighLevel's cost predictability and feature bundling delivers better ROI than paying per-seat plus per-feature in Follow Up Boss.
- HighLevel supports white-labeling and sub-account management natively — features designed for agencies managing multiple client CRM instances. Follow Up Boss lacks a native white-label model, forcing agencies to operate under Follow Up Boss branding or manage client data in separate paid accounts.
Questions, answered
Follow Up Boss to HighLevel migration questions
How long does a Follow Up Boss to HighLevel migration take?
Most Follow Up Boss to HighLevel migrations complete in 48–72 hours of clock time for accounts with under 25,000 records. Larger accounts with 200,000+ records or extensive custom fields extend to 5–8 days. The longest planning step is mapping your Follow Up Boss Action Plans to HighLevel Workflows — this manual rebuild runs parallel to the data migration and is scoped separately. FlitStack sequences the data migration so your team can start the automation rebuild immediately after the sample migration is approved, rather than waiting for the full data run to finish.
Will my Follow Up Boss Action Plans migrate to HighLevel Workflows?
No. FlitStack AI migrates data and schema only — Action Plans, Smart Lists, and automation sequences do not transfer automatically. Follow Up Boss Action Plans use a trigger-step-delay model that has no direct import path into HighLevel's Workflow builder. We export your Action Plan definitions as a structured JSON reference document that lists every trigger, step, delay, and message template. Your team rebuilds these in HighLevel's Workflow builder using that reference. This is the most time-intensive part of a Follow Up Boss migration and should be scoped as a separate project phase from the data migration.
What happens to Follow Up Boss Smart Lists in HighLevel?
Follow Up Boss Smart Lists filter by stage transition time, days since last contact, lead source, and property type — behavior that requires a manual recreation in HighLevel. FlitStack exports your Smart List definitions and maps their filter logic to a HighLevel tag schema and Opportunity custom field structure. Because HighLevel uses Tags rather than query-based segments, the segmentation approach differs: Smart Lists update in real-time; HighLevel Tags reflect the state at the time of tagging. We provide a tag-naming convention guide and a mapping table that translates each Smart List criterion to the recommended HighLevel equivalent.
Can I migrate Follow Up Boss custom fields to HighLevel?
Yes. Follow Up Boss custom fields (text, number, date, dropdown) map to HighLevel custom fields on Contacts or Opportunities. Text, number, and date fields migrate as their direct HighLevel equivalents. Dropdown custom fields require value-by-value mapping since Follow Up Boss choice labels may differ from your HighLevel choice labels. FlitStack creates the destination custom fields before data lands and maps each value explicitly in the migration run. Recurring date fields (e.g., birthdays, anniversaries) are preserved with their recurrence flag as a custom text note in HighLevel.
What happens to my Follow Up Boss lead source and Zillow attribution data?
Follow Up Boss tracks lead source (Zillow, Realtor.com, website, etc.) as a system field. HighLevel has no native lead-source field. FlitStack preserves the full source attribution by creating a Tag on each Contact (e.g., tag: 'Source: Zillow') and an optional custom field for reporting. Zillow-specific attribution metadata (agent ID, property ID, lead type) is stored as custom fields on the Contact record since HighLevel has no native Zillow integration. If your team relies on Zillow attribution for agent performance tracking, you will need to use HighLevel's Tags and reporting to recreate that layer.
Does the migration affect my Follow Up Boss account during cutover?
No. FlitStack AI uses scoped read access on Follow Up Boss — your team keeps working in Follow Up Boss throughout the migration window. We export data via the Follow Up Boss API with a sliding-window rate limiter to avoid hitting API limits. A delta-pickup window (24–48 hours) after the initial migration run captures any contacts, deals, or tasks created or modified in Follow Up Boss during the cutover, so HighLevel reflects your final state at go-live. No records are deleted or modified in Follow Up Boss at any point during the process.
What happens to Follow Up Boss Stages and Deal pipeline data?
Follow Up Boss Stages (Lead, Active, Pending, Sold, Dead) map to named Pipeline Stages within a HighLevel Pipeline. Teams with a single deal flow map to one Pipeline; teams with separate buyer and seller flows create multiple Pipelines in HighLevel. Stage transition timestamps in Follow Up Boss are preserved as custom datetime fields on the Opportunity in HighLevel for reporting continuity. The deal value, expected close date, and assigned Contact all transfer directly — a Follow Up Boss Deal becomes a HighLevel Opportunity associated with the mapped Contact.
Related migrations
Sources: official documentation
- Rename standard objects in your CRM — HighLevel Support
- Bulk import Companies using a CSV file — HighLevel Support
- Association limits — HighLevel Support
- Custom Objects in all plans + higher limit — HighLevel Support
- Unique field support for Custom Objects — HighLevel Support
- HighLevel platform limits — HighLevel Support
- Importing Contacts and Opportunities via CSV — HighLevel Support
Get a quote
Moving from Follow Up Boss to HighLevel?
Tell us roughly how many records and objects you have. We scope the mapping and the HighLevel setup with you, then send a quote.
Get a quote