Migrate from Follow Up Boss to Microsoft Dynamics 365 Sales

FUB People split into Dynamics 365 Contacts (qualified buyers/sellers) and Leads (pre-contact prospects) based on FUB stage. Stages 'Lead' and 'Prospect' route to Lead; 'Active', 'Client', and 'Closed' route to Contact. The migration preserves the FUB stage as a custom column (FUB_Stage__c) for reporting continuity.

FUB Companies map directly to Dynamics 365 Accounts in a one‑to‑one relationship. The FUB domain/website value populates Account.Website, and any parent‑company hierarchy in FUB translates to Account.ParentAccountId. Primary contact information from FUB becomes the primary Contact on the Account, while secondary contacts are stored as Account Contact Relationships. Address, phone, and custom fields on the FUB company record create matching columns on the Account, ensuring a complete profile after migration.

FUB Deals migrate as Dynamics 365 Opportunities. The FUB pipeline maps to a Business Process Flow; deal stages map to Opportunity Stage values per process. Each FUB pipeline requires a separate Business Process Flow in Dynamics. Deal amount, close date, and owner transfer directly.

FUB pipelines become Dynamics 365 Business Process Flows. Teams with multiple FUB pipelines (e.g., Buy-side, Sell-side, Rental) create multiple BPFs — each with its own stage set. We deliver a BPF mapping plan before migration so your Dynamics admin can pre-create the flows.

FUB tasks and action items map to Dynamics 365 Tasks. Original due dates, assignees (resolved by email), and task subjects transfer. Completed-at timestamps preserve as custom datetime fields. FUB system tasks (e.g., 'Auto-Email Sent') surface as Tasks with a source flag.

FUB notes migrate to Dynamics 365 Annotations. Rich-text formatting in FUB notes converts to HTML in Annotation.noteText. Notes attached to specific People or Deals link via RegardingObjectId. Inline images in FUB notes are downloaded and re-hosted as Dynamics 365 notes attachments.

FUB tags are multi-value string properties. We map them to a custom multivalue text column (FUB_Tags__c) or as Dynamics 365 Topics on Activities — your admin chooses. Tag-based segmentation in FUB should be rebuilt as Dynamics views with filter criteria on the tags column.

FUB lead sources (Zillow, Realtor.com, referrals, etc.) have no native Dynamics 365 equivalent. We create a custom picklist field (LeadSource_FUB__c) on the Lead and Contact entities and map values value-by-value. Your team then maps these to Dynamics' native LeadSource on Leads.

FUB action plans — drip sequences of tasks, stage changes, emails, and tags — have no direct Dynamics 365 equivalent. FlitStack AI exports action plan definitions as a structured JSON playbook, including trigger conditions, step order, and step types, for your Dynamics admin to rebuild using Power Automate or Dynamics Sales Automation sequences.

FUB custom fields (text, date, number, dropdown) create matching Dataverse columns on the Contact, Account, or Opportunity tables. FUB dropdown choices map to Dataverse choice columns with the same option labels. Character limits in FUB (256 max) do not apply in Dynamics.

FUB logged emails map to Dynamics 365 email Activity records. The Regarding field links to the Contact or Lead. Email subjects, bodies (HTML), timestamps, and sender/recipient addresses preserve. Email sync requires a connected Exchange or SMTP setup in Dynamics.

FUB call records become Dynamics 365 Phone Call activity records. Duration, direction (inbound or outbound), phone number, and outcome notes transfer directly to the Phone Call entity. Call recordings stored in FUB are re‑uploaded to Dynamics 365 SharePoint (or Dataverse file columns if SharePoint is unavailable) and linked to the parent Contact or Opportunity via Annotation records, preserving the full conversation history for reference.

FUB file attachments re-upload to Dynamics 365 SharePoint Online (if the environment is SharePoint-connected) or stored as Dataverse file columns. Files over 128MB chunk via the Dynamics 365 file upload API. Filenames over 256 characters truncate at migration time with a warning flag.

FUB team members resolve to Dynamics 365 SystemUser records by email address match. Unmatched FUB owners flag as migration warnings — your team invites them to Dynamics first or assigns their records to a fallback owner. User-specific FUB settings (e.g., individual calling plans) do not transfer.

FUB Smart Lists (dynamic contact filters) have no direct Dynamics 365 equivalent. We document each Smart List's filter criteria as a reference for rebuilding as Dynamics Saved Views or using Power Automate to maintain equivalent dynamic segments. Static exported Smart List results migrate as contact records.