Migrate from Actimo to Salesforce Sales Cloud

Actimo employee records map directly to Salesforce Contacts. Each employee's name, email, phone, department, and location become Contact fields. The primary company association in Actimo maps to Contact.AccountId — if no company field exists in Actimo, FlitStack creates a placeholder Account or flags the record for manual assignment.

Actimo records flagged as 'prospect employees' (pre-hire onboarding records) route to Salesforce Lead instead of Contact. The split is based on Actimo's employee_status field: 'active' or 'inactive' maps to Contact; 'invited' or 'pending' maps to Lead with a custom Actimo_Status__c field preserved for reference.

Actimo message campaigns (news posts, announcements) become Salesforce Campaigns. Each employee's open/click action on a message becomes a Campaign Member record with custom Engagement_Type__c (Opened / Clicked / Bounced) and Activity_Date__c — allowing you to report on engagement within Salesforce's campaign model.

Actimo learning paths have no Salesforce native equivalent. FlitStack creates a Course__c custom object with fields for path name, description, estimated_duration, and module_count. This custom object must be deployed to Salesforce before data migration — FlitStack delivers the setup manifest as part of the migration plan.

Each employee's enrollment in a learning path maps to a custom Enrollment__c junction object linking Contact (WhoId) to Course__c (WhatId). Enrollment fields include start_date, completion_date, score, and status (In Progress / Completed / Overdue). The junction object is required because Salesforce standard objects cannot express this N:1 employee-to-course relationship natively.

Actimo pulse surveys with their question-and-answer structure require a custom Survey__c parent object and SurveyResponse__c child object per employee response. Each response row carries question text, answer value, and submission timestamp. This schema is non-trivial and must be pre-built in Salesforce before migration runs.

Actimo one-on-one feedback entries map to Salesforce Tasks. The feedback subject maps to Task.Subject, the content maps to Task.Description, the scheduled date maps to Task.ActivityDate, and the employee maps to Task.WhoId (Contact lookup). FlitStack preserves the feedback thread structure by creating a chain of Tasks with a common custom Feedback_Thread_Id__c field.

Actimo message-level engagement events (opens, clicks, replies) are merged into Salesforce Tasks with a custom Type value of 'Engagement'. Each Task's Subject carries the message title, WhoId links to the Contact, and a custom Engagement_Type__c pick-list stores the specific action. This consolidates disparate event types into a single Salesforce object.

Actimo's manager-on-employee relationship maps to a custom Manager__c lookup field on Contact pointing to another Contact record. If the manager is also a Salesforce user, FlitStack resolves the email match to link the Contact's Manager__c to the corresponding User record — enabling Salesforce's hierarchical reporting features.

Actimo admin users who created content or owned campaigns become Salesforce Users, matched by email. FlitStack flags any Actimo user without a corresponding Salesforce User as an Unmatched_Owner__c record — your admin either provisions a Salesforce license or reassigns ownership to an existing user before migration commits.

Actimo's composite engagement score or NPS per employee has no Salesforce native field. FlitStack migrates the numeric score to a custom Number field on Contact. If Actimo stores multiple score types (engagement, pulse, eNPS), each stores in its own custom field — Engagement_Score__c, NPS_Score__c — as defined in the migration plan.

Files attached to Actimo messages, learning paths, or survey content are downloaded and re-uploaded to Salesforce Files (ContentDocument / ContentVersion model). File size limits apply — Salesforce Files default to 25MB per file. Inline images in Actimo content are extracted and rehosted as Salesforce Files linked to the relevant Contact or custom object.

Actimo's automated onboarding sequences, survey triggers, and message drip campaigns have no Salesforce equivalent that migrates automatically. FlitStack exports the Actimo flow definitions as a JSON-structured rebuild reference document — documenting trigger conditions, action sequences, timing rules, and employee segments — so your Salesforce admin can reconstruct equivalent Flows in Salesforce.