Migrate from Force24 to Microsoft Dynamics 365 Sales

Force24 Contacts map to Dynamics 365 Contact by default. Contacts with Lifecycle Stage indicating a qualified buyer map to Contact; contacts with an unqualified status map to Lead if the customer uses Dynamics Lead management. We compute the split during transformation using the lifecycle_stage and hs_lead_status properties. The original Force24 Lifecycle Stage migrates as a custom field (f24_original_lifecycle__c) on both Lead and Contact for audit and reporting continuity.

Force24 Company records map to Dynamics 365 Account. Force24 stores only a name and URL on the company record by default. We populate the Account Name and Website fields and use the Force24 company ID as an external key for deduplication. Account is inserted before Contact so the AccountId lookup is satisfied at Contact insert time.

Force24 does not maintain a native Deals or Opportunities object. If deal data exists in an integrated CRM that also moves to Dynamics 365, those deal records migrate separately using the source CRM's deal-to-Opportunity mapping. Force24 itself carries no pipeline or deal stage data. We document this gap in the migration scope and recommend that the customer either recreates opportunities in Dynamics 365 post-migration or migrates them from the source CRM if that platform is also changing.

Force24 engagement events (email opens, clicks, SMS sends, form submissions, meeting records) map to Dynamics 365 ActivityPointer records. Each engagement type receives the appropriate activity type code: email activities as Email, SMS as Task, meeting records as Appointment. We preserve the original Force24 engagement timestamp as the ActivityDate on the Dynamics record and link the WhoId to the migrated Contact or Lead and the WhatId to the related Account if available.

Force24 Custom Objects (e.g. Bookings, Event Registrations) map to Dataverse custom entities. These require pre-coordination with Force24 support for API access since Custom Object endpoints are not publicly documented. We extract the Custom Object schema (field names and types), create the equivalent Dataverse custom entity and attributes in the destination Dynamics 365 environment, then re-link the Custom Object records to the corresponding Contact or Account records using the lookup field values extracted from Force24.

Force24 contact tags migrate as a Dynamics 365 multi-select picklist field on the Contact entity, or as a text field if the tag count exceeds picklist limits. We export the full tag set per contact, deduplicate the global tag vocabulary, and create the picklist values in Dataverse before import. The customer chooses the tag strategy during scoping.

Force24 Smart List membership (which contacts belong to each segment) migrates as a static list in Dynamics 365. We export the segment criteria and the full contact ID set per Smart List, then recreate the membership as a Contact list in Dynamics 365. The active, real-time behavioural filter logic cannot be transferred. We document each Smart List's filter conditions so the customer's admin can recreate them as a Dynamics 365 Marketing segment or a Power Automate flow.

Force24 lead scoring values stored on contacts migrate as an integer field (f24_lead_score__c) on the Dynamics 365 Contact or Lead. The scoring rule logic itself (which behaviours and properties contribute how many points) is Force24 configuration and does not transfer. We provide a written inventory of the scoring rules with their thresholds and contributing properties so the customer can configure equivalent scoring in Microsoft Dynamics 365 Sales or Microsoft Sales Copilot.