Migrate from Follow Up Boss to Salesforce Sales Cloud

Direct map for most Follow Up Boss person records. Salesforce requires AccountId on Contact, so each person is linked to an Account record (created from Follow Up Boss company data or a default placeholder). Original Follow Up Boss person ID stored as Source_System_ID__c for traceability.

Follow Up Boss person records in early stages (Lead, Prospect) route to Salesforce Lead. Active and Customer stage records route to Salesforce Contact. The split happens during migration based on the source stage value. This prevents duplicate records and respects Salesforce's lead-conversion model.

Follow Up Boss person records include organization data such as company name and website. These migrate as Salesforce Account records, with the person record linked via AccountId. Parent-child organization hierarchies present in Follow Up Boss map directly to Salesforce Account.ParentId to preserve organizational structure relationships in the destination system.

Follow Up Boss stage names migrate as Opportunity Stage values tied to a Salesforce Sales Process. The original stage name also preserved in FUB_Stage__c custom field for reporting continuity. Each Follow Up Boss pipeline maps to one Salesforce Record Type.

Follow Up Boss pipelines become Salesforce Record Types with corresponding Sales Processes that define the stage sequence. Stage probability weights and forecast categories are re-applied per record type to maintain pipeline-specific metrics. Organizations with multiple distinct pipelines require multiple record types, each with dedicated page layouts and stage picklist values scoped to that pipeline.

Follow Up Boss tags migrate as a custom multi-select picklist field (FUB_Tags__c) on Contact and Lead. Tag values are extracted, deduplicated, and loaded into the picklist definition before migration. Teams may alternatively choose a custom Tag junction object for N:N tagging.

Action Plans define triggered sequences of emails, texts, tasks, and stage changes. No Salesforce equivalent migrates automatically. FlitStack exports the action plan definitions as JSON with step logic, triggers, and timing. Salesforce admins use this as a reference to rebuild equivalent flows.

Follow Up Boss tasks map one-to-one to Salesforce Task records with full field preservation. Original assigned dates, due dates, status values, priority levels, and subject text are carried over during migration. Task owner resolution occurs by matching Follow Up Boss assigned_to email addresses against the Salesforce user list, with matched records receiving the appropriate OwnerId; any unmatched tasks receive a designated fallback owner to ensure every record has a valid assignment in Salesforce.

Follow Up Boss calendar events representing meetings and phone calls migrate as Salesforce Event records with complete temporal and descriptive metadata preserved. Original start times, end times, duration calculations, location details, and subject text transfer directly. Attendee relationships linking to Follow Up Boss person records are maintained in Salesforce through the EventWhoIds relationship, ensuring the full context of each interaction is preserved for team reference.

Follow Up Boss notes containing plain text body content migrate as Salesforce Note records linked to the appropriate parent Contact or Lead. Rich-text formatted attachments stored with notes require separate handling: these files are downloaded from Follow Up Boss and re-uploaded to Salesforce Files, then related to the parent record. Created date timestamps and original owner assignments are preserved throughout to maintain an accurate audit trail for compliance and historical reference.

Follow Up Boss custom fields map to Salesforce custom fields on the target object (Contact, Lead, or Account). Field type determines Salesforce field type: text to Text, date to Date, number to Number, dropdown to Picklist. Picklist values are migrated with the field definition.

Follow Up Boss users assigned as record owners are matched to Salesforce users by email address lookup across both platforms. Successfully matched records receive the corresponding Salesforce OwnerId to maintain proper assignment chains. Any Follow Up Boss owners without matching Salesforce user accounts or with email address mismatches are flagged in a pre-migration validation report, allowing administrators to either provision new Salesforce user accounts for legacy owners or assign a fallback owner before records are inserted into the destination system.