Migrate from Apifon to Odoo CRM

Apifon Contacts with a completed purchase event, sales interaction, or high engagement score map to Odoo Contact tied to a res.partner record. Contacts with no sales activity or opt-in only status map to Odoo Lead. Channel consent flags (sms_consent, viber_consent, email_subscription) migrate as custom boolean fields on both Lead and Contact so the customer's admin can reference original opt-in status for GDPR compliance.

Apifon Audience Lists are membership groups that segment Contacts for campaign targeting. Each unique Audience List name becomes an Odoo Tag. If a Contact belongs to multiple Audience Lists, it receives multiple Tags. Suppression list membership (contacts blocked from sends) migrates as Tags prefixed with BLOCK_ so the customer's admin can replicate suppression logic in Odoo's mail blacklist or marketing exclusion groups.

Apifon Campaigns represent message sends or automated sequences. Campaign name, status, channel designation, send timestamp, and target audience summary migrate as an Odoo Opportunity record with a linked Note holding the campaign metadata and channel assignment. Message content, template variables, and body text are exported as separate template documentation for manual Odoo email template creation. Campaign-level delivery receipts and engagement rates (delivered, opened, clicked, failed) migrate as custom fields on the Opportunity.

Apifon message templates (SMS, Viber, Email, RCS) are reusable message patterns with variable placeholders. We export template name, channel, full body content, and placeholder variable names as a structured JSON document. Odoo email templates are created through the UI or XML-RPC API, but the content requires manual entry because template body formatting (HTML for email, character limits for SMS) must be validated in the destination. We do not create Odoo templates as code; we deliver the complete source content for the admin to recreate.

Apifon automated flows define trigger-based message sequences with conditional branching and smart failover (SMS fallback when Viber is undelivered). Odoo has no native SMS failover or multichannel message automation; CRM Activity Plans schedule activities against Leads and Contacts but do not send messages. We export the full flow sequence, trigger conditions, step order, and failover rules as human-readable documentation for the customer's Odoo admin to rebuild using Odoo Automated Actions, Server Actions, or a third-party SMS integration like Twilio.

Apifon sign-up forms collect contacts and assign them to Audience Lists with consent captured per field. We export form field names, field types, required flags, audience assignment rules, and GDPR consent field designations. Odoo Website forms use the forms builder with field-to-model mapping. We deliver a field-level mapping document showing which Apifon form fields correspond to which Odoo contact fields so the customer's admin can recreate the form and maintain the same data collection and segmentation logic.

Apifon campaign performance events (delivered count, opened count, clicked count, failed count, delivery rate, open rate, click rate) are available as aggregate metrics per campaign per channel. We create custom fields on the Odoo Opportunity object (e.g., sms_delivered_count__c, email_open_rate__c, viber_click_count__c) and populate them with the aggregated Apifon analytics data at migration time. Raw event-level logs do not migrate because Odoo does not have an event tracking model equivalent to Apifon's analytics engine.

Apifon channel credentials (sender IDs, Viber business account tokens, RCS configurations, SMS sender names) are platform-specific and tied to Apifon's carrier relationships. We export the channel-to-identifier mapping as a configuration document. The customer's admin must reconfigure SMS routing in Odoo through a third-party SMS gateway (Twilio, Msg91, or a local carrier API) because Odoo CRM does not include native multichannel SMS or Viber routing. Outgoing email servers (SMTP) migrate more directly through Odoo's outgoing mail server configuration.

Apifon supports custom fields on Contacts that extend the base schema beyond phone, email, and name. We export field names, data types, and all populated values. Custom fields are applied as custom fields on the Odoo res.partner model. Field type mapping: Apifon text becomes Char, Apifon number becomes Float or Integer, Apifon date becomes Date, Apifon checkbox becomes Boolean. Selection fields map to Odoo Selection fields.

Apifon captures consent timestamps and channel-specific opt-in flags required for GDPR compliance in Southern Europe. We preserve opt_in_timestamp, consent_channel, and withdrawal_timestamp as custom fields on the migrated Contact or Lead record. This ensures the customer maintains a GDPR defensible audit trail at the destination even though Odoo CRM does not have a native GDPR consent management module.

Apifon users who created campaigns, flows, or sign-up forms may have contact attribution. We extract distinct user references from record creation metadata and attempt email matching against Odoo User records. Users without a match go to a reconciliation queue for the customer's admin to provision before record import resumes.

Apifon suppression rules prevent specific contacts from receiving messages. We export suppressed contact identifiers (phone numbers, email addresses) and suppression reasons. At Odoo CRM, email addresses are added to the mail.blacklist table to prevent unsolicited email sends. Phone number suppression requires the customer's chosen SMS gateway (Twilio, Msg91) to be configured with a blocklist.