Migrate from Apifon to Nutshell

Apifon Contacts map to Nutshell People records. The Apifon phone number becomes the People phone field, email becomes the email field, and full name splits into Nutshell's first_name and last_name fields. Channel-specific opt-in flags (SMS, Viber, Email, RCS consent) migrate as custom fields on the People record using Nutshell's customFields dictionary, with boolean values or timestamp values depending on what Apifon exposes in the export. GDPR consent flags require special handling: if Apifon stores a global consent timestamp and a per-channel consent flag, both are preserved so the sales team can demonstrate lawful basis at the destination.

Apifon Audience Lists are named groups that Contacts can belong to simultaneously. We map each distinct Audience List to a Nutshell Tag. If a Contact is in multiple Audience Lists, the Contact receives multiple Tags. Suppression-list flags (contacts explicitly blocked from a list) migrate as a tag on the Contact record indicating suppression status. If the customer has audience-level segmentation logic, we export it as a written note so the segmentation can be rebuilt using Nutshell's tag-based filtering in People views.

Apifon Campaigns (message sends or automated sequences) map to Nutshell Campaigns. Campaign name, status, channel designation (SMS, Viber, Email, RCS), and send timestamp migrate. Message content and template body migrate as Campaign Description or as a linked Note on the Campaign. Campaign delivery receipts (sent, delivered, failed) migrate as aggregate Campaign statistics fields if Nutshell's Campaign object supports custom fields in the destination tier; otherwise they are documented in a written campaign history report delivered alongside the migration.

Apifon message templates (SMS, Viber, Email, RCS) are reusable message skeletons with variable placeholders. We export template content and variable structure as Notes attached to a root Template record in Nutshell. For SMS and Viber templates, the character count and variable count are documented so the team knows which templates require rebuild as Nutshell email templates or as standard text. RCS templates have no Nutshell equivalent; these are documented as a separate list requiring a replacement channel strategy.

Apifon Sign-up Forms collect contacts with consent and assign them to Audience Lists. We export the form structure (field names, field types, required flags) and the audience assignment rule as a structured Note in Nutshell. Nutshell does not have a native form builder equivalent to Apifon's drag-and-drop forms; the form-field-to-audience mapping is documented so the team can recreate the collection logic using a third-party form tool (Typeform, Google Forms, or Nutshell's import via CSV) and apply the audience segmentation manually or via tag assignment.

Apifon Analytics Events track campaign-level KPIs: delivery rate, open rate, click rate, failure rate, and channel-specific engagement. We export these as summary metrics per campaign and per channel in a structured Note attached to the corresponding Nutshell Campaign. Nutshell's standard Campaign object does not store engagement analytics in the same structure, so the metrics are preserved as historical reference rather than as live CRM data. If the customer has a BI tool or data warehouse, we export the analytics as a CSV alongside the migration.

Apifon stores channel credentials: sender IDs for SMS, Viber business account IDs, RCS configuration, and email sender domains. We export the channel mapping as a structured configuration inventory noting which channels are active, the sender identity used, and which require re-authentication in Nutshell. Nutshell integrates with Gmail, Outlook, and Mailchimp for email sends; SMS and Viber require a third-party integration (Twilio, MessageBird, or similar) to be configured post-migration. The channel configuration inventory clarifies which channels the customer must re-establish and with which provider.

Apifon Custom Fields on Contacts (any non-standard fields the customer added) migrate to Nutshell customFields on the People record. We export field names, data types, and all populated values. Nutshell supports text, currency, date, number, and multi-select custom field types. If Apifon uses a data type that Nutshell does not support natively, we convert to the closest Nutshell equivalent (for example, Apifon date-time fields become Nutshell date fields with a separate text note for time component). All custom field values migrate even if empty, so the schema is complete in Nutshell.