Migrate from Apifon to Freshsales

Apifon Contacts with phone number and email map to Freshsales Contacts. We preserve channel-specific opt-in flags (SMS_opt_in, Viber_opt_in, Email_opt_in) as custom fields on the Freshsales Contact record. The Apifon contact record ID is stored in a custom field apifon_contact_id__c for audit traceability. GDPR consent timestamps migrate as custom date fields. Duplicate resolution uses email as the primary dedupe key with phone as secondary.

Apifon Audience Lists represent segmented groups of Contacts. Each Audience List becomes a Freshsales Tag applied to every Contact member. Suppression lists (contacts explicitly excluded from a campaign) are documented as exclusion rules and carried forward as custom exclusion tags or a separate tag prefix (e.g., SUPPRESSED_) so the customer's admin can apply them in Freshsales or a downstream marketing tool. List-level GDPR consent aggregation migrates as a note on the tag.

Apifon custom fields on Contacts (beyond the base name, email, phone, and opt-in metadata) migrate to Freshsales custom fields of matching type: text fields map to text, numeric fields to number, date fields to date, and multi-select properties to picklist where the picklist values are pre-defined. We create the destination schema in Freshsales before import and preserve the original Apifon field API name in the field description for reference.

Apifon Campaigns are message-send objects with timing, channel, and template assignment. Freshsales has a Campaign object (primarily used in Freshsales Suite with marketing features). We export campaign metadata (name, status, channel, start date, audience size) as a structured record set that the customer's admin can use to recreate Campaigns in Freshsales or map them to Freshsales Workflows. Campaign history does not replicate as Freshsales does not track message campaign performance in the same way.

Apifon message templates (SMS, Viber, Email, RCS) are reusable objects with variable placeholders. Freshsales supports Email Templates but not SMS or Viber templates natively. We export template content, channel designation, and placeholder structure as a written template inventory document that the customer's admin uses to recreate templates in Freshsales Email Templates (for Email) and document SMS template copy for any third-party SMS integration configured in Freshsales.

Apifon Sign-up Forms collect contacts and assign them to Audiences with consent captured. We export form structure (field names, field types, required status) and audience assignment rules as a form field mapping document. Freshsales Web Forms capture leads but do not have the same audience assignment and channel consent model. The customer uses this document to configure Freshsales Web-to-Lead forms or a third-party form tool with equivalent audience mapping.

Apifon Analytics Events capture campaign performance (delivered, opened, clicked, failed) as aggregate KPIs per campaign and per channel. We export summary metrics as structured data and map delivery rates and engagement rates to custom numeric fields on the Contact or as a Campaign record in Freshsales. Individual event-level history (which contact received which message) does not have a standard destination equivalent and is documented as a data retention note rather than imported as structured records.

Apifon Channel Configurations (sender IDs for SMS, Viber business account credentials, RCS configurations) are platform-specific and cannot transfer to Freshsales because Freshsales does not have native Viber or RCS channels. We export the channel inventory (sender ID, channel type, account status) as a written handoff document. The customer's admin reconfigures SMS via a Freshsales-compatible provider (Twilio, MessageBird) and documents Viber and RCS as channels that require an external messaging tool.

Apifon Landing Pages built with the drag-and-drop builder are not accessible via API and cannot be migrated. We export the list of landing page URLs, the form fields embedded on each page, and the audience assignment rules as a written reference document. The customer's marketing team recreates landing pages in Freshsales Web-to-Lead, a CMS, or a dedicated landing page tool. No page content migrates.