Migrate from Follow Up Boss to Pipedrive

Follow Up Boss people map 1:1 to Pipedrive Persons. Name, email, phone, address, and all standard contact properties migrate directly. Unmatched email addresses are flagged before the full run so you can either invite users or assign a fallback owner.

Follow Up Boss company records map to Pipedrive Organizations. Company name, domain/website, address, and employee count fields map directly. Multi-company associations on a single contact collapse to one primary Organization link in Pipedrive with additional relationships surfaced as Organization-Person relationship roles.

Follow Up Boss deals map to Pipedrive Deals with all standard fields — deal name, value, stage, close date, owner, and linked contact/organization. Each deal is assigned to the appropriate Pipedrive Pipeline based on the source pipeline grouping. Deal-person and deal-organization relationships are preserved during migration, ensuring your complete sales history transfers with intact association references.

Follow Up Boss pipelines map directly to Pipedrive Pipelines. Each Follow Up Boss pipeline becomes a named Pipedrive Pipeline with its own Stage set. If your Follow Up Boss account uses a single pipeline, that maps to one Pipedrive Pipeline; multi-pipeline accounts generate multiple Pipedrive Pipelines.

Follow Up Boss stage values map to Pipedrive Stage names per Pipeline. Stage names are preserved verbatim where possible; if a stage name conflicts within a Pipeline, a disambiguated name is created and a mapping table is delivered in the migration plan. Stage order is preserved.

Follow Up Boss tags migrate as Pipedrive tags on both Person and Deal records. Tags are preserved exactly as stored — tag names, capitalization, and spacing are carried over without modification. Tags that do not yet exist in Pipedrive are automatically created during the migration run, and the migration process maintains consistent tag application across all affected records.

Follow Up Boss custom fields require pre-creation in Pipedrive before data loads. Date fields map to Pipedrive date fields, text fields to varchar or text depending on length, number fields to double, and dropdown fields to enum. Field labels are preserved; API key names differ between platforms and are reconciled in the mapping plan.

Follow Up Boss events — calls, emails, texts, and notes — map to Pipedrive Activities with the corresponding type (call, email, task, meeting-note). Original timestamps, event content, and linked person/deal associations are preserved. Pipedrive's Activity model groups all interaction types under one object.

Follow Up Boss Action Plans are automated follow-up sequences with email drips, tasks, and stage-change triggers. Pipedrive has no equivalent structure — Sequences are manual-outreach drips and Automations are condition-triggered. FlitStack exports Action Plan definitions as structured JSON with step order, conditions, and delays so your Pipedrive admin can rebuild them as Pipedrive Automations.

Follow Up Boss tracks lead source attribution. If you use a dedicated source field in Follow Up Boss, we recommend creating a custom field in Pipedrive (dropdown or text) to preserve the source label on each Person record. Source data is migrated as-is; value normalization is available as an add-on.

Follow Up Boss stores high-priority contact notes in a Background field. These migrate as Pipedrive Person notes with a 'Background' label prefix so your team can distinguish them from general interaction notes. Background content is treated as plain text — formatting is not preserved.

Follow Up Boss owner IDs resolve to Pipedrive users by email address match. Unmatched owners are flagged before migration — your team either invites them to Pipedrive first or reassigns their records to a designated fallback user. Historical owner attribution is preserved in a custom note on each record.