Migrate from Act-On to Pipedrive

Act-On Contact maps directly to Pipedrive Person. Standard fields (firstname, lastname, email, phone, mobilephone, title) pass through cleanly. The Act-On Lifecycle Stage property migrates to a Pipedrive custom field lifecyclestage__c for audit continuity. We use email as the dedupe key during import to prevent duplicate Persons.

Act-On Company maps to Pipedrive Organization. Company name maps to Organization name, domain to website, industry to industry picklist, and address fields to the Organization address block. Organization is created before any Person import so that the Person.organization_id lookup is satisfied at insert time.

Act-On's one-to-many Contact-to-Company relationship resolves at migration time. We look up the Organization ID using the Act-On contact's company field and write it to Person.organization_id. Any Contact with a company name that has no matching Organization record is held for reconciliation.

Act-On Tags export as label arrays per contact. We map them to Pipedrive Labels on the Person record and create Activity labels for any tag that represents an event rather than a category. Dynamic Act-On List membership is not technically equivalent to a tag; we document each dynamic list's filter logic as a Pipedrive filter view reference.

Act-On Lists are audience segments used for campaign targeting. We preserve List membership as a Pipedrive Label on each Person (e.g., Label: 'Q4 Webinar Attendees'). The underlying dynamic or static logic of the Act-On List does not transfer; we document the filter conditions in a written reference so the admin can create equivalent Pipedrive filter views or segmentation.

Act-On calculates engagement scores using proprietary weighting across email opens, clicks, page visits, and form submissions. The formula does not export. We migrate the current numeric score for each Contact as a static integer in a custom field Pipedrive custom field engagement_score__c. The score must be recalculated or replaced with Pipedrive-compatible scoring logic post-migration.

Act-On email send history, subject lines, open and click records migrate as timestamped Activity entries linked to the Person. Each activity receives a type designation (email_sent, email_opened, email_clicked) and a timestamp from the Act-On engagement record. HTML body content is not migrated; only the activity record and metadata transfer.

Act-On form submission data migrates as Activity entries with a type of form_submission on the Person record. The form field values and submission timestamp migrate; the form embed code does not transfer and must be re-implemented in Pipedrive Web Forms or a third-party form tool.

Act-On's Custom Data schemas export via the Custom Objects API as structured records. We read the schema definition, pre-create matching custom fields in Pipedrive (with appropriate field types: text, number, date, drop-down), and import existing records as custom field values on the corresponding Person or Organization. If the Act-On custom object has relationships to other objects, those map to custom lookup fields in Pipedrive.

Act-On Automated Programs define multi-step nurture sequences with branching, delays, and CRM actions. These are workflow definitions rather than data records and are not accessible via API for export. We document each Program's trigger, steps, conditions, and actions as a written reference artifact. The customer's admin rebuilds the equivalent logic in Pipedrive's automation builder using that document as a blueprint.