Migrate from Apifon to Mailchimp

Apifon Contacts with email addresses migrate directly to Mailchimp Contacts. The Apifon phone number migrates as a Phone merge field and as an ADDRESS merge field if a physical address is present. Channel-specific consent flags (SMS opt-in, Viber opt-in, Email opt-in) from Apifon encode as individual TAGs in Mailchimp (e.g., consent_sms_opted_in, consent_viber_opted_in) and as custom merge fields if the customer requires granular GDPR documentation. Contacts without a valid email address are held in a reconciliation queue because Mailchimp requires an email address as the primary identifier.

Apifon Audience Lists migrate to Mailchimp Audiences as the top-level grouping structure. Each Apifon Audience List becomes a Mailchimp Audience with the list name preserved. Sub-group membership within an Apifon Audience List migrates as Mailchimp Tags so that segment logic carries forward. If multiple Apifon Audiences contain the same contact, Mailchimp's merge-overwrite behavior is applied during import and the customer chooses whether to consolidate into one Audience or maintain separate ones.

Apifon Campaigns migrate to Mailchimp Campaigns where the campaign has an email channel designation. Campaign name, status (draft, scheduled, sent), and timing metadata transfer. Campaign content (subject line, body HTML, from name, from email) migrates where the Apifon API exposes the body field. SMS and Viber-only campaigns from Apifon cannot be sent from Mailchimp because Mailchimp's SMS feature requires a separate paid integration; these are documented as non-migratable with a recommendation to evaluate Mailchimp SMS as a separate setup.

Apifon message templates (SMS, Viber, Email) with email channel designation migrate to Mailchimp Templates. Template content, variable placeholders (e.g., {{first_name}}, {{discount_code}}), and channel designation transfer as Mailchimp Template content. SMS and Viber templates cannot be sent from Mailchimp and are documented as template inventory for the customer's operations team to assess for email adaptation.

Apifon custom fields on Contacts extend the base schema with business-specific properties. We export field names, data types, and all populated values and create corresponding Mailchimp Merge Fields of equivalent type (text, number, date, address, phone). Multi-value custom fields (e.g., interests selected) map to Mailchimp TEXT merge fields with comma-separated values or to GROUP merge fields if Mailchimp's Interest Category structure is available in the destination account tier.

Apifon Sign-up Forms define the field structure and Audience assignment for contact collection. We export form field names, field types, required/optional designation, and the target Audience List assignment. These migrate as Mailchimp Signup Forms pointing to the corresponding Audience. Note that Apifon GDPR consent checkbox configurations migrate as form field documentation; the customer's Mailchimp admin configures the consent language and double opt-in behavior in Mailchimp's form builder.

Apifon Automated Flows define trigger-based message sequences across channels. We export the flow trigger (event-based or time-based), step sequence, and channel routing as human-readable documentation. Mailchimp Customer Journeys use a different trigger and action model; the documentation we deliver maps each Apifon flow step to a recommended Customer Journey configuration and the customer's marketing team rebuilds the logic. Smart failover rules (SMS fallback for undelivered Viber) are documented separately because Mailchimp's journey builder handles fallback differently.

Apifon campaign analytics (delivered count, open count, click count, bounce count, unsubscribe count, conversion events) migrate as aggregate summary records attached to the corresponding migrated Campaign. Mailchimp's reporting API exposes per-campaign metrics that we cross-validate against the imported Apifon summary data. Individual event-level data (exact timestamps per open or click) does not migrate because Apifon's analytics API does not expose granular event logs and Mailchimp's reporting is campaign-aggregated by default.

Apifon channel credentials (sender IDs for SMS, Viber business account identifiers, RCS configurations) are platform-specific and do not transfer to Mailchimp. We document the sender identities in use and recommend that the customer's Mailchimp admin set up Domain Authentication (SPF/DKIM) for email sending and the Mailchimp SMS integration separately. The channel mapping document we deliver serves as the reference for which sender addresses need recreation.