CRM migration
Field-level mapping, validation, and rollback between Follow Up Boss and Freshsales. We move data and schema; workflows are rebuilt natively in Freshsales.
Follow Up Boss
Source
Freshsales
Destination
Compatibility
11 of 12
objects map 1:1 between Follow Up Boss and Freshsales.
Complexity
BStandard
Timeline
48–72 hours
Overview
Follow Up Boss and Freshsales both model contacts, companies, and deals — but the underlying data structures diverge significantly. Follow Up Boss stores everything under a unified 'People' object with stage tags, action plans, and real-estate-specific fields like Lender and Source. Freshsales splits contacts into Lead and Contact objects with a separate Account object for companies, and uses Lifecycle Stages (Pro+ plans) to track prospect progression. The migration carries over all person records, company records, deals, tags, notes, call logs, and custom fields via the Follow Up Boss API. Action Plans — Follow Up Boss's automated workflow engine — cannot migrate; we export their definitions as a rebuild reference for Freshsales Workflows and Sales Sequences. Freshsales's Freddy AI contact scoring (Pro and Enterprise plans) requires a Freshsales-native scoring model and does not import from Follow Up Boss lead scores. During extraction we preserve original creation timestamps, tag assignments, and owner email references in custom fields on the Freshsales record to maintain audit continuity. Custom fields (text, date, number, dropdown) are recreated on the corresponding Freshsales objects, with pick-list values mapped value‑by‑value to avoid mismatches. Companies become Account records linked via AccountId, handling multi‑contact relationships through Account Contact Relationships. Call logs convert into Freshsales Sales Activities (or Tasks on Growth plans), retaining date, duration, and direction. A sample validation run, delta‑pickup, and rollback plan safeguard data integrity.
Every standard and custom field arrives verified.
AI proposes the map; you confirm before any record moves.
Parent–child, lookups, and ownership stay linked.
Calls, emails, meetings — with original timestamps.
Documents, uploads, and inline notes move with the record.
Why teams make this switch
Leaving
What's pushing teams away
Choosing
What's pulling them in
Object mapping
Each row shows how a Follow Up Boss object lands in Freshsales, including any object-level transformations, lookup resolution, or schema-design dependencies.
Typical mapping — final map is confirmed during the sample migration step.
Follow Up Boss
People
Freshsales
Lead / Contact
1:manyFollow Up Boss stores all contacts in a single 'People' object regardless of lifecycle stage. We split by source stage value: contacts marked as 'Client' or 'Closed' route to Freshsales Contact; all others route to Freshsales Lead. The split preserves the original stage tag as a Lifecycle Stage value on the destination record.
Follow Up Boss
People.stage
Freshsales
Lifecycle Stage (Contact) / Lead Status
1:1Follow Up Boss stage tags (e.g., New Lead, Contacted, Showing, Under Contract, Closed) have no direct Freshsales equivalent on the Contact object. On Pro+ plans, we create a custom Lifecycle_Stage__c pick-list field and map each Follow Up Boss stage to the nearest Freshsales lifecycle value. Lower-tier plans map to the Lead Status pick-list.
Follow Up Boss
Company
Freshsales
Account
1:1Follow Up Boss company records map 1:1 to Freshsales Account records. Company name, website, address, and phone fields migrate directly. Multi-contact companies in Follow Up Boss (N:1 or N:N relationships) collapse to the primary AccountId on each contact with secondary relationships stored as Account Contact Relationships.
Follow Up Boss
Deal
Freshsales
Deal
1:1Follow Up Boss deals map directly to Freshsales Deals. Each deal carries its pipeline name, stage value, deal value, close date, and assigned agent. If Follow Up Boss uses multiple pipelines, we create multiple Freshsales deal stages within a single pipeline (or multiple pipelines on Pro+ plans with territory management).
Follow Up Boss
Tag
Freshsales
Tag
1:1Follow Up Boss tags migrate as Freshsales Tags. Tags are preserved on both Lead/Contact and Deal records. Freshsales supports tag-based filtering and reporting. Note that tag-based segmentation in Follow Up Boss may require Freshsales Smart Lists or custom filters for equivalent reporting.
Follow Up Boss
Note / Background
Freshsales
Note
1:1Follow Up Boss notes and Background fields (the 'most important notes' section per contact) migrate as Freshsales Notes attached to the corresponding Lead or Contact record. Original timestamps and author attribution preserved. Rich-text formatting in Follow Up Boss notes converts to plain text for Freshsales compatibility.
Follow Up Boss
Call Log
Freshsales
Sales Activity / Task
1:1Follow Up Boss call logs with date/time, duration, and outcome notes migrate as Freshsales Sales Activities (on Pro+ plans with Custom Sales Activities enabled) or as Tasks on the contact record. Call direction (inbound/outbound) mapped to Freshsales activity type. Original timestamps preserved; call recordings are not stored in Follow Up Boss and thus do not transfer.
Follow Up Boss
Action Plan
Freshsales
Workflow / Sales Sequence
1:1Follow Up Boss Action Plans — automated sequences of emails, texts, and tasks triggered by stage changes — cannot be imported into Freshsales Workflows. We export Action Plan definitions (trigger conditions, step sequence, timing delays) as a structured JSON document your Freshsales admin can use to rebuild equivalent Workflows and Sales Sequences in Freshsales.
Follow Up Boss
Custom Field (text, date, number, dropdown)
Freshsales
Custom Field
1:1Follow Up Boss custom fields (text, date, number, dropdown) map to Freshsales custom fields. Dropdown custom fields in Follow Up Boss require value-by-value mapping to Freshsales pick-list options. Date fields with the recurring flag (e.g., birthdays, anniversaries) migrate as date fields in Freshsales with no calendar recurrence engine equivalent.
Follow Up Boss
Lead Source
Freshsales
Lead Source
1:1Follow Up Boss lead source tracking (e.g., Zillow, Realtor.com, Referral) migrates as Freshsales Lead Source. If Follow Up Boss uses custom lead-source values not in Freshsales's default pick-list, we add them as custom pick-list options before migration. We verify that pick-list values match, correcting case or punctuation differences. After migration, the Freshsales Lead Source field shows the source labels for segmentation and reporting in Freshsales pipelines and Smart Lists.
Follow Up Boss
Assigned Agent / Lender
Freshsales
Owner / Contact Role
1:1Follow Up Boss assigned agents migrate as Freshsales Owner by email match to Freshsales user accounts. Unmatched agents are flagged before migration for manual assignment. Lender associations in Follow Up Boss map to a custom 'Lender__c' contact field or Contact Role on the related Deal.
Follow Up Boss
Attachment / File
Freshsales
File / Attachment
1:1Follow Up Boss file attachments on person or deal records migrate to Freshsales Files attached to the corresponding record. File size limits: Freshsales supports up to 25MB per file. We re-upload attachments to Freshsales storage and preserve original filenames. We check compatibility and rename duplicates by appending a suffix to avoid overwrites. After upload, files appear in the record's Attachments tab, allowing users to view or download them from Freshsales.
| Follow Up Boss | Freshsales | Compatibility | |
|---|---|---|---|
| People | Lead / Contact1:many | Fully supported | |
| People.stage | Lifecycle Stage (Contact) / Lead Status1:1 | Fully supported | |
| Company | Account1:1 | Fully supported | |
| Deal | Deal1:1 | Fully supported | |
| Tag | Tag1:1 | Fully supported | |
| Note / Background | Note1:1 | Fully supported | |
| Call Log | Sales Activity / Task1:1 | Fully supported | |
| Action Plan | Workflow / Sales Sequence1:1 | Fully supported | |
| Custom Field (text, date, number, dropdown) | Custom Field1:1 | Fully supported | |
| Lead Source | Lead Source1:1 | Fully supported | |
| Assigned Agent / Lender | Owner / Contact Role1:1 | Fully supported | |
| Attachment / File | File / Attachment1:1 | Fully supported |
Gotchas + challenges
Platform-specific issues from each side, plus the pair-specific challenges that don't show up on either platform's page on its own.
Follow Up Boss gotchas
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
Freshsales gotchas
Freddy AI is Pro-tier only despite heavy marketing
Post-migration emails and sequences are disabled
Bot session credits are a one-time 500-session allocation
Phone credits charged per minute with no cap
File storage limits scale with plan tier
Pair-specific challenges
Migration approach
Inventory Follow Up Boss data and map stage taxonomy
FlitStack AI connects to your Follow Up Boss account via API using a read-only key. We export all People records (including stage tags, custom fields, and tags), Company records, Deal records, Call Logs, Notes, and Custom Field definitions (field types, pick-list choices). We identify the full set of stage tag values used across your database and map each to a Freshsales Lifecycle Stage or Lead Status value. We also inventory Action Plan definitions for the export-for-rebuild package.
Configure Freshsales target schema
Before data lands in Freshsales, we create the required custom fields (Lifecycle_Stage__c, Lender__c, Source_System_ID__c, Original_Create_Date__c) on the Lead and Contact objects. On Pro+ plans, we configure Lifecycle Stages matching your Follow Up Boss stage taxonomy. We add any custom pick-list values needed for Lead Source. We request Freshsales user accounts to be created for agents whose emails appear as assigned owners, so owner resolution by email match can complete without leaving records unassigned.
Resolve owners and run entity-order migration
Follow Up Boss owner emails are matched against Freshsales user accounts by email address. Unmatched owners are flagged; your team either creates Freshsales users or assigns records to a fallback owner before migration runs. We sequence the migration to satisfy foreign-key dependencies: Accounts first, then Leads/Contacts linked to those accounts, then Deals linked to Contacts. Tags and Custom Fields are attached during the record create step.
Run sample migration with field-level validation
A representative slice of 100–500 records (spanning contacts across stages, deals across pipelines, and notes) migrates first. We generate a field-level diff report comparing source values against Freshsales destination values for every mapped field. You review stage mapping, owner resolution, custom field population, and tag assignment before the full run commits. This validation step catches any pick-list mismatches or owner resolution gaps before they affect your full database.
Execute full migration with delta-pickup and rollback plan
The full dataset migrates against Freshsales using the validated mapping from the sample run. A delta-pickup window (24–48 hours) captures any records created or modified in Follow Up Boss during the cutover window. All operations are logged to an audit trail. If reconciliation fails — missing records, owner resolution gaps, or pick-list mismatches — one-click rollback reverts the Freshsales environment to its pre-migration state. The Action Plan export JSON is delivered alongside the migration report for your Freshsales admin to use during Workflow rebuild.
Platform deep dives
Follow Up Boss
Source
Strengths
Weaknesses
Freshsales
Destination
Strengths
Weaknesses
Complexity grading
Standard CRM migration. 2 of 8 objects need a mapping; the rest are 1:1.
Overall complexity
Standard migration
Derived from compatibility, mapping clarity, API constraints, and data volume across Follow Up Boss and Freshsales.
Object compatibility
2 of 8 objects need a mapping; the rest are 1:1.
Field mapping clarity
Field mapping is derived from defaults — final spec confirmed during the sample migration.
Timeline complexity
8-object category — typical timelines run 2–7 days end-to-end.
API constraints
Follow Up Boss: 250 requests per 10-second sliding window (125 on limited accounts). Enforced server-side with HTTP 429 responses..
Data volume sensitivity
Follow Up Boss doesn't expose a bulk API — REST + parallelization used for high-volume runs.
Estimator
Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.
Step 1
Pick a category, then your source and destination platforms.
Category
FAQ
Answers to the questions buyers ask most during Follow Up Boss to Freshsales migration scoping. Not seeing yours? Book a call.
Walk through your Follow Up Boss to Freshsales migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationAdjacent paths
Other ways to leave Follow Up Boss
Other ways to arrive at Freshsales
Ready when you are
Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.