Migrate from Actito to Pipedrive

Actito Profile records map directly to Pipedrive Person. All standard profile attributes (first name, last name, email, phone, address) migrate as typed fields. Custom profile attributes migrate to Pipedrive custom fields on Person. The Profile's entity assignment maps to a Pipedrive Pipeline or a custom field for multi-entity partitioning when the customer's Actito licence spans B2C and B2B populations.

Actito Profiles linked to a Company relationship (via a Profile-to-Company attribute) map to Pipedrive Organization. We inspect the relationship definition during scoping, extract the related Company name and attributes from the relevant Custom Table, and create the Organization record before the Person import so that Person.organization_id is satisfied at insert time.

Actito Custom Tables describing companies (billing details, company size, industry classification, account tier) map to Pipedrive Organization custom fields. When a single Actito Custom Table contains multiple rows per Profile, we flatten the most recent or highest-priority row into Organization fields and flag additional rows for reconciliation.

Actito Custom Tables describing subscription details, product lines, or financial records map to Pipedrive Deal. Each Custom Table row referencing a Profile creates a Deal record. The Deal title derives from the Custom Table name plus a record identifier. Custom Table fields map to Deal custom fields. Deal stage and probability derive from a configuration mapping table provided by the customer during scoping.

Actito Custom Tables with non-account and non-deal schemas (product preferences, behavioral attributes, service history) map to custom fields on the parent object (Person or Organization). We inspect field types during scoping and translate Actito field types to Pipedrive-supported equivalents: string to text, integer to int, decimal to currency or double, date to date, boolean to checkbox.

Profile-level opt-in status, double opt-in confirmation date, and channel consent flags migrate to Pipedrive Person. The GDPR compliance flag from Actito maps to a Person custom field and the email opt-out status maps to HasOptedOutOfEmail. We preserve the full preference tree as structured custom fields when Pipedrive's standard fields do not capture channel-level granularity.

Actito campaign names, targeting criteria, and schedule metadata do not have a direct Pipedrive equivalent because Pipedrive has no campaign execution object. We migrate campaign configuration as a structured Note attached to the relevant Person or Deal so that admins have an audit trail of the original campaign assignment. The actual campaign content (email body, SMS template) does not transfer.

Actito Scenarios (event-triggered automation workflows) do not migrate to Pipedrive Workflows because the trigger models differ: Actito uses event-based conditions on Profile attributes; Pipedrive Workflows use CRM record triggers (deal stage change, activity creation). We deliver a written Scenario inventory with trigger descriptions, action steps, and Pipedrive Workflow equivalents for the customer's admin to rebuild.

Actito engagement records (opens, clicks, sends) are generated by Actito's platform during campaign execution and are not available for programmatic export. We do not migrate engagement interaction events. We migrate any manually logged activities from Actito (as notes or tasks) to Pipedrive Activity records attached to the Person.

Actito's Entity-based licence partitioning maps to Pipedrive Pipelines when the customer uses multiple Actito entities for separate lines of business (e.g., B2C vs B2B). We create a Pipedrive Pipeline per Actito Entity and map each Profile's entity assignment to the target Pipeline. If only one Pipeline is needed, entity assignment is stored as a Person or Deal custom field.