Migrate from Apifon to monday CRM

Apifon Contact records map to Monday.com People (the CRM-native contact object) with phone number, email, and name preserved. Channel-specific consent flags (sms_optin, viber_optin, email_optin, rcs_optin) migrate as boolean columns on the People record. Any Apifon custom fields on Contact extend the People schema with custom columns of equivalent type. We resolve duplicate phone numbers and emails during import using Monday.com's People dedup logic.

Apifon Audience Lists (named groups used for segmentation and suppression) map to Monday.com Tags on People records, with the tag name matching the audience list name. If the customer has suppression rules (contacts blocked from specific campaigns), we create a Tag per suppression list and document the rule logic separately for the customer to implement in Monday.com Automations. List membership count is preserved as a tag count metric in the migration report.

Apifon Campaigns (one-off or automated message sends) become Items on a dedicated Campaign Board in Monday.com. We create columns for Campaign Name, Channel (SMS, Viber, Email, RCS), Status (draft, scheduled, active, paused, completed), Start Date, End Date, and Audience (linked via Tag or custom Contact column). Campaign message content migrates to a Long Text column only if the Apifon API exposes it; otherwise we document the template reference for manual re-entry.

Apifon automated flows with trigger conditions and step sequences do not migrate as automation code. We export every active flow as a written document that lists the trigger, conditions, channel routing, delay rules, and message content references. The customer rebuilds each flow in Monday.com Automations using the Monday.com recipe builder. Smart SMS failover logic (switching from Viber to SMS on non-delivery) requires a manual rebuild as a separate Automation with conditional branching.

Apifon message templates with variable placeholders migrate as Monday.com Item Templates attached to the Campaign Board, with the variable syntax documented. For templates used across multiple campaigns, we recommend the customer create Item Templates in Monday.com that include the template body and placeholder markers. Channel designation (SMS, Viber, Email, RCS) maps to a single-select column in Monday.com.

Apifon Sign-up Forms collect contacts and assign them to audiences with consent captured. We export the form structure (field names, field types, required status) and the audience assignment rules as a written document. The customer rebuilds forms in Monday.com or a third-party form tool (Typeform, JotForm) and manually configure the audience assignment as Tags on new People records.

Apifon campaign performance metrics (delivered count, opened count, clicked count, failed count, delivery rate, engagement rate) migrate as number columns on the Campaign Board Items. Historical event data per campaign per channel is preserved as static values. Ongoing analytics require the customer to configure Monday.com's Dashboard widgets or integrate a reporting tool post-migration.

Apifon channel credentials (sender IDs, Viber business account IDs, RCS configurations) are platform-specific and do not transfer to Monday.com. We document the channel mapping (which Apifon channel maps to which messaging vendor in Monday.com's context) and flag which configurations require re-authentication. The customer must configure their SMS gateway, Viber business account, and email sender in Monday.com Integrations after migration.

Apifon custom fields on Contacts extend the base schema with customer-defined properties. We export field names, types (text, number, date, boolean, multi-select), and all populated values. Each custom field maps to a Monday.com custom column of the equivalent type: text fields map to Text columns, dates to Date columns, booleans to Checkbox columns, and multi-select options to Tags or Dropdown columns depending on the intended use.