Migrate from Snovio to Twenty CRM

Snovio Prospect profiles (name, email, company, role, custom fields) map to Twenty Person records. We map standard fields 1:1 and flag Snovio custom field values for translation into Twenty custom fields. Important: Twenty's standard Person object has limited default fields; your admin must create industry-standard fields (jobTitle, department, website, phone types, social profiles) in Settings → Data Model before the CSV import runs. We provide the field creation checklist during scoping. Email addresses are used as the dedupe key during import to prevent duplicate Person records.

Snovio stores company data within Prospect profiles rather than as separate objects. We extract unique company names and domains from Prospect records and create Twenty Company records before importing People. The company name maps to Company.displayName. Twenty's Company object also requires custom field creation for industry, employee count, and annual revenue if those Snovio fields exist in your prospect data. Company domain is stored as the Website field and used for matching against existing Companies during deduplication.

Snovio Campaigns contain sequence steps, timing rules, and channel settings (email or LinkedIn). Twenty CRM uses Workflows with record-triggered, scheduled, and screen variants. We do not migrate campaign configurations as live automations. We export campaign structure as a structured data inventory (step sequence, delay intervals, channel assignment, step type) and deliver it as a written playbook so your admin can rebuild the cadence in Twenty's Workflow builder. LinkedIn sequences require a third-party LinkedIn automation tool if multichannel sequences continue post-migration.

Snovio Recipients are unique leads who received at least one email. We map Recipients to Twenty Person records, preserving the recipient status (active, bounced, replied) as a custom picklist field on the Person. The full recipient list, including Snovio-specific recipient IDs, is exported so you can remap to Twenty's native contact identifiers. Engagement history (open timestamps, click URLs, reply dates) migrates as Task records linked to the Person, giving your team the activity timeline without relying on Snovio's unreliable tracking pixel data.

Snovio's delivered, bounced, opened, clicked, and replied counts per campaign are KPIs that do not have a direct Twenty CRM equivalent because Twenty lacks a native campaign analytics dashboard. We migrate these metrics as a Campaign Summary custom object or as a structured CSV report that your admin can reference for post-migration benchmarking. Do not expect these numbers to appear as live dashboards in Twenty; they are preserved as a data artifact for comparison against Twenty's own engagement tracking going forward.

Snovio Pipeline Deals (deal name, stage, owner, associated contact) map to Twenty Opportunity records. We translate Snovio pipeline stage names to Twenty Opportunity stage values, which your admin defines in Settings → Data Model as part of the Opportunity object configuration. Owner assignments resolve by email match against Twenty Users. Deals without a linked contact are created as Opportunities with no Person association and flagged for manual linking post-migration.

Snovio's connected mailboxes and warm-up configurations (warm-up volume, rotation settings) are exported as a structured configuration document. We cannot migrate SMTP credentials or OAuth tokens because Snovio does not expose these via its documented API. Your admin reconfigures mailbox connections in Twenty's Settings → Accounts section after migration. The warm-up settings document serves as a reference for re-establishing sender reputation practices in Twenty or a separate warm-up tool.

Snovio Unibox aggregates email replies into a shared inbox view. We export reply metadata (sender, timestamp, thread reference) as Task records linked to the corresponding Person in Twenty. Full email body content does not migrate because Snovio's threading export is limited and email threading does not map cleanly to Twenty's activity model. The thread reference document allows your team to cross-reference conversations in Snovio if audit access remains available post-subscription.

Snovio custom fields on Prospect profiles map to Twenty custom fields on Person and Company objects. Field types are translated: text to TEXT, number to NUMBER, date to DATE, picklist to SELECT, multi-select to MULTI_SELECT. Multi-checkbox fields become Twenty multi-select fields. Before import, your admin creates all custom fields in Settings → Data Model — CSV import creates records only, not fields. We provide the complete field schema from Snovio and a field creation guide for Twenty. Any field referencing a Snovio-only concept (e.g., credit balance, recipient score) is flagged as non-migratable.

LinkedIn message sequences and connection request records exist in Snovio only if the LinkedIn add-on ($69/month) was active. We export LinkedIn campaign configuration and recipient lists as a structured document. The actual LinkedIn OAuth tokens and connection records cannot be transferred to Twenty. If your team relies on LinkedIn sequences, you need a dedicated LinkedIn automation platform (e.g., Phantombuster, MeetAlfred, LinkedIn Sales Navigator sequences) to continue the cadence post-migration. The inventory document ensures your admin knows which sequences existed and who the recipients were.