Migrate from Follow Up Boss to Twenty CRM

Follow Up Boss Person maps 1:1 to Twenty People. Standard contact fields (name, email, phone, address) transfer directly. The Person's company link resolves to a Twenty Companies record if the source company exists in the migration set. Additional fields like source and stage also transfer when present in the source data, ensuring complete contact profiles in Twenty.

Follow Up Boss Company maps to Twenty Companies. Industry, employee count, annual revenue, and domain fields map directly where present. Parent-company hierarchies in Follow Up Boss map to the Parent Company relation in Twenty using the same company as the parent.

Follow Up Boss Deal maps to Twenty Opportunities. Deal name, amount, expected close date, and pipeline stage transfer directly. The pipeline stage in Follow Up Boss maps to a Twenty Opportunity stage within the configured pipeline. Deal associations to People and Companies are preserved through email and domain linking in Twenty's relationship system.

Follow Up Boss Pipeline configuration maps to a Twenty pipeline with configurable stages. Each pipeline in Follow Up Boss becomes a separate stage set in Twenty's Opportunity pipeline settings. Stages are recreated before migration so the importer can route records correctly.

Action Plans (automated multi-step sequences) have no direct equivalent in Twenty CRM. We export Action Plan definitions as a JSON blueprint documenting step order, wait times, trigger conditions, and task types. Rebuild in Twenty's workflow builder or via API is manual work handled by your team or a Twenty specialist.

Follow Up Boss events (calls logged, emails sent, meetings scheduled) map to Twenty Tasks. The task subject, body, due date, and completion status transfer with original timestamps preserved. Call disposition notes map to the task body in Twenty. Meeting details including start and end times are captured in task metadata for complete activity history.

Follow Up Boss notes attached to People, Companies, or Deals map to Twenty Notes. Notes are linked to the corresponding People or Companies record via the import relation mechanism using email for People and domain for Companies. The original note body and creation timestamp are preserved in Twenty's Notes object for full audit trail continuity.

Follow Up Boss tags do not have a native equivalent in Twenty's base schema. We create a Tags__c custom text field or multi-select field on the People object and populate it with comma-separated tag values from Follow Up Boss during migration.

Follow Up Boss stage-transition timestamps are preserved as custom datetime fields in Twenty (Stage_Entered_Date__c, Stage_Changed_At__c) on the Opportunity record. These enable reporting continuity for pipeline velocity analysis after go-live. The timestamp history allows teams to reconstruct deal progression and calculate average time spent in each stage for accurate forecasting.

Follow Up Boss custom fields of types text, date, number, and dropdown map to Twenty custom fields created in Settings → Data Model before import. Dropdown fields map to Twenty select fields with the same choice values. Field-level type is preserved; note that Follow Up Boss does not allow field type changes post-creation.

Follow Up Boss user assignments (deal owner, assigned agent) resolve by email match against Twenty Workspace Members. Unmatched owners are flagged pre-migration; your team either invites them to Twenty first or assigns records to a fallback owner. No record lands without a resolved Twenty owner.

Follow Up Boss file attachments on People, Companies, or Deals are downloaded and re-uploaded to Twenty. File size limits apply per the self-hosted or cloud configuration. Inline images in notes are extracted and hosted separately as Twenty does not natively render embedded images from external URLs.