Migrate from Actimo to Microsoft Dynamics 365 Sales

Learning paths are sequential structures with no Dynamics 365 native equivalent

Actimo learning paths define ordered sequences of courses, quizzes, and milestones that employees complete in a specific order. Microsoft Dynamics 365 Sales has no native learning path or course sequencing entity. We create a custom LearningPath Dataverse table and a LearningPathEnrollment junction entity linking paths to Contact records, but the sequential progression logic (course A must be completed before course B) cannot be migrated automatically. Your Dynamics 365 administrator must rebuild progression rules using Power Automate flows or custom business logic. FlitStack delivers the learning path metadata (course names, order, prerequisites) as a rebuild reference document so your team can reconstruct sequences in Dynamics 365 Learning Path or a third-party LMS.

Gamification engagement scores and badges lack a native Dynamics 365 home

Actimo tracks employee engagement through gamification: points earned, badges awarded, and leaderboard rankings. Microsoft Dynamics 365 Sales has no native gamification or engagement scoring entity. We migrate the most recent total engagement score as a custom Number field (new_engagementscore) on the Contact record and store badge names as a text field, but Dynamics 365 cannot natively display leaderboards, calculate point differentials, or trigger recognition workflows based on gamification data. Teams that rely on Actimo's gamification to drive employee motivation need to rebuild leaderboard reports in Power BI or accept that this data serves as historical reference only. FlitStack flags all gamification records for admin review before the migration commits.

Pulse survey anonymity conflicts with Dynamics 365 audit requirements

Actimo supports anonymous pulse surveys where employee identities are hidden from managers. Microsoft Dynamics 365 Sales requires every record to have an owner and maintains a full audit trail tied to the user who created the record. When migrating anonymous survey responses, FlitStack must assign the response to a designated admin user or system user rather than the anonymous employee, which breaks the anonymity guarantee. Teams with legally protected anonymous feedback processes (common in HR and compliance contexts) need to decide whether to migrate anonymous responses to a restricted-access custom entity or exclude them from the migration entirely. FlitStack surfaces this decision point during the pre-migration planning phase.

Actimo's user email uniqueness constraint differs from Dynamics 365 Contact

Actimo allows multiple user accounts to share the same email address in some configurations (common in multi-brand or franchise scenarios where one employee works across multiple Actimo workspaces). Microsoft Dynamics 365 Contact requires emailaddress1 to be unique per Contact record when duplicate detection rules are active. Migration of shared-email users creates a collision that FlitStack resolves by appending a workspace suffix to the email address (e.g., [email protected] becomes [email protected]_workspaceA) and flagging these records for admin review. The suffix approach ensures data integrity in Dynamics 365 but may affect email-based workflows that rely on exact email matching. Admins should update email filters in Power Automate flows and Dynamics 365 email workflows after migration.

Custom training properties require Dataverse schema creation before migration

Actimo training objects support arbitrary custom properties (fields that administrators define beyond the standard course name, enrollment date, and quiz score). Microsoft Dynamics 365 Sales Professional tier imposes a 15-table limit that includes custom entities. Teams with extensive training custom properties may need to upgrade to Sales Enterprise (unlimited custom tables) or consolidate custom fields on existing tables before migration begins. FlitStack audits Actimo's custom property count during the planning phase and delivers a Dataverse schema plan specifying which custom entities to create, what fields to add, and whether a license tier upgrade is recommended. This schema must be deployed in Dynamics 365 before the migration data load runs.