Migrate from Apifon to Pipedrive

Apifon Contact records map to Pipedrive Person. The primary identifiers — phone number and email — migrate to Pipedrive's phone and email fields respectively. Channel-specific consent flags (SMS opt-in, Viber opt-in, Email opt-in, RCS opt-in) migrate as custom fields on Person: apifon_sms_consent__c, apifon_viber_consent__c, apifon_email_consent__c, and apifon_rcs_consent__c as boolean or date fields depending on what Apifon exposes. Any custom field values on the Apifon Contact extend as Pipedrive custom Person fields created via the Fields API before migration.

Apifon Contacts may carry a company_name field. We extract all unique company_name values and create Pipedrive Organization records from them. Each Apifon Contact with a company_name link is then linked to the corresponding Organization via Person's org_id. If an Apifon Contact has no company_name, it becomes an unlinked Person in Pipedrive. We deduplicate Organization names during merge to avoid creating duplicate Account records.

Apifon Audience Lists are named groups of Contacts used for segmentation and campaign targeting. We map each Audience List to a Pipedrive Tag (e.g., tag name = 'Newsletter_Subscribers_Q4') applied to the Person records in that list. If suppression rules apply (Contacts in Audience X are excluded from Campaign Y), we document them as a written suppression matrix for the customer's admin to configure as filter views or exclusion Tags in Pipedrive. Alternative: if the customer has fewer than 20 audiences, we offer a custom multi-select field audience_lists__c on Person instead of Tags.

Apifon Campaigns represent individual message sends or automated sequences with name, status, channel, and timing metadata. Pipedrive has no native Campaign object, so we migrate Campaign metadata as a Note on the relevant Person record, tagged with the channel (e.g., Note title: 'Campaign: Summer_Sale_2024 | SMS | Sent 2024-07-15'). For aggregate campaign performance data (delivery rate, open rate, click rate), we create custom fields on Person: last_campaign_date__c, last_channel__c, and engagement_score__c as a derived integer.

Apifon Campaign Analytics Events (delivered, opened, clicked, failed) aggregate per campaign. We split these into Person-level custom fields capturing the most recent event per channel: last_sms_delivered__c, last_email_opened__c, last_viber_clicked__c, and campaign_failure_count__c. Summary delivery rates per campaign are preserved as notes. Historical event-level data beyond the most recent per-person-per-channel event is documented as an aggregate CSV for the customer to import into a BI tool if needed.

Apifon SMS Templates store reusable message body and variable placeholders (e.g., {{first_name}}, {{coupon_code}}). We migrate Template content as a Note on the Person record where the template was last used, with the Note title indicating template name and channel. Variable placeholders are preserved in the Note body so the customer can reference the original template structure when rebuilding in Pipedrive's email template or automation system.

Apifon Email, Viber, and RCS Templates migrate similarly to SMS Templates — as Notes on the Person record with channel designation in the Note title. Email templates used for formal outreach may also be preserved as Pipedrive Email Templates (a standard feature from Advanced tier) if the template structure supports static body content without dynamic Apifon-specific merge syntax.

Apifon Sign-up Forms collect Contacts and assign them to Audience Lists with consent captured per channel. We export the form structure (field names, field types, required flags) and the Audience List assignment rule as a written form-to-audience mapping document. Pipedrive does not have a native form builder in the core CRM; the customer rebuilds forms in Pipedrive Web-to-Lead, Typeform, or HubSpot Forms and maps field outputs to Pipedrive Person custom fields using the documented mapping.

Apifon Channel Configurations — SMS Sender IDs, Viber Business Account credentials, RCS sender setup — are Apifon-platform-specific and have no equivalent in Pipedrive, which relies on external integrations (e.g., Mailchimp, Twilio) for outbound messaging. We document the active channel configurations and flag which require re-authentication in the customer's new messaging tool. We do not transfer credentials.

Apifon Contacts may carry custom field extensions beyond the base schema (phone, email, name, consent flags). We export all custom field names, types, and populated values. Before migration, we use Pipedrive's Fields API (GET /v1/personFields, POST /v1/personFields) to pre-create equivalent custom Person fields in the destination org. Field type mapping: text strings to varchar, dates to date, integers to int, booleans to bool. Any custom fields without populated data in Apifon are still created in Pipedrive as empty fields for future use.