Migrate from Apifon to Microsoft Dynamics 365 Sales

Apifon Contacts map to Microsoft Dynamics 365 Sales Contact records. Phone number migrates to Telephone1 or MobilePhone; email migrates to EmailAddress1; first and last name map to FirstName and LastName. Channel-specific GDPR consent flags (SMS opt-in, Viber opt-in, Email opt-in, timestamp of last consent) migrate to corresponding custom fields on the Contact record. We preserve the original Apifon contact ID as a custom field apifon_contact_id__c for audit traceability.

Apifon Audience Lists map to Dynamics 365 Marketing Lists or static CRM Lists depending on whether the customer uses Dynamics 365 Marketing as an add-on. Each list membership is a ListMember record in Dynamics. Suppression rules from Apifon (contacts who have opted out or are flagged as excluded) migrate as exclusion criteria documented in a separate suppression list. If Dynamics 365 Marketing is not licensed, audience lists migrate as Tags on Contact records.

Apifon Campaigns map to Microsoft Dynamics 365 Sales Campaign records. Campaign name, channel designation (SMS, Viber, Email, RCS), status, scheduled start and end dates, and campaign owner transfer directly. Apifon's campaign-level KPIs (delivery rate, open rate, click rate) transfer as custom fields on the Dynamics Campaign record for historical reference. Message content does not transfer via API and is documented separately for manual recreation.

Apifon message templates (SMS, Viber, Email, RCS) store content, variable placeholders, and channel designation. The template metadata (name, channel, variable list, character count) exports to a template inventory document. We do not create the template in Dynamics; the customer's Dynamics admin recreates templates using the documented variable mapping. This ensures channel-specific formatting (SMS character limits, Viber rich media support) is handled correctly in the destination.

Apifon sign-up forms collect contacts and assign them to audiences with consent captured. We export the form structure (field names, field types, field order) and the audience assignment rule as a form-to-audience mapping document. Dynamics Web-to-Lead or Dynamics 365 Marketing Forms rebuild these as the customer's admin directs. The exported mapping ensures the same contact-to-audience logic is maintained post-migration.

Apifon custom fields on Contacts extend the base schema. We export all custom field definitions (field name, field type, populated values) and create corresponding custom fields on the Dynamics Contact entity during schema provisioning. Custom field type mapping follows standard conventions: Apifon text fields map to Dynamics Single Line of Text, numeric fields map to Number or Decimal, date fields map to Date or DateTime, and multi-select fields map to Option Set. All populated values transfer as records are imported.

Apifon channel credentials (SMS sender IDs, Viber business account IDs, RCS configurations) are Apifon-platform-specific and do not transfer to Dynamics. We document which channels were active on each Apifon campaign and provide a channel setup checklist for the customer's admin to re-authenticate sender IDs and routing in Microsoft Dynamics 365 Sales or the relevant Dynamics 365 Marketing channel connector.

Apifon campaign performance events (delivered, opened, clicked, failed) export as aggregate summary metrics per campaign and per channel. These transfer as custom fields on the Dynamics Campaign record (e.g., sms_delivery_rate__c, email_open_rate__c). If the customer requires detailed historical analytics, we document the export schema for connection to Power BI or Azure Synapse for long-term reporting outside Dynamics.