Migrate from Convertkit to Twenty CRM

ConvertKit subscribers map directly to Twenty People records. Every subscriber record — including those added via form, API, or import — transfers with all standard properties (email, first name, last name) and any subscribed-to state preserved. Original create dates surface as a custom field since Twenty sets CreatedDate at import time.

ConvertKit has no native Company object, but subscriber email domains can cluster contacts by organization. FlitStack creates Twenty Company records for each unique domain with more than one associated subscriber, using the domain as the Company name and setting Website from the domain. Your team specifies the minimum subscriber threshold per domain (default: 2).

Each ConvertKit subscriber linked to a domain that generated a Company record gets a CompanyId relation on their People record. Subscribers with domains below the threshold land as standalone People with no Company link. This creates the contact-account hierarchy Twenty's CRM model requires.

ConvertKit's tag taxonomy is a core organizing structure — subscribers often carry 5–20 tags. We create a custom multi-select field on People called Tags__c and populate it with each subscriber's full tag set. Tag values are stored as-is; if you need tag-based segmentation in Twenty, this field drives filter views immediately after import.

ConvertKit custom fields migrate 1:1 to Twenty custom fields of the matching type. Text → text, number → number, date → date. Select pick-lists in ConvertKit map to Twenty select fields with the same option values — we validate option names match before import to avoid silent failures.

ConvertKit multi-select fields transfer to Twenty multi-select fields. Option values are preserved verbatim. Note that Twenty's multi-select display differs from ConvertKit's tag-style UI — users see a pill selector in both platforms but the underlying storage and filter behavior are equivalent.

ConvertKit checkbox fields store true/false values and map directly to Twenty checkbox fields without requiring transformation logic. The boolean values transfer directly between platforms. When ConvertKit uses 1/0 encoding instead of true/false text, our pre-processing step normalizes the values to proper boolean format before loading them into Twenty's People records.

ConvertKit forms are embedded email-capture tools with styling, field configuration, and trigger logic. Twenty has no native form builder — forms must be rebuilt using a third-party tool (Typeform, HubSpot Forms, or custom HTML) and integrated via Twenty's API or webhook endpoints. We export form configuration as a reference JSON for rebuilding.

ConvertKit sequences are time-delayed email series attached to subscribers with delivery state tracking (sent, open, click, replied). Twenty's workflow builder handles trigger-action automations but not email delivery — email sequences must be rebuilt in a dedicated email tool (e.g., Mailchimp, Loops) connected to Twenty via API. We export sequence definitions as a step-by-step rebuild guide.

ConvertKit broadcast history records which subscribers received each campaign. This data is historical and not actionable in Twenty's CRM model. We offer an optional summary: each broadcast becomes a Note on all recipients, recording subject, send date, and open rate for audit continuity. This is opt-in because it can create thousands of Note records.

ConvertKit products (digital goods, paid newsletters, subscriptions) have no native CRM equivalent. We create a custom Product object in Twenty with fields for name, price, type, and link to the People record of purchasers. Purchase history migrates as a relation between People and Product.

ConvertKit's subscribed/unsubscribed/bounced state maps directly to Twenty's optOut boolean field on People. Unsubscribed and bounced contacts set optOut to true, while active subscribers set it to false. Bounced emails set a separate bouncedAt timestamp field on the People record. This dual-field approach ensures Twenty respects global unsubscribe signals from ConvertKit's GDPR and CAN-SPAM compliance record while preserving bounce history for re-permission follow-up workflows.