Migrate from Actimo to Freshsales

Actimo contacts map to Freshsales Contact records by default. Contacts flagged as sales-ready or with active deals in Actimo can route to Freshsales Lead instead, preserving original engagement data on the record. FlitStack AI resolves the split by matching contact properties against your specified routing rules before migration.

Actimo company records map directly to Freshsales Accounts. Company name maps to Account Name; industry, employee count, and annual revenue map to standard Freshsales Account fields. If Actimo stores multiple contacts per company, the primary account association is set on each Contact record via the AccountId lookup.

Actimo engagement_score maps to a custom Number field on Freshsales Contact — Engagement_Score__c. Freshsales has no native equivalent to Actimo's engagement scoring methodology. The field must be created in Freshsales before migration begins, and FlitStack AI populates it with the numeric score extracted from Actimo's contact records during the load phase.

Actimo training_completion_rate maps to a custom Number field — Training_Completion_Rate__c — on Freshsales Contact. This stores the percentage of training content the employee has completed. Freshsales has no native training tracking module; the field supports reporting on workforce development post-migration.

Actimo message_open_count and message_click_count map to custom Number fields — Messages_Opened__c and Messages_Clicked__c — on Freshsales Contact. These preserve engagement volume from Actimo's internal communications tool so team leaders can review communication participation rates and click-through metrics directly within Freshsales after migration completes.

Actimo tags map directly to Freshsales Tags, which are a native tagging construct available on Contact, Lead, Account, and Deal records. Tags migrate as-is without transformation. If tag names conflict with existing Freshsales tags, FlitStack AI appends a source prefix for disambiguation.

Actimo department_name maps to a custom text field — Department__c — on Freshsales Contact. If department is stored at the company level in Actimo, it also populates Department__c on the associated Freshsales Account record for cross-object reporting queries that span both contacts and accounts within the same department filter.

Actimo last_engagement_date maps to a custom Date field — Last_Engagement_Date__c — on Freshsales Contact. This preserves the timestamp of the employee's most recent interaction with Actimo content, enabling churn-risk scoring and re-engagement workflow triggers in Freshsales based on inactivity windows.

Actimo assigned_training_paths map to a custom text field — Assigned_Training_Paths__c — on Freshsales Contact, storing the list of training modules assigned to each employee. Training content files themselves do not migrate to Freshsales; they remain in Actimo or are exported separately.

Actimo survey response counts and engagement rates map to custom Number fields on Freshsales Contact — Survey_Responses__c and Survey_Engagement_Rate__c. Full survey question-and-answer history does not have a direct Freshsales equivalent; FlitStack AI exports survey data as a CSV reference file and documents the rebuild path in Freshsales Forms or a custom object.

Actimo owner_id resolves to Freshsales OwnerId by matching the owner's email address against Freshsales user accounts. Unmatched owners are flagged before migration; your team either invites them to Freshsales first or assigns their records to a fallback owner. No contact lands in Freshsales without a resolved owner.