Migrate from Apifon to Salesforce Sales Cloud

Apifon Contacts map to either Salesforce Lead or Contact depending on sales relationship status. We use a scoping-defined rule: Contacts in an active Campaign or assigned to a sales queue map to Salesforce Lead; Contacts associated with a known business entity and in a post-conversion lifecycle stage map to Salesforce Contact with an AccountId resolved. Channel consent flags (SMS, Viber, Email, RCS opt-in) migrate as custom fields on both Lead and Contact (e.g., apifon_sms_optin__c, apifon_viber_optin__c) to preserve GDPR compliance records. Phone number and email migrate as standard Phone and Email fields with a dedupe check on email before insert.

Apifon Audience Lists group Contacts for segmentation. We map each Audience List to a Salesforce Topic with TopicAssignment records linked to the Contact or Lead, or to a multi-select picklist field on Contact (apifon_audiences__c) depending on list count. Lists with suppression rules (contacts who should not receive messages) map to a custom suppression field apifon_suppressed__c set to true, or to a Salesforce Exclusion List on the relevant Campaign. Audience list membership is resolved after the Contact/Lead split so that membership is correctly attributed.

Apifon Contacts may carry a company name field. We extract all distinct company name values from Contact records and create Salesforce Account records with the company name as Account Name. A dedupe check prevents duplicate Accounts. After Account creation, we backfill AccountId on the Contact or Lead records that reference that company. If the company name field is absent or empty, the Contact or Lead is imported without an AccountId and flagged for manual account assignment.

Apifon Campaigns (one-off and automated message sends) map to Salesforce Campaign records. Campaign name, status, channel (SMS, Viber, Email, RCS), start and end dates migrate as standard Salesforce Campaign fields. Apifon campaign suppression rules are documented separately as Campaign Exclusion Lists. Campaign performance metrics (delivered, opened, clicked, failed) migrate as Salesforce Campaign statistics. Campaign Members are created by resolving the Apifon Contact references against the migrated Lead and Contact records.

Apifon Contacts included in a Campaign become Salesforce Campaign Member records linked to the Campaign and the resolved Lead or Contact. Campaign Member Status migrates from Apifon's per-contact delivery status (delivered, failed, pending). A contact in multiple Apifon Campaigns generates multiple Campaign Member records under one Salesforce Campaign. We resolve the Lead or Contact ID for each Campaign Member using the email dedupe key.

Apifon automated flows define trigger-based message sequences with smart SMS failover (automatically switching to SMS when Viber is undelivered). This conditional routing logic is not exposed in a machine-readable format. We export the flow trigger conditions, step sequence, channel assignments, delay durations, and failover configuration as human-readable documentation. Salesforce admin rebuilds the equivalent logic in Salesforce Flow or a sales engagement tool (High Velocity Sales, Outreach, Salesloft) post-migration.

Apifon message templates (SMS, Viber, Email, RCS) with variable placeholders are exported with full content, channel designation, and placeholder names. Email templates migrate as Salesforce EmailTemplate records where the template is Email-type and compatible with Salesforce's merge field syntax. SMS and Viber templates are documented with variable positions for manual recreation in an SMS gateway (Twilio, MessageBird) or Salesforce SMS/Push integration.

Apifon sign-up forms collect contacts and assign them to audiences with consent captured. We export form field names, field types, required/optional designation, and the audience assignment rule (which Audience List the contact joins on submission). This is delivered as a written form-field-to-audience map. Salesforce admin recreates the form in Salesforce Web-to-Lead, Experience Cloud, or an AppExchange form tool and configures the field mappings and lead assignment rules.

Apifon campaign performance events (delivered count, opened count, clicked count, failed count) are available as aggregate KPIs per campaign and per channel. We migrate these as Salesforce Campaign statistics fields and as custom number fields on a Campaign Analytics custom object linked to Campaign if the metrics require per-channel granularity. Historical aggregate delivery rates and engagement data are preserved for reporting continuity.

Apifon channel credentials (sender IDs, Viber business account IDs, RCS configurations) are platform-specific and do not transfer to Salesforce because they are tied to Apifon's carrier relationships. We export the channel mapping as documentation showing which Apifon channels were active per campaign. Salesforce admin reconnects SMS through a Salesforce SMS integration (Twilio, SMS Magic, mvp.text), Viber through a partner gateway, and Email through Salesforce's own Email relay or an AppExchange email gateway.

Apifon custom fields on Contact records extend the base schema (e.g., loyalty tier, birthday, preferred language). We export field names, data types, and all populated values. Field types are mapped to Salesforce equivalents: text to Text(255), number to Number, date to Date, checkbox to Checkbox, picklist to Picklist. All custom fields are pre-created in the Salesforce org via the metadata API or manually in Setup before record import begins.

Apifon stores opt-in timestamps and consent flags per channel. GDPR consent records are preserved as custom date and boolean fields on Lead and Contact (e.g., apifon_sms_consent_date__c, apifon_email_consent_date__c, apifon_consent_given__c). These fields are configured as non-editable or as audit fields where the Salesforce edition supports field history tracking, ensuring the consent record is preserved as-is and not accidentally overwritten during data load.