Migrate from Actimo to Pipedrive

Actimo user profiles map directly to Pipedrive Person records. Name, email, phone, job title, department, and location fields translate 1:1. Actimo's engagement score, training completion count, and last training date are stored as custom fields on the Person record in Pipedrive.

Actimo company records map to Pipedrive Organization records. Company name, domain, address, industry, and employee count translate directly. Pipedrive Organizations can then be linked to Person records via the Person-Organization relationship. The address and industry fields use Pipedrive's standard Organization fields, and employee count is stored as a custom field since Pipedrive has no native employee count field. Organization records are created first to establish lookup keys before Person records are loaded.

Actimo user-to-company associations map to Pipedrive's built-in Person-Organization relationship. In Pipedrive, each Person can be linked to one primary Organization via the relationship field. Secondary organization associations are not natively supported and are preserved as a note on the Person record.

Actimo's composite engagement score has no Pipedrive native equivalent. We create a custom Number field (engagement_score__c) on the Person object and populate it from Actimo's exported engagement score value. Pipedrive supports numeric custom fields via the /personFields API endpoint, which requires field name, field type, and returns a hash key for API reference during record creation. The engagement score is a decimal value scaled per Actimo's calculation methodology.

Actimo training completion data — courses started, courses completed, last training date, quiz average score — has no Pipedrive native equivalent. We map each metric to a separate custom field on the Person record: courses_completed__c (Number), last_training_date__c (Date), quiz_score__c (Number). These custom fields are created via the /personFields API before the migration run, and each field is referenced by its hash key when writing Person records. The quiz_score__c stores the average as a decimal rounded to two places.

Actimo message analytics (open rate, click rate, delivery status, message count) map to custom fields on Person. Pipedrive has no native activity analytics equivalent for message engagement. Custom fields capture the most recent analytics snapshot per user. Each metric becomes a dedicated custom field on the Person record: message_open_rate__c (percentage), message_click_rate__c (percentage), message_delivery_status__c (string), and message_count__c (number). These are created via the /personFields API before data loading.

Actimo pulse survey response data — last survey date, response status, aggregate score — migrates as a custom text or number field on Person. Pipedrive Activities do not support survey-type response tracking natively, so this data is preserved as a reference custom field. The last_survey_response__c field stores the most recent survey date and status as a combined string, while aggregate scores are stored in a separate quiz_score__c field on the Person record.

Actimo onboarding flows, learning paths, and engagement sequences are platform-native constructs stored outside the exportable data layer. Pipedrive has its own automation engine (Automations and Sequences) that must be rebuilt. We export a JSON reference of your workflow definitions for your Pipedrive admin to use as a rebuild guide.

Actimo integrations with HR systems (Sympa, other HRIS connectors) are configuration-level connections that do not export as data. Pipedrive integrations must be rebuilt separately. We document your existing integrations so your Pipedrive admin can configure equivalent connections in Pipedrive's Marketplace.

Actimo engagement dashboards and analytics reports are platform-native reporting constructs. Pipedrive's reporting layer operates on CRM data (deals, activities, pipeline metrics) and does not natively understand Actimo engagement metrics. Engagement dashboards must be rebuilt using Pipedrive's analytics tools or a third-party BI layer.

Actimo files attached to user profiles (training certificates, uploaded documents, compliance records) are downloaded and reattached to the corresponding Pipedrive Person record as a Note with an attached file. The Note includes the original filename, upload date from Actimo, and a reference to the source export batch. Pipedrive stores files within its 5–100GB per-user storage limit depending on plan. Files are uploaded via the /files API endpoint and linked to the Person via the Note object.

HR-sourced data such as hire date and employment status that Actimo synced from an HRIS integration migrates as custom fields on Person. Pipedrive has no native HR field equivalent, so hire_date__c (Date) and employment_status__c (String) are created as custom fields to preserve this context. The employment_status__c field stores values like Active, On Leave, or Terminated, matching Actimo's status taxonomy. Both fields are created via /personFields before migration.

Actimo stores location and department data for non-desk workers that often comes from HRIS integrations. These migrate as custom string fields on Pipedrive Person records since Pipedrive has no native non-desk workforce management fields. Site_location__c and department__c preserve organizational context in the CRM. Site_location__c stores the physical location or site code, and department__c stores the organizational department name as a free-text string.

Actimo tracks communication activities as part of its engagement record. Any logged calls or meeting data that can be exported from Actimo's activity log maps to Pipedrive Activities of type 'Call' or 'Meeting', preserving the original date, subject, and user owner assignment.