Migrate from Actito to Salesforce Sales Cloud

Actito Profiles are the central record type and map directly to Salesforce Contact. All standard and custom profile attributes migrate to typed Salesforce fields or custom fields. The profile identifier (id) is preserved in a custom field actito_profile_id__c for reconciliation. Reference dates and subscription metadata transfer as related field values.

Actito Custom Tables connected to Profiles via relationships map to Salesforce Custom Objects. We inspect the table schema during scoping, map field types to Salesforce equivalents (TEXT becomes Text, NUMBER becomes Number, DATE becomes Date), and pre-create the destination schema including lookup relationships to the parent Contact before data import.

Actito Entities partition all resources (data structures, campaigns, scenarios) within a licence and often map to business units or brands. We preserve entity names and assignments as Salesforce Account records with a custom entity_type__c field so that each business unit lands in the correct partition. The primary entity becomes the primary Account; additional entities become child Accounts under a hierarchy.

Actito campaigns span email, SMS, push, call center, print, and web channels. Campaign configuration metadata (name, schedule, targeting criteria, content references) migrates to Salesforce Campaign. We flag which channel configurations apply to which Salesforce Campaign type and note that email sender authentication (DKIM, SPF) must be reconfigured on the destination email infrastructure.

Actito Scenarios are event-triggered automation workflows with branching rules and action steps. We do not migrate Scenarios as executable code because the automation model differs from Salesforce Flow. We deliver a written inventory of every active Scenario including trigger conditions, branching logic, action sequences, and delays, with a recommended Salesforce Flow equivalent for each. The customer's admin or a Salesforce partner rebuilds them post-migration.

Actito email channel configuration (sender profile, template, routing) maps to Salesforce Campaign settings and Email Administration. DKIM, SPF, and return-path DNS records must be reconfigured for the Salesforce org's sending domain. We preserve sender reputation settings as documentation for the Salesforce admin to implement.

Actito SMS channel configuration migrates as a Salesforce Campaign with SMS-specific custom fields. Actual SMS sending requires an AppExchange SMS product (e.g., Twilio, Peltexx) post-migration; we document the current Actito SMS configuration as a requirements artifact for the integration setup.

Push channel configurations and device opt-in status migrate to Salesforce MobilePush. Device tokens transfer as a custom MobilePush Token object. Push campaign performance history does not migrate; we flag this for the customer to archive from Actito before cutover.

Profile-level opt-in and preference data migrates as structured custom fields on Contact. Double opt-in status, channel-level consent flags (email, SMS, push), and subscription group memberships transfer to custom fields (consent_email__c, consent_sms__c, consent_push__c, subscription_groups__c) with a consent_timestamp__c date field per channel.

Actito web tracking goals and behavioural event definitions migrate as configuration records in a Salesforce Custom Object. We map goal names, trigger conditions, and associated profile attributes to the destination's event-tracking equivalents. Actual web tracking requires Salesforce Marketing Cloud or a third-party analytics integration post-migration.

Actito segment-building rules and profile selection criteria map to Salesforce Campaign Member records. Complex criteria using Actito-specific operators (is last month, behavioural triggers) are documented with a recommended Salesforce filter or Report equivalent. Active segments are implemented as Salesforce Campaigns with static or dynamic Campaign Member lists post-migration.

Actito export job definitions (CSV, Excel, ZIP/GZIP compression) are preserved as documentation. We use Actito's ETL export jobs to extract large datasets during migration rather than looping API calls, then decompress and transform the output for Salesforce Bulk API ingestion.

ETL jobs and webhook subscriptions defined in Actito are documented as job definitions with their trigger conditions and action targets. Since webhook URLs and ETL credentials are destination-specific, we preserve the job structure and flag the endpoints requiring reconfiguration on the Salesforce side (Inbound Change Data Capture, Outbound Messaging, or Platform Events).

Interaction events (opens, clicks, bounces, unsubscribes) are generated by Actito's platform during campaign execution and are not available for programmatic export via the standard API. We do not migrate these records. We advise exporting and archiving Actito campaign reports before cutover so that historical email performance data is preserved in the customer's reporting archive.

Actito users referenced on Profiles, Custom Tables, and Campaigns resolve by email match against the Salesforce destination org's User table. We allocate API keys across migration phases (profile export, custom table export, scenario export) rather than running parallel record streams, staying within Actito's 5-key licence limit.