Migrate from Act-On to Salesforce Sales Cloud

Act-On Contacts with lifecycle stage of prospect or unknown map to Salesforce Lead. Contacts with lifecycle stage of customer, evangelist, or partner map to Salesforce Contact tied to a Salesforce Account. We compute the split using Act-On's lifecycle_stage property and preserve the original value in a custom field ao_original_lifecycle__c on both Lead and Contact for audit. The customer approves the split matrix during discovery before any data moves.

Act-On Company records map directly to Salesforce Account. The Company name becomes Account.Name; industry and custom company fields migrate to standard or custom Account fields. Account is created before Contact import so that AccountId lookup is satisfied at Contact insert time.

Act-On Lists are audience segments used for targeting campaigns. Static Lists migrate as Salesforce Campaign records with Campaign Members seeded from the Contact/Lead mapping. Dynamic Lists cannot replicate their rule logic; we document the segment criteria as a reference and the customer rebuilds as a Salesforce Campaign or Smart List. List membership for small static lists migrates as a multi-select picklist or tag field on the Contact/Lead.

Act-On calculates engagement scores using proprietary weighting across email opens, clicks, page visits, and form submissions. The calculation rules do not export. We migrate the current numeric score as a static integer in a custom field ao_engagement_score__c on Lead and Contact. The customer configures Salesforce-native scoring (Einstein Lead Scoring or a custom Flow-based scoring model) post-migration.

Act-On's Custom Data Schema defines user-defined field extensions per object. We read the schema definition via Act-On's API, export all existing records, and write them to Salesforce custom objects with equivalent API names (__c suffix). The destination schema is pre-created in a Sandbox before any data import, including custom field types, lookup relationships, and validation rules.

Act-On email content, subject lines, and send history are accessible via API. HTML email bodies migrate as ContentDocument records linked to the relevant Account, Contact, or Campaign. Email templates do not migrate as live templates; we deliver a content inventory document listing subject, body copy, and images for the customer's admin to recreate in Salesforce Email Templates or Marketing Cloud.

Act-On web form field definitions and submission data migrate; the form embed code does not transfer. We deliver a form field inventory mapping each Act-On form field to a Salesforce field and recommend Salesforce Web-to-Lead (standard) or Experience Cloud Form Builder (if the customer licenses Experience Cloud) as the replacement implementation.

Act-On logs email opens, clicks, form submissions, and other behavioural events as timestamped activity records. We export activity history as Task records linked to the Contact or Lead, with the original engagement type (open, click, form_submission) preserved in a custom Task field ao_engagement_type__c. Volume can be large; we chunk by date range and use Bulk API 2.0.

Call logs from Act-On map to Salesforce Task with TaskSubtype = Call. Duration, disposition, and any notes migrate to custom Task fields. Meeting records map to Salesforce Event with StartDateTime, EndDateTime, and Location preserved. Attendee resolution is limited by Act-On's API; we link to the primary Contact or Lead only.

Act-On Contact and Company tags export as label arrays. We map them to Salesforce multi-select picklist fields on Lead and Contact for operational use, or to Salesforce Topics with TopicAssignment records for content classification. The customer chooses the tag strategy during scoping.

Act-On owners (users who own contacts, companies, and programs) map to Salesforce User records by email match. Any Act-On Owner without a matching Salesforce User is held in a reconciliation queue for the customer's admin to provision before record import resumes.

Act-On Programs define multi-step nurture sequences stored server-side. They are not accessible via the API and cannot be migrated as code. We export all Contact data within each Program (who entered, when, which branch they took) as a historical record and deliver a Program blueprint document listing sequence steps, entry criteria, delays, and actions. The customer's admin rebuilds the Program in Salesforce Flow using that document as reference.